[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
2:02 p.m.
Hot deployment : You are trying to use a connection factory that has been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
When using war exploded deployment and invoke "explode" ant target to hot deploy
components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
3:04 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Bernard Labno commented on JBSEAM-3844:
---------------------------------------
I propose following code in Initialization.redeploy :
for (String name : Contexts.getApplicationContext().getNames()) {
if (name.endsWith(Initialization.COMPONENT_SUFFIX)) {
try {
Component instance = (Component) Component.getInstance(name);
if (EntityManagerFactory.class.equals(instance.getBeanClass())) {
((EntityManagerFactory)
Component.getInstance(instance.getName())).startup(instance);
Contexts.removeFromAllContexts(instance.getName());
}
} catch (ClassCastException ex) {
}
}
}
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
1:40 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Bernard Labno updated JBSEAM-3844:
----------------------------------
Attachment: Initialization.java.patch
Proposed patch. Tested with "test" target.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Attachments: Initialization.java.patch
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
1:11 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3844:
------------------------------
Fix Version/s: 2.1.2.CR1
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.1.2.CR1
Attachments: Initialization.java.patch
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
12:05 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Bernard Labno updated JBSEAM-3844:
----------------------------------
Attachment: stacktrace.txt
Provided patch is wrong !!! I overlooked the fact that EntityManagerFactory component
would be recreated on every page load, so no data will get into database. There is a need
to check if it is connected to the right datasource instance (an open one). It is not
enough to check with isOpen() method for it returns true and the stacktrace says "You
are trying to use a connection factory that has been shut down: ManagedConnectionFactory
is null." .
And I don't know how to get to the ManagedConnectionFactory. My workaround for now is
to create copy of "explode" ant task but remove "datasource" task from
depends attribute.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.1.2.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
4:05 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
nmatrix nmatrix commented on JBSEAM-3844:
-----------------------------------------
Has any progress been made on this issue? I'm using JBoss Developer Studio Version:
2.0.0.CR2 and I'm still encountering this exact same issue.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
8:27 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Christian Bauer updated JBSEAM-3844:
------------------------------------
Comment: was deleted
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
1:13 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-3844:
-----------------------------------
This was a problem in seam-gen. In the generated project, the datasource Ant target was
copying the -ds.xml file with overwrite="true". That would cause the database
connection pool to be restarted and therefore leave the EntityManagerFactory dead in the
water. The correct approach is to not allow the datasource to be swapped.
Granted, if you are running in production and you want to swap the datasource, then Seam
needs to accomodate that. So for cases when you really do intend to reset the connection
pool, I think Seam should detect this situation and rebuild the EntityManagerFactory.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
1:13 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-3844:
-----------------------------------
...but please note that this is NOT part of redeploy. If you a redeploying, then the
EntityManagerFactory is already getting kicked and there is nothing that needs to be done.
The fix needs to be for Seam to detect a change in the datasource while the application is
running.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
6:10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Cody Lerum commented on JBSEAM-3844:
------------------------------------
Am I correct in assuming that changing
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
tofile="${deploy.dir}/${project.name}-ds.xml"
overwrite="true"/>
</target>
to
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
tofile="${deploy.dir}/${project.name}-ds.xml"
overwrite="false"/>
</target>
will fix the issue as long as I'm not changing editing a datasource?
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
11:59 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Bernard Labno commented on JBSEAM-3844:
---------------------------------------
I add a copy of "explode" target and remove "datasource" from
"depends" attribute :
<target name="explode" depends="stage,datasource"
description="Deploy the exploded archive">
<fail unless="jboss.home">jboss.home not set</fail>
<mkdir dir="${war.deploy.dir}"/>
<copy todir="${war.deploy.dir}">
<fileset dir="${war.dir}"/>
</copy>
</target>
<target name="quick-explode" depends="stage"
description="Deploy the exploded archive">
<fail unless="jboss.home">jboss.home not set</fail>
<mkdir dir="${war.deploy.dir}"/>
<copy todir="${war.deploy.dir}">
<fileset dir="${war.dir}"/>
</copy>
</target>
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.0.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
2:26 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Sherif Mansour commented on JBSEAM-3844:
----------------------------------------
Thanks for posting Bernard, been troubleshooting this issue for a few days now. It would
be great to get the datasource target to not overwrite by default.. save a bit of
headaches.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Fix For: 2.2.1.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
5:43 p.m.
New subject: [JBoss JIRA] Assigned: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Marek Novotny reassigned JBSEAM-3844:
-------------------------------------
Assignee: Marek Novotny
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Assignee: Marek Novotny
Fix For: 2.2.1.CR1
Attachments: Initialization.java.patch, stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
10:23 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Marek Novotny updated JBSEAM-3844:
----------------------------------
Attachment: (was: Initialization.java.patch)
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Assignee: Marek Novotny
Fix For: 2.2.1.CR1
Attachments: stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
4:51 p.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down
[
https://jira.jboss.org/jira/browse/JBSEAM-3844?page=com.atlassian.jira.pl...
]
Marek Novotny closed JBSEAM-3844.
---------------------------------
Resolution: Out of Date
the overwrite attribute in copy task in seam-gen build scripts was removed by another
commit.
Hot deployment : You are trying to use a connection factory that has
been shut down
-----------------------------------------------------------------------------------
Key: JBSEAM-3844
URL: https://jira.jboss.org/jira/browse/JBSEAM-3844
Project: Seam
Issue Type: Bug
Components: Hot Deploy
Affects Versions: 2.1.1.CR2
Reporter: Bernard Labno
Assignee: Marek Novotny
Fix For: 2.2.1.CR1
Attachments: stacktrace.txt
When using war exploded deployment and invoke "explode" ant target to hot
deploy components (even if there is no changes) I get this error :
Caused by: javax.resource.ResourceException: You are trying to use a connection factory
that has been shut down: ManagedConnectionFactory is null.
As I've inspected the problem is that javax.persistence.EntityManagerFactory changes
and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot
deployment.
2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name
'java:seamcourseDatasource'
2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name
'java:seamcourseDatasource'
I think that Initialization.redeploy method needs to be updated to reinitialize all
EntityManagerFactory instances but I'm not sure and need confirmation from experienced
seam dev.
--
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
5349
days inactive
5757
days old
14 comments
8 participants
participants (8)
-
Bernard Labno (JIRA) -
Christian Bauer (JIRA)
-
Cody Lerum (JIRA)
-
Dan Allen (JIRA)
-
Marek Novotny (JIRA)
-
nmatrix nmatrix (JIRA)
-
Pete Muir (JIRA)
-
Sherif Mansour (JIRA)