March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-10) Training Material

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-10?page=all ] Ovidiu Feodorov updated JBMESSAGING-10: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Training Material > ----------------- > > Key: JBMESSAGING-10 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-10 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Documentation and Training > Reporter: Ivelin Ivanov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-116) Create a 'messaging' configuration in jboss-head

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-116?page=all ] Ovidiu Feodorov updated JBMESSAGING-116: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Create a 'messaging' configuration in jboss-head > ------------------------------------------------ > > Key: JBMESSAGING-116 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-116 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Affects Versions: 1.0.0 alpha PR2 (clustered) > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > > Update jboss-head/build/build.xml partition-build to create a "messaging" configuration. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-147) Make jms local transactions in doubt

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-147?page=all ] Ovidiu Feodorov updated JBMESSAGING-147: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Make jms local transactions in doubt > ------------------------------------ > > Key: JBMESSAGING-147 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-147 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > When 2PC is used, jms server "transactions" (i.e. not JTA transactions - internal server side tx) can be left "hanging" in prepared state by badly behaved or crashed clients. > However we don't want to remove them since we do not know that recovery will not occur in the future therefore we should flag them as in doubt so the administrator can come in and deal with them heuristically -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-378) Use memory leak detection within the testsuite

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-378?page=all ] Ovidiu Feodorov updated JBMESSAGING-378: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Use memory leak detection within the testsuite > ---------------------------------------------- > > Key: JBMESSAGING-378 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-378 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 2 minutes > Remaining Estimate: 2 minutes > > Clebert's stuff. -- 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
0
0 / 0

[JBoss JIRA] Updated: (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 updated JBMESSAGING-410: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) (was: 1.0.1.CR5) > 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, 1.2.0.Beta2, 1.0.1.SP4 > Reporter: Elias Ross > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: Unscheduled > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-309) Rename createXXXDelegate methods

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-309?page=all ] Ovidiu Feodorov updated JBMESSAGING-309: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Rename createXXXDelegate methods > -------------------------------- > > Key: JBMESSAGING-309 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-309 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Rename createXXXDelegate methods in ServerXXEndpoint classes to createXXXEndpoint, since they create endpoints, not delegates. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-211) Destination programmatic deployment example/integration test

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-211?page=all ] Ovidiu Feodorov updated JBMESSAGING-211: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Destination programmatic deployment example/integration test > ------------------------------------------------------------ > > Key: JBMESSAGING-211 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-211 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Optional > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Write the corresponing docs/example/programmatic-deployment integration 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-218) Persistent services are very noisy in the logs when the table(s) they are trying to create already exists

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-218?page=all ] Ovidiu Feodorov updated JBMESSAGING-218: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Persistent services are very noisy in the logs when the table(s) they are trying to create already exists > --------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-218 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-218 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core Persistence > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > JDBCDurableSubscriptionStore, JDBCMessageStore, JDBCTransactionLog try to create their corresponding tables during their inialization procedure and litter the logs with SQLException stack traces if the corresponding tables exist: > java.sql.SQLException: Table already exists: TRANSACTION in statement [CREATE TABLE TRANSACTION] > at org.hsqldb.jdbc.Util.sqlException(Util.java:61) > at org.hsqldb.jdbc.jdbcStatement.fetchResult(jdbcStatement.java:1580) > ..... > Use a less noisy way to insure the tables exist. Swallowing the SQLException is not a solution, since it may signal other problems with the database. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-210) ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-210?page=all ] Ovidiu Feodorov updated JBMESSAGING-210: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal > ---------------------------------------------------------------------- > > Key: JBMESSAGING-210 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-210 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > ServerPeer.createTopic(...)/createQueue(...) are JMX managed operations that allow to programatically create a JMS destination. The implementation is suboptimal in that it parses a literal representation of an destination MBean configuration and deploys the resulted org.w3c.dom.Element. It also accesses directly ServiceCreator and UnifiedClassLoader3 interfaces. Review the implementation. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-321) Use lock free queues for JDK1.5

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-321?page=all ] Ovidiu Feodorov updated JBMESSAGING-321: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Use lock free queues for JDK1.5 > ------------------------------- > > Key: JBMESSAGING-321 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-321 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > JDK1.5 concurrent classes utilise processor Compare and Swap (CAS) instructions to allow wait free (lock free) data struictures to be created. > We could detect whether the user is running JDK1.5 and use non blocking synchronization in our queues. Should improve concurrency. -- 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
0
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