We reverted to 3.2.6 and all is well. I can make calls to remote beans from within jboss again.
The following item in the 3.2.7RC1 change log looks suspicious: http://sourceforge.net/docman/display_doc.php?docid=25427&group_id=22866 anonymous wrote : JNDI/Naming | | * - Update parseNameForScheme to make a copy of the input name if its being modified due to a schema prefix. The modified name is stored in the Hashtable env under the key jnp.parsedName. This fixes a problem with external names being modified by the Context calls. - Update the MulticastSocket used for discover to use the InitialContext env jnp.localAddress if defined to control the interface the broadcast is sent out on. | o naming/src/main/org/jnp/interfaces/NamingContext.java | o naming/src/main/org/jnp/interfaces/NamingContextFactory.java | This is workable for us, but it would be nice to know what the problem is. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867017#3867017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867017 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
