[ http://jira.jboss.com/jira/browse/JBAS-1376?page=comments#action_12315277 ] Daniel commented on JBAS-1376: ------------------------------
Thanks, although the only useful thing you had to say was to direct me to jnp.timeout. > JBoss freezes if the wrong port is specified for JNDI lookup. > ------------------------------------------------------------- > > Key: JBAS-1376 > URL: http://jira.jboss.com/jira/browse/JBAS-1376 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-3.2.5 Final > Environment: Solaris 2.8, JDK 1.4.2_05 > Reporter: Daniel > Assignee: Adrian Brock > Priority: Minor > > > I have an EJB client which I was trying to run. Unfortunately I managed to > specify port 1098 (RMI) instead of port 1099 (JNDI) for the client to use. > The net effect was that the client froze on the second line of code below: > Context _jndiContext = new javax.naming.InitialContext(); > _jndiContext.lookup( name ); > I wasted a few hours today figuring why the client didn't seem to be doing > anything and just kept hanging. In my opinion not throwing an exception in > this situation is a bug. The server should do that and report that the client > is trying to use the wrong protocol instead of just hanging without doing > anything. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
