1:49 p.m.
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:49 p.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2076:
------------------------------
Fix Version/s: 7.1.0.Beta1
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:06 p.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2076:
------------------------------
Description:
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
was:
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:16 a.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
Short term solution is to make container managed entity manager wrapper classes not
serializable (ExtendedEntityManager is currently serializable).
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 a.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
I'm still investigating and learning about this issue. I created
https://hibernate.onjira.com/browse/HHH-6727 based on my perception that its important for
this jira.
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 p.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
Since this issue is related to clustering/replication of the extended persistence context,
I'm entering some notes on that here. For clustering support, I'm thinking of
including the SFSBXPCMap related data, in the ExtendedEntityManager serialization
payload.
This would be controlled by a JPA hook (SPI) that clustering could call into on the thread
performing the serialization. This might use a ThreadLocal, so a call before/after
serialization would be expected. This might be used for optimizing the payload size as
well (for the case when multiple SFSBs reference the same XPC mentioned here
http://community.jboss.org/docs/DOC-13822).
It might be easier to transfer the SFSBXPCMap data if we use a UUID to identify the XPC
instance. The organization would probably change from:
private ConcurrentHashMap<SFSBContextHandle, List<EntityManager>>
contextToXPCMap =
new ConcurrentHashMap<SFSBContextHandle, List<EntityManager>>();
private ConcurrentHashMap<EntityManager, List<SFSBContextHandle>>
XPCToContextMap =
new ConcurrentHashMap<EntityManager, List<SFSBContextHandle>>();
To:
private ConcurrentHashMap<SFSBContextHandle, List<EntityManagerUUID>>
contextToXPCMap =
new ConcurrentHashMap<SFSBContextHandle, List<EntityManagerUUID>>();
private ConcurrentHashMap<EntityManagerUUID, List<SFSBContextHandle>>
XPCToContextMap =
new ConcurrentHashMap<EntityManagerUUID, List<SFSBContextHandle>>();
A UUID to EntityManager Map will be needed as well (and kept up to date after replication,
XPC creation/destroy).
This impacts how we do passivation/activation...
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:09 a.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
When the EJB3 container passivates an extended persistence context, all of the SFSBs that
reference the extended persistence context will also need to be passivated.
I mentioned needing some SPI above for clustering. I think that the EJB3 container will
probably also need to use the SPI. I'm thinking of two method calls:
1. void serializeXPCStart()
2. SessionID[] serializeXPCFinish()
Where SessionID is from StatefulSessionComponentInstance.getId().
Note: perhaps SFSBPCMap could change to just storing the SessionID obtained from
StatefulSessionComponentInstance.getId().
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 p.m.
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2076:
------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
activation/passivation of extended persistence context
------------------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2076:
------------------------------
Summary: serialization of extended persistence context (was:
activation/passivation of extended persistence context)
Description:
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
was:
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support activation/passivation. SFSBXPCMap should instead reference the XPC via an
uuid (or something like that), that can be used to get the XPC (if SFSB is in activated
state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:16 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2076:
------------------------------
Priority: Blocker (was: Major)
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:05 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
Next NotSerializableException http://pastie.org/3018508 to solve
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
AS7-2076 also depends on [HHH-6897|https://hibernate.onjira.com/browse/HHH-6897]
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
HHH-6897 is also assigned to me...
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
http://pastie.org/3024597 is a classloading problem that occurs when the unit test, tries
to deserialize. We get a "java.lang.ClassNotFoundException:
org.hibernate.ejb.EntityManagerImpl from [Module "org.jboss.as.jpa:main"]
The org.hibernate.ejb.EntityManagerImpl class shouldn't be on the org.jboss.as.jpa
modules path, that is not a surprise. That class should be on the application module
class path. It seems that I need to deserialize with the application classpath.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
switched to a new branch https://github.com/scottmarlow/jboss-as/tree/cluster4
Currently, I'm hitting a classloading problem during deserialization. The TCCL is the
JPA module. I have the app module identifier and need to load the app module classloader
with it (don't know how yet). And then switch the TCCL to that.
Also need to add a new Hibernate property (hibernate.entity_manager_factory_name) for
HHH-6897 and use that same property in AS7. This will specify the EMF name, so it can be
looked up. The other part of the HHH-6897 change is defaulting the EMF name to the PU
name (which we will override with the fully application scoped PU name).
I need to investigate AS7-2703, to see if there is any work there for us.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
I simplified the code changes and will review again for other ways to reduce risk. I have
HHH-6897 working but will make one more improvement I think. I changed the interceptors
to be serializable. I just started the compliance tests locally and will see how the
results look in 12 hours or so. Looking good so far for CR1.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 a.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
test run #2 passed all of the tests (laptop overheated 50% into the first test run
yesterday).
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
The HHH-6897 code changes are looking good (to me), will see what feedback I get tomorrow.
I'm running more tests tonight.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
HHH-6897 is fixed.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow edited comment on AS7-2076 at 12/20/11 1:33 PM:
-------------------------------------------------------------
HHH-6897 is fixed (Hibernate 4.0.1.Final will include it).
was (Author: smarlow):
HHH-6897 is fixed.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:43 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2076:
-----------------------------------
After testing for JBCTS-1231 is complete tonight, should be able to request a pull of
https://github.com/scottmarlow/jboss-as/tree/cluster10 and close this jira.
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:09 p.m.
New subject: [JBoss JIRA] (AS7-2076) serialization of extended persistence context
[
https://issues.jboss.org/browse/AS7-2076?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2076:
------------------------------
Description:
Allow extended persistence context to be serialized.
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
was:
Currently, SFSBXPCMap directly references ExtendedEntityManager. ExtendedEntityManager
implements the extended persistence context (contains a direct reference of the underlying
persistence context.
To support serialization. SFSBXPCMap should instead reference the XPC via an uuid (or
something like that), that can be used to get the XPC (if SFSB is in activated state).
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
serialization of extended persistence context
---------------------------------------------
Key: AS7-2076
URL: https://issues.jboss.org/browse/AS7-2076
Project: Application Server 7
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Blocker
Fix For: 7.1.0.Final
Allow extended persistence context to be serialized.
Note EJB 3.1 specification section 4.2.1 titled Instance Passivation and Conversational
State:
"
A container must not passivate a stateful session bean with an extended persistence
context unless the
following conditions are met:[9]
* All the entities in the persistence context are serializable.
* The EntityManager is serializable.
[9] The container is not permitted to destroy a stateful session bean instance because it
does not meet these requirements.
"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4642
days inactive
4744
days old
21 comments
6 participants
participants (6)
-
Jason Greene (Updated) (JIRA) -
Scott Marlow (Commented) (JIRA)
-
Scott Marlow (Created) (JIRA)
-
Scott Marlow (Issue Comment Edited) (JIRA)
-
Scott Marlow (JIRA)
-
Scott Marlow (Updated) (JIRA)