April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-949) jboss-messaging-1.2.0.sp1 continually tries to create tables on startup

by Tom Cunningham (JIRA)

jboss-messaging-1.2.0.sp1 continually tries to create tables on startup ----------------------------------------------------------------------- Key: JBMESSAGING-949 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-949 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.SP1 Environment: Mac OS X 10.4.9, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Tim Fox After deploying jbossmessaging, I see SQLExceptions for create table statements, indexes, and a unique constraint violation on a test insert into JBM_USER. Steps to reproduce: - Install a fresh jboss-4.0.5.GA w/ejb3 - Set JBOSS_HOME environment variable to point to the new JBoss installation - Go to the util directory in jboss-messaging-1.2.0.sp1 - ant -f release-admin.xml - Start JBoss - Shutdown JBoss - Start JBoss - watch for exceptions in server/messaging/log/server.log 2007-04-27 12:29:18,589 DEBUG [org.jboss.messaging.core.plugin.JDBCSupport] Failed to execute: CREATE TABLE JBM_MSG_REF (CHANNEL_ID BIGINT, MESSAGE_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY(CHANNEL_ID, MESSAGE_ID)) java.sql.SQLException: Table already exists: JBM_MSG_REF in statement [CREATE TABLE JBM_MSG_REF] at org.hsqldb.jdbc.Util.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source) at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:186) at org.jboss.messaging.core.plugin.JDBCSupport.createSchema(JDBCSupport.java:230) at org.jboss.messaging.core.plugin.JDBCSupport.start(JDBCSupport.java:156) at org.jboss.messaging.core.plugin.JDBCPersistenceManager.start(JDBCPersistenceManager.java:123) at org.jboss.messaging.core.plugin.JDBCPersistenceManagerService.startService(JDBCPersistenceManagerService.java:88) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy39.start(Unknown Source) at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:613) -- 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
1
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-342) Functional tests bundled with the release should be functional

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-342?page=all ] Tim Fox updated JBMESSAGING-342: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Priority: Minor (was: Major) > Functional tests bundled with the release should be functional > -------------------------------------------------------------- > > Key: JBMESSAGING-342 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-342 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1.CR1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The functional tests whose source code comes with the release should be compilable and runnable, so they can validate the release at unpacking. -- 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] Commented: (JBMESSAGING-353) ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows

by Aaron Walker (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-353?page=comments#action_12... ] Aaron Walker commented on JBMESSAGING-353: ------------------------------------------ I will retest this on both my G4 Powerbook and Macbook Pro and let you know > ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows > ----------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-353 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-353 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade, Tests and Performance > Affects Versions: 1.0.0, 1.0.1.CR1 > Environment: mac osx 10.4.6 > JDK 1.4.2_09 > JDK 1.5.0_04 > Reporter: Aaron Walker > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: messaging-tests.trace.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The testRedeliveryTransacted fail with the following: > 1) testRedeliveryTransacted(org.jboss.test.messaging.jms.ConnectionConsumerTest)junit.framework.AssertionFailedError: Didn't receive correct messages > at org.jboss.test.messaging.jms.ConnectionConsumerTest.testRedeliveryTransacted(ConnectionConsumerTest.java:224) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58) > The issue revolves around the sess.rollback around line 433 in that after the rollback and the 3 messages get redelivered and on the 3rd message the following if (!tm.getJMSRedelivered()) at line 481 evaluates to true in that the getJMSRedelivered() is false when it should be true. By placing a 1ms sleep just prior to the rollback you can get the test to pass. So after my initial investigation It appears that it may be some sort of threading issue that shows up on my mac. > I will attached the TRACE log for this If you look at line 765 of the log it shows that the delivery count for the message is 0 when it should be 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-186) Get rid of all TODOs and FIXMEs from the code

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Tim Fox updated JBMESSAGING-186: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Assignee: Tim Fox > Get rid of all TODOs and FIXMEs from the code > --------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.1.CR1 > > -- 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-186) Check that all TODOs and FIXMEs correspond to known JIRA tasks

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Tim Fox updated JBMESSAGING-186: -------------------------------- Summary: Check that all TODOs and FIXMEs correspond to known JIRA tasks (was: Get rid of all TODOs and FIXMEs from the code) Description: .. and if not, create appropriate JIRA tasks. > Check that all TODOs and FIXMEs correspond to known JIRA tasks > -------------------------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.1.CR1 > > > .. and if not, create appropriate JIRA tasks. -- 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-375) Grouping of messages with JMSXGroupId

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Tim Fox updated JBMESSAGING-375: -------------------------------- Fix Version/s: 2.0.0 CR1 (was: Unscheduled) > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 CR1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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-314) Ensure Messaging core has no dependencies on the JMS facade

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ] Tim Fox updated JBMESSAGING-314: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Ensure Messaging core has no dependencies on the JMS facade > ----------------------------------------------------------- > > Key: JBMESSAGING-314 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Messaging core still has some dependencies on the jms facade. These should be factored out. -- 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-406) Enable file based persistent stores

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ] Tim Fox updated JBMESSAGING-406: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) Also Berkely DB and stuff implemented by RHM > Enable file based persistent stores > ----------------------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > > Implement non shared file based persistent store. > Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this. > Also look at HOWL. http://howl.objectweb.org/ -- 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-322) Deploying an MDB for a destination that doesn't exist fails.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-322?page=all ] Tim Fox updated JBMESSAGING-322: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Deploying an MDB for a destination that doesn't exist fails. > ------------------------------------------------------------ > > Key: JBMESSAGING-322 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-322 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Fix For: 1.2.1.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the destination an MDB is configured with doesn't exist, the MDB Container's JMSContainerInvoker tries to create the destination and fails because uses a non-portable interface that only works with JBossMQ. > Line 1201, org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination() > // invoke the server to create the destination > server.invoke(new ObjectName("jboss.mq:service=DestinationManager"), ..... > -- 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-373) Different persistance destinations for different JMS destinations

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ] Tim Fox updated JBMESSAGING-373: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Different persistance destinations for different JMS destinations > ----------------------------------------------------------------- > > Key: JBMESSAGING-373 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373 > Project: JBoss Messaging > Issue Type: Feature Request > Affects Versions: 1.0.0, 1.0.1.CR1 > Reporter: Milena > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > We need to store the messages from different queues into a different tables, ot at least to separate them somehow. > This is not possible with the current JBOSS Messaging as I was told. > The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging. -- 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 April 2007