WST Demo (Phorum)

[marklittle]

Author: icgifford
Date: 08-12-05 12:21

I'm trying to run the WST Demo using JBoss 3.2.6 and jdk1.4.2_06.
When i submit a booking request i get the following error in JBoss for both Atomic Transaction and Business Activity.

Any Ideas?

Ian Gifford

11:43:00,078 ERROR [Engine] StandardContext[/ws-c]Activation Coordinator Listene
r Servlet: MessageListenerServlet
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.arjuna.wsc.messaging.jaxm.MessageListenerServlet.onMessage(Messag
eListenerServlet.java:97)
at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
at com.arjuna.wsc.messaging.jaxm.MessageListenerServlet.doPost(MessageLi
stenerServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:75)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrinc
ipalValve.java:66)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:158)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)

at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:683)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NoClassDefFoundError: org/apache/axis/SOAPPart
at com.arjuna.wsc.messaging.jaxm.axisbug.ArjunaMessageContext.setMessage
Context(ArjunaMessageContext.java:64)

[marklittle]

Author: Kevin Conner
Date: 08-12-05 14:30

Hiya Ian.

> I'm trying to run the WST Demo using JBoss 3.2.6 and
> jdk1.4.2_06.
> When i submit a booking request i get the following error in
> JBoss for both Atomic Transaction and Business Activity.
>
> Any Ideas?

> Caused by: java.lang.NoClassDefFoundError:
> org/apache/axis/SOAPPart
> at
> com.arjuna.wsc.messaging.jaxm.axisbug.ArjunaMessageContext.setMessage
> Context(ArjunaMessageContext.java:64)

The missing class is from the Axis SOAP library distributed with JBoss. Can you please check that the axis.jar file is present within your JBoss server instance?

The other thing to note about JBoss 3.2.6 is the existence of a bug that prevents the correct functioning of Jboss.net. The bug number was 1042176 under the sourceforge bug system but this is no longer accessible (JBoss have moved to JIRA). I would advise installing JBoss 3.2.7 if you have not already manage to patch 3.2.6.

Kev

[marklittle]

Author: icgifford
Date: 08-12-05 15:49

Well i've added the axis.jar to the lib and now i get:

exception

javax.servlet.ServletException: Servlet execution threw an exception
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)


root cause

java.lang.NoClassDefFoundError
com.arjuna.xts.nightout.clients.proxies.RestaurantServiceATServiceLocator.getRestaurantServiceAT(RestaurantServiceATServiceLocator.java:43)
com.arjuna.xts.nightout.clients.BasicClient.initialise(BasicClient.java:138)
com.arjuna.xts.nightout.clients.BasicClient.doGet(BasicClient.java:176)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)

Am i missing anything else?
Thanks
Ian

[marklittle]

Author: Kevin Conner
Date: 08-12-05 20:06

Hiya Ian

icgifford wrote:
> Well i've added the axis.jar to the lib and now i get:

This is not the right thing to do, there will be other libraries associated with it.

It sounds as if you are running the 'default' server instance and not the 'all' server instance.

You should either
- run the 'all' server configuration (run.sh -c all)
or
- copy the jboss-net.sar directory from the server/all/deploy directory into server/default/deploy.

We would prefer the first, it does not involve a change to the jboss installation, but the second is equivalent.

Please remember the warning about the 3.2.6 bug. If you have not patched your installation then you will get a NullPointerException thrown from the JBoss code.

Hope this helps,
Kev

[marklittle]

Author: icgifford
Date: 08-16-05 17:09

Kev

I'm running jboss 3.2.6 WITH the bug fix AND running the 'all' server configuration and i'm still getting the same error as before when i select 'submit' on the client web page.

I can't find any AXIS SOAP library distributed with JBoss 3.2.6, the only axis lib i can find in JBoss is the 'axis-ws4ee.jar' but i had to use the 'axis.jar' from my installation of AXIS to solve the inital problem i had.

I've tried running the demo through web methods glue aswell and it just hangs after the line:
CLIENT: starting the transaction...
when its trying to execute 'ut.begin();' in BasicClient.java

Any help gratefully received.
Cheers
Ian

[marklittle]

Author: Kevin Conner
Date: 08-31-05 11:56

Hiya Ian.

Sorry about the delay in responding, I've been away on holiday for a couple of weeks.

icgifford wrote:
> I'm running jboss 3.2.6 WITH the bug fix AND running the
> 'all' server configuration and i'm still getting the same error
> as before when i select 'submit' on the client web page.
>
> I can't find any AXIS SOAP library distributed with JBoss
> 3.2.6, the only axis lib i can find in JBoss is the
> 'axis-ws4ee.jar' but i had to use the 'axis.jar' from my
> installation of AXIS to solve the inital problem i had.

The one from the jboss-net.sar directory should be the correct one. I'll double check everything and get back to you on this.

> I've tried running the demo through web methods glue aswell
> and it just hangs after the line:
> CLIENT: starting the transaction...
> when its trying to execute 'ut.begin();' in
> BasicClient.java

Can you please tell me which version of glue you are using? Is it an evaluation or supported version? There was an update to 5.0.2 that was needed before the demo would work.

> Any help gratefully received.

Sorry you have been having problems, I'll try to get them addressed ASAP.

Kev

[marklittle]

Author: Kevin Conner
Date: 08-31-05 13:09

Hiya Ian.

I owe you a very big apology. It looks like I did not update the jboss 3.2.6 test version from 3.2.6RC1 to 3.2.6 when we released ATS4.

> The one from the jboss-net.sar directory should be the
> correct one. I'll double check everything and get back to you
> on this.

The axis code changed between RC1 and RC2, from the standard axis.jar to the jboss version axis-ws4ee.jar.

The purpose of the code that is causing your issue was to fix a bug in Axis. It appears, at least from a cursory inspection, that the jboss version does not contain the same bug. I will make a change so that this fix is no longer applied when running under 3.2.6RC2 upwards and will requalify against 3.2.6 and 3.2.7. I should, hopefully, be able to send you a patched version tomorrow.

Once again, please accept my apologies for these problems.

Kev

[marklittle]

Author: Kevin Conner
Date: 09-01-05 17:05

Hiya Ian.

An update on progress.

> The purpose of the code that is causing your issue was to fix
> a bug in Axis. It appears, at least from a cursory inspection,
> that the jboss version does not contain the same bug. I will
> make a change so that this fix is no longer applied when
> running under 3.2.6RC2 upwards and will requalify against 3.2.6
> and 3.2.7. I should, hopefully, be able to send you a patched
> version tomorrow.

The version of axis in 3.2.6 does indeed contain the same error. I have managed to implement a version of our workaround for 3.2.6 but, unfortunately, have discovered a more serious issue. The DeserializationContextImpl does not handle SAX character events correctly, causing text elements to have their value truncated. The version in 3.2.7 correctly handles multiple calls to the SAX characters event.

We will, unfortunately, not be able to support JBoss 3.2.6. It is likely that we will support 3.2.6RC1 (as it already passes) and 3.2.7 (qualifying now)

If there are no other issues then I will be in a position to send you a patched jar file tomorrow.

Apologies once again for the trouble caused,
Kev

[marklittle]

Author: Kevin Conner
Date: 09-06-05 10:57

Hiya Ian.

> If there are no other issues then I will be in a position to
> send you a patched jar file tomorrow.

Unfortunately there is a big issue preventing the deployment of the demo using the 3.2.7 version of JBoss.

The JBoss version of axis no longer picks up the axis client-config.wsdd file from within the deployable ear, it uses the classloader for the AxisClient instead of the thread context one to find the file. The consequence of this is that the JBoss axis will only load the client-config.wsdd found within jboss-net.sar.

Our demo relies on the specification of interceptors on both the server and client sides, the client side being specified through the client-config.wsdd file. If the client handlers aren't configured then there will be no transaction context passed to the service via the SOAP header block. I have tried numerous classloader configurations to try and get JBoss to load the correct configuration file but each attempt has been met with failure. Unfortunately the demo application will have to be rewritten for this version of JBoss.

At this point we can only support JBoss versions up to 3.2.6RC1.

Were you able to obtain the glue patch from webMethods? Have you managed to get the transaction system working with glue?

Kev