March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-520) Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary.

by Joel Lindheimer (JIRA)

Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary. ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-520 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-520 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows XP, JBossServer4.0.4GA, Oracle10G Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Create a simple receiver, but do not place it within a Transaction boundary; shut down the server; look up the tables and you will see all the messages are still in the Messages and MessageRef tables. ========================================= Observations using a debbuger reveal the following: ========================================= Looking over the org.jboss.resource.adapter.jms.JmsManagedConnection the setup method will always call createXAQueueSession() and create an XAQueconnection as transacted and Session.SESSION_TRANSACTED. That being the case, non-XA Queues have no message-deletion problems with the current version (RC4) because the API removes all messages that are "not transacted and (!ack==1). I am guessing that using XA is problematic because the persistence layer is expecting manipulation of the transacted XASession--which for some reason is not working in this version of Messaging. More specifically, I suspect that when MDBs are tested you are not seeing this problem because the container is doing needed magic to manage the XASession transacted state, and therefore everything works fine therein. And consequently, when operating as a non-MDB client, AKA a simple Receiver, there is something missing in the equation ergo the problems that I have been reporting regarding the ClickCommerce applications which use Receivers and not MDBs. Work-around: None; the strategy for my team is to NOT use an XAQueueConnection while waiting for a fix. -- 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

5
11
0 / 0

[JBoss JIRA] Created: (JBBUILD-351) Boolean.parseBoolean() not replaced with a JDK 1.4 compat method

by Manik Surtani (JIRA)

Boolean.parseBoolean() not replaced with a JDK 1.4 compat method ---------------------------------------------------------------- Key: JBBUILD-351 URL: http://jira.jboss.com/jira/browse/JBBUILD-351 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Environment: This bug exists in JBossRetro-1.0.4.GA Reporter: Manik Surtani Assigned To: Paul Gier http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Boolean.html#parseBoole... should be replaced with http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Boolean.html#valueOf(ja... and then converting the resulting Boolean object into a primitive. -- 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: (JBPORTAL-1262) Look into optimizing the memory usage during the upload archive usecase.

by Sohil Shah (JIRA)

Look into optimizing the memory usage during the upload archive usecase. ------------------------------------------------------------------------- Key: JBPORTAL-1262 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1262 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6 Final Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6 Final This is particularly when uploading big archives 50MB or more. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1193) Do-not-modify-URL-option for URLs in the WYSIWYG editor

by Nils Kassube (JIRA)

Do-not-modify-URL-option for URLs in the WYSIWYG editor ------------------------------------------------------- Key: JBPORTAL-1193 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1193 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final, 2.6.DR1 Reporter: Nils Kassube Assigned To: Roy Russo I'd like to have a "Do not modify URL" checkbox. So the URL is not munged in any way. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1212) Fine Grained CMS permissions not accurately enforced in a clustered environment

by Sohil Shah (JIRA)

Fine Grained CMS permissions not accurately enforced in a clustered environment ------------------------------------------------------------------------------- Key: JBPORTAL-1212 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1212 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.Beta1 Problem Explanation: Due to issues with JackRabbit internal caching, the PortalCMS Service is setup as a HA-Singleton service in a clustered environment. One side effect is that, when PortalCMS calls are made from nodes other than the singleton node, the User Principal is not propagated through the Singleton Proxy. Hence, the call is treated as an "Anoymous" user call instead of the currently "Logged In" User. Note: This is not an issue in a non-clustered environment -- 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] Created: (JBBUILD-349) Create archetype for JBoss projects

by Paul Gier (JIRA)

Create archetype for JBoss projects ----------------------------------- Key: JBBUILD-349 URL: http://jira.jboss.com/jira/browse/JBBUILD-349 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Fix For: MavenBuild 1.2 Maven includes archetypes that can be used for creating a default pom.xml. An archetype should be created for the JBoss projects. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-837) Write a JBoss Messaging Best Practices Guide

by Ovidiu Feodorov (JIRA)

Write a JBoss Messaging Best Practices Guide -------------------------------------------- Key: JBMESSAGING-837 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-837 Project: JBoss Messaging Issue Type: Feature Request Components: Documentation and Training Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.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

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-584) Eliminate jgroups.jar "processing"

by Ovidiu Feodorov (JIRA)

Eliminate jgroups.jar "processing" ---------------------------------- Key: JBMESSAGING-584 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-584 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.CR1 During the release procedure, the current release script expands jgroups.jar and removes service deployment descriptos (gossip-service.xml multiplexer-service.xml). It has just been confirmed by the JGroups team that the presence of those deployment descriptors is not intentional, it's just an unwanted artifact of their release process. Get rid of "jgroups jar processing" as soon as we upgrade our dependency to a "clean" jgroups jar. -- 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: (JBMESSAGING-905) org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose() fails on Linux

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose() fails on Linux ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-905 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-905 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.GA junit.framework.AssertionFailedError at org.jboss.test.messaging.jms.clustering.FailoverValveTest.testConcurrentClose(FailoverValveTest.java:287) -- 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: (JBMESSAGING-438) Allow ports used by JBossMessaging to be mapped using ServiceBindingManager

by Tim Fox (JIRA)

Allow ports used by JBossMessaging to be mapped using ServiceBindingManager --------------------------------------------------------------------------- Key: JBMESSAGING-438 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-438 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.GA -- 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

4
12
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 March 2007