-
1. Re: Communication between JBoss 2.2.1 and JBoss 3.0.3
juha Oct 23, 2002 1:00 PM (in response to adressin)It is true in some cases, not sure if it applies to your case or not.
What is the stack trace you get when using narrow()? What errors you get (if any) when you use a normal Java cast for the lookup instead of narrow() ?
And finally, what JDK versions are you running with?
-- Juha -
2. Re: Communication between JBoss 2.2.1 and JBoss 3.0.3
adressin Oct 23, 2002 1:58 PM (in response to adressin)Here is the stack dump for jnp "narrow" call:
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:296)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at com.a.lims.control.LIMSDelegate.delegateWork(LIMSDelegate.java:61)
at com.a.lims.bic.LimsBicImpl.doWork(LimsBicImpl.java:20)
at com.enter.apps.agents.bic.AsynchBIC.doWork(AsynchBIC.java:3267)
at com.enter.apps.agents.bic.AsynchBIC.run(AsynchBIC.java:3170)
at java.lang.Thread.run(Thread.java:484)
I am using JDK 1.3.1_01 on client and JDK 1.3.1-b24 on server (JBoss 3)
Thanks,
Aaron -
3. Re: Communication between JBoss 2.2.1 and JBoss 3.0.3
adressin Oct 23, 2002 2:27 PM (in response to adressin)Oh... and here is the dump when I just do a plain java cast on the lookup call:
java.lang.ClassCastException: org.jnp.interfaces.MarshalledValuePair
at com.a.lims.control.LIMSDelegate.delegateWork(LIMSDelegate.java:61)
at com.a.lims.bic.LimsBicImpl.doWork(LimsBicImpl.java:20)
at com.e.apps.agents.bic.AsynchBIC.doWork(AsynchBIC.java:3267)
at com.e.apps.agents.bic.AsynchBIC.run(AsynchBIC.java:3170)
at java.lang.Thread.run(Thread.java:484)
Please note that this is not a problem when I run this client from the command line both remotely and locally... only when I run it within the context of JBoss 2.2.1.
Thanks, Aaron -
4. Re: Communication between JBoss 2.2.1 and JBoss 3.0.3
juha Oct 23, 2002 5:29 PM (in response to adressin)well looks like the last class cast exception is coming from the naming implementation, so it seems its an incompatibility between the two different JBoss versions.