File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Exception in deploying axis2.war in JBoss4.05

 
Amol Chavan
Greenhorn
Posts: 28
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have dowloaded latest version of JBoss (JBoss 4.05GA) and Axis2 and deployed axis2.war file in Tomcat 5.5 as well as in JBoss 4.05.
In both application server application is running fine but in JBoss it is throwing strange exception on console but still it is not affecting application.
Guys can you help on this as I am new to Webservices and Axis.

Exception is as follows:

13:31:58,651 WARN [UDP] packet from /192.168.133.89:1153 has different version (0227?) from ours (02271). This may cause problems
13:31:58,651 ERROR [UDP] exception=java.io.StreamCorruptedException: invalid stream header
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:753)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:268)
at org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:670)
at org.jgroups.protocols.UDP$IncomingPacketHandler.run(UDP.java:1332)
at java.lang.Thread.run(Thread.java:595)


Though application is running fine, the above mentioned exception is being thrown by application continuously when deployed on JBoss 4.05 while in tomcat 5.5 its running without such exception.

Please help if you know the reason.
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have dowloaded latest version of JBoss (JBoss 4.05GA) and Axis2 and deployed axis2.war file in Tomcat 5.5 as well as in JBoss 4.05.


Where have you placed the axis2.war? Is it in %JBOSS_HOME%/server/default/deploy or is it in %JBOSS_HOME%/server/all/deploy. The reason why i ask this is, the stacktrace mentions something related to jgroups which comes into picture during clustering (i.e. when you place the war in %JBOSS_HOME%/server/all/deploy)
 
radhi devi
Greenhorn
Posts: 3
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jaikiran Pai:


Where have you placed the axis2.war? Is it in %JBOSS_HOME%/server/default/deploy or is it in %JBOSS_HOME%/server/all/deploy. The reason why i ask this is, the stacktrace mentions something related to jgroups which comes into picture during clustering (i.e. when you place the war in %JBOSS_HOME%/server/all/deploy)


Hi,
I also have the same problem.
Am having ews.war in server/all/deploy from JBOSS server.
Is it the reason?
Do Advise me.
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"radhi radhi"

Please check your mail, for a message from JavaRanch.
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by radhi radhi:
Hi,
I also have the same problem.
Am having ews.war in server/all/deploy from JBOSS server.
Is it the reason?
Do Advise me.


Do you want to have clustering services of JBoss. If no, then move your ews.war to server/default/deploy and start the server using



However, if you want to have clustering services, then let the war remain where it is now. The reason you see that exception might have to do with other machines in the network (maybe your LAN) which are becoming a part of the cluster. These other nodes might be having a different version of JBoss jars which might be causing this exception.
 
radhi devi
Greenhorn
Posts: 3
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for u'r reply.

Actually Our EWS.war should be in the path server/all/deploy .
We can't change it. So is there any other way to avoid such exception..
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please check the JBoss instances and their versions, which are becoming part of the cluster. It looks like different versions of JBoss are coming to form a cluster. I guess, you will have to isolate different versions of JBoss which are forming the cluster. See if TwoClustersSameNetwork is of any help.
 
Alex Chevelev
Greenhorn
Posts: 1
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We also had this issue. We had two instances of jboss 4.0.5 in cluster and were getting these messages in log. It was because we had two implementations of JGroups with different version located in server/default/lib. Occasionally each of servers in cluster were choosing its own implementation so they were incompatible: 2.2.8 and 2.2.7.1. The removal of redundant jar resolved the issue.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic