Found the problem...  jndi.properties needed a change...  Please disregard
this issue...

-----Original Message-----
From: Hanson, Matthew [mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 7:27 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] 3.2.2 -> 3.2.3 = CommunicationException for
Clie nts


Haven't seen any response on this, so I thought I would retry...

Has anyone encountered client JNDI problems when upgrading to 3.2.3?

Please help!

Regards,
Matt Hanson

-----Original Message-----
From: Hanson, Matthew [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 8:53 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] 3.2.2 -> 3.2.3 = CommunicationException for
Clie nts


Sorry, we just upgraded to jboss 3.2.3.  Apologies...

-----Original Message-----
From: Hanson, Matthew [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 8:27 AM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] 3.2.2 -> 3.2.3 = CommunicationException for
Clients


Hi,

We just upgraded to jboss 3.2.2.  All beans, as written for 3.2.2, deployed
fine to the container.  However, the first simple client tests that I ran
are having JNDI problems.  Here is the stack trace:

     [echo] Client CLASSPATH =
C:\jboss-3.2.3\client\concurrent.jar;C:\jboss-3.2.3\client\getopt.jar
;C:\jboss-3.2.3\client\gnu-regexp.jar;C:\jboss-3.2.3\client\jacorb.jar;C:\jb
oss-3.2.3\client\jboss-c
lient.jar;C:\jboss-3.2.3\client\jboss-common-client.jar;C:\jboss-3.2.3\clien
t\jboss-iiop-client.jar;
C:\jboss-3.2.3\client\jboss-j2ee.jar;C:\jboss-3.2.3\client\jboss-jaas.jar;C:
\jboss-3.2.3\client\jbos
s-jsr77-client.jar;C:\jboss-3.2.3\client\jboss-net-client.jar;C:\jboss-3.2.3
\client\jboss-system-cli
ent.jar;C:\jboss-3.2.3\client\jboss-transaction-client.jar;C:\jboss-3.2.3\cl
ient\jbossall-client.jar
;C:\jboss-3.2.3\client\jbosscx-client.jar;C:\jboss-3.2.3\client\jbossha-clie
nt.jar;C:\jboss-3.2.3\cl
ient\jbossjmx-ant.jar;C:\jboss-3.2.3\client\jbossmq-client.jar;C:\jboss-3.2.
3\client\jbosssx-client.
jar;C:\jboss-3.2.3\client\jcert.jar;C:\jboss-3.2.3\client\jmx-connector-clie
nt-factory.jar;C:\jboss-
3.2.3\client\jmx-ejb-connector-client.jar;C:\jboss-3.2.3\client\jmx-invoker-
adaptor-client.jar;C:\jb
oss-3.2.3\client\jmx-rmi-connector-client.jar;C:\jboss-3.2.3\client\jnet.jar
;C:\jboss-3.2.3\client\j
np-client.jar;C:\jboss-3.2.3\client\jsse.jar;C:\jboss-3.2.3\client\log4j.jar
;C:\jboss-3.2.3\client\x
doclet-module-jboss-net.jar;F:\Personal\Java\proj\hbrm\lib\ejb-hbrm.jar;F:\P
ersonal\Java\proj\hbrm\l
ib\hbrm.jar;C:\jargs-0.4\lib\jargs.jar;C:\eclipse\plugins\org.junit_3.8.1\ju
nit.jar;C:\junit-addons-
1.4\junit-addons-1.4.jar;C:\junit-addons-1.4\src.jar
     [java] TestLog4j caught an unexpected exception!
     [java] javax.naming.CommunicationException: Receive timed out.  Root
exception is java.net.Sock
etTimeoutException: Receive timed out
     [java]     at java.net.PlainDatagramSocketImpl.receive(Native Method)
     [java]     at java.net.DatagramSocket.receive(DatagramSocket.java:671)
     [java]     at
org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093)
     [java]     at
org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1223)
     [java]     at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
     [java]     at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
     [java]     at
javax.naming.InitialContext.lookup(InitialContext.java:347)
     [java]     at
homebrew.ejb.session.util.AccountFacadeUtil.getHome(AccountFacadeUtil.java:2
7)

Here are the jndi.properties entries:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

Have there been changes to the JNDI for 3.2.3?  If so, could someone provide
me with the new values?  No source/configurations changes were introduced
during the upgrade.

Regards,
Matt Hanson


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to