-
1. Re: EJB Client stops after getting the context
sgturner Sep 28, 2002 10:03 AM (in response to dineshbsam)Hmmm. Never seen that problem. Check what properties you are using to get the Context. What happens if your code tries to use some other methods of Context besides lookup? Try using some of the Context methods to display contents of Context.
-
2. Re: EJB Client stops after getting the context
dineshbsam Oct 3, 2002 4:39 AM (in response to dineshbsam)Hi!
Thanks for the reply..
i'm still stuck at the same.. i'm not able to figure out why this is happening. my bean get deployed sucessfully.
--
12:38:21,915 INFO [MainDeployer] Successfully completed deployment of package:
file:/C:/jbosstomcat/server/default/deploy/Product.jar
12:38:21,945 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
tomcat/server/default/deploy/Log.jar
12:38:22,055 INFO [EjbModule] Creating
12:38:22,075 INFO [EjbModule] Deploying Log
12:38:22,976 INFO [EjbModule] Created
12:38:22,976 INFO [EjbModule] Starting
12:38:22,986 INFO [EjbModule] Started
12:38:22,986 INFO [MainDeployer] Successfully completed deployment of package:
file:/C:/jbosstomcat/server/default/deploy/Log.jar
12:38:23,016 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
tomcat/server/default/deploy/HelloMDB.jar
12:38:23,127 INFO [EjbModule] Creating
12:38:23,147 INFO [EjbModule] Deploying HelloTopicMDB
12:38:23,197 INFO [EjbModule] Created
12:38:23,207 INFO [EjbModule] Starting
12:38:23,207 INFO [EjbModule] Started
12:38:23,217 INFO [MainDeployer] Successfully completed deployment of package:
file:/C:/jbosstomcat/server/default/deploy/HelloMDB.jar
---
but, i tried setting the properties inside the code as well.
--
Properties env = new Properties();
env.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.setProperty("java.naming.provider.url", "localhost:1099");
env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
//Get initailcontext
Context ctx = new InitialContext(env);
--
but when i run the client.. it gets the context & stops there.
--
C:\jbosstomcat\ejbexam\jbossmdb>javac -classpath .;c:\jbosstomcat\client\ejb.jar
;c:\j2sdkee1.3.1\lib\j2ee.jar HelloClient.java
C:\jbosstomcat\ejbexam\jbossmdb>java -classpath .;c:\jbosstomcat\client\jboss-c
lient.jar;c:\jbosstomcat\client\jbosssx-client.jar;c:\jbosstomcat\client\jnp-cli
ent.jar;c:\j2sdkee1.3.1\lib\j2ee.jar HelloClient
--
pls. help.
regards
Dinesh -
3. Re: EJB Client stops after getting the context
domarm Dec 11, 2002 5:19 PM (in response to dineshbsam)Did you ever get this problem figured out? I'm having the same problem.
Thanks, Matt -
4. Re: EJB Client stops after getting the context
domarm Dec 11, 2002 5:55 PM (in response to dineshbsam)My client program hangs after doing a JNDI lookup on the initial context. In my code I get the InitialContext just fine. But when I try to get an EJB home object from it, it just sits there. Profiling my CPU shows the JVM gives up on the lookup about 10 seconds after I start it. Basically, nothing happens. Every once in a while, if I let go long enough, lookup will return null. I'm getting no Exceptions and nothing is getting written to the logs. This is very frustrating since I can't provide more details.
I've been going through the forums for the past day now and haven't really found anything that helps.
Help, I need to port our app to JBoss and can't even do a simple JNDI lookup!!!
Thanks, Matt -
5. Re: EJB Client stops after getting the context
juha Dec 13, 2002 1:14 PM (in response to dineshbsam)try playing with your NICs, try disconnecting from network etc and see if it makes a diff. Usually some kind of funky network setup that prevents JVM (RMI?) from connecting.
-
6. Re: EJB Client stops after getting the context
venko Jan 6, 2003 6:08 AM (in response to dineshbsam)I am also facing exactly similar problem.
It is really frustating.
If you have found any souliton please let me know.
venkox@yahoo.com
thanks,
venko. -
7. Re: EJB Client stops after getting the context
weber Jan 6, 2003 10:57 AM (in response to dineshbsam)couldn't you post the code (along with the descriptors)?
PS: I've faced a similar situation some time ago and it was a network misconfiguation issue. Perhaps, you should take a look in the /etc/hosts file.
cya,
Weber