[ http://jira.jboss.com/jira/browse/JBAS-1495?page=history ]
Scott M Stark closed JBAS-1495:
-------------------------------
Resolution: Done
Fix Version: JBossAS-4.0.2 Final
JBossAS-3.2.8 Final
This is caused by the ejb proxy optimization issue described in the linked to
JBAS-1442 issue. There is a testcase for cross server ejb calls that verifies
jndi lookups and ejb calls between servers are working.
> Looking up a session bean on one server from within another in JBoss 3.2.7
> --------------------------------------------------------------------------
>
> Key: JBAS-1495
> URL: http://jira.jboss.com/jira/browse/JBAS-1495
> Project: JBoss Application Server
> Type: Bug
> Components: EJBs, Naming
> Versions: JBossAS-3.2.7 Final
> Environment: Windows or Linux, x86, JBoss 3.2.7
> Reporter: Matt Lee
> Assignee: Scott M Stark
> Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
>
> We have processes within once instance of JBoss that need to access session
> beans in a remote instance of JBoss.
> We just upgraded from 3.2.3 to 3.2.7 and JNDI lookups to remote servers
> stopped working. The funny thing is that there are no exceptions, but the
> JNDI lookup always returns a reference to a local bean. I always put in the
> java.naming.provider.url property for the InitialContext and if i put in the
> name of my local server it all works. When i put in the name of a remote
> server i get a bean on the local server.
> This all works fine from a normal client, but when the code inside JBoss
> tries to be the client it does not work.
> We didn't change any code for the upgrade or any of the deployment
> descriptors so if there is something we can do to resolve the remote
> references I would love to hear it.
> Also, if I pass in a bogus server name, i do get an error that it could not
> connect, so it is doing something correctly.
> Reverting to 3.2.6 solves the problem
> As advised on the forums, i tried setting "jnp.disableDiscovery=true" in the
> environment without success.
--
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
