-
1. Re: error:javax.naming.CommunicationException
juha Feb 9, 2004 12:52 AM (in response to harsh_pandit)Your client side libs are out of sync with the server side. Maybe you've updated the server recently?
-
2. Re: error:javax.naming.CommunicationException
harsh_pandit Feb 9, 2004 2:48 AM (in response to harsh_pandit)Thanks for ur reply
But I have install jboss-3.2.3 recently and also not using ANT instead ,I m using jar commnad to create and deploy jar files.
None of the old versions of jboss are used in past.
please describe me procedure to solve this problem.
I will be very thankful of u. -
3. Re: error:javax.naming.CommunicationException
juha Feb 9, 2004 3:02 AM (in response to harsh_pandit)What is in your client's classpath? Where does your client get its JBoss libraries from?
-
4. Re: error:javax.naming.CommunicationException
harsh_pandit Feb 9, 2004 3:50 AM (in response to harsh_pandit)I have set following paths.
JBOSS_HOME=c:\jboss-3.2.3
JBOSS_DIST=c:\jboss-3.2.3
JAVA_HOME=c:\j2sdk1.4.0
CLASSPATH= c:\jboss-3.2.3\client\j2ee.jar;
c:\jboss-3.2.3\client\jboss-client.jar;
c:\jboss-3.2.3\lib\jboss-common.jar;
c:\jboss-3.2.3\client\jbosssx-client.jar;
c:\jboss-3.2.3\client\jnp-client.jar;
c:\jboss-3.2.3\lib\log4j-boot.jar
and I run program from
C:\JAVA\ejbprogram\java ConverterClient.
so what is wrong in paths.
If any paht is needed so tell me.
Thanks -
5. Re: error:javax.naming.CommunicationException
pilhuhn Feb 9, 2004 4:24 AM (in response to harsh_pandit)Try to just put jbossclient-all.jar (besides your own classes) in the classpath.
-
6. Re: error:javax.naming.CommunicationException
harsh_pandit Feb 9, 2004 4:40 AM (in response to harsh_pandit)Thanks I found solution