[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] Philippe Marschall updated AS7-5584: ------------------------------------ Component/s: JMX (was: Naming) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] kknd22 commented on AS7-5584: ----------------------------- Thanks for the quick fix. I posted on the following on the original discussion as well.... 22. Sep 24, 2012 1:09 PM (in response to Philippe Marschall) Re: JBoss7 JNDI Thanks for the quick turn around and fix. I manually apply the temp fix on the local source code of the base source 7.1.1.Final. JNDI binding start to work now! However, it only work up till 7 bindings. Whenever we go 8 entries of jndi or above, the deployment hangs (ctrl-c can stop the server either). Through the debugger and thread dump, it indicated that the wait was on org.jboss.as.naming.WritableServiceBasedNamingStore public void bind(final Name name, final Object object) throws NamingException { .... builder.install(); try { listener.await(); } ..... Any idea why 8 is such magic number? Is it that I did not apply the patch correctly or we might just discover another defect? Thanks -Chris -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] kknd22 commented on AS7-5584: ----------------------------- The start method simply return right after doing the jndi bind: public void start() throws Exception { System.out.println("\n\n================================start: " + __count++ + ", " + _jndiName + "\n\n"); _object = createObject (); bind (_jndiName); _started = true; System.out.println("\n\n================================START DONE: " + _jndiName + "\n\n"); } protected void bind (String jndiName) throws NamingException { InitialContext rootCtx = new InitialContext (); Name fullName = rootCtx.getNameParser ("").parse (jndiName); if (_serializable) { createSubcontext (rootCtx, fullName.getPrefix (fullName.size () - 1)); rootCtx.bind (fullName, _object); } else { NonSerializableFactory.rebind (fullName, _object, true); } } I used the debugger to verify it did return. For 7 jdni, I observed that all "===start:" fan out and then all "====START DONE:" came back. For over 8 jndi entries, seeing 8 ""===start:" fan out then it hangs indefinitely. BTW, through debugger, I was able to chase down the magic number 8: class org.jboss.msc.service.ServiceContainerImpl: ServiceContainerImpl(String name, int coreSize, long timeOut, TimeUnit timeOutUnit) // -- at runtime coreSize is 8. I have the feeling that 8 might not be the issue. The issue seems to be each fan out thread is blocked until the all service jndi binding have been submitted. If the entry size is bigger than 8 then it will block forever. Now I am looking at class org.jboss.as.naming.WritableServiceBasedNamingStore private class BindListener extends AbstractServiceListener<Object> { ... } BTW, anyway to configure the coreSize 8 to a bigger number for the time being? Thanks -Chris -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-5584: ------------------------------------- I have merged this in master, and created a 7.1 PR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira