jboss-jira February 2007

jboss-jira@lists.jboss.org

15 participants
2194 discussions

[JBoss JIRA] Reopened: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=all ] Ovidiu Feodorov reopened JBMESSAGING-410: ----------------------------------------- Reopening the issue, as Messaging-layer level changes required to fix [url]http://jira.jboss.org/jira/browse/JBMESSAGING-721[/url] will modify again the behavior described here. The changes will be made public in 1.0.1.SP4 and 1.2.0.CR1. The way an XASession behaves in absence of a JTA transaction is incompletely specified, so it is inevitable that different implemenation would work differently. Ultimately, it's up to the JCA layer, not the JMS layer, to enforce a certain behavior. For more discussions on the subject, please also read [url]http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98577[/url]. The issue will stay open until after the 1.2.0.GA release, when we will have more time to experiment with controversial subjects like this. > java:/JmsXA in no-tx context does not work the same way as JBossMQ > ------------------------------------------------------------------ > > Key: JBMESSAGING-410 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410 > Project: JBoss Messaging > Issue Type: Bug > Components: Configuration and Management > Affects Versions: 1.0.1.CR2 > Reporter: Elias Ross > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.0.1.CR5 > > > The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory. > Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility. > The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced. > QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA"); > ... > QueueConnection queueConnection = queueCF.createQueueConnection(); > QueueSession queueSession = > queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE); > QueueSender queueSender = queueSession.createSender(queue); > ObjectMessage om = queueSession.createObjectMessage(); > queueSender.send(om); > queueSender.close(); > queueSession.close(); > queueConnection.close(); -- 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
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-214) goddamn keyword collisions damn it damn damn

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-214?page=comments#action_12352051 ] Michael Neale commented on JBRULES-214: --------------------------------------- Kudos for solving this Edson ! > goddamn keyword collisions damn it damn damn > -------------------------------------------- > > Key: JBRULES-214 > URL: http://jira.jboss.com/jira/browse/JBRULES-214 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Priority: Critical > Fix For: 3.1-m3 > > > Getting more complaints about collisions with keywords. Things like "end" are obvious, but even "duration" etc... > Parser possibly needs to be a bit cleverer (not sure why duration is barfing.. but anyway). > I guess the only clear way forward is to enforce newline characters. > Most often the problem happens in the LHS. On the RHS its just "end" that is a 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

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-340) Update getting started guide

by Mark Little (JIRA)

Update getting started guide ---------------------------- Key: JBESB-340 URL: http://jira.jboss.com/jira/browse/JBESB-340 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.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

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-637) Replace ListBox in MetaData widget as it can't be tweaked visually or behaviorally

by Michael Neale (JIRA)

Replace ListBox in MetaData widget as it can't be tweaked visually or behaviorally ---------------------------------------------------------------------------------- Key: JBRULES-637 URL: http://jira.jboss.com/jira/browse/JBRULES-637 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
1
0 / 0

← Newer
1
...
217
218
219
220
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007