[JBoss-dev] [ jboss-Bugs-731524 ] Problem Using jbossall-client.jar

[SourceForge.net <no...@so...>]

Bugs item #731524, was opened at 2003-05-02 14:28
Message generated for change (Comment added) made by allisonb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731524&group_id=22866

Category: None
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Bob Allison (allisonb)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem Using jbossall-client.jar

Initial Comment:
When trying to run a client with [jboss]/client/jbossall-client.jar in the 
classpath, I would get the following exception when retrieving a Bean 
Home: 
 
javax.naming.CommunicationException: Failed to retrieve stub from 
server x.x.x.x:1100 [Root exception is java.io.InvalidClassException: 
org.jboss.ha.framework.interfaces.HARMIClient; local class 
incompatible: stream classdesc serialVersionUID = 
-1886684369797675810, local class serialVersionUID = 
-1227816478666532463] 
        at 
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:210) 
        at 
org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1050) 
        at 
org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1158) 
        at 
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:478) 
        at 
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 
        at javax.naming.InitialContext.lookup(InitialContext.java:347) 
 
The client works correctly if I place each jar file in [jboss]/client in the 
classpath. 
 
While scanning the build files to locate what went into the 
jbossall-client.jar file, I noticed something that seemed odd, and it 
may relate to the problem.  The jar task builds a jar file named 
"${install.client}/jbossall-client.jar" from the files dumped into a 
temporary directory named "build".  Right before this step is an unjar 
task while extracts a set of jar files from "${install.client}"; the fileset 
includes "*-client.jar" and excludes "jboss-all-client.jar".  Shouldn't the 
name of the excluded jar match the name of the one being built? 

----------------------------------------------------------------------

>Comment By: Bob Allison (allisonb)
Date: 2003-05-03 07:27

Message:
Logged In: YES 
user_id=24762

I see the same value in both jars on my system as well.  I
wonder where the client is getting a different value?

One thing I am doing "weird":  I have packaged the
application to run with a "java -jar" command line, which
was when this started happening.  (To make this work the jar
files for JBoss are listed in the manifest.)  Any ideas why
this would work differently?

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-05-02 21:23

Message:
Logged In: YES 
user_id=175228

Is this with your own incremental build? The -1227816478666532463L id is 
the current 3.2.0 release value and this is seen in both the jbossall-client.jar 
and the jbossha-client.jar:

[starksm@nukes client]$ serialver -classpath jbossall-client.jar 
org.jboss.ha.framework.interfaces.HARMIClient 
org.jboss.ha.framework.interfaces.HARMIClient:    static final long 
serialVersionUID = -1227816478666532463L;
[starksm@nukes client]$ serialver -classpath jbossha-client.jar 
org.jboss.ha.framework.interfaces.HARMIClient
org.jboss.ha.framework.interfaces.HARMIClient:    static final long 
serialVersionUID = -1227816478666532463L;

I can see how an incremental build could produce a problem but not a clean
build. The build.xml has been fixed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=731524&group_id=22866