innodb_log_file_size = 1536M
innodb_flush_log_at_trx_commit = 0innodb_buffer_pool_size = 12G (75% of 16G)
OutOfMemoryError error. To instruct the JVM to create a heap dump in such a situation, start your Java application with the -XX:+HeapDumpOnOutOfMemoryError option.| Element Name | Description |
| types | A container for abstract type definitions defined using XML Schema |
| message | A definition of an abstract message that may consist of multiple parts, each part may be of a different type |
| portType | An abstract set of operations supported by one or more endpoints (commonly known as an interface); operations are defined by an exchange of messages |
| binding | A concrete protocol and data format specification for a particular portType |
| service | A collection of related endpoints, where an endpoint is defined as a combination of a binding and an address (URI) |
<definitions .... >
<types>
<xsd:schema .... />*
</types>
</definitions>
<definitions .... >
<message name="nmtoken"> *
<part name="nmtoken" element="qname"? type="qname"?/> *
</message>
</definitions>
Definition is the root of the WSDL.
Interfaces (portTypes)
It has input and output request. PortType is nothing but an interface which conveys the request andresponse parameters.<definitions .... > <portType name="nmtoken"> <operation name="nmtoken" .... /> * </portType> </definitions>
A portType is still considered an abstract definition because you don't know how its messages are represented on the wire until you apply a binding.Bindings
The WSDL binding element describes the concrete details of using a particular portType with a given protocol. The binding element contains several extensibility elements as well as a WSDLoperation element for each operation in the portType it's describing.