April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-312) Refactor persistencemanager

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ] Tim Fox updated JBMESSAGING-312: -------------------------------- Summary: Refactor persistencemanager (was: De-monolithise persistencemanager) Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Refactor persistencemanager > --------------------------- > > Key: JBMESSAGING-312 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Refactor PersistenceManager to make less monolithic. > The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store. > Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState. > The TransactionCallback should be removed to it's own java file. > The locking operations should occur in the caller. > There should be an abstraction PMTxContext which can be passed into PM operations to group them. > This should dramatically clarify and simplify things -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-353) ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-353?page=all ] Tim Fox updated JBMESSAGING-353: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows > ----------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-353 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-353 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade, Tests and Performance > Affects Versions: 1.0.0, 1.0.1.CR1 > Environment: mac osx 10.4.6 > JDK 1.4.2_09 > JDK 1.5.0_04 > Reporter: Aaron Walker > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: messaging-tests.trace.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The testRedeliveryTransacted fail with the following: > 1) testRedeliveryTransacted(org.jboss.test.messaging.jms.ConnectionConsumerTest)junit.framework.AssertionFailedError: Didn't receive correct messages > at org.jboss.test.messaging.jms.ConnectionConsumerTest.testRedeliveryTransacted(ConnectionConsumerTest.java:224) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58) > The issue revolves around the sess.rollback around line 433 in that after the rollback and the 3 messages get redelivered and on the 3rd message the following if (!tm.getJMSRedelivered()) at line 481 evaluates to true in that the getJMSRedelivered() is false when it should be true. By placing a 1ms sleep just prior to the rollback you can get the test to pass. So after my initial investigation It appears that it may be some sort of threading issue that shows up on my mac. > I will attached the TRACE log for this If you look at line 765 of the log it shows that the delivery count for the message is 0 when it should be 1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-377) Competing consumer on subscriptions

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ] Tim Fox updated JBMESSAGING-377: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Competing consumer on subscriptions > ----------------------------------- > > Key: JBMESSAGING-377 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-353) ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-353?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-353: ------------------------------------- We need to get hold of a Mac and retest this - I suspect the problem no longer occurs since the delivery code has completely changed since then. > ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows > ----------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-353 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-353 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade, Tests and Performance > Affects Versions: 1.0.0, 1.0.1.CR1 > Environment: mac osx 10.4.6 > JDK 1.4.2_09 > JDK 1.5.0_04 > Reporter: Aaron Walker > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: messaging-tests.trace.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The testRedeliveryTransacted fail with the following: > 1) testRedeliveryTransacted(org.jboss.test.messaging.jms.ConnectionConsumerTest)junit.framework.AssertionFailedError: Didn't receive correct messages > at org.jboss.test.messaging.jms.ConnectionConsumerTest.testRedeliveryTransacted(ConnectionConsumerTest.java:224) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58) > The issue revolves around the sess.rollback around line 433 in that after the rollback and the 3 messages get redelivered and on the 3rd message the following if (!tm.getJMSRedelivered()) at line 481 evaluates to true in that the getJMSRedelivered() is false when it should be true. By placing a 1ms sleep just prior to the rollback you can get the test to pass. So after my initial investigation It appears that it may be some sort of threading issue that shows up on my mac. > I will attached the TRACE log for this If you look at line 765 of the log it shows that the delivery count for the message is 0 when it should be 1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-728) Clustering touch ups

by Ovidiu Feodorov (JIRA)

Clustering touch ups -------------------- Key: JBMESSAGING-728 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-728 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (GPD-55) Description support on node elements

by Koen Aers (JIRA)

Description support on node elements ------------------------------------ Key: GPD-55 URL: http://jira.jboss.com/jira/browse/GPD-55 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM JPDL Designer 3.1.0.alpha2 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-58) Delegation configuration does not always show the right controls

by Koen Aers (JIRA)

Delegation configuration does not always show the right controls ---------------------------------------------------------------- Key: GPD-58 URL: http://jira.jboss.com/jira/browse/GPD-58 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-42) Add script configuration on fork

by Koen Aers (JIRA)

Add script configuration on fork -------------------------------- Key: GPD-42 URL: http://jira.jboss.com/jira/browse/GPD-42 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-21) Add support for the process-state

by Koen Aers (JIRA)

Add support for the process-state --------------------------------- Key: GPD-21 URL: http://jira.jboss.com/jira/browse/GPD-21 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha2 Basic support is already provided. What still needs to be added is a way to configure. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-365) Cannot send messages to a destination configured with a security role other than "guest", using UsersRolesLoginModule

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-365?page=all ] Tim Fox updated JBMESSAGING-365: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Cannot send messages to a destination configured with a security role other than "guest", using UsersRolesLoginModule > --------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-365 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-365 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Security > Affects Versions: 1.0.0 > Environment: Windows 2000, JDK 1.4.1_05 > Reporter: Oliver Hernandez > Fix For: 1.2.1.CR1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > A JMS client errors out with the following when a queue is configured with a security role other than "guest": > 2006-04-28 14:33:42,313 WARN [outbound] An exception occurred on the server side when making remote invocation. The exception returned from server does not include a stack trace. Original server side exception message is User jms is NOT authenticated > javax.jms.JMSSecurityException: User jms is NOT authenticated > Messaging is configured to use UsersRolesLoginModule. See forum post for details on reproducing the problem. -- 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, 2 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 April 2007