Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.lang.NoClassDefFoundError: com.ibm.ws.wstx.handler.WSATGenerator

378 views
Skip to first unread message

DWWorks

unread,
Sep 7, 2009, 1:48:23 AM9/7/09
to
When I invoke a Web Service with JAX-WS Dispatch from a MDB that runs as a transaction, I receive the following stack trace:

[07.09.09 07:34:16:032 CEST] 0000004a LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onMessage" on bean "BeanId(SWoMV1#ProcessExecution.jar#InvocationHandlerMessageBean, null)". Exception data: java.lang.NoClassDefFoundError: com.ibm.ws.wstx.handler.WSATGenerator (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
at com.ibm.ws.wstx.WSTXClientTCMImpl.handleInbound(WSTXClientTCMImpl.java:100)
at com.ibm.ws.wstx.WSTXClientTCMImpl.cleanupContext(WSTXClientTCMImpl.java:81)
at org.apache.axis2.util.ThreadContextMigratorUtil.performContextCleanup(ThreadContextMigratorUtil.java:192)
at org.apache.axis2.jaxws.core.controller.impl.AxisInvocationController.postExecute(AxisInvocationController.java:630)
at org.apache.axis2.jaxws.core.controller.impl.AxisInvocationController.execute(AxisInvocationController.java:562)
at org.apache.axis2.jaxws.core.controller.impl.AxisInvocationController.doInvokeAsync(AxisInvocationController.java:260)
at org.apache.axis2.jaxws.core.controller.impl.InvocationControllerImpl.invokeAsync(InvocationControllerImpl.java:260)
at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.invokeAsync(BaseDispatch.java:329)

Environment is WebSphere 7.0, MS Vista.

Any help is appreciated

Jon Hawkes

unread,
Sep 8, 2009, 4:30:35 AM9/8/09
to
I believe this is fixed in 7005. Please install that level of WAS and if the
problem persists, raise a PMR.

"DWWorks" <Dieter....@informatik.uni-stuttgart.de> wrote in message
news:883841098.1252302534...@ltsgwas009.sby.ibm.com...

bkail

unread,
Sep 8, 2009, 7:40:12 PM9/8/09
to
There should be a "Caused by" exception that indicates the root cause of the "(initialization failure)". If not, there should be an exception elsewhere in the logs that includes "WSATGenerator.(...)". As a first guess, this is a product issue that will require a PMR.
0 new messages