RE: Axis, JMS and SOAP issue.

[Arin George <ar...@privacyinc.com>]

Hello,

---
What we are trying to do:
   We are trying to call JMS using a java bean running in axis running
in tomcat.  We are trying to create the jms socket within axis.  We are
getting a 42 Invocation Error.  This seems to be very generic error.
---

---
What we are using:
1) Apache Axis 1.1
2) Sun 1 JMS Message Queue 3.5
3) Tomcat 5.0.19
---

---
What the symptoms are:
1) The code seems to be going to some function call and not returning.
Actual Example...

Code running in axis:

   System.out.println("Hello 1");
   Status s = new Status();
   System.out.println("Hello 2");

Code sitting in Status.jar in the axis lib directory:

   public Status() { System.out.println("GoodBye 1"); }

Output we get in catalina.out:

   Hello 1
---

---
Questions:
1) Is there any log file for axis and tomcat (other than catalina.out)
where we may recieve a more precise error?
2) Has there been any known problems using Sun 1 JMS Message Queue 3.5
with axis?
3) Would you have any suggestions on debugging this error?
---


Any help is appreciated, thank you.

Best Regards,
Arin George.

Re: Axis, JMS and SOAP issue.

[Biörn Biörnstad <bi...@vis.ethz.ch>]

>    We are trying to call JMS using a java bean running in axis running
> in tomcat.  We are trying to create the jms socket within axis.  We are
> getting a 42 Invocation Error.  This seems to be very generic error.
You need to be more speicific. From your description I understand that you're 
talking to JMS directly and not using the JMS transport of Axis?

> 1) Is there any log file for axis and tomcat (other than catalina.out)
> where we may recieve a more precise error?
Configure the logging mechanism (log4j) to get more output in catalina.out. 
Adding a log4j.properties file to the classpath of the webapp should help. Set 
the Level of the root logger to DEBUG for a lot of output.

> 2) Has there been any known problems using Sun 1 JMS Message Queue 3.5
> with axis?
I have been using JORAM both directly and through the JMS transport and have not 
encountered any JMS specific problems.

> 3) Would you have any suggestions on debugging this error?
- Try running your JMS code outside Axis (assuming your accessing JMS directly)
- Make sure all the classes/JARs necessary for your JMS provider are available 
to your web service.

HTH,
Bioern