You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Ro...@nl.equens.com on 2012/10/24 14:49:21 UTC

RE: [Axis2] System hangs

Hi Martin,

 

Sorry for my late response. I thought the problem was solved. But...

There is still the same problem with the generated service. Now I used your reconstruction of the wsdl. (see attachment)

 

 

This (corrupt) soap message causes the problem :

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.abc.com/Authorisation/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

      <v1:GetAuthorisationByCriteriaRequest>

         <UserId>11</UserId>

         <SearchCriteria>

            <byContractId>

               <Next>

                  <TerminalId>11</TerminalId>

                  <BrandId>11</BrandId>

               </Next>

            </byContractId>                           <---  after byContract should be the right place

         <Amount Currency="EUR">

            <Amount>111</Amount>

         </Amount>

         </SearchCriteria>                            (tag in the wrong place. this order causes a "loop" and a cpu usage of 50%)

      </v1:GetAuthorisationByCriteriaRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

 

I think Axis2 has a problem with mixing the optional tags.

 

 

________________________________

Van: Martin Gainty [mailto:mgainty@hotmail.com] 
Verzonden: donderdag 23 augustus 2012 0:16
Aan: java-user@axis.apache.org
Onderwerp: RE: [Axis2] System hangs

 

Robert

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
then later <namespace:unqualifiedElement is unnecessary
when unqualifiedElement without the namespace will do just fine

also note that xs:schema whose namespace points nowhere is better qualified with a "real XMLSchema" as defined here
<xsd:schema
        xmlns:xsd="http://www.w3.org/2001/XMLSchema" 

notice each abberrant xsd was inlined and then nonexistent namespaces and unnecessary namespaces were stripped off and replaced by standard internal namespace tns:

e.g. cur were replaced by tns:
<!-- xs:attribute name="Currency" type="cur:currencyCodeAlpha3Type" -->
        <xs:attribute name="Currency" type="tns:currencyCodeAlpha3Type"

iphautt was replaced by tns since you already defined ALL of the elements qualified by iphautt
type="tns:TerminalIdType" />
                <!-- type="iphautt:TerminalIdType" / -->

iphautm was replaced by tns since you already defined ALL of the elements qualified by iphautm
           type="tns:GetAuthorisationByCriteriaRequestType" />
                <!-- type="iphautm:GetAuthorisationByCriteriaRequestType" / -->

for your own edification the namespace must have a referencable schema with elements that will be referenced so in the case of 
xmlns:iphautm="http://www.abc.com/Authorisation/messages/v1.0/"
http://www.abc.com/Authorisation/messages/v1.0/ MUST contain a valid schema for each of the elements qualified by iphautm
type="iphautm:GetAuthorisationByCriteriaRequestType"
where GetAuthorisationByCriteriaRequestType MUST BE a SimpleType or ComplexType defined within that namespace

then once I got all of the no-schema namespaces out of the way ...I finally got the code generated

$AXIS_HOME\core\branches\java\1_3\modules\integration\test\Robert>"$JAVA_HOME\bin\java" -Xms1024m -Xmx1024m -cp "!AXIS2_CLASS_PATH!" org.apache.axis2.wsdl.WSDL2Java -o martin -ss -sd -l java -uri SomeService.wsdl

cd martin

$AXIS_HOME\core\branches\java\1_3\modules\integration\test\Robert\martin>dir
 Volume in drive C is SQ004813V04
 Volume Serial Number is 661D-F85D

 Directory of $AXIS_HOME\core\branches\java\1_3\modules\integration\test\Robert\martin

08/22/2012  05:46 PM    <DIR>          com
08/22/2012  05:46 PM    <DIR>          schemaorg_apache_xmlbeans
 
 Directory of $AXIS_HOME\core\branches\java\1_3\modules\integration\test\Robert\martin\com\abc\www
08/22/2012  05:49 PM               390 service.xml

Bedankt,
Martin Gainty 
______________________________________________ 
Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 

Ez az üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.





________________________________

Subject: FW: [Axis2] System hangs
Date: Wed, 22 Aug 2012 16:09:04 +0200
From: Robert.vanDijk@nl.equens.com
To: java-user@axis.apache.org

And with attachments...

 

________________________________

Van: Robert.vanDijk@nl.equens.com [mailto:Robert.vanDijk@nl.equens.com] 
Verzonden: woensdag 22 augustus 2012 16:05
Aan: java-user@axis.apache.org
Onderwerp: RE: [Axis2] System hangs

 

You are right, sorry.

 

The problem is still there.

 

I attached the complete WSDL and XSD. 

 

Correct soap msg:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.abc.com/Authorisation/v1.0/" xmlns:v11="http://www.abc.com/Authorisation/messages/v1.0/" xmlns:v12="http://www.abc.com/Authorisation/types/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

      <v1:GetAuthorisationByCriteriaRequest>

         <v11:UserId>ss</v11:UserId>

         <v11:SearchCriteria>

            <v11:byMerchantId>

               <v11:First>

                  <v11:MerchantId>12</v11:MerchantId>

               </v11:First>

            </v11:byMerchantId>

         </v11:SearchCriteria>

         <v11:Amount Currency="EUR">

            <v12:Amount>10000</v12:Amount>

         </v11:Amount>

      </v1:GetAuthorisationByCriteriaRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

Currupt one:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.abc.com/Authorisation/v1.0/" xmlns:v11="http://www.abc.com/Authorisation/messages/v1.0/" xmlns:v12="http://www.abc.com/Authorisation/types/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

      <v1:GetAuthorisationByCriteriaRequest>

         <v11:UserId>ss</v11:UserId>

         <v11:SearchCriteria>

            <v11:byMerchantId>

               <v11:First>

                  <v11:MerchantId>12</v11:MerchantId>

               </v11:First>

            </v11:byMerchantId>

         <v11:Amount Currency="EUR">

            <v12:Amount>10000</v12:Amount>

         </v11:Amount>

         </v11:SearchCriteria>                     (this order causes problems)

      </v1:GetAuthorisationByCriteriaRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

 

 

________________________________

Van: Martin Gainty [mailto:mgainty@hotmail.com] 
Verzonden: woensdag 22 augustus 2012 14:10
Aan: java-user@axis.apache.org
Onderwerp: RE: [Axis2] System hangs

 

the correct one is incorrect

CORRECT

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.company.com/Xyz/ABC/Item/v1.0/" xmlns:v11="http://www.company.com/Xyz/ABC/Item/messages/v1.0/" xmlns:v12="http://www.company.com/Xyz/ABC/Item/types/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

 

      <!-- why do you have spaces in your element name -->

      <v1: GetItemByCriteriaRequest >

         <v11:UserId>bla</v11:UserId>

         <v11:SearchCriteria>

            <v11:byMerchantId>

               <v11:First>

                  <v11:Data4Key>12345678901</v11: Data4Key>

               </v11:First>

            </v11:byMerchantId>

         </v11:SearchCriteria>

         <v11:Data5 Attr="ABC">

            <v12: Data5>1000</v12: Data5>

         </v11: Data5>

      </v1:GetAuthorisationByCriteriaRequest>

      <!-- WHAT IS GetAuthorisationByCriteriaRequest -->

 

   </soapenv:Body>

</soapenv:Envelope>


Please supply 
COMPLETE WSDL 
COMPLETE XSD (do not omit any elements such as GetAuthorisationByCriteriaRequest and do not omit included XSDs)

Bedankt,
Martin 
______________________________________________ 
Note de déni et de confidentialité

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

 

________________________________

Subject: [Axis2] System hangs
Date: Wed, 22 Aug 2012 08:22:27 +0200
From: Robert.vanDijk@nl.equens.com
To: java-user@axis.apache.org

Hi all,

 

When I call my service (using soapui) with an invalid soap message, the cpu usage goes up to 50%. Followed by the same message again, the usage goes up to 100%. In both cases no response.

After stopping the webserver, the cpu usage goes back to normal.

 

There are some choice fields and an optional field in the request. If I mess up one specific closing tag (example: see corrupt soap message below), the problem occurs.

 

I think this is a dangerous bug. Any comments about this problem?

Should I raise a jira issue?

 

It's easy to "trigger" this problem.

- Generate code from wsdl

- Produce an aar file (no skeleton implementation needed)

- Deploy the aar (for example locally on your PC)

- Use soapui for the invalid soap message

- Windows task manager shows the performance

 

Configuration:

Java 1.6.0.27

Tomcat 7

Axis2 1.6.1 and axis 1.6.2

 

 

Regards,

  

Robert van Dijk

 

 

 

 

****************************************************************************************************************************************************************************************

Servlet.log

 

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - getAction (null) from org.apache.axis2.client.Options@46a55e

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.MessageContext  - Old SoapAction is (null)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.MessageContext  - New SoapAction is (http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - setAction Old action is (null)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - setAction New action is (http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.builder.BuilderUtil  - Input contentType (text/xml;charset=UTF-8)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.builder.BuilderUtil  - CharSetEncoding from content-type (UTF-8)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.transport.TransportUtils  - createSOAPEnvelope using Builder (class org.apache.axis2.builder.SOAPBuilder) selected from type (text/xml)

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.builder.BuilderUtil  - char set encoding set from default =UTF-8

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.om.util.StAXUtils  - XMLStreamReader is org.apache.axiom.util.stax.dialect.WoodstoxStreamReaderWrapper

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder  - Starting to process SOAP 1.1 message

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder  - Build the OMElement Envelope by the StaxSOAPModelBuilder

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder  - Build the OMElement Header by the StaxSOAPModelBuilder

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder  - Build the OMElement Body by the StaxSOAPModelBuilder

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "Transport"

2012-07-25 10:26:18,356 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "Transport"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Transport'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.dispatchers.RequestURIBasedServiceDispatcher  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking for Service using target endpoint address : http://wpd03610:8080/axis2/services/ItemService

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.i18n.ProjectResourceBundle  - org.apache.axis2.i18n.resource::handleGetObject(servicefound)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.AbstractDispatcher  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Found AxisService : ItemService

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'SOAPActionBasedDispatcher' in Phase 'Transport'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - getAction (http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria) from org.apache.axis2.client.Options@46a55e

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.MessageContext  - SoapAction is (http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.dispatchers.ActionBasedOperationDispatcher  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking for Operation using Action : http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.description.AxisService  - getOperationBySOAPAction: Operation (org.apache.axis2.description.InOutAxisOperation@df8b14,{http://www.company.com/Xyz/ABC/Item/v1.0/}GetItemByCriteria) for soapAction: http://www.company.com/Xyz/ABC/Item/v1.0/GetItemByCriteria found in action map.

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.i18n.ProjectResourceBundle  - org.apache.axis2.i18n.resource::handleGetObject(operationfound)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.AbstractDispatcher  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Found AxisOperation : GetItemByCriteria

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "Transport"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "Addressing"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "Addressing"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'AddressingInHandler' in Phase 'Addressing'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.handlers.addressing.AddressingInHandler  - No headers present corresponding to http://www.w3.org/2005/08/addressing

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.handlers.addressing.AddressingInHandler  - No headers present corresponding to http://schemas.xmlsoap.org/ws/2004/08/addressing

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'AddressingBasedDispatcher' in Phase 'Addressing'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "Addressing"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "Security"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "Security"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "Security"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "PreDispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "PreDispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "PreDispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "Dispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "Dispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'SOAPActionBasedDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'RequestURIOperationDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'AddressingValidationHandler' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.addressing.AddressingHelper  - getAddressingRequirementParemeterValue: value: 'null'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'HTTPLocationBasedDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'GenericProviderDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'MustUnderstandValidationDispatcher' in Phase 'Dispatch'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher  - JAXWS MustUnderstandValidationDispatcher.invoke on AxisService ItemService; AxisOperation org.apache.axis2.description.InOutAxisOperation@df8b14

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "Dispatch"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.addressing.AddressingHelper  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] isReplyRedirected: ReplyTo is null. Returning false

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "RMPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "RMPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "RMPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "OperationInPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "OperationInPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking Handler 'MustUnderstandChecker' in Phase 'OperationInPhase'

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.jaxws.dispatchers.MustUnderstandUtils  - Building list of understood headers for all operations under ItemService

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.jaxws.dispatchers.MustUnderstandUtils  - Parameter not on ItemService; org.apache.axis2.jaxws.description.EndpointDescription.handlerParameterQNames

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.jaxws.dispatchers.MustUnderstandUtils  - Adding headers from SOAP handlers; headers = null

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "OperationInPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking pre-condition for Phase "soapmonitorPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Invoking phase "soapmonitorPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.engine.Phase  - [MessageContext: logID=ae5d5bd551a9dfda404b5f3740983af6c47527532aa068e3] Checking post-conditions for phase "soapmonitorPhase"

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - getAction (null) from org.apache.axis2.client.Options@b79701

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.MessageContext  - Old WSAAction is (null)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.MessageContext  - New WSAAction is (http://www.company.com/Xyz/ABC/Item/v1.0/ItemPortType/GetItemByCriteriaResponse)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - setAction Old action is (null)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.client.Options  - setAction New action is (http://www.company.com/Xyz/ABC/Item/v1.0/ItemPortType/GetItemByCriteriaResponse)

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axis2.context.ConfigurationContext  - messageID is null.

2012-07-25 10:26:18,403 ["http-bio-8080"-exec-4] DEBUG org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder  - Build the OMElement GetItemByCriteriaRequest by the StaxSOAPModelBuilder

<at this point axis2 hangs.....>

 

****************************************************************************************************************************************************************************************

Soap messages

-          First one is correct. 

-          The </v11:SearchCriteria> tag in second one is in the wrong order. This will cause the problem... System hangs

 

CORRECT

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.company.com/Xyz/ABC/Item/v1.0/" xmlns:v11="http://www.company.com/Xyz/ABC/Item/messages/v1.0/" xmlns:v12="http://www.company.com/Xyz/ABC/Item/types/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

      <v1: GetItemByCriteriaRequest >

         <v11:UserId>bla</v11:UserId>

         <v11:SearchCriteria>

            <v11:byMerchantId>

               <v11:First>

                  <v11:Data4Key>12345678901</v11: Data4Key>

               </v11:First>

            </v11:byMerchantId>

         </v11:SearchCriteria>

         <v11:Data5 Attr="ABC">

            <v12: Data5>1000</v12: Data5>

         </v11: Data5>

      </v1:GetAuthorisationByCriteriaRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

CORRUPT

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.company.com/Xyz/ABC/Item/v1.0/" xmlns:v11="http://www.company.com/Xyz/ABC/Item/messages/v1.0/" xmlns:v12="http://www.company.com/Xyz/ABC/Item/types/v1.0/">

   <soapenv:Header/>

   <soapenv:Body>

      <v1: GetItemByCriteriaRequest >

         <v11:UserId>bla</v11:UserId>

         <v11:SearchCriteria>

            <v11:byMerchantId>

               <v11:First>

                  <v11:Data4Key>12345678901</v11: Data4Key>

               </v11:First>

            </v11:byMerchantId>

         <v11:Data5 Attr="ABC">

            <v12: Data5>1000</v12: Data5>

         </v11: Data5>

         </v11:SearchCriteria>                  (wrong order)

      </v1:GetAuthorisationByCriteriaRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

 

****************************************************************************************************************************************************************************************

 

    <xs:complexType name="GetItemByCriteriaRequestType">

        <xs:sequence>

            <xs:element

                name="UserId"

                type="iphautt:UserIdType" />

            <xs:element name="SearchCriteria">

                <xs:complexType>

                    <xs:choice>

                        <xs:element name="byMerchantId">

                            <xs:complexType>

                                <xs:choice>

                                    <xs:element

                                        name="First"

                                        type="tns:Data4KeyType" />

                                    <xs:element

                                        name="Next"

                                        type="tns:Data6KeyType" />

                                </xs:choice>

                            </xs:complexType>

                        </xs:element>

                        <xs:element name="byContractId">

                            <xs:complexType>

                                <xs:choice>

                                    <xs:element

                                        name="First"

                                        type="tns:Data7KeyType" />

                                    <xs:element

                                        name="Next"

                                        type="tns:Data6KeyType" />

                                </xs:choice>

                            </xs:complexType>

                        </xs:element>

                    </xs:choice>

                </xs:complexType>

            </xs:element>

            <xs:element

                name="Data5"

                type="iphautt:Data5Type"

                minOccurs="0"

                maxOccurs="1" />

        </xs:sequence>

    </xs:complexType>

 

 

 

    <xs:complexType name="Data7KeyType">

        <xs:sequence>

            <xs:element

                name="Data1"

                type="iphautt:Data1Type" />

            <xs:element

                name="Data2"

                type="iphautt:Data2Type" />

            <xs:element

                name="Data3"

                type="iphautt:Data3Type" />

            <xs:element

                name="Data4"

                type="iphautt:Data4Type" />

        </xs:sequence>

    </xs:complexType>

 

    <xs:complexType name="Data6KeyType">

        <xs:sequence>

            <xs:element

                name="Data1"

                type="iphautt:Data1Type" />

            <xs:element

                name="Data2"

                type="iphautt:Data2Type" />

            <xs:element

                name="Data3"

                type="iphautt:Data3Type" />

            <xs:element

                name="Data4"

                type="iphautt:Data4Type" />

            <xs:element

                name="Data5"

                type="iphautt:Data5Type" />

        </xs:sequence>

    </xs:complexType>

 

 

    <xs:complexType name="Data4KeyType">

        <xs:sequence>

            <xs:element

                name="Data4"

                type="iphautt:Data4Type" />

        </xs:sequence>

    </xs:complexType>

 

 

 

 

 

 

------------------------------------------------------------------------------------------------
Disclaimer:

The contents of this electronic mail message are only binding upon Equens or its affiliates, if the contents of the message are accompanied by a lawfully recognised type of signature. The contents of this electronic mail message are privileged and confidential and are intended only for use by the addressee. If you have received this electronic mail message by error, please notify the sender and delete the message without taking notices of its content, reproducing it and using it in any way.

------------------------------------------------------------------------------------------------
 

------------------------------------------------------------------------------------------------
Disclaimer:
The contents of this electronic mail message are only binding upon Equens or its affiliates, if the contents of the message are accompanied by a lawfully recognised type of signature. The contents of this electronic mail message are privileged and confidential and are intended only for use by the addressee. If you have received this electronic mail message by error, please notify the sender and delete the message without taking notices of its content, reproducing it and using it in any way.
------------------------------------------------------------------------------------------------
 

------------------------------------------------------------------------------------------------
Disclaimer:

The contents of this electronic mail message are only binding upon Equens or its affiliates, if the contents of the message are accompanied by a lawfully recognised type of signature. The contents of this electronic mail message are privileged and confidential and are intended only for use by the addressee. If you have received this electronic mail message by error, please notify the sender and delete the message without taking notices of its content, reproducing it and using it in any way.

------------------------------------------------------------------------------------------------
 

--------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org For additional commands, e-mail: java-user-help@axis.apache.org


------------------------------------------------------------------------------------------------
Disclaimer:
The contents of this electronic mail message are only binding upon Equens or its affiliates, if the contents of the message are accompanied by a lawfully recognised type of signature. The contents of this electronic mail message are privileged and confidential and are intended only for use by the addressee. If you have received this electronic mail message by error, please notify the sender and delete the message without taking notices of its content, reproducing it and using it in any way.
------------------------------------------------------------------------------------------------