September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2156) Patch to add expiry queue support to JBossMQ

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2156?page=all ] Adrian Brock updated JBAS-2156: ------------------------------- Comment: was deleted > Patch to add expiry queue support to JBossMQ > -------------------------------------------- > > Key: JBAS-2156 > URL: http://jira.jboss.com/jira/browse/JBAS-2156 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Elias Ross > Assigned To: Elias Ross > Attachments: expiry.diff, expiry.diff, expiry.txt, ExpiryDestinationTestCase.java > > > Added attributes "ExpiryDestination" to DestinationMBean and DestinationManagerMBean to indicate an ObjectName of queue to receive expired messages. This destination queue must be bound into JNDI when this queue starts. > The messages are copied over to this queue when expiry time is reached and the original expiration and destination is kept in the vendor parameters "JBOSS_ORIG_EXPIRATION" and "JBOSS_ORIG_DESTINATION". The same JMSMessageID is kept in the copied message. > The limitation of this is that the queue must be located on the same local JBoss server. > Another limitation is that the expired message is only removed after its copy has been added to the new destination. Ideally, the "move" would happen within a single transaction. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2156) Patch to add expiry queue support to JBossMQ

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2156?page=all ] Adrian Brock updated JBAS-2156: ------------------------------- Fix Version/s: (was: No Release) > Patch to add expiry queue support to JBossMQ > -------------------------------------------- > > Key: JBAS-2156 > URL: http://jira.jboss.com/jira/browse/JBAS-2156 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Elias Ross > Assigned To: Elias Ross > Attachments: expiry.diff, expiry.diff, expiry.txt, ExpiryDestinationTestCase.java > > > Added attributes "ExpiryDestination" to DestinationMBean and DestinationManagerMBean to indicate an ObjectName of queue to receive expired messages. This destination queue must be bound into JNDI when this queue starts. > The messages are copied over to this queue when expiry time is reached and the original expiration and destination is kept in the vendor parameters "JBOSS_ORIG_EXPIRATION" and "JBOSS_ORIG_DESTINATION". The same JMSMessageID is kept in the copied message. > The limitation of this is that the queue must be located on the same local JBoss server. > Another limitation is that the expired message is only removed after its copy has been added to the new destination. Ideally, the "move" would happen within a single transaction. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2156) Patch to add expiry queue support to JBossMQ

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2156?page=all ] Adrian Brock updated JBAS-2156: ------------------------------- Comment: was deleted > Patch to add expiry queue support to JBossMQ > -------------------------------------------- > > Key: JBAS-2156 > URL: http://jira.jboss.com/jira/browse/JBAS-2156 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Elias Ross > Assigned To: Elias Ross > Attachments: expiry.diff, expiry.diff, expiry.txt, ExpiryDestinationTestCase.java > > > Added attributes "ExpiryDestination" to DestinationMBean and DestinationManagerMBean to indicate an ObjectName of queue to receive expired messages. This destination queue must be bound into JNDI when this queue starts. > The messages are copied over to this queue when expiry time is reached and the original expiration and destination is kept in the vendor parameters "JBOSS_ORIG_EXPIRATION" and "JBOSS_ORIG_DESTINATION". The same JMSMessageID is kept in the copied message. > The limitation of this is that the queue must be located on the same local JBoss server. > Another limitation is that the expired message is only removed after its copy has been added to the new destination. Ideally, the "move" would happen within a single transaction. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2150) Disable automatic JBossMQ destination construction

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2150?page=all ] Adrian Brock closed JBAS-2150. ------------------------------ Fix Version/s: JBossAS-5.0.0.Beta (was: No Release) Resolution: Done Assignee: Adrian Brock This was done a while ago in JBoss5. > Disable automatic JBossMQ destination construction > -------------------------------------------------- > > Key: JBAS-2150 > URL: http://jira.jboss.com/jira/browse/JBAS-2150 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Adrian Brock > Assigned To: Adrian Brock > Fix For: JBossAS-5.0.0.Beta > > > The automatic construction of JBossMQ destination construction is not portable > and confuses most users when they configure things wrong. > They don't get a reasonable error message, and sometimes no error message at all. > This was made configurable in JBoss4 and should be disabled in JBoss5 > See conf/standardjboss.xml > - <CreateJBossMQDestination>true</CreateJBossMQDestination> > + <CreateJBossMQDestination>false</CreateJBossMQDestination> > The testsuite will need fixing for any MDB deployments that were using this feature > to have explicit destination deployments. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2409) EJB3 JMS Integration

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2409?page=all ] Adrian Brock reassigned JBAS-2409: ---------------------------------- Assignee: William DeCoste Assigned to Bill to update the status. > EJB3 JMS Integration > -------------------- > > Key: JBAS-2409 > URL: http://jira.jboss.com/jira/browse/JBAS-2409 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final > Reporter: Adrian Brock > Assigned To: William DeCoste > Fix For: JBossAS-4.0.6.CR1 > > > Need to determine whether the legacy JMS MDB integration using ServerSessionPools directly > needs to be refactored to cover both EJB2.1 and EJB3.0 -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2150) Disable automatic JBossMQ destination construction

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2150?page=all ] Adrian Brock updated JBAS-2150: ------------------------------- Comment: was deleted > Disable automatic JBossMQ destination construction > -------------------------------------------------- > > Key: JBAS-2150 > URL: http://jira.jboss.com/jira/browse/JBAS-2150 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Adrian Brock > Fix For: No Release > > > The automatic construction of JBossMQ destination construction is not portable > and confuses most users when they configure things wrong. > They don't get a reasonable error message, and sometimes no error message at all. > This was made configurable in JBoss4 and should be disabled in JBoss5 > See conf/standardjboss.xml > - <CreateJBossMQDestination>true</CreateJBossMQDestination> > + <CreateJBossMQDestination>false</CreateJBossMQDestination> > The testsuite will need fixing for any MDB deployments that were using this feature > to have explicit destination deployments. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3091) Session recycle bug in org.jboss.jms.asf.StdServerSession

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3091?page=all ] Adrian Brock closed JBAS-3091. ------------------------------ Fix Version/s: (was: JBossAS-4.0.6.CR1) Resolution: Won't Fix This issue is replaced by the rewrite of the session pool on the linked task. > Session recycle bug in org.jboss.jms.asf.StdServerSession > --------------------------------------------------------- > > Key: JBAS-3091 > URL: http://jira.jboss.com/jira/browse/JBAS-3091 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Roland R?z > > If a JMS provider throws an unchecked Exception out of Session.run(), the method org.jboss.jms.asf.StdServerSession.run() does recycled the Session without making a rollback on the Session before. If the next message on this recycled Session will be commited the older Message which has been already consumed from the Messaging System before when throwing the Exception will be lost. Because of the Exception this older Message has neither been rollbacked nor committed before. > To avoid this problem a Session.rollback() needs to be called before recycling it in case of any unchecked Exception. (See code snippet below!) > Possible Fix: > public void run() > { > boolean trace = log.isTraceEnabled(); > if (trace) > log.trace("running..."); > try > { > if (xaSession != null) > xaSession.run(); > else > session.run(); > } > // To avoid loosing Messages rollback the Session in case of any Exception from the JMS provider > catch (Throwable e) { > log.error("Exception occured during the Session.run(). Call Session.rollback() before recycling it.", e); > try { > if (xaSession != null) > xaSession.rollback(); > else > session.rollback(); > } > catch (JMSException ex) { > log.error("Exception occured when calling Session.rollback()", e); > } > } > finally > { > if (trace) > log.trace("recycling..."); > > recycle(); > if (trace) > log.trace("finished run"); > } > } -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2575) Hibernate usage in JBoss Messaging

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2575?page=all ] Adrian Brock closed JBAS-2575. ------------------------------ Fix Version/s: (was: JBossAS-5.0.0.Beta) Resolution: Rejected > Hibernate usage in JBoss Messaging > ---------------------------------- > > Key: JBAS-2575 > URL: http://jira.jboss.com/jira/browse/JBAS-2575 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > > Currently, JBoss Messaging is going down the path of pluggable "persistence managers" attempted by JBossMQ in order to achieve database portability. As discussed numerous times, we should introduce Hibernate here to achieve this portability rather than maintaining all this stuff for the various databases. Plus would give Messaging a much easier way to introduce some of the other benefits/features of using Hibernate (caching, 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2575) Hibernate usage in JBoss Messaging

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2575?page=all ] Adrian Brock reopened JBAS-2575: -------------------------------- > Hibernate usage in JBoss Messaging > ---------------------------------- > > Key: JBAS-2575 > URL: http://jira.jboss.com/jira/browse/JBAS-2575 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > > Currently, JBoss Messaging is going down the path of pluggable "persistence managers" attempted by JBossMQ in order to achieve database portability. As discussed numerous times, we should introduce Hibernate here to achieve this portability rather than maintaining all this stuff for the various databases. Plus would give Messaging a much easier way to introduce some of the other benefits/features of using Hibernate (caching, 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2575) Hibernate usage in JBoss Messaging

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2575?page=all ] Adrian Brock closed JBAS-2575. ------------------------------ Resolution: Rejected Steve, you need to reopen this issue in the messaging project. I cannot move this issue there since it is a subtask? > Hibernate usage in JBoss Messaging > ---------------------------------- > > Key: JBAS-2575 > URL: http://jira.jboss.com/jira/browse/JBAS-2575 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > Fix For: JBossAS-5.0.0.Beta > > > Currently, JBoss Messaging is going down the path of pluggable "persistence managers" attempted by JBossMQ in order to achieve database portability. As discussed numerous times, we should introduce Hibernate here to achieve this portability rather than maintaining all this stuff for the various databases. Plus would give Messaging a much easier way to introduce some of the other benefits/features of using Hibernate (caching, 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

19 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006