[jboss-jira] [JBoss JIRA] Commented: (JBAS-7588) Investigate org.jboss.test.ejb.lifecycle.test failures

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12509423#action_12509423 ] 

Brian Stansberry commented on JBAS-7588:
----------------------------------------

Ok, so this ties in to the general problem of moving jboss:service=WebServer out of conf/jboss-service.xml and into deploy/. See http://community.jboss.org/thread/146133 for a partial discussion. The trick to the whole thing is java.rmi.server.RMIClassLoaderSpi and java.rmi.server.codebase have to be set before anything binds anything into JNDI, because the bind operation creates a javax.rmi.MarshalledObject, which triggers the one-time-only read of these properties that Adrian alludes to.

A semi-elegant fix is to move LocalNamingBean to deploy and establish correct dependencies. This causes difficulties for any deployer that directly binds stuff in JNDI. Surmountable difficulties, but difficulties. The question is whether to do that, or just hack something for M2 pending ProfileService work in M3 that AIUI is going to make the whole conf/jboss-service.xml, deployers/, deploy/ distinction obsolete.

My plan was to decide on that next week, once all the component upgrades for M2 are done. I've got a bunch of M2 JIRAs assigned to me related to this. A month ago I worked through and tested how to move everything into deploy, it's mostly a matter of checking whether M2 actually *has* deployers that directly bind stuff in JNDI and then making a go/no-go decision. There were some in the plans a month ago, but last I checked they weren't actually implemented.

Moving jboss:service=WebServer back into conf/jboss-service.xml won't work without ugly hacking. It depends on David Lloyd's threads stuff, which in turn depends on deployers/jboss-threads.deployer.

Jaikiran, feel free to assign this JIRA to me, unless your r100158 is sufficient to fix the test; otherwise it's just part of the overall work. Thanks for your help on this.

> Investigate org.jboss.test.ejb.lifecycle.test failures
> ------------------------------------------------------
>
>                 Key: JBAS-7588
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7588
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira