[JBoss JIRA] Created: (EJBTHREE-659) SFSB throws exception with second passivation
by Ben Wang (JIRA)
SFSB throws exception with second passivation
---------------------------------------------
Key: EJBTHREE-659
URL: http://jira.jboss.com/jira/browse/EJBTHREE-659
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: EJB 3.0 RC9 - FD
I have created a test case to illustrate this for both SimpleStatefulCache and StatefulTreeCache, NestedBeanUnitTestCase (cache and clusteredsession). Basically, if we do this:
bean.getXXX
sleep(10000); // to passivate
bean.getXXX; // to acitvate
sleep(10000); // to passivate again
This will produce:
2006-07-24 04:46:59,358 ERROR [org.jboss.ejb3.cache.simple.SimpleStatefulCache] problem passivation thread^M
javax.ejb.EJBException: Could not passivate; failed to save state^M
at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:363)^M
at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196)^M
at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129)^M
Caused by: java.lang.NullPointerException^M
at org.jboss.serial.util.StringUtil.calculateUTFSize(StringUtil.java:319)^M
at org.jboss.serial.util.StringUtil.saveString(StringUtil.java:63)^M
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeUTF(DataContainer.java:265)^M
at org.jboss.ejb3.stateful.StatefulBeanContextReference.writeExternal(StatefulBeanContextReference.java:65)^M
at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58)^M
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275)^M
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:197)^M
at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181)^M
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287)^M
at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:347)^M
... 2 more^M
This is caused by a bug from ProxiedStatefuleBeanContext serialization where we dont serialiaze parentRef if it is not null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Created: (JBPM-714) packaging just the webapp takes way to long
by Ronald van Kuijk (JIRA)
packaging just the webapp takes way to long
-------------------------------------------
Key: JBPM-714
URL: http://jira.jboss.com/jira/browse/JBPM-714
Project: JBoss jBPM
Issue Type: Feature Request
Affects Versions: jBPM 3.2 alpha 1
Environment: Eclipse 3.2, gpd 3.0.11, jdk 1.5 windhoos
Reporter: Ronald van Kuijk
Assigned To: Tom Baeyens
Fix For: jBPM 3.2
Packaging just the webapp takes 13 seconds. In this time the 'global' compile is used. This results in packaging jbpm-jpdl.jar twice and copying it to the repository twice.
This should be optimised in combination with a 'deploy' target which deploys it to a configured location.
Even better would be if it is a real WTP web (sub?) project which can have things like 'auto deployment' small updates to .xhtml files available immediately, etc....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Created: (JBMESSAGING-437) Non durable subscription optimization
by Tim Fox (JIRA)
Non durable subscription optimization
-------------------------------------
Key: JBMESSAGING-437
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-437
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.0.1.CR3
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.0.2
Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs.
Basically I think we can acknowledge them before they are sent from server to client.
This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks.
On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver.
This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months