Sorry, you are still on the right forum, but then I ask me why nobody from the developer of axis/J-1.4 is answering if they want to have axis/J and axis2/J questions on the same forum?
Josef So your issue is NOT only an axis client and server issue implemented with axis-1.4? right? In this case please read http://axis.apache.org/axis/java/install.html and there be aware about ...... Things you have to know A lot of problems with Axis are encountered by people who are new to Java, server-side Java and SOAP. While you can learn about SOAP as you go along, writing Axis clients and servers is not the right time to be learning foundational Java concepts, such as what an array is, or basic application server concepts such as how servlets work, and the basics of the HTTP protocol. Things you need to know before writing a Web Service: 1. Core Java datatypes, classes and programming concepts. 2. What threads are, race conditions, thread safety and sychronization. 3. What a classloader is, what hierarchical classloaders are, and the common causes of a "ClassNotFoundException". 4. How to diagnose trouble from exception traces, what a NullPointerException (NPE) and other common exceptions are, and how to fix them. 5. What a web application is; what a servlet is, where classes, libraries and data go in a web application. 6. How to start your application server and deploy a web application on it. 7. What a network is, the core concepts of the IP protocol suite and the sockets API. Specifically, what is TCP/IP. 8. What HTTP is. The core protocol and error codes, HTTP headers and perhaps the details of basic authentication. 9. What XML is. Not necessarily how to parse it or anything, just what constitutes well-formed and valid XML. Axis and SOAP depends on all these details. If you don't know them, Axis (or anyone else's Web Service middleware) is a dangerous place to learn. Sooner or later you will be forced to discover these details, and there are easier places to learn than Axis. If you are completely new to Java, we recommend you start off with things like the Java Tutorials on Sun's web site, and perhaps a classic book like Thinking in Java <http://www.mindview.net/Books/TIJ/> , until you have enough of a foundation to be able to work with Axis. It is also useful to have written a simple web application, as this will give you some knowledge of how HTTP works, and how Java application servers integrate with HTTP. You may find the course notes from Mastering the World Wide Web <http://www.cs.indiana.edu/classes/a348-dger/fall2002/notes/> useful in this regard, even though Axis is only introduced in lecture 28. Be aware that there is a lot more needed to be learned in order to use Axis and SOAP effectively than the listing above. The other big area is "how to write internet scale distributed applications". Nobody knows how to do that properly yet, so that you have to learn this by doing. ....... This said, the remainder is still worth reading and learning: Now to your writing, reading one more time! Recently we moved away from weblogic to axis for webservice implementation When I read this I have the first concern: you are not migrating away from weblogic to axis webservices. BUT you take 2 steps at once at least. So I ask a few questions now which you as developer should never ever forget if you ask in a forum. 1. May I ask you kindly what OS do you have for client and for server? Because complex, threading and RT issues may depend on OS as well 2. Be aware axis/J-1.4 was not made for Java Version : 1.6.0_16, so why not trying an earlier Java Version i.e. 1.4 and related JVM's? THEN 3. You migrate from application server weblogic to a different application server! Which one? Is it Tomcat, or JBoss, or Glasfish or what???????? And which version? 4. Can you specific on that and give me the OS and Application Server on which you intend to run your axis/J-1.4 web service? 5. You have your client code written in axis/J-1.4 at Weblogic time and it remains as it is! Yes or no? Did you rewrite your client code it for axis/J-1.4 6. Given the client is on a different platform then your axis/J-1.4 service. What is it? OS, Java Version, and confirm axis/J-1.4? 7. If not done so: The first step you take is to switch away from a Weblogic AS to a Tomcat AS, did you do so? Which version of Tomcat is installed? 8. You have your service code written/configured properly for axis/J-1.4 and booth run more or less but show intermittent problems under heavy load? 9. What is heavy load? How many request hit the application server tomcat per second? You can see that at http://your-server:8080/manager/status/all 10. I ask this because most of the concurrency and multithreading issues are addressed in Tomcat; 11. It is Tomcat which receives the many concurrent requests and calls the servlet called "axis" 12. Axis-Engine has further to dispatch according to axis message processing rules, EP's, using more or less thread safe code! J 13. So what are your results seen when you have re-written your service code and configuration details for your new AS AND 14. all runs on JVM -> Tomcat -> axi2/J-1.4 -> your-service? 15. AND You forget to say, how intermittent, how frequently you receive this exception? 16. If the exception is seen only sometimes/intermittently, (once every 5 minutes on heavy load) why can the client not implement proper exception handling, wait 3 seconds and re-send the same request to the service again? Let me know and may we get it. Josef Von: Raghavendra Seshadri [mailto:raghavendra_sesha...@mindtree.com] Gesendet: Montag, 20. Juni 2011 10:17 An: java-user@axis.apache.org Betreff: RE: Axis 1.4 Issue Due to restrictions on the webservices were are using , we cannot migrate to Axis2 for stub generation as of now. Thanks for informing, I will check the right forum From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: Monday, June 20, 2011 1:11 PM To: java-user@axis.apache.org Subject: AW: Axis 1.4 Issue What about migrating to Axis2-1.6.0 (Java)? Because Axis and Axis2 whatever versions are two pairs of shoes, and you are asking the Axis2 Forum Josef Von: Raghavendra Seshadri [mailto:raghavendra_sesha...@mindtree.com] Gesendet: Freitag, 17. Juni 2011 05:01 An: java-user@axis.apache.org Betreff: RE: Axis 1.4 Issue We are using Axis Java version 1.4, From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: Thursday, June 16, 2011 5:22 PM To: java-user@axis.apache.org Subject: AW: Axis 1.4 Issue Are you talking about AXIS2/J or AXIS? Josef Von: Raghavendra Seshadri [mailto:raghavendra_sesha...@mindtree.com] Gesendet: Mittwoch, 15. Juni 2011 12:18 An: java-user@axis.apache.org Betreff: Axis 1.4 Issue Hi , I am Raghavendra I work for Mindtree, Recently we moved away from weblogic to axis for webservice implementation, we are using Axis 1.4 for stub generation. We are facing an intermittent issue. We need your help in this regard We are getting the following Axis fault message intermittently, we see this issue mainly when multiple requests are hitting the same server, we could say concurrent requests (Multithreaded as well) AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.NullPointerException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException at org.apache.axis.encoding.DeserializerImpl.valueComplete(DeserializerImpl .java:247) at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.ja va:509) at org.apache.axis.encoding.DeserializationContext.endElement(Deserializati onContext.java:1087) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java: 171) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j ava:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2467) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) Axis Version : 1.4 Java Version : 1.6.0_16 Currently we don't have request sent, we are trying to reproduce it to capture more details, Please let us know when this error can occur and possible fix for this Thanks & Regards Raghavendra ________________________________ http://www.mindtree.com/email/disclaimer.html
