[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=comments#action_37604 ] Hiram Chirino commented on AMQ-1078: fix in 4.1 branch rev 480862 > Messages consumed with the Resource Adapter are intermittently not delivered > > > Key: AMQ-1078 > URL: https://issues.apache.org/activemq/browse/AMQ-1078 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Connector >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.2.0, 4.1.1 > > > The cause is that the ActiveMQSessionExecutor was starting and using it's > dispatch thread instead of the Thread managed by the resource adapter. -- 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-1052) Connection is not released by broker when client is killed when client is sending to a queue that is full
Connection is not released by broker when client is killed when client is sending to a queue that is full - Key: AMQ-1052 URL: https://issues.apache.org/activemq/browse/AMQ-1052 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.1.2 -- 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] Updated: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
[ https://issues.apache.org/activemq/browse/AMQ-1047?page=all ] Hiram Chirino updated AMQ-1047: --- Assignee: Adrian Co (was: Hiram Chirino) > ActiveMQ admin scripts should hide JMX from the user as much as possible. > - > > Key: AMQ-1047 > URL: https://issues.apache.org/activemq/browse/AMQ-1047 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Adrian Co > Fix For: 4.2.0 > > > The fact that JMX is being used to access the management functions of the > Broker should be hidden from the user of the admin scripts as much as > possible. > For example, users should not be displayed objects names of a list of > subscriptions. They should be shown the subscription ids of the > subscriptions. The same goes for connections and so forth. -- 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] Assigned: (AMQ-1046) Consolidate the ActiveMQ admin scripts to a single command line script
[ https://issues.apache.org/activemq/browse/AMQ-1046?page=all ] Hiram Chirino reassigned AMQ-1046: -- Assignee: Adrian Co (was: Fritz Oconer) > Consolidate the ActiveMQ admin scripts to a single command line script > -- > > Key: AMQ-1046 > URL: https://issues.apache.org/activemq/browse/AMQ-1046 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Adrian Co > Fix For: 4.2.0 > > > Right now we have serveral command line scripts in the ActiveMQ bin directory > of the binary distribution. They are used for admin purposes. They are less > than ideal because some of them have very generic names and might clash with > existing commands if the activemq bin directory is added to the PATH of a > unix system. > I think it would be more idea if we consolidated all the command so that are > executed using just 1 script. Something like: > $ activemq-admin list > $ activemq-admin stat > $ activemq-admin browse > etc. etc. etc. This way only 2 executable scripts are added to the path: > (1) activemq - the binary that starts up ActiveMQ > (2) activemq-admin - the binary used to manage the ActiveMQ instance. -- 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-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.
ActiveMQ admin scripts should hide JMX from the user as much as possible. - Key: AMQ-1047 URL: https://issues.apache.org/activemq/browse/AMQ-1047 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0 The fact that JMX is being used to access the management functions of the Broker should be hidden from the user of the admin scripts as much as possible. For example, users should not be displayed objects names of a list of subscriptions. They should be shown the subscription ids of the subscriptions. The same goes for connections and so forth. -- 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-1046) Consolidate the ActiveMQ admin scripts to a single command line script
Consolidate the ActiveMQ admin scripts to a single command line script -- Key: AMQ-1046 URL: https://issues.apache.org/activemq/browse/AMQ-1046 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Fritz Oconer Fix For: 4.2.0 Right now we have serveral command line scripts in the ActiveMQ bin directory of the binary distribution. They are used for admin purposes. They are less than ideal because some of them have very generic names and might clash with existing commands if the activemq bin directory is added to the PATH of a unix system. I think it would be more idea if we consolidated all the command so that are executed using just 1 script. Something like: $ activemq-admin list $ activemq-admin stat $ activemq-admin browse etc. etc. etc. This way only 2 executable scripts are added to the path: (1) activemq - the binary that starts up ActiveMQ (2) activemq-admin - the binary used to manage the ActiveMQ instance. -- 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] Resolved: (AMQ-746) JournalPersistenceAdapterGBean needs to resolve the persistence adapter directory via serverInfo.resolveServer
[ https://issues.apache.org/activemq/browse/AMQ-746?page=all ] Hiram Chirino resolved AMQ-746. --- Resolution: Won't Fix Geronimo no longer uses this GBean. > JournalPersistenceAdapterGBean needs to resolve the persistence adapter > directory via serverInfo.resolveServer > -- > > Key: AMQ-746 > URL: https://issues.apache.org/activemq/browse/AMQ-746 > Project: ActiveMQ > Issue Type: Bug > Components: Geronimo Integration >Affects Versions: 3.2.4 >Reporter: Gianny DAMOUR > Fix For: 3.2.5 > > Attachments: GERONIMO-1638-AMQ.patch > > > The current implementation resolves the persistence adapter directory via > serverInfo.resolve. This causes a problem with the multi-server feature: the > journal is located at var/activemq/journal instead of name>/var/activemq/journal -- 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] Resolved: (AMQ-319) ActiveMQ hangs when initial connection to broker fails using reliable transport
[ https://issues.apache.org/activemq/browse/AMQ-319?page=all ] Hiram Chirino resolved AMQ-319. --- Fix Version/s: 4.0.3 (was: 3.2.5) Resolution: Fixed Assignee: Hiram Chirino Since you can set a max reconnect attempt in 4.0.. this problem is not an issue there anymore. > ActiveMQ hangs when initial connection to broker fails using reliable > transport > > > Key: AMQ-319 > URL: https://issues.apache.org/activemq/browse/AMQ-319 > Project: ActiveMQ > Issue Type: Improvement > Components: JMS client >Affects Versions: 3.0 >Reporter: Ramzi Saba > Assigned To: Hiram Chirino > Fix For: 4.0.3 > > > Make these changes in the JMS client to avoid blocking on startup in case all > brokers are down: > 1- Start the reliable tcp channel in its own thread (seems there was an > attempt to do so anyway) > 2- Synchronous and asynchronous client calls (via session, consumer, etc.) to > the reliable tcp channel should simply verify if a reliable channel has been > already established, else throw a JMSException, alternatively allow the > client to configure a timeout (currently it's hardcoded for synchronous calls > only I believe). > 3- Other than starting the reliable channel, the client should not be > responsible of reestablishing a lost or unavailable channel. I would delegate > reliability to the reliable channel itself. > 4- Look into adding a listener to allow for a silent client startup and > reconnect behind the scene once the broker is up -- 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] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[ https://issues.apache.org/activemq/browse/AMQ-734?page=all ] Hiram Chirino updated AMQ-734: -- Fix Version/s: 4.1.1 (was: 4.0.1) I've got a feeling that this was related to the timing issues addressed in issue: https://issues.apache.org/activemq/browse/AMQ-1044 which is now fixed. Could one you guys retest against a source build from the 4.1 branch and let me know if it resolves this issue? > Network connections do not reconnect when using static: with failover=true > -- > > Key: AMQ-734 > URL: https://issues.apache.org/activemq/browse/AMQ-734 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Affects Versions: 4.0 > Environment: winxp java1.5.6 >Reporter: tao > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.2.0, 4.1.1 > > > If I pull out RJ45 port from net card ,waiting a time ,then put RJ45 port > net card .Network is resume.Other computer always throw errors and net > channel can't work. -- 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] Updated: (AMQ-1036) web-console broken (queue browsing).
[ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]
Hiram Chirino updated AMQ-1036:
---
Fix Version/s: 4.1.1
4.2.0
(was: 4.1.0)
> web-console broken (queue browsing).
>
>
> Key: AMQ-1036
> URL: https://issues.apache.org/activemq/browse/AMQ-1036
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: incubation
>Reporter: Dave Syer
> Assigned To: Adrian Co
> Fix For: 4.2.0, 4.1.1
>
>
> I managed to build and launch the web-console from svn, but the queue
> browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size}
> that do not exist. When I hacked queue.jsp to remove references to those
> properties I got another error on trying to purge a queue:
> RequestURI=/activemq-web-console/purgeDestination.action
> Caused by:
> java.lang.IllegalArgumentException: Target bean must not be null
> at org.springframework.util.Assert.notNull(Assert.java:113)
> at
> org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
> at
> org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
> at
> org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
> at
> org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
> at
> org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
> at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
> at
> org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
> at
> org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
> at
> org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
> ...
--
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] Updated: (AMQ-910) backoffMultiplier should be a double value
[ https://issues.apache.org/activemq/browse/AMQ-910?page=all ] Hiram Chirino updated AMQ-910: -- Fix Version/s: 4.2.0 (was: 4.0.1) > backoffMultiplier should be a double value > -- > > Key: AMQ-910 > URL: https://issues.apache.org/activemq/browse/AMQ-910 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Daniel Aioanei > Fix For: 4.2.0 > > > Having org.apache.activemq.ra.ActiveMQActivationSpec.backOffMultiplier as a > short value is too limiting. I think a double value would be more > appropriate. For instance, I'd like to set it to about 1.1 but that's not > possible at the time being. -- 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] Resolved: (AMQ-1016) 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"
[ https://issues.apache.org/activemq/browse/AMQ-1016?page=all ] Hiram Chirino resolved AMQ-1016. Fix Version/s: 4.1.1 4.2.0 Resolution: Fixed Assignee: Hiram Chirino Fix applied in trunk rev 474872 and in 4.1 branch rev 474876 > 4.1 RC1: META-INF/spring.schemas refers to building user > "file:/Users/chirino/" > --- > > Key: AMQ-1016 > URL: https://issues.apache.org/activemq/browse/AMQ-1016 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.1.0 > Environment: n/a >Reporter: Endre Stølsvik > Assigned To: Hiram Chirino >Priority: Minor > Fix For: 4.1.1, 4.2.0 > > > Referring to the 4.1 RC1 posted by Hiram Chirino Oct 06, here: > http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974 > The META-INF file spring.schemas have the single line. > "http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd" > Notice "file:/" and "Users/chirino". Referring to > org.springframework.beans.factory.xml.PluggableSchemaResolver's javadoc: > "schema-location should also be a schema file in the classpath", and that > no-one can tell what structure I will have on my fs, this must be wrong. In > addition, I most probably won't have a user name "chirino". > PS: In addition, the doc at > > http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html > refers as such: > xmlns:amq="http://activemq.org/config/1.0"; > .. and .. > xsi:schemaLocation="http://activemq.org/config/1.0 > http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd"; > Wouldn't it be nice if this was put at a better place than such a > snapshot-build URI? It could be put where it will reside when 4.1 actually is > out, w/o anyone being to angry about changes during the finalization period, > I personally believe. -- 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] Updated: (AMQ-327) Orphanded/lost queue messages in various failover tests in two broker configuration
[ https://issues.apache.org/activemq/browse/AMQ-327?page=all ] Hiram Chirino updated AMQ-327: -- Fix Version/s: 4.2 (was: 4.1.0) > Orphanded/lost queue messages in various failover tests in two broker > configuration > --- > > Key: AMQ-327 > URL: https://issues.apache.org/activemq/browse/AMQ-327 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0 > Environment: w2k & RH 9.0 jdk1.4.2 >Reporter: Dennis Cook > Assigned To: John Heitmann > Fix For: 4.2.0 > > Attachments: AMQ-327.tar.gz > > > Seems like the messages being passed to a broker where no client is connected > when the failed broker is re-established. This message is "lost" until a > client is connected to this broker. -- 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] Updated: (AMQ-375) advisory and MBean notification if a slow consumer is killed (with access to the userName in in the message)
[ https://issues.apache.org/activemq/browse/AMQ-375?page=all ] Hiram Chirino updated AMQ-375: -- Fix Version/s: 4.2 (was: 4.1.0) > advisory and MBean notification if a slow consumer is killed (with access to > the userName in in the message) > - > > Key: AMQ-375 > URL: https://issues.apache.org/activemq/browse/AMQ-375 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Reporter: james strachan > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-132) Remotting logging of clients under flow control
[ https://issues.apache.org/activemq/browse/AMQ-132?page=all ] Hiram Chirino updated AMQ-132: -- Fix Version/s: 4.2 (was: 4.1.0) > Remotting logging of clients under flow control > --- > > Key: AMQ-132 > URL: https://issues.apache.org/activemq/browse/AMQ-132 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Barry Kaplan > Fix For: 4.2.0 > > > When performance testing a system (or troubleshooting slowdowns in > production) it would be very helpful to know when any client has come under > flow control. This information would be logged (via jmx events?) including > the identification of the broker(s) that cannot keep up, and the > corresponding client(s) that have been throttled. -- 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] Updated: (AMQ-371) auto protocol switch from openwire to stomp on JMS client in case some 4.0 JMS client cannot work with some late version (like 8.3) of ActiveMQ server - we can always move ba
[ https://issues.apache.org/activemq/browse/AMQ-371?page=all ] Hiram Chirino updated AMQ-371: -- Fix Version/s: 4.2 (was: 4.1.0) > auto protocol switch from openwire to stomp on JMS client in case some 4.0 > JMS client cannot work with some late version (like 8.3) of ActiveMQ server - > we can always move back to stomp > - > > Key: AMQ-371 > URL: https://issues.apache.org/activemq/browse/AMQ-371 > Project: ActiveMQ > Issue Type: Improvement > Components: JMS client >Reporter: james strachan > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-367) Axis/JMS/ActiveMQ demo
[ https://issues.apache.org/activemq/browse/AMQ-367?page=all ] Hiram Chirino updated AMQ-367: -- Fix Version/s: 4.2 (was: 4.1.0) > Axis/JMS/ActiveMQ demo > -- > > Key: AMQ-367 > URL: https://issues.apache.org/activemq/browse/AMQ-367 > Project: ActiveMQ > Issue Type: New Feature >Affects Versions: 3.1 >Reporter: Chris Berry > Fix For: 4.2.0 > > Attachments: axis-jms-demo.zip > > > I have created a self-contained demo of using Axis/JMS/ActiveMQ > James suggested that I pass it along for possible inclusion in the examples > All of the code is in the enclosed ZIP > Cheers, > -- Chris -- 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] Updated: (AMQ-361) duplicate delivery, already consumed messages are reconsumed after server restart
[ https://issues.apache.org/activemq/browse/AMQ-361?page=all ] Hiram Chirino updated AMQ-361: -- Fix Version/s: 4.2 (was: 4.1.0) > duplicate delivery, already consumed messages are reconsumed after server > restart > - > > Key: AMQ-361 > URL: https://issues.apache.org/activemq/browse/AMQ-361 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Message Store, JCA Container >Affects Versions: 4.0 > Environment: windows xp, jdk 1.5, embedded activemq 3.1 broker, jboss > 4.02, persistent messages with derby db. >Reporter: Gokturk Ozer > Fix For: 4.2.0 > > Attachments: 1.log > > > I am running an embedded activemq broker inside jboss server, I send 1000 > messages with ~10K size each to a queue, these messages are consumed by MDBs. > After all the messages are consumed, I check the queue via hermes, it also > shows no message in the queue. Everything works perfect up to this point. I > observe the problem after I stop the jboss server. I connect to derby > database via networkserver, I still see some messages in activemq_msgs table. > I shutdown derby networkserver and start jboss again, I see from the log that > some of the messages which were consumed previously, are being consumed > again. If I start the server without deploying the MDB and check the queue > via hermes, I see some but not all the messages which were consumed > previously still in the queue, before restart hermes was showing no messages. -- 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] Updated: (AMQ-340) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification
[ https://issues.apache.org/activemq/browse/AMQ-340?page=all ] Hiram Chirino updated AMQ-340: -- Fix Version/s: 4.2 (was: 4.1.0) > allow topics in particular but also queues to have a 'namespace URI' like > WS-Notification > - > > Key: AMQ-340 > URL: https://issues.apache.org/activemq/browse/AMQ-340 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan > Assigned To: james strachan > Fix For: 4.2.0 > > > This would allow a real clean mapping from WS-N topics and ActiveMQ at the > protocol level. We could use the namespace as a level of indirection to map > to a broker, a cluster of brokers or even a particular area of a network etc. > The namespace could be a broker's name too. -- 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] Updated: (AMQ-404) winxp sp2 and mysql4.1.15 throw error
[ https://issues.apache.org/activemq/browse/AMQ-404?page=all ] Hiram Chirino updated AMQ-404: -- Fix Version/s: 4.2 (was: 4.1.0) > winxp sp2 and mysql4.1.15 throw error > -- > > Key: AMQ-404 > URL: https://issues.apache.org/activemq/browse/AMQ-404 > Project: ActiveMQ > Issue Type: Bug > Components: Message Store >Affects Versions: 3.2 >Reporter: tao > Fix For: 4.2.0 > > > 2005-11-04 11:24:17,909 [Cleanup Timmer ] ERROR JDBCPersistenceAdapter > - Error in cleanup due to: com.mysql.jdbc.CommunicationsException: > Communications link failure due to underlying exception: > ** BEGIN NESTED EXCEPTION ** > java.net.SocketException > MESSAGE: java.net.BindException: Address already in use: connect > STACKTRACE: > java.net.SocketException: java.net.BindException: Address already in use: > connect > at > com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) > at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284) > at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541) > at com.mysql.jdbc.Connection.(Connection.java:1474) > at > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) > at > org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) > at > org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) > at > org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) > at > org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) > at > org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257) > at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:534) > ** END NESTED EXCEPTION ** > Last packet sent to the server was 0 ms ago. > com.mysql.jdbc.CommunicationsException: Communications link failure due to > underlying exception: > ** BEGIN NESTED EXCEPTION ** > java.net.SocketException > MESSAGE: java.net.BindException: Address already in use: connect > STACKTRACE: > java.net.SocketException: java.net.BindException: Address already in use: > connect > at > com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) > at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284) > at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541) > at com.mysql.jdbc.Connection.(Connection.java:1474) > at > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) > at > org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) > at > org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) > at > org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) > at > org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) > at > org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257) > at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:534) > ** END NESTED EXCEPTION ** > Last packet sent to the server was 0 ms ago. > at com.mysql.jdbc.Connection.createNewIO(Connection.java:2607) > at com.mysql.jdbc.Connection.(Connection.java:1474) > at > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) > at > org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) > at > org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) > at > org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) > at > org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) > at > org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544) > at > org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418) > at > org.a
[jira] Updated: (AMQ-376) security plugin which can use, say, LDAP to authenticate the user, then use a custom database table to associate roles to users and destinations to roles
[ https://issues.apache.org/activemq/browse/AMQ-376?page=all ] Hiram Chirino updated AMQ-376: -- Fix Version/s: 4.2 (was: 4.1.0) > security plugin which can use, say, LDAP to authenticate the user, then use a > custom database table to associate roles to users and destinations to roles > - > > Key: AMQ-376 > URL: https://issues.apache.org/activemq/browse/AMQ-376 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan > Fix For: 4.2.0 > > > BTW have added org.activemq.security.SecurityAdminMBean as a simple MBean API > to the admin of these things. > Note we wanna cache the security state; then have a notification (via JMS > Topic) to flush/reload the data when folks change it - so performance is > great and the security configuration is highly dynamic -- 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] Updated: (AMQ-431) only send a message once for multiple consumers on the same connection (for topics)
[ https://issues.apache.org/activemq/browse/AMQ-431?page=all ] Hiram Chirino updated AMQ-431: -- Fix Version/s: 4.2 (was: 4.1.0) > only send a message once for multiple consumers on the same connection (for > topics) > --- > > Key: AMQ-431 > URL: https://issues.apache.org/activemq/browse/AMQ-431 > Project: ActiveMQ > Issue Type: Improvement >Reporter: james strachan > Fix For: 4.2.0 > > > in 3.x we sent a message once with a list of all the MessageConsumers on it > so that we could avoid sending multiple messages over a socket when several > consumers are on the same connection. We should add back that optimisation -- 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] Updated: (AMQ-382) Security plugin using database tables for user, role, destination mapping; along with an MBean to administer them and a JMS subscription & notification of when they change so
[ https://issues.apache.org/activemq/browse/AMQ-382?page=all ] Hiram Chirino updated AMQ-382: -- Fix Version/s: 4.2 (was: 4.1.0) > Security plugin using database tables for user, role, destination mapping; > along with an MBean to administer them and a JMS subscription & notification > of when they change so we can reload the cache > -- > > Key: AMQ-382 > URL: https://issues.apache.org/activemq/browse/AMQ-382 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan > Fix For: 4.2.0 > > > So the idea is its cached in RAM for speed; then it gets reloaded from the > database if folks change it. -- 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] Updated: (AMQ-378) add pluggable Policy which is fired in a background Timer to detect slow consumers for non-durable topics and kill them (maybe with a pre-warning of being slow a little befor
[ https://issues.apache.org/activemq/browse/AMQ-378?page=all ] Hiram Chirino updated AMQ-378: -- Fix Version/s: 4.2 (was: 4.1.0) > add pluggable Policy which is fired in a background Timer to detect slow > consumers for non-durable topics and kill them (maybe with a pre-warning of > being slow a little before being killed) > - > > Key: AMQ-378 > URL: https://issues.apache.org/activemq/browse/AMQ-378 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-453) Clustering subscriptions
[ https://issues.apache.org/activemq/browse/AMQ-453?page=all ] Hiram Chirino updated AMQ-453: -- Fix Version/s: 4.2 (was: 4.1.0) > Clustering subscriptions > > > Key: AMQ-453 > URL: https://issues.apache.org/activemq/browse/AMQ-453 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.2.0 > > > To be able to use ServiceMix WS-Notification in a cluster, we need to be able > to: > * attach some data to the subscription > * provide a way to retrieve subscription informations from the > NotificationBroker (using consumer advisory ?) > * cluster subscriptions (sticky durable subscriber ?) > See irc log from 21/12/2005 from 21:14 > http://servlet.uwyn.com/drone/log/hausbot/servicemix/20051221 -- 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] Updated: (AMQ-468) Queue load balancing - optionally give highest priority to the local connection, then local broker then networks
[ https://issues.apache.org/activemq/browse/AMQ-468?page=all ] Hiram Chirino updated AMQ-468: -- Fix Version/s: 4.2 (was: 4.1.0) > Queue load balancing - optionally give highest priority to the local > connection, then local broker then networks > > > Key: AMQ-468 > URL: https://issues.apache.org/activemq/browse/AMQ-468 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Rob Davies > Fix For: 4.2.0 > > > For Queues, as an option assign the highest priority for dispatching to the > local connection, then the local broker, then the cluster etc. > Right now we favour consumers on the local broker above consumers on remote > brokers. However we should prioritise consumers on the same session, > connection or VM transport above consumers in other processes etc -- 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] Updated: (AMQ-488) Broker side message redelivery due to client death should be tracked so that the message can be sent to the DLQ.
[ https://issues.apache.org/activemq/browse/AMQ-488?page=all ] Hiram Chirino updated AMQ-488: -- Fix Version/s: 4.2 (was: 4.1.0) > Broker side message redelivery due to client death should be tracked so that > the message can be sent to the DLQ. > > > Key: AMQ-488 > URL: https://issues.apache.org/activemq/browse/AMQ-488 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-512) enhance the command line tools to allow messages on queues to be browsed, queues to be purged, messages deleted, dead letter queues to be redispatched to orginal queues etc
[ https://issues.apache.org/activemq/browse/AMQ-512?page=all ] Hiram Chirino updated AMQ-512: -- Fix Version/s: 4.2 (was: 4.1.0) > enhance the command line tools to allow messages on queues to be browsed, > queues to be purged, messages deleted, dead letter queues to be redispatched > to orginal queues etc > > > Key: AMQ-512 > URL: https://issues.apache.org/activemq/browse/AMQ-512 > Project: ActiveMQ > Issue Type: New Feature >Reporter: james strachan > Assigned To: Adrian Co > Fix For: 4.2.0 > > > You should be able to reuse the MBeans for the operations of these commands -- 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] Updated: (AMQ-528) 4.0 M4 NullPointerException while shutting down
[ https://issues.apache.org/activemq/browse/AMQ-528?page=all ] Hiram Chirino updated AMQ-528: -- Fix Version/s: 4.2 (was: 4.1.0) > 4.0 M4 NullPointerException while shutting down > --- > > Key: AMQ-528 > URL: https://issues.apache.org/activemq/browse/AMQ-528 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 > Environment: RedHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL > 5.0.18 for Linux >Reporter: Leon Hu >Priority: Critical > Fix For: 4.2.0, 4.0.3 > > > Setup: > 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast > discovery. activemq.xml: > > > > dataSource="#mysql-ds"/> > > > > discoveryUri="multicast://default"/> > > > > > > > > > destroy-method="close"> > > value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/> > > > > > Similar for B2 and B3. > Two queues: Q1 and Q2. > Two producers, one for each queue, both producers connected to B1. > One Q1 cosumer connected to B1, another Q1 consumer on B2. > One Q2 consumer connected to B2, another Q2 consumer connected to B3. > Steps: > Start the brokers and start sending messages to the queue. > After a while, stop the brokers (Sequence does not matter) > See the errors in catalina.out of the Tomcat that has a broker with both > producers and consumers connected > The problems: > 1. > Exception in thread "ActiveMQ Scheduler" java.lang.NullPointerException > at > edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) > at > edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) > at > edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) > at > edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) > Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ > Scheduler" Exception in thread "ActiveMQ Scheduler" at > edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) > at java.lang.Thread.run(Thread.java:595) > java.lang.NullPointerException > at > edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219) > Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ > Scheduler" Exception in thread "ActiveMQ Scheduler" at > edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99) > at > edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88) > at > edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137) > at > edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470) > Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ > Scheduler" at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667) > at java.lang.Thread.run(Thread.java:595) > 2. The same exception is logged to the log file (in my case catalina.out) for > hundreds of times, resulting a log file exceeding 150 MB in 2 minutes. -- 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] Updated: (AMQ-732) Infinite recovery loop.
[ https://issues.apache.org/activemq/browse/AMQ-732?page=all ]
Hiram Chirino updated AMQ-732:
--
Fix Version/s: 4.2
(was: 4.1.0)
> Infinite recovery loop.
> ---
>
> Key: AMQ-732
> URL: https://issues.apache.org/activemq/browse/AMQ-732
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0
> Environment: Linux RHEL 3
>Reporter: Maxim Fateev
> Assigned To: Hiram Chirino
> Fix For: 4.2.0, 4.0.3
>
> Attachments: activemq-data-1-journal.tar.gz,
> activemq-data-2-journal.tar.gz
>
>
> 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] LogFileMan
[jira] Updated: (AMQ-631) verify that HttpsTransportBrokerTest won't hang on other environment
[ https://issues.apache.org/activemq/browse/AMQ-631?page=all ] Hiram Chirino updated AMQ-631: -- Fix Version/s: 4.2 (was: 4.1.0) > verify that HttpsTransportBrokerTest won't hang on other environment > > > Key: AMQ-631 > URL: https://issues.apache.org/activemq/browse/AMQ-631 > Project: ActiveMQ > Issue Type: Task > Components: Test Cases >Affects Versions: 4.0 RC2 >Reporter: Adrian Co > Assigned To: Adrian Co > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-594) SimpleNetworkTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-594?page=all ] Hiram Chirino updated AMQ-594: -- Fix Version/s: 4.2 (was: 4.1.0) > SimpleNetworkTest hangs > --- > > Key: AMQ-594 > URL: https://issues.apache.org/activemq/browse/AMQ-594 > Project: ActiveMQ > Issue Type: Bug > Components: Test Cases >Affects Versions: 4.0 RC2 >Reporter: Darwin Flores > Assigned To: Rob Davies > Fix For: 4.2.0 > > > The SimpleNetworkTest appears to be hanging in Linux platform -- 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] Updated: (AMQ-690) Allow the timer to be configured (and disabled) for the async clear down of durable topic messages
[ https://issues.apache.org/activemq/browse/AMQ-690?page=all ] Hiram Chirino updated AMQ-690: -- Fix Version/s: 4.2 (was: 4.1.0) > Allow the timer to be configured (and disabled) for the async clear down of > durable topic messages > -- > > Key: AMQ-690 > URL: https://issues.apache.org/activemq/browse/AMQ-690 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0 RC2 > Environment: all >Reporter: Kyle Himmerick >Priority: Minor > Fix For: 4.2.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Allow the timer to be configured (and disabled) for the async clear down of > durable topic messages. > So Retroactive Consumers can receive all messages ever sent on a durable topic -- 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] Updated: (AMQ-693) STOMP C client ready for Sun Workshop 6 and above on Solaris
[ https://issues.apache.org/activemq/browse/AMQ-693?page=all ] Hiram Chirino updated AMQ-693: -- Fix Version/s: 4.2 (was: 4.1.0) > STOMP C client ready for Sun Workshop 6 and above on Solaris > > > Key: AMQ-693 > URL: https://issues.apache.org/activemq/browse/AMQ-693 > Project: ActiveMQ > Issue Type: Improvement > Components: JMS client >Affects Versions: 4.0 RC2 > Environment: Sun Workshop 6 and above on Solaris 8 and above >Reporter: vik dhawan >Priority: Minor > Fix For: 4.2.0 > > Attachments: stompc.tar > > > Here i modified STOMP C client so it can run on Solaris platform. I > saparated producer and concumer for distributed tracking purposes. > Thanks! -- 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] Updated: (AMQ-567) Time in queue statistics handy
[ https://issues.apache.org/activemq/browse/AMQ-567?page=all ] Hiram Chirino updated AMQ-567: -- Fix Version/s: 4.2 (was: 4.1.0) > Time in queue statistics handy > -- > > Key: AMQ-567 > URL: https://issues.apache.org/activemq/browse/AMQ-567 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0 M4 > Environment: any >Reporter: Scott Ellsworth > Fix For: 4.2.0 > > > It would be very keen if the JMX console exposed queue statistics, such as > average length of time in queue for current messages, longest/shortest time > in queue for current messages, average time in queue for serviced messages > (as opposed to those waiting), longestlshortest time for same, and a list of > messages in the queue with when they were posted, and how long they have been > waiting. -- 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] Updated: (AMQ-767) avoid use of XHTML in activemq-web-console so things work great in IE 6
[ https://issues.apache.org/activemq/browse/AMQ-767?page=all ] Hiram Chirino updated AMQ-767: -- Fix Version/s: 4.2 (was: 4.1.0) > avoid use of XHTML in activemq-web-console so things work great in IE 6 > --- > > Key: AMQ-767 > URL: https://issues.apache.org/activemq/browse/AMQ-767 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0.1 >Reporter: james strachan > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception
[ https://issues.apache.org/activemq/browse/AMQ-751?page=all ] Hiram Chirino updated AMQ-751: -- Fix Version/s: 4.2 (was: 4.1.0) > Extend ExceptionListener mechanism by creating a custom AMQ exception which > would provide more detail about the exception > - > > Key: AMQ-751 > URL: https://issues.apache.org/activemq/browse/AMQ-751 > Project: ActiveMQ > Issue Type: Improvement > Components: JMS client, Broker >Reporter: Massive Boisson >Priority: Minor > Fix For: 4.2.0 > > > To quote James: > "I wonder if we could add a neater non-JMS extension to ActiveMQ to make it > easier to be notified asynchronously of which Message objects could not be > sent? I guess we could just use the ExceptionListener and use a custom type > of Exception which contained the Message object?" > I think this would greatly increase the usefulness of async sends. -- 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] Updated: (AMQ-644) create Java Service Wrapper for ActiveMQ
[ https://issues.apache.org/activemq/browse/AMQ-644?page=all ] Hiram Chirino updated AMQ-644: -- Fix Version/s: 4.2 (was: 4.1.0) > create Java Service Wrapper for ActiveMQ > > > Key: AMQ-644 > URL: https://issues.apache.org/activemq/browse/AMQ-644 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Reporter: james strachan > Assigned To: Joseph Dennis Gapuz >Priority: Minor > Fix For: 4.2.0 > > Attachments: wrapper.conf > > > http://wrapper.tanukisoftware.org/doc/english/introduction.html -- 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] Updated: (AMQ-546) Network brokers have long reconnect times and they receive duplicate messages
[ https://issues.apache.org/activemq/browse/AMQ-546?page=all ] Hiram Chirino updated AMQ-546: -- Fix Version/s: 4.2 (was: 4.1.0) > Network brokers have long reconnect times and they receive duplicate messages > - > > Key: AMQ-546 > URL: https://issues.apache.org/activemq/browse/AMQ-546 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 3.2, 4.0 M4 >Reporter: Hiram Chirino > Fix For: 4.2.0 > > > Initially reported at: > http://forums.activemq.org/posts/list/202.page > Notice that the forum has a JUnit test case that demonstrates the problem. -- 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] Updated: (AMQ-616) SpringTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-616?page=all ] Hiram Chirino updated AMQ-616: -- Fix Version/s: 4.2 (was: 4.1.0) > SpringTest hangs > > > Key: AMQ-616 > URL: https://issues.apache.org/activemq/browse/AMQ-616 > Project: ActiveMQ > Issue Type: Test > Components: Test Cases >Affects Versions: 4.0 RC2 >Reporter: Darwin Flores > Assigned To: Rob Davies > Fix For: 4.2.0 > > > The SpringTest appears to be hanging in Linux platform -- 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] Updated: (AMQ-730) 4.x Javadoc
[ https://issues.apache.org/activemq/browse/AMQ-730?page=all ] Hiram Chirino updated AMQ-730: -- Fix Version/s: 4.2 (was: 4.1.0) > 4.x Javadoc > --- > > Key: AMQ-730 > URL: https://issues.apache.org/activemq/browse/AMQ-730 > Project: ActiveMQ > Issue Type: Wish > Components: Documentation >Affects Versions: 4.0 >Reporter: jason evans > Fix For: 4.2.0 > > > While ActiveMQ proves to be a high quality open-source JMS implementation the > incomplete Javadoc decreases developer understanding, development and test > time, and overall confidence of the adoption of each implementation. Although > I have submitted this as a wish I would like to see an effort to beef up the > documentation. I believe the community will benefit tremendously! -- 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] Updated: (AMQ-720) Use the Apache Commons CLI to parse the command line
[ https://issues.apache.org/activemq/browse/AMQ-720?page=all ] Hiram Chirino updated AMQ-720: -- Fix Version/s: 4.2 (was: 4.1.0) > Use the Apache Commons CLI to parse the command line > > > Key: AMQ-720 > URL: https://issues.apache.org/activemq/browse/AMQ-720 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 4.1.0 >Reporter: Adrian Co > Assigned To: Adrian Co > Fix For: 4.2.0 > > > Change the current way of parsing command line to use the apache commons cli > for a more standard format. -- 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] Updated: (AMQ-652) Potential infinite loop in ActiveMQ shutdown processing when in Geronimo
[ https://issues.apache.org/activemq/browse/AMQ-652?page=all ] Hiram Chirino updated AMQ-652: -- Fix Version/s: 4.2 (was: 4.1.0) > Potential infinite loop in ActiveMQ shutdown processing when in Geronimo > > > Key: AMQ-652 > URL: https://issues.apache.org/activemq/browse/AMQ-652 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Affects Versions: 4.0 > Environment: Geronimo >Reporter: Hiram Chirino > Fix For: 4.2.0 > > > Need to check to see if this is still valid against 4.x > see: > http://issues.apache.org/jira/browse/GERONIMO-1494 -- 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] Updated: (AMQ-648) Changing the default JMX URL
[ https://issues.apache.org/activemq/browse/AMQ-648?page=all ] Hiram Chirino updated AMQ-648: -- Fix Version/s: 4.2 (was: 4.1.0) > Changing the default JMX URL > > > Key: AMQ-648 > URL: https://issues.apache.org/activemq/browse/AMQ-648 > Project: ActiveMQ > Issue Type: Wish > Components: Documentation >Affects Versions: 4.0 M4 >Reporter: Bruce Mitchener >Priority: Minor > Fix For: 4.2.0 > > > Most of the command line utilities accept a jmxurl parameter, but there > doesn't seem to be an easy way to set up ActiveMQ to use a JMX URL other than > the default. I'd wanted to do so for my development environment so that I > could run a JMX console on my desktop and connect to the server running on > another machine. At ab0oo's suggestion, I'll use an SSH port forward (ssh > remotehost -L1099:localhost:1099) for now, but it'd be nice to see this > covered in some form in the JMX notes. -- 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] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true
[ https://issues.apache.org/activemq/browse/AMQ-734?page=all ] Hiram Chirino updated AMQ-734: -- Fix Version/s: 4.2 (was: 4.1.0) > Network connections do not reconnect when using static: with failover=true > -- > > Key: AMQ-734 > URL: https://issues.apache.org/activemq/browse/AMQ-734 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Affects Versions: 4.0 > Environment: winxp java1.5.6 >Reporter: tao > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.0.1, 4.2.0 > > > If I pull out RJ45 port from net card ,waiting a time ,then put RJ45 port > net card .Network is resume.Other computer always throw errors and net > channel can't work. -- 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] Updated: (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.
[ https://issues.apache.org/activemq/browse/AMQ-796?page=all ] Hiram Chirino updated AMQ-796: -- Fix Version/s: 4.2 (was: 4.1.0) > Client may shtudown when failover connection is reconnecting. We need to > maintain at least 1 non-daemon thread alive. > -- > > Key: AMQ-796 > URL: https://issues.apache.org/activemq/browse/AMQ-796 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Fix For: 4.2.0, 4.0.3 > > > Dejan Reported on the User lists: > Hi, > after some experiments I found that this problem only exists if there are no > other threads in the application. It seems like connection thread dies > before it manages to reconnect. By starting another thread in the > application, it succeeds to recover from master failure and reconnect to the > slave broker. So I have a workaround for now, but it would be nice to make > this work even for simple (single-threaded) clients. > Regards, > Dejan -- 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] Updated: (AMQ-815) generate a warning by default if a client connects via openwire using a different release version of the broker
[ https://issues.apache.org/activemq/browse/AMQ-815?page=all ] Hiram Chirino updated AMQ-815: -- Fix Version/s: 4.2 (was: 4.1.0) > generate a warning by default if a client connects via openwire using a > different release version of the broker > --- > > Key: AMQ-815 > URL: https://issues.apache.org/activemq/browse/AMQ-815 > Project: ActiveMQ > Issue Type: Improvement >Reporter: james strachan > Assigned To: Hiram Chirino > Fix For: 4.2.0 > > > While we can be quite liberal in supporting backwards compatible clients, the > default should be to warn folks if they connect via different versions - as > thats often an indication of classpath issues. > Maybe have 3 options - lenient (try to work with anything), warning (just log > warning on connection), strict (disconnect non-similar version clients) -- 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] Updated: (AMQ-795) security plugin to deal with temporary queue and topics better
[ https://issues.apache.org/activemq/browse/AMQ-795?page=all ] Hiram Chirino updated AMQ-795: -- Fix Version/s: 4.2 (was: 4.1.0) > security plugin to deal with temporary queue and topics better > -- > > Key: AMQ-795 > URL: https://issues.apache.org/activemq/browse/AMQ-795 > Project: ActiveMQ > Issue Type: Improvement >Reporter: james strachan > Assigned To: Jonas Lim > Fix For: 4.2.0 > > > Allow a role to be specified for read/write/admin of temporary queue and > temporary topics -- 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] Updated: (AMQ-804) Use of Temporary Destinations over broker networks can cause the network bridges to die.
[ https://issues.apache.org/activemq/browse/AMQ-804?page=all ] Hiram Chirino updated AMQ-804: -- Fix Version/s: 4.2 (was: 4.1.0) > Use of Temporary Destinations over broker networks can cause the network > bridges to die. > > > Key: AMQ-804 > URL: https://issues.apache.org/activemq/browse/AMQ-804 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Hiram Chirino > Assigned To: Rob Davies > Fix For: 4.2.0 > > > And when the bridge dies, it is not re-established. -- 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] Updated: (AMQ-821) Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)
[ https://issues.apache.org/activemq/browse/AMQ-821?page=all ]
Hiram Chirino updated AMQ-821:
--
Fix Version/s: 4.2
(was: 4.1.0)
> Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)
>
>
> Key: AMQ-821
> URL: https://issues.apache.org/activemq/browse/AMQ-821
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Environment: Net 1.1
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: ActiveMQTextMessage.cs.diff, nant.build.diff
>
>
> sizeof(int) is unsafe code on Net-1.1.
> I've attached patches to put the code in unsafe { ... } block, plus fix to
> nant.build. Same code also (still) compiles on 2.0.
--
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] Updated: (AMQ-876) Kaha DB cannot locate queue data files
[ https://issues.apache.org/activemq/browse/AMQ-876?page=all ] Hiram Chirino updated AMQ-876: -- Fix Version/s: 4.2 (was: 4.1.0) > Kaha DB cannot locate queue data files > -- > > Key: AMQ-876 > URL: https://issues.apache.org/activemq/browse/AMQ-876 > Project: ActiveMQ > Issue Type: Bug > Components: Message Store >Affects Versions: 4.1.0 > Environment: WinXP >Reporter: Vadim Pesochinskiy > Assigned To: Rob Davies > Fix For: 4.2.0 > > Attachments: test.zip > > > Keep getting exception below. Note that you are looking for queue-data-1, > but actual file name is data-queue-data-1 > $ pwd > /cygdrive/d/amq/activemq-kaha/kaha.db > $ ls > data-kaha-1 data-queue-data-1 index-kaha index-queue-data > index-transactions > javax.jms.JMSException: java.io.IOException: Could not locate data file > queue-data-1 > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46) > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1154) > at > org.apache.activemq.TransactionContext.commit(TransactionContext.java:260) > at > org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:464) > at > com.barra.cp.common.io.MultiQueueReceiver.onMessage(MultiQueueReceiver.java:163) > at > com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.runMultiQueue(SingleMessageMultiQueueReceiver.java:176) > at > com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.doRun(SingleMessageMultiQueueReceiver.java:143) > at > com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.run(SingleMessageMultiQueueReceiver.java:124) > at java.lang.Thread.run(Unknown Source) > Caused by: org.apache.activemq.kaha.RuntimeStoreException: > java.io.IOException: Could not locate data file queue-data-1 > at > org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:340) > at > org.apache.activemq.kaha.impl.MapContainerImpl.remove(MapContainerImpl.java:265) > at > org.apache.activemq.store.kahadaptor.KahaMessageStore.removeMessage(KahaMessageStore.java:68) > at > org.apache.activemq.store.kahadaptor.KahaTransaction.commit(KahaTransaction.java:92) > at > org.apache.activemq.store.kahadaptor.KahaTransactionStore.commit(KahaTransactionStore.java:95) > at > org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:68) > at > org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:154) > at > org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92) > at > org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92) > at > org.apache.activemq.broker.MutableBrokerFilter.commitTransaction(MutableBrokerFilter.java:102) > at > org.apache.activemq.broker.AbstractConnection.processCommitTransactionOnePhase(AbstractConnection.java:330) > at > org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:99) > at > org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:228) > at > org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:63) > at > org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92) > at > org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67) > at > org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:123) > at > org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:123) > at > org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:88) > at > org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:127) > ... 1 more > Caused by: java.io.IOException: Could not locate data file queue-data-1 > at > org.apache.activemq.kaha.impl.DataManager.getDataFile(DataManager.java:117) > at > org.apache.activemq.kaha.impl.StoreDataReader.readItem(StoreDataReader.java:62) > at > org.apache.activemq.kaha.impl.DataManager.readItem(DataManager.java:121) > at > org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:337) > ... 20 more -- 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] Updated: (AMQ-861) Kaha DB files are not removed
[ https://issues.apache.org/activemq/browse/AMQ-861?page=all ] Hiram Chirino updated AMQ-861: -- Fix Version/s: 4.2 (was: 4.1.0) > Kaha DB files are not removed > - > > Key: AMQ-861 > URL: https://issues.apache.org/activemq/browse/AMQ-861 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.1 > Environment: Win XP, Java 5 >Reporter: Vadim Pesochinskiy > Assigned To: Rob Davies > Fix For: 4.2.0 > > > I have request-response point to point test case, which I ran for 12 hours. > Each message is exactly 5KBytes. This is what I see in the Kaha directory: > 779 Aug 1 17:03 roots-data1 > 32M Aug 2 15:28 queue-data4 > 32M Aug 2 18:02 queue-data5 > 32M Aug 2 19:03 queue-data6 > 32M Aug 2 20:04 queue-data7 > 32M Aug 2 21:05 queue-data8 > 32M Aug 2 22:07 queue-data9 > 32M Aug 2 23:08 queue-data10 > 32M Aug 3 00:09 queue-data11 > 32M Aug 3 01:10 queue-data12 > 32M Aug 3 02:12 queue-data13 > 32M Aug 3 03:13 queue-data14 > 32M Aug 3 04:19 queue-data15 > 32M Aug 3 05:20 queue-data16 > 32M Aug 3 06:21 queue-data17 > 32M Aug 3 07:22 queue-data18 > 32M Aug 3 08:23 queue-data19 > 19M Aug 3 09:25 queue-data20 > 8.6K Aug 3 09:52 kaha.idx -- 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] Updated: (AMQ-908) Authorization plugin should have configurable principal classes
[ https://issues.apache.org/activemq/browse/AMQ-908?page=all ]
Hiram Chirino updated AMQ-908:
--
Fix Version/s: 4.2
(was: 4.1.0)
> Authorization plugin should have configurable principal classes
> ---
>
> Key: AMQ-908
> URL: https://issues.apache.org/activemq/browse/AMQ-908
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 4.0.1
>Reporter: Aaron Mulder
> Fix For: 4.2.0, 4.0.3
>
>
> Currently, if you configure the authorization plugin, it assumes that all
> principals listed should be of type
> {{org.apache.activemq.jaas.GroupPrincipal}}. This is OK if you're using
> ActiveMQ LoginModules, but since there's a fairly small supply of those, it
> would be great if you could use arbitrary login modules and tell the
> authorization plugin which principal classes to use. For example,
> {{groupClass="weblogic.security.principal.WLSGroupImpl}} or something like
> that. A good first step would be to let you change the group class. A good
> second step would be to let you specify user and group classes and then
> somehow indicate which names are which (e.g.
> {{admin="administrators,user:aaron,user:bob"}} or whatever). Someday maybe
> it will be nice to support any arbitrary combination of principal classes but
> that seems far away.
> When instantiating the principal classes, I imagine we should use a
> constructor with a single String argument if available, or else a default
> constructor plus a "setName" method, or else I guess bail.
--
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] Updated: (AMQ-943) Pluggable Stomp Message Mapping
[ https://issues.apache.org/activemq/browse/AMQ-943?page=all ] Hiram Chirino updated AMQ-943: -- Fix Version/s: 4.2 (was: 4.1.0) > Pluggable Stomp Message Mapping > --- > > Key: AMQ-943 > URL: https://issues.apache.org/activemq/browse/AMQ-943 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport >Affects Versions: 4.1.0 >Reporter: Dejan Bosanac > Assigned To: Brian McCallister > Fix For: 4.2.0 > > Attachments: protocol-mapping.patch > > > I have finally found time to finish this. Here's the draft version of the > Pluggable Stomp Message Mapping implementation. > Few notes: > - New interface has been defined: ProtocolMapping (I wanted to use the same > name as the message header that we check) > - There are two implementations of this interface: DefaultProtocolMapping and > ByteProtocolMapping > - I used FactoryFinder to create appropriate mapper. The finder use the > following path to find keys: > META-INF/services/org/apache/activemq/transport/mapping/ (we can change this > if you want) > - The appropriate mapper is used according to the "protocol-mapping" header > in the CONNECT message. For example protocol-mapping:byte for > ByteProtocolMapping handler. > - Currently I have implemented only the mapper for BytesMessage since I > wasn't sure whether you want to integrate JSON mapper for MapMessages or > distribute it in a separate library. > - I have changed the test case that tests subscription for byte messages > - This solution is not compatible with current mapping for byte messages. If > you want backward compatibility, I can hard-code it in a ProtocolConverter > class (as it was) since it could not be implemented through this mechanism. > TODO: > - test it more (create more unit test cases and test it more in a real > environment) > - create a proper documentation so others can create their handlers. > - create a proper JavaDoc documentation for key interfaces and classes > - create JSON mapper (integrated or external) > - fix STOMP client(s) > Give it a try and let me know your impressions > Dejan Bosanac -- 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] Updated: (AMQ-979) Allow NetworkConnections to bi-directional
[ https://issues.apache.org/activemq/browse/AMQ-979?page=all ] Hiram Chirino updated AMQ-979: -- Fix Version/s: 4.2 (was: 4.1.0) > Allow NetworkConnections to bi-directional > -- > > Key: AMQ-979 > URL: https://issues.apache.org/activemq/browse/AMQ-979 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Reporter: Rob Davies > Assigned To: Rob Davies > Fix For: 4.2.0 > > > Network connections are generally one way - with messages only flowing out > from the broker that made the network connection. > In order to support WAN hub/spoke - where the central broker is behind a > firewall, and can only receive inbound connections, it is necessary to enable > optional b-idirectional network connections. > This issue was raised on the activemq-dev list: > http://www.nabble.com/Having-some-trouble-making-a-simple-network...-tf2449661.html -- 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] Updated: (AMQ-967) setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but doc says otherwise
[ https://issues.apache.org/activemq/browse/AMQ-967?page=all ] Hiram Chirino updated AMQ-967: -- Fix Version/s: 4.2 (was: 4.1.0) > setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but > doc says otherwise > > > Key: AMQ-967 > URL: https://issues.apache.org/activemq/browse/AMQ-967 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Affects Versions: 4.1.0, 4.0.2 >Reporter: Renaud Bruyeron > Fix For: 4.2.0, 4.0.3 > > Attachments: patch.txt > > > The documentation > (http://incubator.apache.org/activemq/resource-adapter-properties.html) > suggests that setting maximumRedeliveries to -1 means "no maximum", i.e. > infinite retries. > However, my tests (and the code) show that -1 is equivalent to 0 (i.e. no > redelivery). > The patch attempts to fix this. -- 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] Updated: (AMQ-962) Messages are read from queue but not removed
[ https://issues.apache.org/activemq/browse/AMQ-962?page=all ] Hiram Chirino updated AMQ-962: -- Fix Version/s: 4.2 (was: 4.1.0) > Messages are read from queue but not removed > > > Key: AMQ-962 > URL: https://issues.apache.org/activemq/browse/AMQ-962 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client, Broker >Affects Versions: 4.0.1 > Environment: Java Virtual Machine: Java HotSpot(TM) Server VM version > 1.5.0_06-b05JIT > compiler: HotSpot Server Compiler > Operating System: Windows XP 5.1 > Architecture: x86 > Number of processors: 1 > Total physical memory: 1,048,048 kbytes > Free physical memory: 107,240 kbytes > Committed virtual memory: 374,048 kbytes > Total swap space: 2,518,944 kbytes > Free swap space: 721,416 kbytes >Reporter: Randy >Priority: Critical > Fix For: 4.2.0 > > > Using Spring, configured a VM message broker (non-persistant) and a message > consumer that reads messages from queue. > Messages are read from queue, but despite calling message.acknowledge(); > messages remain on the queue (and consume memory). > I turned off optimiseAcknowledge. > May be related to bug# AMQ-716. > > > > > > > class="org.apache.activemq.pool.PooledConnectionFactory"> > > > > vm://localhost > > > false > > > > > class="org.springframework.jms.core.JmsTemplate"> > > > > -- 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] Updated: (AMQ-998) add support for stomp+ssl
[ https://issues.apache.org/activemq/browse/AMQ-998?page=all ] Hiram Chirino updated AMQ-998: -- Fix Version/s: 4.2 (was: 4.1.0) > add support for stomp+ssl > - > > Key: AMQ-998 > URL: https://issues.apache.org/activemq/browse/AMQ-998 > Project: ActiveMQ > Issue Type: New Feature > Components: Transport >Reporter: james strachan > Fix For: 4.2.0 > > -- 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] Updated: (AMQ-984) make the "slave" status of a broker available through JMX (in jdbc-master-slave mode)
[ https://issues.apache.org/activemq/browse/AMQ-984?page=all ] Hiram Chirino updated AMQ-984: -- Fix Version/s: 4.2 (was: 4.1.0) > make the "slave" status of a broker available through JMX (in > jdbc-master-slave mode) > - > > Key: AMQ-984 > URL: https://issues.apache.org/activemq/browse/AMQ-984 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 4.1.0 >Reporter: Renaud Bruyeron >Priority: Minor > Fix For: 4.2.0 > > > Right now, it is not possible to know that a broker is in "Attempting to > acquire the exclusive lock to become the Master broker" mode via JMX, even > though this would be a natural place to find out. > Do you think it would be possible to expose the DatabaseLocker or the > JDBCPersistenceAdapter over JMX so that a simple boolean isMaster() can be > queried? -- 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] Updated: (AMQ-1014) Invalid Schema URL for example config file
[ https://issues.apache.org/activemq/browse/AMQ-1014?page=all ] Hiram Chirino updated AMQ-1014: --- Fix Version/s: 4.2 (was: 4.1.0) > Invalid Schema URL for example config file > -- > > Key: AMQ-1014 > URL: https://issues.apache.org/activemq/browse/AMQ-1014 > Project: ActiveMQ > Issue Type: Bug > Components: Test Cases >Affects Versions: 4.1.0 >Reporter: Bernhard Wellhöfer > Fix For: 4.2.0 > > Attachments: XMLSpy1.png, XMLSpy2.png > > > The config file > https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/spring-embedded-xbean.xml > should ise http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd as schema > URL for Spring 2.0. Moreover and more worse the used schema URL > (http://activemq.org/config/1.0 > http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd) > for ActiveMQ points to a schema file which is not valid. -- 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] Updated: (AMQ-999) Message dispatcher issues (use dedicated dispatching thread for each session)
[ https://issues.apache.org/activemq/browse/AMQ-999?page=all ] Hiram Chirino updated AMQ-999: -- Fix Version/s: 4.2 (was: 4.1.0) > Message dispatcher issues (use dedicated dispatching thread for each session) > - > > Key: AMQ-999 > URL: https://issues.apache.org/activemq/browse/AMQ-999 > Project: ActiveMQ > Issue Type: Improvement > Components: NMS (C# client) >Affects Versions: 4.0.2 > Environment: Windows >Reporter: Rob Lugt > Assigned To: james strachan > Fix For: 4.2.0 > > Attachments: amq999-patch.txt, AtomicBoolean.cs, DispatchingThread.cs > > > There are a number of issues with the dispatching of inbound messages. > - A slow consumer will potentially use and block all ThreadPool threads > - Use of a ThreadPool thread to dispatch a single message is inefficient due > to context switching > - No mechanism to suspend asynchronous delivery to a session (i.e. > Connection.Stop() is currently a no-op) > - Retroactive consumer is currently broken because retoractive messages are > delivered before the listener delegate is assigned. > - [minor] Application cannot predict which thread messages will be dispatched > on > All of these problems can simply be resolved by creating a dedicated > dispatcher thread for a session -- 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] Updated: (AMQ-1010) Simplify SimpleAuthenticationPlugin Configuration
[ https://issues.apache.org/activemq/browse/AMQ-1010?page=all ] Hiram Chirino updated AMQ-1010: --- Fix Version/s: 4.2 (was: 4.1.0) > Simplify SimpleAuthenticationPlugin Configuration > - > > Key: AMQ-1010 > URL: https://issues.apache.org/activemq/browse/AMQ-1010 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 4.1.0 >Reporter: Dejan Bosanac > Fix For: 4.2.0 > > Attachments: simple-auth.patch > > > In order to be useful, SimpleAuthenticationPlugin has to be easy to configure > and well documented. I added some additional logic in order to make it play > well with XBean. The patch also contains an additional class > (AuthenticationUser) and the appropriate test suite. > The example configuration is as follows (taken from simple-auth-broker.xml): > > >password="manager" group="users,admins"/> >password="password" group="users"/> >password="password" group="guests"/> > > > I will make a proper documentation for the "Security" page if this > functionality ever gets committed in the repository. -- 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] Updated: (AMQ-1002) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml
[ https://issues.apache.org/activemq/browse/AMQ-1002?page=all ] Hiram Chirino updated AMQ-1002: --- Fix Version/s: 4.2 (was: 4.1.0) > org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml > - > > Key: AMQ-1002 > URL: https://issues.apache.org/activemq/browse/AMQ-1002 > Project: ActiveMQ > Issue Type: Test >Reporter: Hiram Chirino > Fix For: 4.2.0 > > > Upgrading to spring 2.0 broker this test. Commenting out till we can fix it. -- 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] Updated: (AMQ-1013) Web console does not escape message details (/activemq-web-console/message.jsp)
[ https://issues.apache.org/activemq/browse/AMQ-1013?page=all ] Hiram Chirino updated AMQ-1013: --- Fix Version/s: 4.2 (was: 4.1.0) > Web console does not escape message details > (/activemq-web-console/message.jsp) > --- > > Key: AMQ-1013 > URL: https://issues.apache.org/activemq/browse/AMQ-1013 > Project: ActiveMQ > Issue Type: Improvement > Environment: OS X 10.4.8 / Java 1.5 / ActiveMQ 4.1-SNAPSHOT >Reporter: Stefan Arentz > Fix For: 4.2.0 > > > The web console does not html-escape the message contents on the /message.jsp > page which makes it difficult to see a xml test message. -- 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] Resolved: (AMQ-1031) Message delivered out of order to a MessageListener when session is transced and a rollback occurs.
[ https://issues.apache.org/activemq/browse/AMQ-1031?page=all ] Hiram Chirino resolved AMQ-1031. Resolution: Fixed Fixed in trunk revision 472345 > Message delivered out of order to a MessageListener when session is transced > and a rollback occurs. > --- > > Key: AMQ-1031 > URL: https://issues.apache.org/activemq/browse/AMQ-1031 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > This is actually spotted by a message in the broker log saying that > "Acknowledgment out of sync (Normally occurs when failover connection > reconnects)" or in some previous version of ActiveMQ, an async exception > being delivered to the client with a similar error message. -- 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] Resolved: (AMQ-1032) Avoid a delivery delay on the first redelivery.
[ https://issues.apache.org/activemq/browse/AMQ-1032?page=all ] Hiram Chirino resolved AMQ-1032. Resolution: Fixed Implemented in trunk revision 472345 > Avoid a delivery delay on the first redelivery. > --- > > Key: AMQ-1032 > URL: https://issues.apache.org/activemq/browse/AMQ-1032 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > The first time a message is redelivered, it always waits at the initial > redelivery delay. Since logic may be different to handle a message that has > the redelivered flag enabled, there is a chance that the first time that a > message is redeliver it will not fail the same way the original delivery > failed. We should only start using a redelivery delay on subsequent > redeliveries. -- 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-1032) Avoid a delivery delay on the first redelivery.
Avoid a delivery delay on the first redelivery. --- Key: AMQ-1032 URL: https://issues.apache.org/activemq/browse/AMQ-1032 Project: ActiveMQ Issue Type: Improvement Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 The first time a message is redelivered, it always waits at the initial redelivery delay. Since logic may be different to handle a message that has the redelivered flag enabled, there is a chance that the first time that a message is redeliver it will not fail the same way the original delivery failed. We should only start using a redelivery delay on subsequent redeliveries. -- 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-1031) Message delivered out of order to a MessageListener when session is transced and a rollback occurs.
Message delivered out of order to a MessageListener when session is transced and a rollback occurs. --- Key: AMQ-1031 URL: https://issues.apache.org/activemq/browse/AMQ-1031 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 This is actually spotted by a message in the broker log saying that "Acknowledgment out of sync (Normally occurs when failover connection reconnects)" or in some previous version of ActiveMQ, an async exception being delivered to the client with a similar error message. -- 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] Updated: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
[ https://issues.apache.org/activemq/browse/AMQ-978?page=all ] Hiram Chirino updated AMQ-978: -- Attachment: Net-Stomp-0.31-bytemessage-support.patch I've made a modification to the Net::Stomp 0.31 package so that it can support receiving TextMessage and ByteMessages. We need to feed this back to the upstream maintainer so that it can get back on CPAN. > No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java > JMS Producer/Consumer > --- > > Key: AMQ-978 > URL: https://issues.apache.org/activemq/browse/AMQ-978 > Project: ActiveMQ > Issue Type: Bug > Components: Connector > Environment: This problem seems platform independent: It happens in > Linux, Mac OSX, and Windows. > Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module > Net-Stomp-0.31 >Reporter: Sileshi Kassa > Assigned To: Hiram Chirino > Attachments: Net-Stomp-0.31-bytemessage-support.patch, Publisher.pl, > Subscriber.pl > > > Facts: Perl Stomp client Producer and Consumer works fine >Java JMS client Producer and Consumer works fine > I have also used other Perl Stomp protocol implementation with no problem. > The problem happens when I mix Java and Perl clients > Scenario Test 1: > A. Perl Stomp client Consumer > B. Java JMS client Producer > Scenario Test 2: > A. Java JMS client Consumer > B. Perl Stomp client Producer > I have looked into it via Java JMX management jconsole, and it seems to me > there is a wall between > the stomp server and default server. It the stomp server only passes messages > coming from stomp lients > and default server also does the same. > If this is truly the case, and this is by design, I will be very > disappointed. There should not be any wall. > A message is message irrespective of its source and should be delivered to > any one that is listening > on the same destination. > I will attach the Perl clients testcases. > For Java client, a simple JMS client Producer and Consumer with the same > topic used as > the perl side will do the job. The topic I used on the perl side: > "/topic/Test.CrossDelivery" > and the Java side topic is "Test.CrossDelivery" > This problem is a show stopper for us. -- 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] Reopened: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
[ https://issues.apache.org/activemq/browse/AMQ-978?page=all ] Hiram Chirino reopened AMQ-978: --- Assignee: Hiram Chirino > No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java > JMS Producer/Consumer > --- > > Key: AMQ-978 > URL: https://issues.apache.org/activemq/browse/AMQ-978 > Project: ActiveMQ > Issue Type: Bug > Components: Connector > Environment: This problem seems platform independent: It happens in > Linux, Mac OSX, and Windows. > Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module > Net-Stomp-0.31 >Reporter: Sileshi Kassa > Assigned To: Hiram Chirino > Attachments: Publisher.pl, Subscriber.pl > > > Facts: Perl Stomp client Producer and Consumer works fine >Java JMS client Producer and Consumer works fine > I have also used other Perl Stomp protocol implementation with no problem. > The problem happens when I mix Java and Perl clients > Scenario Test 1: > A. Perl Stomp client Consumer > B. Java JMS client Producer > Scenario Test 2: > A. Java JMS client Consumer > B. Perl Stomp client Producer > I have looked into it via Java JMX management jconsole, and it seems to me > there is a wall between > the stomp server and default server. It the stomp server only passes messages > coming from stomp lients > and default server also does the same. > If this is truly the case, and this is by design, I will be very > disappointed. There should not be any wall. > A message is message irrespective of its source and should be delivered to > any one that is listening > on the same destination. > I will attach the Perl clients testcases. > For Java client, a simple JMS client Producer and Consumer with the same > topic used as > the perl side will do the job. The topic I used on the perl side: > "/topic/Test.CrossDelivery" > and the Java side topic is "Test.CrossDelivery" > This problem is a show stopper for us. -- 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] Resolved: (AMQ-997) Use the ACTIVEMQ_BASE environment variable to support running multiple broker instances from he same activemq install
[ https://issues.apache.org/activemq/browse/AMQ-997?page=all ]
Hiram Chirino resolved AMQ-997.
---
Resolution: Fixed
implemented.
> Use the ACTIVEMQ_BASE environment variable to support running multiple broker
> instances from he same activemq install
> -
>
> Key: AMQ-997
> URL: https://issues.apache.org/activemq/browse/AMQ-997
> Project: ActiveMQ
> Issue Type: New Feature
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> The activemq startup shell scripts are allready using / find the
> ACTIVEMQ_HOME which is where AcitiveMQ has been installed. Currently, you
> can only run one instance of the broker per ActiveMQ installation directory.
> We should support running multiple broker instances using that same
> ACTIVEMQ_HOME. All the per broker instance variable data should be relative
> to a new ACTIVEMQ_BASE enviroment variable.
> By default the ACTIVEMQ_BASE == ACTIVEMQ_HOME so that sarting up the default
> activemq instance continues to behave as it allways has.
> Createing a new per instance directory, as admin should only have to do:
> {code}
> export ACTIVEMQ_BASE=/path/to/new/directory
> mkdir -p ${ACTIVEMQ_BASE}
> cp -R ${ACTIVEMQ_HOME}/conf ${ACTIVEMQ_BASE}
> {code}
> customize the ${ACTIVEMQ_BASE}/conf/activemq.xml file
> And to run the new instance:
> {code}
> export ACTIVEMQ_BASE=/path/to/new/directory
> ${ACTIVEMQ_HOME}/bin/activemq
> {code}
--
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-997) Use the ACTIVEMQ_BASE environment variable to support running multiple broker instances from he same activemq install
[
https://issues.apache.org/activemq/browse/AMQ-997?page=comments#action_37249 ]
Hiram Chirino commented on AMQ-997:
---
Folks sometimes need to add jar files to the ActiveMQ classpath to add a
database driver for example. it is usually added the the ${ACTIVEMQ_HOME}/lib
directory, but to support cases where admins do not want users modifying the
ActiveMQ install directory. We should also add any jars in the
${ACTIVEMQ_BASE}/lib and ${ACTIVEMQ_BASE}/lib/optional directories to the
ActiveMQ classpath.
> Use the ACTIVEMQ_BASE environment variable to support running multiple broker
> instances from he same activemq install
> -
>
> Key: AMQ-997
> URL: https://issues.apache.org/activemq/browse/AMQ-997
> Project: ActiveMQ
> Issue Type: New Feature
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> The activemq startup shell scripts are allready using / find the
> ACTIVEMQ_HOME which is where AcitiveMQ has been installed. Currently, you
> can only run one instance of the broker per ActiveMQ installation directory.
> We should support running multiple broker instances using that same
> ACTIVEMQ_HOME. All the per broker instance variable data should be relative
> to a new ACTIVEMQ_BASE enviroment variable.
> By default the ACTIVEMQ_BASE == ACTIVEMQ_HOME so that sarting up the default
> activemq instance continues to behave as it allways has.
> Createing a new per instance directory, as admin should only have to do:
> {code}
> export ACTIVEMQ_BASE=/path/to/new/directory
> mkdir -p ${ACTIVEMQ_BASE}
> cp -R ${ACTIVEMQ_HOME}/conf ${ACTIVEMQ_BASE}
> {code}
> customize the ${ACTIVEMQ_BASE}/conf/activemq.xml file
> And to run the new instance:
> {code}
> export ACTIVEMQ_BASE=/path/to/new/directory
> ${ACTIVEMQ_HOME}/bin/activemq
> {code}
--
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-997) Use the ACTIVEMQ_BASE environment variable to support running multiple broker instances from he same activemq install
Use the ACTIVEMQ_BASE environment variable to support running multiple broker
instances from he same activemq install
-
Key: AMQ-997
URL: https://issues.apache.org/activemq/browse/AMQ-997
Project: ActiveMQ
Issue Type: New Feature
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
Fix For: 4.1
The activemq startup shell scripts are allready using / find the ACTIVEMQ_HOME
which is where AcitiveMQ has been installed. Currently, you can only run one
instance of the broker per ActiveMQ installation directory. We should support
running multiple broker instances using that same ACTIVEMQ_HOME. All the per
broker instance variable data should be relative to a new ACTIVEMQ_BASE
enviroment variable.
By default the ACTIVEMQ_BASE == ACTIVEMQ_HOME so that sarting up the default
activemq instance continues to behave as it allways has.
Createing a new per instance directory, as admin should only have to do:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
mkdir -p ${ACTIVEMQ_BASE}
cp -R ${ACTIVEMQ_HOME}/conf ${ACTIVEMQ_BASE}
{code}
customize the ${ACTIVEMQ_BASE}/conf/activemq.xml file
And to run the new instance:
{code}
export ACTIVEMQ_BASE=/path/to/new/directory
${ACTIVEMQ_HOME}/bin/activemq
{code}
--
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] Resolved: (AMQ-960) Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN
[ https://issues.apache.org/activemq/browse/AMQ-960?page=all ] Hiram Chirino resolved AMQ-960. --- Resolution: Fixed Assignee: Hiram Chirino > Improved error reporting for SSL and transports. Changed Username for SSL > cert to the DN > > > Key: AMQ-960 > URL: https://issues.apache.org/activemq/browse/AMQ-960 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport >Affects Versions: 4.1 > Environment: all >Reporter: Kelly Campbell > Assigned To: Hiram Chirino > Fix For: 4.1 > > Attachments: activemq-patch-20061006-1.patch, > activemq-patch-20061006-2.patch > > > The attached patch provides better error reporting for transport errors by > reporting the host which was trying to connect. > It also provides a toString for SslTransport to distinguish it from the > regular tcp transport, and includes some improved javadoc for the new SSL > client certificate authentication feature. > Additionally, it changes the username reported through the JMSXUserId field > to be the full distinguished name rather than the username mapped in the > users properties file. -- 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-960) Improved error reporting for SSL and transports. Changed Username for SSL cert to the DN
[ https://issues.apache.org/activemq/browse/AMQ-960?page=comments#action_37202 ] Hiram Chirino commented on AMQ-960: --- Thanks Kelly! patch applied in trunk rev 464659 > Improved error reporting for SSL and transports. Changed Username for SSL > cert to the DN > > > Key: AMQ-960 > URL: https://issues.apache.org/activemq/browse/AMQ-960 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport >Affects Versions: 4.1 > Environment: all >Reporter: Kelly Campbell > Fix For: 4.1 > > Attachments: activemq-patch-20061006-1.patch, > activemq-patch-20061006-2.patch > > > The attached patch provides better error reporting for transport errors by > reporting the host which was trying to connect. > It also provides a toString for SslTransport to distinguish it from the > regular tcp transport, and includes some improved javadoc for the new SSL > client certificate authentication feature. > Additionally, it changes the username reported through the JMSXUserId field > to be the full distinguished name rather than the username mapped in the > users properties file. -- 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-976) Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects.
Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects. Key: AMQ-976 URL: https://issues.apache.org/activemq/browse/AMQ-976 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 If the Transport and TransportListener interfaces can be abstracted even more so that they move around Objects instead of Commands and Responses. This would allow us to use most of the Transport components with other command sets besides the current ActiveMQ one. The main use case I'm thinking of is the possibility of supporting the qpid command set directly by the broker. -- 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] Updated: (AMQ-938) Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable and overriding of the SUNJMX
[ https://issues.apache.org/activemq/browse/AMQ-938?page=all ] Hiram Chirino updated AMQ-938: -- Fix Version/s: 4.0.3 (was: 4.0.2) > Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable > and overriding of the SUNJMX > -- > > Key: AMQ-938 > URL: https://issues.apache.org/activemq/browse/AMQ-938 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.3 > > > This will allow folks to be able to customized thier run enviorment without > having to modify the activemq start script -- 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-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=comments#action_36952 ] Hiram Chirino commented on AMQ-915: --- Applied patch to to 4.0 branch rev 443423 > Failover transport does not replay all the transaction operations on failover. > -- > > Key: AMQ-915 > URL: https://issues.apache.org/activemq/browse/AMQ-915 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Adrian Co > Fix For: 4.1 > > > If transactions are being used on a connection that is using failover.. these > is a small chance that the transaction will fail or the connection will fail > due to a partial tx being run when the client reconnects. > I will change the failover transport to buffer up all the tx operations that > are run against the broker and on failure, replay those operations. -- 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] Updated: (AMQ-922) Add the ability to remove transport connectors dynamically
[ https://issues.apache.org/activemq/browse/AMQ-922?page=all ] Hiram Chirino updated AMQ-922: -- Summary: Add the ability to remove transport connectors dynamically (was: Add a removeConnector() to BrokerServer to remove added transport connectors.) Description: Add a removeConnector() to BrokerServer to remove added transport connectors. > Add the ability to remove transport connectors dynamically > --- > > Key: AMQ-922 > URL: https://issues.apache.org/activemq/browse/AMQ-922 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > Add a removeConnector() to BrokerServer to remove added transport connectors. -- 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] Resolved: (AMQ-923) Add the ability to remove network connectors dynamically
[ https://issues.apache.org/activemq/browse/AMQ-923?page=all ] Hiram Chirino resolved AMQ-923. --- Resolution: Fixed Done in trunk rev 434068 > Add the ability to remove network connectors dynamically > > > Key: AMQ-923 > URL: https://issues.apache.org/activemq/browse/AMQ-923 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- 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-923) Add the ability to remove network connectors dynamically
Add the ability to remove network connectors dynamically Key: AMQ-923 URL: https://issues.apache.org/activemq/browse/AMQ-923 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- 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-922) Add a removeConnector() to BrokerServer to remove added transport connectors.
Add a removeConnector() to BrokerServer to remove added transport connectors. - Key: AMQ-922 URL: https://issues.apache.org/activemq/browse/AMQ-922 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- 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] Work stopped: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Work on AMQ-912 stopped by Hiram Chirino. > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Test Cases, Transport >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- 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-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=comments#action_36934 ] Hiram Chirino commented on AMQ-912: --- Hi Sepand, I reviewed the patch and I noticed that the standard apache licence header is not on the new files included in the patch. Could you please add the headers and create a new diff? Thanks, Hiram > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Test Cases, Transport >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- 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] Resolved: (AMQ-911) Transient connection failure with Failover transport can cause InvalidClientIDException
[ https://issues.apache.org/activemq/browse/AMQ-911?page=all ] Hiram Chirino resolved AMQ-911. --- Resolution: Fixed fix applied to trunk in rev 440588 > Transient connection failure with Failover transport can cause > InvalidClientIDException > --- > > Key: AMQ-911 > URL: https://issues.apache.org/activemq/browse/AMQ-911 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > It shows up as errors on the broker log: > Error occured while processing sync command: > javax.jms.InvalidClientIDException: Broker: localhost - Client: > ID:hchirino-mac.local-51624-1157486953862-2:0 already connected -- 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-911) Transient connection failure with Failover transport can cause InvalidClientIDException
[ https://issues.apache.org/activemq/browse/AMQ-911?page=comments#action_36908 ] Hiram Chirino commented on AMQ-911: --- Easiest way to reporduce it to run the broker on a machine connected with a ethernet cable to 2nd machine. Run the producer example on the second machine with: ant producer -DsleepTime=100 -Dmax=10 -Durl='failover://(tcp://firstmachine:61616)' and connect and disconnect the ethernet cable between the machines. If debug logging is enable on the broker, you should see the error. > Transient connection failure with Failover transport can cause > InvalidClientIDException > --- > > Key: AMQ-911 > URL: https://issues.apache.org/activemq/browse/AMQ-911 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > It shows up as errors on the broker log: > Error occured while processing sync command: > javax.jms.InvalidClientIDException: Broker: localhost - Client: > ID:hchirino-mac.local-51624-1157486953862-2:0 already connected -- 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-911) Transient connection failure with Failover transport can cause InvalidClientIDException
Transient connection failure with Failover transport can cause InvalidClientIDException --- Key: AMQ-911 URL: https://issues.apache.org/activemq/browse/AMQ-911 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.0.2 It shows up as errors on the broker log: Error occured while processing sync command: javax.jms.InvalidClientIDException: Broker: localhost - Client: ID:hchirino-mac.local-51624-1157486953862-2:0 already connected -- 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] Resolved: (AMQ-891) InterruptedException handling tweaks
[ https://issues.apache.org/activemq/browse/AMQ-891?page=all ] Hiram Chirino resolved AMQ-891. --- Fix Version/s: 4.1 4.0.2 Resolution: Fixed Great patch! Applied to trunk rev 439886 and to 4.0 branch rev 439941 > InterruptedException handling tweaks > > > Key: AMQ-891 > URL: https://issues.apache.org/activemq/browse/AMQ-891 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.2 >Reporter: John Heitmann > Assigned To: Hiram Chirino >Priority: Minor > Fix For: 4.1, 4.0.2 > > Attachments: interrupted.patch.gz > > > There were a few spots where the broker was masking the interrupt state after > handling an InterruptedException. This is a lint pass to clean some of that > up. I learned after I made this patch that it's actually slightly better > stylistically to call Thread.interrupt() instead of > Thread.currentThread().interrupt() since it's static and the interrupt state > is global(ish), but this is the version we've tested. -- 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-827) allow the usageManager to be configured in Kb or Mb to make configuration a little easier
[ https://issues.apache.org/activemq/browse/AMQ-827?page=comments#action_36903 ] Hiram Chirino commented on AMQ-827: --- Committed.. trunk rev: 439930 so now you can use any of these to set the limit (it is case insensitive) and ignores extra spaces: limit="20 MB" limit="20M" limit="2 kb" limit="2 k" limit="1G" limit="1 gb" limit="1" rolled back the limitKb limitMb properties since I think it just pollutes the API. > allow the usageManager to be configured in Kb or Mb to make configuration a > little easier > - > > Key: AMQ-827 > URL: https://issues.apache.org/activemq/browse/AMQ-827 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: james strachan > Assigned To: james strachan > Fix For: 4.1 > > > something like > would be much simpler than having to get the > calculator out to type 100 * 1024 * 1024 :) -- 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] Resolved: (AMQ-909) Upgrade to xbean 2.6
[ https://issues.apache.org/activemq/browse/AMQ-909?page=all ] Hiram Chirino resolved AMQ-909. --- Resolution: Fixed done. > Upgrade to xbean 2.6 > > > Key: AMQ-909 > URL: https://issues.apache.org/activemq/browse/AMQ-909 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- 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-827) allow the usageManager to be configured in Kb or Mb to make configuration a little easier
[ https://issues.apache.org/activemq/browse/AMQ-827?page=comments#action_36901 ] Hiram Chirino commented on AMQ-827: --- We can actually support things like limit="20 Mb" now that xbean supports a per property PropertyEditor. The property can stay a long but xbean will convert the value on the fly. Commiting support for this shortly. > allow the usageManager to be configured in Kb or Mb to make configuration a > little easier > - > > Key: AMQ-827 > URL: https://issues.apache.org/activemq/browse/AMQ-827 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: james strachan > Assigned To: james strachan > Fix For: 4.1 > > > something like > would be much simpler than having to get the > calculator out to type 100 * 1024 * 1024 :) -- 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-909) Upgrade to xbean 2.6
Upgrade to xbean 2.6 Key: AMQ-909 URL: https://issues.apache.org/activemq/browse/AMQ-909 Project: ActiveMQ Issue Type: Improvement Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- 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-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=comments#action_36898 ] Hiram Chirino commented on AMQ-855: --- Thanks Vadim, patch applied in trunk rev 439804. Test case passes without error. > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.patch, > ActiveMQMessageConsumer.patch2, PrefetchSubscription.patch, > region.QueueSubscription.java.patch, ZeroPrefetchConsumerTest.java.patch > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- 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-875) TCP connector (server) will stop accepting connection if an invalid connection is made to him.
TCP connector (server) will stop accepting connection if an invalid connection is made to him. -- Key: AMQ-875 URL: https://issues.apache.org/activemq/browse/AMQ-875 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Charles reported on the mailing list: Hi All, We've just had a nasty situation : our ActiveMQ Server standalone plain vanilla TCP Transport, no persistency, no nuffink) on one of our live installations suddenly refused to accept any new connections - no clients could connect. All currently connected clients were fine, and messages were being processed sent and received fine. Just no-one else could connect. After 20 minutes, new connections were suddenly allowed. The following exception was in our log. 2006-Aug-11 12:17:47.726 aqualive [ActiveMQ Transport Server: tcp://blah:61616] ERROR org.apache.activemq.broker.TransportConnector - Could not accept connection: java.net.SocketException: Connection reset by peer: socket write error java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedO utputStream.java:108) at java.io.DataOutputStream.flush(DataOutputStream.java:101) at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:125) at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.jav a:141) at org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormat Negotiator.java:128) at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiato r.java:64) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:52) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:52) at org.apache.activemq.broker.TransportConnection.start(TransportConnection.jav a:75) at org.apache.activemq.broker.TransportConnector$1.onAccept(TransportConnector. java:136) at org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer. java:137) at java.lang.Thread.run(Thread.java:534) My interpretation of the above that something (port scanner maybe ? Our curious IT department ?) is connecting to the listening socket, and the TransportServer is trying to tell the connecting process what the wireformat is - and the connection process is just sitting there, not responding, acknlowedging, or doing anything at all - yet not closing the connection. Therefore, the transport server is blocked, preventing anyone else connecting. After 20 mins - which I am guessing is somekind of lowlevel timeout, seeing as all the default AMQ timeouts seen to be of the order of 1 - 30 secs - a low level TCP exception is thrown, freeing the whole shebang up. I notice there is an InactivityMonitor, and looking at the code there is the following comment // Disable inactivity monitoring while processing a command. Could this be the case ? That - until the wireformat has been negotiated - there is no timeout configured ? Is there anything we can do to reduce this timeout from 20 mins ? Or have I completed gone down the wrong track ? This is AMQ 4.0, Win2K, JRE 1.4.2 Cheers, Charles -- 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] Assigned: (AMQ-815) generate a warning by default if a client connects via openwire using a different release version of the broker
[ https://issues.apache.org/activemq/browse/AMQ-815?page=all ] Hiram Chirino reassigned AMQ-815: - Assignee: Hiram Chirino > generate a warning by default if a client connects via openwire using a > different release version of the broker > --- > > Key: AMQ-815 > URL: https://issues.apache.org/activemq/browse/AMQ-815 > Project: ActiveMQ > Issue Type: Improvement >Reporter: james strachan > Assigned To: Hiram Chirino > Fix For: 4.1 > > > While we can be quite liberal in supporting backwards compatible clients, the > default should be to warn folks if they connect via different versions - as > thats often an indication of classpath issues. > Maybe have 3 options - lenient (try to work with anything), warning (just log > warning on connection), strict (disconnect non-similar version clients) -- 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-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_36651 ] Hiram Chirino commented on AMQ-847: --- your right. the rest of the issue fixed in 4.1 branch rev 426134. > Memory Leaks > > > Key: AMQ-847 > URL: https://issues.apache.org/activemq/browse/AMQ-847 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.3 > > > 1) factoryStats in the connection factory was holding on to connections even > when they are closed. > 2) peer BrokerInfos were never removed even when the peer disconnected. > 3) messages dispatched from a Queue would retain a referece to the client > connection even after they had been acked. > 4) ScheduledThreadPoolExecutor does not always seem to release references to > canceled tasks -- 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] Resolved: (AMQ-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] Hiram Chirino resolved AMQ-847. --- Resolution: Fixed > Memory Leaks > > > Key: AMQ-847 > URL: https://issues.apache.org/activemq/browse/AMQ-847 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.0.3, 4.1 > > > 1) factoryStats in the connection factory was holding on to connections even > when they are closed. > 2) peer BrokerInfos were never removed even when the peer disconnected. > 3) messages dispatched from a Queue would retain a referece to the client > connection even after they had been acked. > 4) ScheduledThreadPoolExecutor does not always seem to release references to > canceled tasks -- 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-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=comments#action_36646 ] Hiram Chirino commented on AMQ-847: --- Fixed in 4.0 branch rev 425922 > Memory Leaks > > > Key: AMQ-847 > URL: https://issues.apache.org/activemq/browse/AMQ-847 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.0.3, 4.1 > > > 1) factoryStats in the connection factory was holding on to connections even > when they are closed. > 2) peer BrokerInfos were never removed even when the peer disconnected. > 3) messages dispatched from a Queue would retain a referece to the client > connection even after they had been acked. > 4) ScheduledThreadPoolExecutor does not always seem to release references to > canceled tasks -- 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-847) Memory Leaks
Memory Leaks Key: AMQ-847 URL: https://issues.apache.org/activemq/browse/AMQ-847 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.0.3, 4.1 1) factoryStats in the connection factory was holding on to connections even when they are closed. 2) peer BrokerInfos were never removed even when the peer disconnected. 3) messages dispatched from a Queue would retain a referece to the client connection even after they had been acked. 4) ScheduledThreadPoolExecutor does not always seem to release references to canceled tasks -- 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-846) Change the maven pom group id to org.apache.activemq and the version to be 4.1-incubator-SNAPSHOT
Change the maven pom group id to org.apache.activemq and the version to be 4.1-incubator-SNAPSHOT - Key: AMQ-846 URL: https://issues.apache.org/activemq/browse/AMQ-846 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- 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
