June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-539) FLUSH: incorrect set of messages after flush

by Bela Ban (JIRA)

FLUSH: incorrect set of messages after flush -------------------------------------------- Key: JGRP-539 URL: http://jira.jboss.com/jira/browse/JGRP-539 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.5 MultiplexerTest.testVirtualSynchrony() creates 2 MuxChannels, then sends 10 messages to each (so each should have 20 messages total). The Channel.startFlush() is called, after 5 secs stopFlush() is called automatically. This returns true, an indication that flush succeeded. However - we see messages being received *after* flush has run - we do not have the same and correct number of elements in both channels -- 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, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBAOP-429) Dispatcher register & unregister don't check state

by Carlo de Wolf (JIRA)

Dispatcher register & unregister don't check state -------------------------------------------------- Key: JBAOP-429 URL: http://jira.jboss.com/jira/browse/JBAOP-429 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Environment: snapshot-20070625 Reporter: Carlo de Wolf It's possible to register two different targets using the same oid. The second register should throw an IllegalStateException. It's possible to unregister an non-existing target, unregister should throw an IllegalStateException. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-539) events on cancel, suspend, resume

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-539?page=all ] Tom Baeyens updated JBPM-539: ----------------------------- Fix Version/s: jBPM jPDL 3.2.2 (was: jBPM jPDL 3.2.1) > events on cancel, suspend, resume > --------------------------------- > > Key: JBPM-539 > URL: http://jira.jboss.com/jira/browse/JBPM-539 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: James Depoorter > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.2 > > > Events on cancel, suspend and resume should be available. > Preferably a "beforeXYZ" and "afterXYZ" -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-752) Rule deployment module

by Michael Neale (JIRA)

Rule deployment module ---------------------- Key: JBRULES-752 URL: http://jira.jboss.com/jira/browse/JBRULES-752 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-534) Transient multiplexer unit test failures

by Vladimir Blagojevic (JIRA)

Transient multiplexer unit test failures ---------------------------------------- Key: JGRP-534 URL: http://jira.jboss.com/jira/browse/JGRP-534 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.5 MulitplexerTest#testReplicationWithTwoChannels unit test fails if bundling is disabled or if thread pool queue is disabled. In addition MultiplexerViewTest fails as well from time to time. After we have enabled bundling (default setting) these failures disappeared (at least on Windows XP and JDK 1.5). We will continue to investigate causes of these transient failures. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Commented: (JBAS-3364) Support PROPAGATION_NESTED in JTA implementation

by Yegor Yenikyeyev (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3364?page=comments#action_12366616 ] Yegor Yenikyeyev commented on JBAS-3364: ---------------------------------------- Thanks for the explanation, Mark! It looks pretty fair to me but what we were really trying to do (when i posted the issue) is just a nested JDBC transaction (which i believe JDBC 3.0 compliant and nested tx-aware) using the same datasource. The original issue was that I discovered a kind of deadlock of wrapping and nested transactions on an object in L2 cache (and this seems to be fixed in 1.4.x). Then i discovered this issue when i dug into details. As for me it looks like commit for nested tx (f2) is not being performed at all. > Support PROPAGATION_NESTED in JTA implementation > ------------------------------------------------ > > Key: JBAS-3364 > URL: http://jira.jboss.com/jira/browse/JBAS-3364 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Yegor Yenikyeyev > > Is it possible to support nested JTA transactions in one of upcoming version? For this moment i see the following in TxManager.java > if (current != null) > { > if (current.isDone()) > disassociateThread(ti); > else > throw new NotSupportedException > ("Transaction already active, cannot nest transactions."); > } -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-935) Update DrlDumper to handle with the new language features

by Fernando Meyer (JIRA)

Update DrlDumper to handle with the new language features --------------------------------------------------------- Key: JBRULES-935 URL: http://jira.jboss.com/jira/browse/JBRULES-935 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR2 Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (GPD-105) revision of the task container configuration form

by Koen Aers (JIRA)

revision of the task container configuration form ------------------------------------------------- Key: GPD-105 URL: http://jira.jboss.com/jira/browse/GPD-105 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0.alpha4 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-3364) Support PROPAGATION_NESTED in JTA implementation

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3364?page=comments#action_12366596 ] Mark Little commented on JBAS-3364: ----------------------------------- In order to support nested transactions you need a nested transaction-aware coordinator and nested transaction-aware participants. The latter is pretty critical because what a participant does when it's told to commit in a nested transaction is completely different to a top-level transaction. Such participants are tailored for the backend datasource. JBossTS provides a nested transaction-aware coordinator and some nested transaction-aware participants. Take a look at the TS manuals (Core Transaction Engine) and you'll see. However, XA doesn't support nested transactions. And while JTA doesn't prevent them, JEE does not allow them for this reason. It's a strange situation to be in, I know! There's no way you can support true nested transactions with XA, so JTA should really be fixed. JBossTS continues to support nested transactions through JTA because you can register non-XA resources with our JTA transactions through other APIs. But as far as TS is concerned it's doing as much as it can. The rest is up to the datasource providers: implement nested transaction participants and this should just work (tm). > Support PROPAGATION_NESTED in JTA implementation > ------------------------------------------------ > > Key: JBAS-3364 > URL: http://jira.jboss.com/jira/browse/JBAS-3364 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Yegor Yenikyeyev > > Is it possible to support nested JTA transactions in one of upcoming version? For this moment i see the following in TxManager.java > if (current != null) > { > if (current.isDone()) > disassociateThread(ti); > else > throw new NotSupportedException > ("Transaction already active, cannot nest transactions."); > } -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-880) Update XML component to handle with 4.0 language changes

by Fernando Meyer (JIRA)

Update XML component to handle with 4.0 language changes -------------------------------------------------------- Key: JBRULES-880 URL: http://jira.jboss.com/jira/browse/JBRULES-880 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: xml Affects Versions: 4.0.0.MR2, 3.1-m1 Reporter: Fernando Meyer Assigned To: Fernando Meyer Priority: Critical - Change XSD schema to validate 4.0 features - Update xml parser to handle with these new features. -- 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, 1 month

1
1
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 June 2007