January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-740) Make sure wireformat is just right

by Tim Fox (JIRA)

Make sure wireformat is just right ---------------------------------- Key: JBMESSAGING-740 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-740 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 We need to get the wireformat exactly right before the 1.2 release since changing it aftwerwards is going to give compatibility issues. We should analyse it and make sure it is exactly correct. Suggestion would be to provide a custom wire format for all invocations, not just the few we currently have so we don't rely on java/jboss serialization. Also wireformat for ping -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-721) Message redelivery doesn't work

by Amit Bhayani (JIRA)

Message redelivery doesn't work -------------------------------- Key: JBMESSAGING-721 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-721 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.SP2 Reporter: Amit Bhayani Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.0.2.CR1 Attachments: mdb.zip Message redelivery in CMT MDB is not working. I set the transaction to setRollbackOnly on MessageDrivenContext within onMessage of MDB and ideally the message should get redelivered. I can see that Message reamins in the queue for long time. No error message is shown in server.log file. I have created a simple testcase (attached here). Sender.java send's 6 messages. Messages 1,2,3,4 and 5 are consumed however for message 6 MDBExample.java sets the setRollbackOnly after this there is no activity and message 6 remains in the queue. This testcase is from jboss-messaging-1.0.1.SP2-src\docs\examples\mdb. Just replace the files to test. -- 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, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-638) Potential memory leak when using 2pc via JCA adapter.

by Tim Fox (JIRA)

Potential memory leak when using 2pc via JCA adapter. ----------------------------------------------------- Key: JBMESSAGING-638 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-638 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.2.CR1 Martin Welss has reported a potential memory leak when using 2pc via the JCA adaptor. It seems that client side TxState instances remain in the resource manager. Need to investigate further. -- 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, 5 months

2
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-963) Eviction thread timer is not a daemon

by Brian Stansberry (JIRA)

Eviction thread timer is not a daemon ------------------------------------- Key: JBCACHE-963 URL: http://jira.jboss.com/jira/browse/JBCACHE-963 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.GA, 1.2.4SP2, 1.2.4, 1.4.1.SP1 Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 The Timer used for the eviction thread needs to have true passed to it's constructor, otherwise it prevents shutdown of the application if stopService() is not invoked. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-773) isLocalInterceptor will invoke local bean when the proxy is remote

by William DeCoste (JIRA)

isLocalInterceptor will invoke local bean when the proxy is remote ------------------------------------------------------------------ Key: EJBTHREE-773 URL: http://jira.jboss.com/jira/browse/EJBTHREE-773 Project: EJB 3.0 Issue Type: Bug Reporter: William DeCoste Assigned To: William DeCoste IsLocalInterceptor checks to see if the container is local based on the OID (e.g. jboss.j2ee:jar=stateless-test.jar,name=CheckedStatelessBean,service=EJB3) via Ejb3Registry.getContainer(oid.toString()). If the bean is deployed identically to the local and remote server and the proxy is remote, the call will still be handled locally. Checking the Ejb3Registry doesn't work in this case. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-270) JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages

by Tom Fennelly (JIRA)

JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages ------------------------------------------------------------------------------------------------------------------ Key: JBESB-270 URL: http://jira.jboss.com/jira/browse/JBESB-270 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 RC1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 5.0 This listener receives messages from a JMS queue and spawns a new thread for the ActionProcessingPipeline instance that is created to process the message. If you hammer this listener with messages (e.g 20 concurrent threads continually pumping messages into the in queue), you'll kill the process through running out of threads to process the messages. The listener should manage the Threads. Use of a Threadpool would probably take care of this for you i.e. can probably get the pool to block while waiting for a free thread to be returned to the pool. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-791) Duplicates clientIDs are not throwing InvalidClientIDException

by Clebert Suconic (JIRA)

Duplicates clientIDs are not throwing InvalidClientIDException -------------------------------------------------------------- Key: JBMESSAGING-791 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-791 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP2, 1.0.1.SP3, 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1, 1.0.1.SP4 -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3784) derby-jdbc2-service.xml not updated to jboss 4.x

by ppc (JIRA)

derby-jdbc2-service.xml not updated to jboss 4.x ------------------------------------------------ Key: JBAS-3784 URL: http://jira.jboss.com/jira/browse/JBAS-3784 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: ppc the file doc/examples/jms/derby-jdbc2-service.xml containt the follow line <depends optional-attribute-name="ConnectionManager">jboss.jca:service=LocalTxCM,name=....</depends> that is applicable to jboss 3.x instead <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=...</depends> according to http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB this errors comes also when form the webstart installer you choose derby as default datasource instead hipersonic. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3785) Syntax Error in derby-jdbc2-service.xml

by ppc (JIRA)

Syntax Error in derby-jdbc2-service.xml --------------------------------------- Key: JBAS-3785 URL: http://jira.jboss.com/jira/browse/JBAS-3785 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: ppc Assigned To: Adrian Brock in the line DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE EXITS (SELECT JMS_TRANSACTIONS.TXID FROM JMS_TRANSACTIONS \ WHERE JMS_TRANSACTIONS.TXID = JMS_MESSAGES.TXID) \ AND JMS_MESSAGES.TXOP = ? there's a syntax error on EXITS istead EXISTS -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-929) MRU eviction algorithm test failures

by Manik Surtani (JIRA)

MRU eviction algorithm test failures ------------------------------------ Key: JBCACHE-929 URL: http://jira.jboss.com/jira/browse/JBCACHE-929 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1, 2.0.0.ALPHA2 Reporter: Manik Surtani Assigned To: Daniel Huang Fix For: 2.0.0.BETA1 org.jboss.cache.eviction.MRUAlgorithmTest in CVS HEAD fails. -- 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, 5 months

1
3
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 January 2007