[jboss-jira] [JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment
[
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
Naming context read-only during SAR deployment
----------------------------------------------
Key: AS7-5584
URL: https://issues.jboss.org/browse/AS7-5584
Project: Application Server 7
Issue Type: Bug
Components: POJO
Affects Versions: 7.1.1.Final
Reporter: Philippe Marschall
During the #start() #stop() method of a legacy SAR the naming context is read only. The
problem seems to be that
{{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the
thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}}
http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi...
--
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