IBM Support

PM44743: A JAVAX.XML.BIND.UNMARSHALEXCEPTION MIGHT OCCUR WHEN INBOUND SOAP MESSAGES ARE DEMARSHALLED.

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When JAX-WS applications are running over a long period
of time, a javax.xml.bind.UnmarshalException
might occur when inbound SOAP messages are demarshalled.

For example:

[11/07/25 22:54:30:768 JST] 00000021 ExceptionFact 1
org.apache.axis2.jaxws.ExceptionFactory logRootCause Root
Cause:javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element
(uri:"http://foo.service.ws.abc.xyz/",
local:"execute"). Expected elements are ...
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.handleStreamException(UnmarshallerImpl.java:445)
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.unmarshal0(UnmarshallerImpl.java:370)
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.unmarshal(UnmarshallerImpl.java:340)
at
com.ibm.xml.xlxp2.jaxb.unmarshal.UnmarshallerImpl.unmarshal(Unma
rshallerImpl.java:289)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext$7.run(JAXBDSConte
xt.java:1063)
at
org.apache.axis2.java.security.AccessController.doPrivileged(Acc
essController.java:76)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.unmarshalByElemen
t(JAXBDSContext.java:1060)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.unmarshal(JAXBDSC
ontext.java:326)
at
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._g
etBOFromReader(JAXBBlockImpl.java:96)
at
org.apache.axis2.jaxws.message.impl.BlockImpl._getBOFromOM(Block
Impl.java:477)
at
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._g
etBOFromOM(JAXBBlockImpl.java:136)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.getBusinessObject(
BlockImpl.java:149)
at
org.apache.axis2.jaxws.message.impl.XMLSpineImpl._getBlockFromOM
Element(XMLSpineImpl.java:620)
at
org.apache.axis2.jaxws.message.impl.XMLSpineImpl.getBodyBlock(XM
LSpineImpl.java:357)
at
org.apache.axis2.jaxws.message.impl.XMLPartBase.getBodyBlock(XML
PartBase.java:521)
at
org.apache.axis2.jaxws.message.impl.MessageImpl.getBodyBlock(Mes
sageImpl.java:670)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMa
rshaller.demarshalRequest(DocLitWrappedMethodMarshaller.java:255
)
...

This is due to the wrong javax.xml.bind.Unmarshaller object
used to unmarshall the message.

Local fix

  • Local Fix/Work Around:

No work around is available

Problem summary

  • ****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  JAX-WS applications.                        *
****************************************************************
* PROBLEM DESCRIPTION: A javax.xml.bind.UnmarshalException     *
*                      might occur when inbound SOAP           *
*                      messages are demarshalled.              *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this       *
*                  APAR.                                       *
****************************************************************
When JAX-WS clients and services are sent a heavy load of
messages over a long period of time, a
javax.xml.bind.UnmarshalException might occur during the
demarshalling of inbound SOAP messages.
For example:
 11/07/25 22:54:30:768 JST  00000021 ExceptionFact 1
org.apache.axis2.jaxws.ExceptionFactory logRootCause Root
Cause:javax.xml.bind.UnmarshalException
- with linked exception:
 javax.xml.bind.UnmarshalException: unexpected element
(uri:"http://foo.service.ws.abc.xyz/",
local:"execute"). Expected elements are ...
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.handleStreamException(UnmarshallerImpl.java:445)
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.unmarshal0(UnmarshallerImpl.java:370)
at
com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerIm
pl.unmarshal(UnmarshallerImpl.java:340)
at
com.ibm.xml.xlxp2.jaxb.unmarshal.UnmarshallerImpl.unmarshal(Unma
rshallerImpl.java:289)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext$7.run(JAXBDSConte
xt.java:1063)
at
org.apache.axis2.java.security.AccessController.doPrivileged(Acc
essController.java:76)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.unmarshalByElemen
t(JAXBDSContext.java:1060)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.unmarshal(JAXBDSC
ontext.java:326)
at
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._g
etBOFromReader(JAXBBlockImpl.java:96)
at
org.apache.axis2.jaxws.message.impl.BlockImpl._getBOFromOM(Block
Impl.java:477)
at
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._g
etBOFromOM(JAXBBlockImpl.java:136)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.getBusinessObject(
BlockImpl.java:149)
at
org.apache.axis2.jaxws.message.impl.XMLSpineImpl._getBlockFromOM
Element(XMLSpineImpl.java:620)
at
org.apache.axis2.jaxws.message.impl.XMLSpineImpl.getBodyBlock(XM
LSpineImpl.java:357)
at
org.apache.axis2.jaxws.message.impl.XMLPartBase.getBodyBlock(XML
PartBase.java:521)
at
org.apache.axis2.jaxws.message.impl.MessageImpl.getBodyBlock(Mes
sageImpl.java:670)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMa
rshaller.demarshalRequest(DocLitWrappedMethodMarshaller.java:255
)
...
This is due to the wrong javax.xml.bind.Unmarshaller object
used to unmarshall the message.

Problem conclusion

  • For performance reasons, the JAX-WS engine caches Unmarshaller
objects for re-using later. This APAR corrects a faulty
algorithm for storing and retrieving Unmarshaller objects.

This same problem is fixed in Feature Pack for Web Services
under APAR PM44824.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.21 and 8.0.0.2.  Please refer to the
Recommended Updates page for delivery information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM44743
    • 

  • Reported component name
    WEBSPHERE APP S
    • 

  • Reported component ID
    5724J0800
    • 

  • Reported release
    700
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2011-07-29
    • 

  • Closed date
    2011-08-30
    • 

  • Last modified date
    2012-01-19
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    
PM44824
    

    • 



Fix information


    

  • Fixed component name
    WEBSPHERE APP S
    • 

  • Fixed component ID
    5724J0800
    • 



Applicable component levels


    

  • R700  PSY
       UP
    • 

  • R800  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            27 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback