[JBoss JIRA] Created: (EJBTHREE-1097) InitialContextFactory doesn't always create a new InitialContext
11:05 a.m.
InitialContextFactory doesn't always create a new InitialContext
----------------------------------------------------------------
Key: EJBTHREE-1097
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.2.GA
Reporter: Carlo de Wolf
InitialContextFactory is not really a factory, it doesn't always create a new
InitialContext.
This can lead to interesting situations if someone closes an InitialContext which
doesn't have any properties and then tries to reuse it.
--
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
5:01 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1097) InitialContextFactory doesn't always create a new InitialContext
[ http://jira.jboss.com/jira/browse/EJBTHREE-1097?page=comments#action_1241... ]
Pavel Kadlec commented on EJBTHREE-1097:
----------------------------------------
I have encountered this issue as well when deploying my ear.
During deploying org.jboss.ejb3.mdb.MDB.getJMSProviderAdapter() closes "shared"
intialContext that is used by eg. org.jboss.ejb3.entity.PersistenceUnitDeployment.
org.jboss.ejb3.entity.PersistenceUnitDeployment.start then crashes with
javax.naming.NoInitialContextException: Need to specify class name in environment or
system property, or as an applet parameter, or in an application resource file:
java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:216)
InitialContextFactory doesn't always create a new InitialContext
----------------------------------------------------------------
Key: EJBTHREE-1097
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.2.GA
Reporter: Carlo de Wolf
InitialContextFactory is not really a factory, it doesn't always create a new
InitialContext.
This can lead to interesting situations if someone closes an InitialContext which
doesn't have any properties and then tries to reuse it.
--
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
5:34 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1097) InitialContextFactory doesn't always create a new InitialContext
[ http://jira.jboss.com/jira/browse/EJBTHREE-1097?page=comments#action_1241... ]
Pavel Kadlec commented on EJBTHREE-1097:
----------------------------------------
Sorry, I did not noticed that my behaviour is discussed in JBAS-5049.
InitialContextFactory doesn't always create a new InitialContext
----------------------------------------------------------------
Key: EJBTHREE-1097
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.2.GA
Reporter: Carlo de Wolf
InitialContextFactory is not really a factory, it doesn't always create a new
InitialContext.
This can lead to interesting situations if someone closes an InitialContext which
doesn't have any properties and then tries to reuse it.
--
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
6061
days inactive
6282
days old
2 comments
2 participants
participants (2)
-
Carlo de Wolf (JIRA) -
Pavel Kadlec (JIRA)