How does Weblogic find out which webservice method to invoke?

Question

Hi!
I developed a webservice which is currently running on weblogic & everything is fine ;). Yesterday I tried to get it running on a different app server (jboss) and it simply would not work. I always got an error, that the operation requested does not exist on the endpoint. I investigated the issue & came to the conclusion that it is correct...the operation requested does really not exist. Now...why does it work on weblogic?!?
Here a few details on the application:
important part from the wsdl & xsds:
<wsdl:message name="performTransactionSearch">
<wsdl:part name="parameters" element="tns:performTransactionSearchRequest" />
</wsdl:message>
<wsdl:portType name="TransactionService">
<wsdl:operation name="performTransactionSearch">
<wsdl:input message="tns:performTransactionSearch" />
<wsdl:output message="tns:performTransactionSearchResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="O2HWOnlyJournalServicePortBinding" type="tns:O2HWOnlyJournalService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
<wsdl:operation name="performTransactionSearch">
<soap:operation soapAction="" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
And here the xsd type:
<xs:element name="performTransactionSearchRequest" type="tns:performTransactionSearchRequest"/>
<xs:element name="performTransactionSearchResponse" type="tns:performTransactionSearchResponse"/>
<xs:complexType name="performTransactionSearchRequest">
<xs:all>
<xs:element name="RequestHeader" type="base:requestHeader" minOccurs="0"/>
<xs:element name="TransactionSearchCriteria" type="wstypes:transactionSearchCriteria" minOccurs="1"/>
</xs:all>
</xs:complexType>
<xs:complexType name="performTransactionSearchResponse">
<xs:sequence>
<xs:element name="SearchResponseItem" type="wstypes:searchResponseItem" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
Last but not least, the method:
public List<SearchResponseItem> performTransactionSearch(RequestHeader header, TransactionSearchCriteria criteria) { ... }
The difference in the soap request messages differs in the outer tag. Weblogic expects what is defined in the xsd -> <performTransactionSearchRequest>, whereas jboss expects the operation/method <performTransactionSearch>.
With jboss it only works w/o the 'Request'-suffix....with Weblogic it only works with the suffix.
In a last attempt I adjusted the xsd, and changed the name for the tag to 'performTransactionSearch'. In that case, both app servers accept the same request (the one w/o the 'Request'-suffix) & it works fine.
Now...long story short ;) ... why is that? I understand why Jboss is not able to work with the "wrong" tag, even though it is strange that it accepts a tag that is not even defined in the xsd.
But, at least to me, I found it even stranger, that weblogic "knows" which operation to invoke. Can anyone give a little insight how a soap message gets processed in wl & how wl finds out which operation to invoke?
Many thanks in advance :).

Answer 1

Hi
I am seeing frequent FULL GC This is because you are creating and destroying objects VERY frequently. Try to look at your design and see where you can reuse objects (i.e. object pooling) if possible, that is if this is adversely affecting performance.
and not able to locate
which particular class/method is calling the
System.gc(). Classes don't call GC. The VM handles that automagically.
I have disabled it using
-XX:DisableExplicitGC and performance issues have
been resolved. Also, I noticed that it does not
happen periodically, so it is not RMI GC. How to find
out who exactly is doing this? Does any of of the
profilers like Optimizeit/Jprobe help find out this.OptimizeIt will tell you everything you need to know. However, NetBeans offers a free profiler now!