[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:
-------------------------------------
Ok thx Aaron. It's hard to find Mac users these days :)
> 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: Aaron Walker
> 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, 3 months
[JBoss JIRA] Assigned: (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 reassigned JBMESSAGING-353:
-----------------------------------
Assignee: Aaron Walker (was: Tim Fox)
> 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: Aaron Walker
> 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, 3 months
[JBoss JIRA] Created: (JBPORTAL-1370) gracefully handle error during wsrp consumer creation
by Prabhat Jha (JIRA)
gracefully handle error during wsrp consumer creation
-----------------------------------------------------
Key: JBPORTAL-1370
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1370
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.CR2
Reporter: Prabhat Jha
Assigned To: Chris Laprun
When a consumer name is blank, create consumer action takes you to HTTP Status 500 error page. It should gracefully handle the error and show a friendly message. As expected, server log has java.lang.IllegalArgumentException: createConsumer requires a non-null, non-empty Consumer identifier
at org.jboss.portal.common.util.ParameterValidation.throwIllegalArgExceptionIfNullOrEmpty(ParameterValidation.java:36)throwsn
--
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, 3 months
[JBoss JIRA] Created: (JBCACHE-1040) Update JBC User User Guide
by Joseph Marques (JIRA)
Update JBC User User Guide
--------------------------
Key: JBCACHE-1040
URL: http://jira.jboss.com/jira/browse/JBCACHE-1040
Project: JBoss Cache
Issue Type: Patch
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Joseph Marques
Assigned To: Joseph Marques
Fix For: 2.0.0.CR2
To do:
* Add visuals to far cache pattern library wiki - http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClusteringPatternsLibrary
** Update "Using Cache Loaders" section to reference it
* Minor updates/clarifications to replication section
* Add initial info for a new "Replication or Invalidation?" section - this may or may not fly, but I thought it might be a nice way to help initial users better understand under what conditions it's better to use one over the other
* Fix TreeCacheArchitecture image, which appears to be invisible in the pdf version of the doc
* Rewrite "full and partial state transfer" section so that the chronology of the steps surrounding partial state transfer for region activation are more easily understood
* Minor addendums to 'strategies' section of 'cacheloaders' chapter
* New eviction regions sub-section to discuss the algorithm for overlapping regions
--
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, 3 months
[JBoss JIRA] Closed: (JBRULES-41) Enhance no-loop functionality
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-41?page=all ]
Edson Tirelli closed JBRULES-41.
--------------------------------
Fix Version/s: 3.1-m2
(was: 3.1-m3)
Resolution: Done
This was fixed by Mark already.
> Enhance no-loop functionality
> -----------------------------
>
> Key: JBRULES-41
> URL: http://jira.jboss.com/jira/browse/JBRULES-41
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rule Assemply/SPI
> Affects Versions: 3.0-beta1
> Reporter: Michael Neale
> Assigned To: Edson Tirelli
> Fix For: 3.1-m2
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> At present, no-loop is simply limited to stopping a rule firing itself with the same facts.
> A common request I get, whenever visiting anyone, is how to remember all rule activations (rule/fact combinations that have fired in the past) and stop the same happening in the future in a single instance of working memory.
> This can be an option set on a per instance, or per haps per-file basis. By default it must be off, as it will require extra memory to record the history, and I don't think it would be suitable for long lived working memories.
> However, for the pseudo "stateless" pattern (which probably 70-80% of people use) it would be quite safe and beneficial.
--
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, 3 months