[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
10:30 a.m.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session
state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Priority: Blocker
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:06 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer updated JBSEAM-4388:
------------------------------------
Priority: Minor (was: Blocker)
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:42 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer reassigned JBSEAM-4388:
---------------------------------------
Assignee: Christian Bauer
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4388:
-----------------------------------------
Preserving state across restarts is definitely not supported for Javabean components in
Session or Conversation context (deserialization occurs too early for the Seam contexts to
be active, and we need the HttpSessionActivationListener for clustering). So if your
components are Javabeans, I'm wondering how you even get to the CNFE.
I'm not sure this would work with EJB components, I haven't tried. Are your
components EJBs?
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:21 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
David Thompson commented on JBSEAM-4388:
----------------------------------------
Yes, we are using JavaBean components not EJB. Our Credentials and Identity which are
scoped at SESSION actually do preserve state across restarts. If I take any of my beans
and scope them at session they will survive restarts. Its only beans at the conversation
context that then make things ugly.
Sorry I don't know more about how JBoss starts up, to help troubleshoot this more.
Would it help if I tried this behavior out with one of the seam examples to see if I get
the same behavior?
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:39 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4388:
-----------------------------------------
So the problem is the following:
A Seam JavaBean component in the HTTP session (SESSION or CONVERSATION scoped) gets
serialized to be stored in a file as the HTTP session is serialized.
When the serialized state is read during redeploy, which is the first thing that happens
after a restart, Tomcat calls the HttpSessionActivationListener methods that have been
transparently applied to any Seam JavaBean component by the Seam proxy factory.
This fails because no Seam context is active at that time, Seam will be started right
after the reactivation of the session state by a servlet listener, which is too late for
any method call on the deserialized component.
It works for the Credentials and Identity components because they are annotated with
@BypassInterceptor, which means that no Seam context is required when a method is called
(including the proxy-added methods of HttpSessionActivationListener). So they can be
stored in a file and restored before Seam starts just fine. Any component that does not
disable the Seam interceptors can't.
My issue is that I can't even reproduce your CNFE because I'm already getting a
"no context is active" exception when my SESSION scoped bean without
@BypassInterceptors is being deserialized before Seam starts again (sessionDidActivate()
is one of the listener methods added by the proxy to the Javabean):
[ScannerThread] 00:29:22,437 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy,
ctxPath=/skeleton, warUrl=.../deploy/skeleton.war/
[ScannerThread] 00:29:22,649 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/skeleton]] Session
attribute event listener threw exception
java.lang.IllegalStateException: Attempted to invoke a Seam component outside an
initialized application
at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36)
at org.jboss.seam.contexts.Lifecycle.setupApplication(Lifecycle.java:134)
at org.jboss.seam.Seam.componentForName(Seam.java:301)
at
org.jboss.seam.intercept.RootInterceptor.getComponent(RootInterceptor.java:226)
at
org.jboss.seam.intercept.JavaBeanInterceptor.callPostActivate(JavaBeanInterceptor.java:164)
at
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:73)
at
my.skeleton.example.model.Test_$$_javassist_seam_0.sessionDidActivate(Test_$$_javassist_seam_0.java)
That's why I'd say this has never been supported at all because I can't see
how it would ever work with the current code.
You need to show me how to get past that exception and to get the CNFE, preferably by
attaching/explaining your code and what component in what deployment environment exactly
is throwing that exception.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:58 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4388:
-----------------------------------------
Note: I'm testing this on JBoss 4.2.3.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:38 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4388:
-----------------------------------------
Testing with a plain and empty seam-gen WAR project on JBoss 5.1 we already have a failure
for Drools deserializaton:
15:35:37,431 ERROR [ManagerBase] Exception loading sessions from persistent storage
java.io.EOFException
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
at
org.drools.common.DroolsObjectInputStream.<init>(DroolsObjectInputStream.java:55)
at
org.drools.common.DroolsObjectInputStream.<init>(DroolsObjectInputStream.java:49)
at org.drools.common.AbstractRuleBase.readExternal(AbstractRuleBase.java:232)
at org.drools.reteoo.ReteooRuleBase.readExternal(ReteooRuleBase.java:179)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1443)
at
org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:942)
at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:394)
at org.apache.catalina.session.StandardManager.load(StandardManager.java:321)
at org.apache.catalina.session.StandardManager.start(StandardManager.java:637)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4402)
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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
9:14 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4388:
-----------------------------------------
After removing drools, everything works as expected in JBoss 5.1. (Surprisingly, probably
HttpSessionActivationListener is called later by this newer Tomcat.)
Create a WAR seam-gen project, create this action:
@Name("Test")
@Scope(ScopeType.CONVERSATION)
public class Test implements Serializable
{
@Logger private Log log;
@In StatusMessages statusMessages;
String foo;
@Begin(join = true)
public void test()
{
// implement your business logic here
log.info("Test.test() action called");
statusMessages.add("test");
}
// add additional action methods
public String getFoo() {
return foo;
}
public void setFoo(String foo) {
this.foo = foo;
}
}
Create a form on an XHTML page that uses a long-running conversation. Fill out the form to
create the state, call 'ant redeploy', reload the page with the same conversation
identifier, state is available.
Please try to reproduce your issue with a fresh seam-gen WAR project.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:10 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
David Thompson commented on JBSEAM-4388:
----------------------------------------
Christian,
Sorry for the delay on this.
I went through all the steps you suggest to create a brand new project, then removed the
drools stuff, and added the class as you mentioned. I then downloaded a brand new fresh
copy of /home/dthompson/jboss-5.1.0.GA-jdk6.zip and installed it. Then went into
server/default/deploy/jbossweb.sar and changed the Manager pathname to be SESSIONS.ser.
Got everything all setup. Started up jboss and then deployed the project to the server.
Application is up and running. I login as Admin (make sure the app works). Fine. Then I
run test.seam and click the button and the conversation starts (can see it in the debug
page.
ant redeploy
And I still get the error, the top of the stack trace looks like:
10:06:43,344 ERROR [ManagerBase] ClassNotFoundException while loading persisted sessions:
java.lang.ClassNotFoundException: org.safmt.TestProject.action.Test
java.lang.ClassNotFoundException: org.safmt.TestProject.action.Test
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Same thing as before.
I'm running on Ubuntu using Java 6. I can send you the TestProject zipped up if you
think that would help.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Christian Bauer
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:56 a.m.
New subject: [JBoss JIRA] Assigned: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
Christian Bauer reassigned JBSEAM-4388:
---------------------------------------
Assignee: Dan Allen (was: Christian Bauer)
Dan, I'm assigning this to you. I'm not sure we need to do much for Seam 2.x but
we definitely should have an automated test early on for Seam 3.x which would check
session persistence across restarts on our appservers.
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Dan Allen
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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:11 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
[
https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.pl...
]
David Thompson commented on JBSEAM-4388:
----------------------------------------
Wanted to add here that I just tried to see if this would work with glassfish.
Unfortunately, the problem also exists there. If I take the project and get it deployed on
glassfish, run the same test I did before in JBoss. Shutdown glassfish (which should save
the persistent state) and the restart it, I see the error very similar to that in JBoss
shown below:
Exception loading sessions from persistent storage java.lang.ClassNotFoundException:
org.safmt.TestProject.action.Test at
com.sun.appserv.server.util.ASURLClassLoader.loadClass(ASURLClassLoader.java:129) at
java.lang.ClassLoader.loadClass(ClassLoader.java:252) at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at
java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at
java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:604) at
org.apache.catalina.util.CustomObjectInputStream.resolveClass(CustomObjectInputStream.java:116)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575) at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at
org.apache.catalina.session.StandardSession.readRemainingObject(StandardSession.java:1926)
at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1834) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849) at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at
org.apache.catalina.session.StandardSession.deserialize(StandardSession.java:1174) at
org.apache.catalina.session.StandardManager.readSessions(StandardManager.java:515) at
org.apache.catalina.session.StandardManager.doLoadFromFile(StandardManager.java:447) at
org.apache.catalina.session.StandardManager.load(StandardManager.java:417) at
org.apache.catalina.session.StandardManager.start(StandardManager.java:859) at
org.apache.catalina.core.StandardContext.managerStart(StandardContext.java:4994) at
org.apache.catalina.core.StandardContext.start(StandardContext.java:5311) at
com.sun.enterprise.web.WebModule.start(WebModule.java:345) at
com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58) at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304) at
com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176) at
com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192) at
com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1762) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1244) at
org.apache.catalina.core.StandardHost.start(StandardHost.java:971) at
com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58) at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304) at
com.sun.appserv.management.util.misc.RunnableBase.run(RunnableBase.java:341) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at
java.util.concurrent.FutureTask.run(FutureTask.java:138) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at
java.lang.Thread.run(Thread.java:619)
Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail
loading session state
--------------------------------------------------------------------------------------
Key: JBSEAM-4388
URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA
Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot
deploy.
Reporter: David Thompson
Assignee: Dan Allen
Priority: Minor
We currently write struts apps. One of the things we do is hot deploy these apps by
setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when
an app is deployed with "ant deploy", the session data can be stored out--app is
torn down-- then when new app deploys the session data restores.
If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the
Conversation Context when the app is deployed, then JBoss throws an error trying to reload
the component and no SESSION data is restored. For example, all logged in users (data
stored in Identity or Credentials) do not restore so all users get the boot. This
doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy
to our production system, this causes problems for us.
The ideal solution, would be to have the conversations to come back to life, but we could
also live with the conversations not being reestablished--but we really need the other
session data (such as login credentials) to live through the deploy.
AFAIK, I have looked all over the web and read the seam reference as well as Seam In
Action and can't find any information about how Conversations can persist over a
session (such as a redeploy this way) or over a cluster.
--
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
5515
days inactive
5620
days old
11 comments
2 participants
participants (2)
-
Christian Bauer (JIRA) -
David Thompson (JIRA)