[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory leak?
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36255 ] james strachan commented on AMQ-735: I'm not sure I understand those pictures. Is the number after the types the number of instances created? If so from those pictures it seems like you've got tons of JMS Session objects (124596 of them!). Why so many JMS sessions? Those are objects your code creates and manages; so I suspect its your code not closing them down and letting them garbage collect? Whic one of the 2 programs is it you ran the profiler on? > Possible 4.0 consumer client memory leak? > - > > Key: AMQ-735 > URL: https://issues.apache.org/activemq/browse/AMQ-735 > Project: ActiveMQ > Type: Bug > Components: JMS client > Versions: 4.0 > Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator) > Reporter: Karthik Sethuraman > Priority: Critical > Attachments: activemq_735.zip, jmsmon.zip > > > On running the attached test programs (one producer on a topic, one consumer > on a topic), the consumer eventually encounters OutOfMemoryError after > receiving around 64 MB of messages). Default JVM heap size is used (64 MB). > The problem does not happen with RC2 build. > The test programs allows specification of message payloads of different > sizes and different message rates, as well number of producer/consumer > threads/instances., topics and topic connection factories, via user > environment variables. > http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-735) Possible 4.0 consumer client memory leak?
[ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36256 ] james strachan commented on AMQ-735: BTW if those numbers are not the number of instances in the JVM - which could be true (they might be hashcodes rather than instance counts) - then the pictures are not helpful - we need to know how many instances of each type there are - i.e. to find a memory leak we need to know what objects are using up all the RAM > Possible 4.0 consumer client memory leak? > - > > Key: AMQ-735 > URL: https://issues.apache.org/activemq/browse/AMQ-735 > Project: ActiveMQ > Type: Bug > Components: JMS client > Versions: 4.0 > Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator) > Reporter: Karthik Sethuraman > Priority: Critical > Attachments: activemq_735.zip, jmsmon.zip > > > On running the attached test programs (one producer on a topic, one consumer > on a topic), the consumer eventually encounters OutOfMemoryError after > receiving around 64 MB of messages). Default JVM heap size is used (64 MB). > The problem does not happen with RC2 build. > The test programs allows specification of message payloads of different > sizes and different message rates, as well number of producer/consumer > threads/instances., topics and topic connection factories, via user > environment variables. > http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-732) Infinite recovery loop.
[
https://issues.apache.org/activemq/browse/AMQ-732?page=comments#action_36257 ]
james strachan commented on AMQ-732:
Great investigation Maxim; sounds like you are on to something.
In an ideal world we'd have an automated system test which did a kill -9 on a
running broker and tested it recovers fine and so forth.
In the meantime, I wonder if you could give us a tarball of the journal files
created after a kill -9 and we can use recovery of those files as an automated
test case.
> Infinite recovery loop.
> ---
>
> Key: AMQ-732
> URL: https://issues.apache.org/activemq/browse/AMQ-732
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux RHEL 3
> Reporter: Maxim Fateev
> Assignee: Hiram Chirino
>
>
> The simplest way to reproduce the problem:
> 1. Remove storage directory.
> 2. Start broker using the following code:
> public static void main(String[] args) throws Exception {
>BrokerService broker = new BrokerService();
>broker.setPersistent(true);
>DefaultPersistenceAdapterFactory pFactory = new
> DefaultPersistenceAdapterFactory();
>pFactory.setJournalLogFiles(1);
>pFactory.setJournalLogFileSize(2048);
>broker.setPersistenceFactory(pFactory);
>broker.setUseJmx(false);
>broker.addConnector("tcp://localhost:61616");
>broker.start();
>Thread.sleep(1l);
>}
> 3. Shutdown the broker.
> 4. Start broker.
> It enters infinite loop
> [ main] BrokerService INFO
> ActiveMQ null JMS Message Broker (localhost) is starting
> [ main] BrokerService INFO For
> help or more information please see: http://incubator.apache.org/activemq/
> [ main] JDBCPersistenceAdapter INFO
> Database driver recognized: [apache_derby_embedded_jdbc_driver]
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER
> VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT,
> MSG BLOB, PRIMARY KEY ( ID ) )
> [ main] DefaultJDBCAdapter DEBUG Could
> not create JDBC tables; The message table already existed. Failure was:
> CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250),
> MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT, MSG BLOB,
> PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in
> Schema 'APP'. SQLState: X0Y32 Vendor code: 2
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS
> (MSGID_PROD,MSGID_SEQ)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL,
> CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR
> VARCHAR(250), LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID,
> SUB_NAME))
> [ main] DefaultJDBCAdapter DEBUG Could
> not create JDBC tables; The message table already existed. Failure was:
> CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, CLIENT_ID
> VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250),
> LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME))
> Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState:
> X0Y32 Vendor code: 2
> [ main] JDBCPersistenceAdapter DEBUG
> Cleaning up old messages.
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND
> EXPIRATION ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
> [ main] DefaultJDBCAdapter DEBUG Deleted
> 0 old message(s).
> [ main] JDBCPersistenceAdapter DEBUG Cleanup
> done.
> [ main] JournalPersistenceAdapter INFO Journal
> Recovery Started from: Active Journal: using 1 x 0.001953125 Megs at:
> /workplace/fateev/install/activemq-4.0-SNAPSHOT/activemq-core/activemq-data/journal
> [ main] JournalPersistenceAdapter DEBUG TRACE
> Entry: RECOVERED
> [Journal Writer] LogFileManager DEBUG
> getNextDataRecordLocation offset=53
[jira] Commented: (AMQ-732) Infinite recovery loop.
[
https://issues.apache.org/activemq/browse/AMQ-732?page=comments#action_36258 ]
james strachan commented on AMQ-732:
BTW you should be able to attach a zipped up tarball of the activemq-data
directory for a broker which can't recover and we can get it working
> Infinite recovery loop.
> ---
>
> Key: AMQ-732
> URL: https://issues.apache.org/activemq/browse/AMQ-732
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux RHEL 3
> Reporter: Maxim Fateev
> Assignee: Hiram Chirino
>
>
> The simplest way to reproduce the problem:
> 1. Remove storage directory.
> 2. Start broker using the following code:
> public static void main(String[] args) throws Exception {
>BrokerService broker = new BrokerService();
>broker.setPersistent(true);
>DefaultPersistenceAdapterFactory pFactory = new
> DefaultPersistenceAdapterFactory();
>pFactory.setJournalLogFiles(1);
>pFactory.setJournalLogFileSize(2048);
>broker.setPersistenceFactory(pFactory);
>broker.setUseJmx(false);
>broker.addConnector("tcp://localhost:61616");
>broker.start();
>Thread.sleep(1l);
>}
> 3. Shutdown the broker.
> 4. Start broker.
> It enters infinite loop
> [ main] BrokerService INFO
> ActiveMQ null JMS Message Broker (localhost) is starting
> [ main] BrokerService INFO For
> help or more information please see: http://incubator.apache.org/activemq/
> [ main] JDBCPersistenceAdapter INFO
> Database driver recognized: [apache_derby_embedded_jdbc_driver]
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER
> VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT,
> MSG BLOB, PRIMARY KEY ( ID ) )
> [ main] DefaultJDBCAdapter DEBUG Could
> not create JDBC tables; The message table already existed. Failure was:
> CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250),
> MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT, MSG BLOB,
> PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in
> Schema 'APP'. SQLState: X0Y32 Vendor code: 2
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS
> (MSGID_PROD,MSGID_SEQ)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION)
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL,
> CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR
> VARCHAR(250), LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID,
> SUB_NAME))
> [ main] DefaultJDBCAdapter DEBUG Could
> not create JDBC tables; The message table already existed. Failure was:
> CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, CLIENT_ID
> VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250),
> LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME))
> Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState:
> X0Y32 Vendor code: 2
> [ main] JDBCPersistenceAdapter DEBUG
> Cleaning up old messages.
> [ main] DefaultJDBCAdapter DEBUG
> Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND
> EXPIRATION ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
> [ main] DefaultJDBCAdapter DEBUG Deleted
> 0 old message(s).
> [ main] JDBCPersistenceAdapter DEBUG Cleanup
> done.
> [ main] JournalPersistenceAdapter INFO Journal
> Recovery Started from: Active Journal: using 1 x 0.001953125 Megs at:
> /workplace/fateev/install/activemq-4.0-SNAPSHOT/activemq-core/activemq-data/journal
> [ main] JournalPersistenceAdapter DEBUG TRACE
> Entry: RECOVERED
> [Journal Writer] LogFileManager DEBUG
> getNextDataRecordLocation offset=53
> [Journal Writer] LogFileManager DEBUG
> getNextDataRecordLocation offset=97
> [Journal Writer] LogFileManager DEBUG
> getNextDataRecordLocation overflowing into
[jira] Created: (AMQ-740) java.lang.UnsupportedOperationException thrown when creating a consumer
java.lang.UnsupportedOperationException thrown when creating a consumer --- Key: AMQ-740 URL: https://issues.apache.org/activemq/browse/AMQ-740 Project: ActiveMQ Type: Bug Versions: 4.0 Reporter: Hiram Chirino Fix For: 4.0.1, 4.1 gregw reported the following stack trace: java.lang.UnsupportedOperationException at java.util.AbstractCollection.add(AbstractCollection.java:216) at java.util.AbstractCollection.addAll(AbstractCollection.java:318) at org.apache.activemq.store.journal.JournalPersistenceAdapter.getDestinations(JournalPersistenceAdapter.java:139) at org.apache.activemq.broker.region.AbstractRegion.getInactiveDestinations(AbstractRegion.java:193) at org.apache.activemq.broker.region.TopicRegion.getInactiveDestinations(TopicRegion.java:254) at org.apache.activemq.broker.region.AbstractRegion.addConsumer(AbstractRegion.java:157) at org.apache.activemq.broker.region.TopicRegion.addConsumer(TopicRegion.java:113) at org.apache.activemq.broker.region.RegionBroker.addConsumer(RegionBroker.java:296) at org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73) at org.apache.activemq.advisory.AdvisoryBroker.addConsumer(AdvisoryBroker.java:77) at org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73) at org.apache.activemq.broker.MutableBrokerFilter.addConsumer(MutableBrokerFilter.java:86) at org.apache.activemq.broker.AbstractConnection.processAddConsumer(AbstractConnection.java:427) at org.apache.activemq.command.ConsumerInfo.visit(ConsumerInfo.java:295) at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62) at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63) at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44) at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:68) at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:73) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1131) at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:1667) at org.apache.activemq.ActiveMQMessageConsumer.(ActiveMQMessageConsumer.java:196) at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:840) at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:800) at org.apache.activemq.web.WebClient.getConsumer(WebClient.java:261) at org.apache.activemq.web.WebClient.getConsumer(WebClient.java:255) at org.apache.activemq.web.MessageListenerServlet.doPost(MessageListenerServlet.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet.java:767) at javax.servlet.http.HttpServlet.service(HttpServlet.java:860) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:423) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:966) at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:46) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:957) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:353) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:567) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:147) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:119) at org.mortbay.jetty.Server.handle(Server.java:248) at org.mortbay.jetty.HttpConnection.handlerRequest(HttpConnection.java:360) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:628) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:611) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:197) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:288) at org.mortbay.jetty.nio.SelectChannelConnector$HttpChannelEndPoint.run(SelectChannelConnector.java:805) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) -- This message is automatically generated by JIRA. - If you think
[jira] Resolved: (AMQ-740) java.lang.UnsupportedOperationException thrown when creating a consumer
[ https://issues.apache.org/activemq/browse/AMQ-740?page=all ] Hiram Chirino resolved AMQ-740: --- Resolution: Fixed Assign To: Hiram Chirino Fix applied to both 4.1 and 4.0.1 branches. > java.lang.UnsupportedOperationException thrown when creating a consumer > --- > > Key: AMQ-740 > URL: https://issues.apache.org/activemq/browse/AMQ-740 > Project: ActiveMQ > Type: Bug > Versions: 4.0 > Reporter: Hiram Chirino > Assignee: Hiram Chirino > Fix For: 4.0.1, 4.1 > > > gregw reported the following stack trace: > java.lang.UnsupportedOperationException > at java.util.AbstractCollection.add(AbstractCollection.java:216) > at java.util.AbstractCollection.addAll(AbstractCollection.java:318) > at > org.apache.activemq.store.journal.JournalPersistenceAdapter.getDestinations(JournalPersistenceAdapter.java:139) > at > org.apache.activemq.broker.region.AbstractRegion.getInactiveDestinations(AbstractRegion.java:193) > at > org.apache.activemq.broker.region.TopicRegion.getInactiveDestinations(TopicRegion.java:254) > at > org.apache.activemq.broker.region.AbstractRegion.addConsumer(AbstractRegion.java:157) > at > org.apache.activemq.broker.region.TopicRegion.addConsumer(TopicRegion.java:113) > at > org.apache.activemq.broker.region.RegionBroker.addConsumer(RegionBroker.java:296) > at > org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73) > at > org.apache.activemq.advisory.AdvisoryBroker.addConsumer(AdvisoryBroker.java:77) > at > org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73) > at > org.apache.activemq.broker.MutableBrokerFilter.addConsumer(MutableBrokerFilter.java:86) > at > org.apache.activemq.broker.AbstractConnection.processAddConsumer(AbstractConnection.java:427) > at > org.apache.activemq.command.ConsumerInfo.visit(ConsumerInfo.java:295) > at > org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201) > at > org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62) > at > org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97) > at > org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63) > at > org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76) > at > org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44) > at > org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:68) > at > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:73) > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1131) > at > org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:1667) > at > org.apache.activemq.ActiveMQMessageConsumer.(ActiveMQMessageConsumer.java:196) > at > org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:840) > at > org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:800) > at org.apache.activemq.web.WebClient.getConsumer(WebClient.java:261) > at org.apache.activemq.web.WebClient.getConsumer(WebClient.java:255) > at > org.apache.activemq.web.MessageListenerServlet.doPost(MessageListenerServlet.java:142) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:767) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:860) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:423) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:966) > at > org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:46) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:957) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:353) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:567) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:147) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:126) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:119) > at org.mortbay.jetty.Server.handle(Server.java:248) > at > org.mortbay.jetty.HttpConnection.handlerRequest(HttpConnection.java:360) > at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:628) > at org.mortbay.jetty.HttpParser
[jira] Resolved: (AMQ-741) Remove the onSendPrepareMessageBody property on the ActiveMQ Connection and ConnectionFactory
[ https://issues.apache.org/activemq/browse/AMQ-741?page=all ] Hiram Chirino resolved AMQ-741: --- Resolution: Fixed commited to both branches. > Remove the onSendPrepareMessageBody property on the ActiveMQ Connection and > ConnectionFactory > - > > Key: AMQ-741 > URL: https://issues.apache.org/activemq/browse/AMQ-741 > Project: ActiveMQ > Type: Improvement > Versions: 4.0 > Reporter: Hiram Chirino > Assignee: Hiram Chirino > Fix For: 4.0.1, 4.1 > > > They are not used for anyting. Could confuse users to see that that property > is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-741) Remove the onSendPrepareMessageBody property on the ActiveMQ Connection and ConnectionFactory
Remove the onSendPrepareMessageBody property on the ActiveMQ Connection and ConnectionFactory - Key: AMQ-741 URL: https://issues.apache.org/activemq/browse/AMQ-741 Project: ActiveMQ Type: Improvement Versions: 4.0 Reporter: Hiram Chirino Assigned to: Hiram Chirino Fix For: 4.0.1, 4.1 They are not used for anyting. Could confuse users to see that that property is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
