[ http://jira.jboss.com/jira/browse/JBESB-1751?page=all ] Work on JBESB-1751 started by Tom Fennelly. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1751?page=all ] Kevin Conner reopened JBESB-1751: --------------------------------- -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1751?page=comments#action_12413279 ] Kevin Conner commented on JBESB-1751: ------------------------------------- RegistryFactory appears to be the part which is broken. It is repeatedly creating the registry and is not thread safe. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1751?page=comments#action_12413307 ] Tom Fennelly commented on JBESB-1751: ------------------------------------- That's very interesting Kev.... I pointed this out to you before (about the RegistryFactory repeatedly creating the Reg instance) and you disregarded the suggestion that this was not right, saying it was the responsibility of the deployer to do it - end of story.... not a matter of opinion etc etc etc ;-) This is why I didn't make the change there lol Anyway... why is it needed... because, as you said rightly in your follow up comment... if it's not initialised, it repeatedly creates the registry instance. Why is this an issue for Standalone and not AS/ESB deployments, because as stated above, the deployers in ESB/AS perform the initialiation (in exactly the same way as I've added it to the Standalone). If it's not intitialised... the InVM transport breaks because it uses an invm registry. I'll reassign to yourself and you can fix it the "right" way ;-) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1751?page=comments#action_12413314 ] Kevin Conner commented on JBESB-1751: ------------------------------------- ROFL, that's what I get for typing before I have had my morning coffee :) never -> ever ;) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1751?page=comments#action_12413315 ] Kevin Conner commented on JBESB-1751: ------------------------------------- "The reason for the change is that the InVM EPRs did not work correctly when running within the StandAloneBootStrapper as the registry is being recreated every time." Will leave this for now and sort out the registry in 4.4. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira