Hi Folks, I have a serious problem with JBoss-2.2/2.2.1 running on my Linux box (SuSE 6.4): The first lookup for a certain bean after a server restart or redeployment always hangs. This happens to my own beans but also to the provided tomcat-test application. I spent a day reading the jboss user and development mailing-lists but I didn't find this error description. So I'm curious whether other people have noticed the problem. The symptoms are: 0. Restart JBoss. 1. Call http://localhost:8080/jboss/servlet/HelloEJB in your browser. It never returns. Stop the request. 2. Call http://localhost:8080/jboss/servlet/HelloEJB again in your browser. It never returns, too. Stop the request. 3. Call the URL a third time. Now the call succeeds. The first call hangs at the lookup of the NonOptimized bean, the second hangs at the lookup of the Optimized bean and after this everything works fine (maybe InitialContext has a cache for paths?). I've tested IBMJava2-13, Blackdown's j2sdk1.3.0 and SUN's jdk1.3.0_02 in any combinations with JBoss-2.2/2.2.1, but it didn't help. On Windows 2000 the application didn't run at all (got the same CommunicationException that Fulco Muriglio reported yet). Any suggestions? Max -- Level of Detail GmbH Brunnenstr.196 10119 Berlin Tel: +49.30.280491-40 FAX: +49.30.280491-59 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
