[jira] Commented: (SM-1048) Camel InOut support
[ https://issues.apache.org/activemq/browse/SM-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40081 ] James Strachan commented on SM-1048: FWIW to ease the Camel - ServiceMix integration; Camel's Exchange now has an ExchangePattern enum to handle InOut, InOnly etc Camel InOut support --- Key: SM-1048 URL: https://issues.apache.org/activemq/browse/SM-1048 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.2 Reporter: Dejan Predovic Assignee: Guillaume Nodet Fix For: 3.2 Attachments: inout.patch CamelJbiEndpoint and ToJbiProcessor do not support InOut exchanges. The attached patch should add the basic support for it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQ-1134) stomp connections in the broker don't get cleared up if the socket dies
stomp connections in the broker don't get cleared up if the socket dies --- Key: AMQ-1134 URL: https://issues.apache.org/activemq/browse/AMQ-1134 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Assigned To: james strachan Fix For: 4.1.1, 4.2.0 it looks like there's a bug causing the connection to keep around -- 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-1134) stomp connections in the broker don't get cleared up if the socket dies
[ https://issues.apache.org/activemq/browse/AMQ-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved AMQ-1134. - Resolution: Fixed stomp connections in the broker don't get cleared up if the socket dies --- Key: AMQ-1134 URL: https://issues.apache.org/activemq/browse/AMQ-1134 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Assigned To: james strachan Fix For: 4.1.1, 4.2.0 it looks like there's a bug causing the connection to keep around -- 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-1067) Stomp consumer not removed if client does not send disconnect message.
[ https://issues.apache.org/activemq/browse/AMQ-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved AMQ-1067. - Resolution: Fixed Fix Version/s: 4.2.0 4.1.1 Stomp consumer not removed if client does not send disconnect message. -- Key: AMQ-1067 URL: https://issues.apache.org/activemq/browse/AMQ-1067 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.1.0 Environment: Solaris 10, Perl 5.8.4 Reporter: Chris Knight Priority: Critical Fix For: 4.1.1, 4.2.0 Attachments: perl.tar.gz Run clearQueue.pl TEST.QUEUE Check in jconsole. The client will still be marked as active even when the script is killed. This prevents any meaningful use of queues if any consumption is done via stomp. -- 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-1130) MySql should use LONGBLOB rather than BLOB for persisting messages to avoid the 64k limit
MySql should use LONGBLOB rather than BLOB for persisting messages to avoid the 64k limit - Key: AMQ-1130 URL: https://issues.apache.org/activemq/browse/AMQ-1130 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Assigned To: james strachan Fix For: 4.1.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] Resolved: (AMQ-1130) MySql should use LONGBLOB rather than BLOB for persisting messages to avoid the 64k limit
[ https://issues.apache.org/activemq/browse/AMQ-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved AMQ-1130. - Resolution: Fixed MySql should use LONGBLOB rather than BLOB for persisting messages to avoid the 64k limit - Key: AMQ-1130 URL: https://issues.apache.org/activemq/browse/AMQ-1130 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Assigned To: james strachan Fix For: 4.1.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] Resolved: (AMQ-1114) ActiveMQ Queue management- How to kill a queue?
[ https://issues.apache.org/activemq/browse/AMQ-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved AMQ-1114. - Resolution: Fixed Fix Version/s: 4.1.0 See the methods on the Queue MBean such as purge() to delete all messages on a queue http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/QueueViewMBean.html#purge() ActiveMQ Queue management- How to kill a queue? --- Key: AMQ-1114 URL: https://issues.apache.org/activemq/browse/AMQ-1114 Project: ActiveMQ Issue Type: Bug Components: Broker, JCA Container Affects Versions: 4.0.1 Environment: Windows XP, Jdk 1.5, ActiveMQ4.0.1 Reporter: Vairavan Chandrasekhar Fix For: 4.1.0 ActiveMQ: Through 'jconsole' we can view all the java components which ever is active. So by this way, we can see the particular queue and also we can able to find how many customers are listening. But I want to manage the queue, like I want to kill a particular queue. Can anybody help me how to proceed with? It's pleasure to explain more if you are not clear. Thanks in advance Shekar -- 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-1093) Client deadlock during failover
[ https://issues.apache.org/activemq/browse/AMQ-1093?page=all ] james strachan resolved AMQ-1093. - Fix Version/s: 4.2.0 Resolution: Fixed I've just committed a patch to trunk for this which I think resolves the issue. There's no test case to easily verify its resolved though (its a tad hard to recreate) so I wonder could you try and see if this is now fixed - if not let us know and we can reopen this issue Client deadlock during failover --- Key: AMQ-1093 URL: https://issues.apache.org/activemq/browse/AMQ-1093 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 4.1.0 Environment: Linux 2.6, java 1.5.0 Reporter: Danielius Jurna Priority: Critical Fix For: 4.2.0 In 4.1.0 there's deadlock on connection failover. There is the scenario: 1. Client consumes message using message listener 2. Conection is lost 3. Client sends message to another queue from messagle listener and waits until connection is restored. 4. Reconnect task blocks on reconnecting. This bug is new to 4.1.0. The problem is in ActiveMQMessageConsumre.dispatch . There is new lock on unconsumedMessages.getMutex() . So the reconnect task cannot invoke ActiveMQMessageConsumre.clearMessagesInProgress(), because lock is acquired by message listener, which waits untill message is sent (untill connection is resumed). Here is stack traces: ActiveMQ Session Task daemon prio=1 tid=0x002b27774260 nid=0x4778 in Object.wait() [0x40ef3000..0x40ef4db0] at java.lang.Object.wait(Native Method) - waiting on 0x002b0020a7c8 (a edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) at java.lang.Object.wait(Object.java:474) at edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75) - locked 0x002b0020a7c8 (a edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) at edu.emory.mathcs.backport.java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:318) at org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:42) at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:75) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1171) at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1548) at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465) at org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:75) - locked 0x002b173fa480 (a org.apache.activemq.ActiveMQMessageProducer) at org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:60) at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:537) at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:513) at org.springframework.jms.core.JmsTemplate$2.doInJms(JmsTemplate.java:479) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:430) at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:477) at lt.elitnet.dbp.das.impl.storage.HI2StorageImpl.storeHI2Message(HI2StorageImpl.java:57) at lt.elitnet.dbp.das.impl.hi2.HI2PersistanceBase.saveIRIContent(HI2PersistanceBase.java:77) at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:203) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:162) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) at org.springframework.orm.hibernate3.HibernateInterceptor.invoke(HibernateInterceptor.java:104) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) at lt.elitnet.dbp.das.impl.alarming.DataBaseConnectionAlarmsPublisher.invoke(DataBaseConnectionAlarmsPublisher.java:59) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) at
[jira] Commented: (AMQ-591) add a per message authorization hook so that content-based authorization can be performed using a special plugin
[ https://issues.apache.org/activemq/browse/AMQ-591?page=comments#action_37642 ] james strachan commented on AMQ-591: Here's the latest links... http://incubator.apache.org/activemq/security.html add a per message authorization hook so that content-based authorization can be performed using a special plugin Key: AMQ-591 URL: https://issues.apache.org/activemq/browse/AMQ-591 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan Fix For: 4.0 RC2 Users may want to look in the message at headers to decide if a user can or cannot consume a 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] Created: (AMQ-1091) add a source distro to the maven2 build
add a source distro to the maven2 build --- Key: AMQ-1091 URL: https://issues.apache.org/activemq/browse/AMQ-1091 Project: ActiveMQ Issue Type: Improvement 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] Resolved: (AMQ-1050) browse -QTopic=* does not seem to return anything...
[ https://issues.apache.org/activemq/browse/AMQ-1050?page=all ] james strachan resolved AMQ-1050. - Resolution: Fixed browse -QTopic=* does not seem to return anything... Key: AMQ-1050 URL: https://issues.apache.org/activemq/browse/AMQ-1050 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.x Reporter: james strachan Assigned To: Adrian Co Fix For: 4.1.1, 4.2.0 I think there's something funny going on in the regex stuff. I tried from the SimpleConsole typing query -QTopic=* and I get nothing. query returns tons of stuff though. I wonder if it might be simpler to have specific arguments for topic and queues? query -topic=* queyr -queue=* to avoid the complex regex of ObjectName 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] Resolved: (AMQ-992) MySQL doesn't honor lock in JDBC Master Slave configuration?
[ https://issues.apache.org/activemq/browse/AMQ-992?page=all ] james strachan resolved AMQ-992. Fix Version/s: 4.1.1 4.2.0 Resolution: Fixed MySQL doesn't honor lock in JDBC Master Slave configuration? Key: AMQ-992 URL: https://issues.apache.org/activemq/browse/AMQ-992 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1.0 Environment: RHEL 4 MySQL 4.x, 5.x mysql-ab_jdbc_driver Reporter: Steven Lotito Fix For: 4.1.1, 4.2.0 Attachments: mysql_obtain_lock.txt I have been attempting to get the new 4.1 JDBC Master Slave configuration working with MySQL. The log from the first broker to start up states: 2006-10-18 09:35:08,558 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker 2006-10-18 09:35:08,559 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] The 2nd broker to start up has an identical message and both brokers listen for connections. The 2nd broker should be waiting for the lock and NOT accepting connections, if I understand http://www.activemq.org/site/jdbc-master-slave.html correctly... Oracle exhibits the expected behavior: When running the exact same configuration (except using an Oracle datasource), the first broker has the same log message as above, while the 2nd broker halts at the Attempting to acquire the exclusive lock to become the Master broker message until I fail the master. Then it becomes the master. Is this a known issue? I was able to replicate it using both MySql 4 and 5 (trying both the MySQL Connector/J 3.1 and MySQL Connector/J 5.0 drivers) -- 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-756) Hangs on creating topic on Windows XP 2002 SP2
[ https://issues.apache.org/activemq/browse/AMQ-756?page=all ] james strachan resolved AMQ-756. Fix Version/s: 4.1.0 Resolution: Cannot Reproduce AFAIK this is now resolved. Let us know and we can reopen if required Hangs on creating topic on Windows XP 2002 SP2 -- Key: AMQ-756 URL: https://issues.apache.org/activemq/browse/AMQ-756 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0 M4 Environment: Windows 2002 XP SP2 Reporter: shantharam Fix For: 4.1.0 On windows server when trying to create a Topic Session code just hangs, here is the Thread Dump, same code works fine Unix and Linux environment StackTrace Remote Thread prio=5 tid=0x0444a1a0 nid=0x15ac runnable [0..55dfb9c] tcp://dubxww11hr/10.251.116.216:29258 prio=5 tid=0x04454868 nid=0xcf4 runnable [550f000..550fd8c] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:48) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:55) at java.io.DataInputStream.readInt(DataInputStream.java:443) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:180) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:135) at java.lang.Thread.run(Thread.java:534) Thread-0 daemon prio=5 tid=0x03733c30 nid=0x508 in Object.wait() [42df000..42dfd8c] at java.lang.Object.wait(Native Method) - waiting on 0x12cb01c8 (a java.util.TaskQueue) at java.util.TimerThread.mainLoop(Timer.java:429) - locked 0x12cb01c8 (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:382) Signal Dispatcher daemon prio=10 tid=0x008ad9f0 nid=0xf8c runnable [0..0] Finalizer daemon prio=9 tid=0x008aafa0 nid=0x1328 in Object.wait() [2faf000..2fafd8c] at java.lang.Object.wait(Native Method) - waiting on 0x12d6cac0 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111) - locked 0x12d6cac0 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x008a9c20 nid=0x760 in Object.wait() [2eaf000..2eafd8c] at java.lang.Object.wait(Native Method) - waiting on 0x12d6cb28 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:429) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115) - locked 0x12d6cb28 (a java.lang.ref.Reference$Lock) main prio=5 tid=0x00037c50 nid=0x1650 in Object.wait() [7e000..7fc3c] at java.lang.Object.wait(Native Method) - waiting on 0x101deeb0 (a edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch) at java.lang.Object.wait(Object.java:429) at edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:173) - locked 0x101deeb0 (a edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch) at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:61) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44) - locked 0x101efb00 (a java.lang.Object) at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:62) at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:67) at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1068) at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1132) at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:251) at org.apache.activemq.ActiveMQConnection.createTopicSession(ActiveMQConnection.java:845) at com.sterlingcommerce.woodstock.event.RemoteEventProcessorImpl.init(RemoteEventProcessorImpl.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at
[jira] Resolved: (AMQ-761) ActiveMQConnectionFactory.setBrokerURL does not set all connection properties corrrectly
[ https://issues.apache.org/activemq/browse/AMQ-761?page=all ]
james strachan resolved AMQ-761.
Fix Version/s: 4.1.0
Resolution: Fixed
ActiveMQConnectionFactory.setBrokerURL does not set all connection properties
corrrectly
Key: AMQ-761
URL: https://issues.apache.org/activemq/browse/AMQ-761
Project: ActiveMQ
Issue Type: Bug
Components: JMS client
Affects Versions: 3.2.2
Environment: Windows XP, Java 1.4.1
Reporter: Jim Beattie
Fix For: 4.1.0
Attachments: UrlSetterTest.java
If I set the brokerUrl of ActiveMQConnectionFactory using setBrokerURL(), the
connection factory does not reparse all of the properties from the URL. As a
result, when a new connection is created, some of the properties from the URL
specified during the construction of the connection factory (typically the
defaults) are used instead. Attached is a unit test to demonstrate the
problem.
As a minimum, the following block of code is required in setBrokerURL(). But
this doesn't really fix it because properties settings from the URL used by
the constructor may not be reset by this code. A structural change may be in
order (e.g. just-in-time parsing of the properties).
if( brokerURL.indexOf(?)= 0 ) {
String options = brokerURL.substring(brokerURL.indexOf(?)+1);
Map properties = URIHelper.parseQuery(options);
if (!properties.isEmpty()) {
BeanUtils.populate(this, properties);
}
--
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-1072) TimeToLive doesn't work on MessageListener
[ https://issues.apache.org/activemq/browse/AMQ-1072?page=all ] james strachan resolved AMQ-1072. - Fix Version/s: 4.1.0 Resolution: Fixed This has been fixed in 4.1 TimeToLive doesn't work on MessageListener Key: AMQ-1072 URL: https://issues.apache.org/activemq/browse/AMQ-1072 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 4.0.1 Reporter: Joseph Leung Fix For: 4.1.0 When a queue message is consumed using MessageListener throught the setMessageListener method, it could recieve the messages even if they are expired. (While using consumer.receive() will discard them). Reproduce Steps: 1. deliver a number of message to a queue with a short expire time. 2. wait until the message should be expired. 3. use MessageConsumer.receive() method to receive the messages, -- You should not receive any messages, and through the monitor console, you should see some messages are left and not discarded. 4. stop the receive() method. 5. add a MessageListener to the same queue, the messages which found left is received by the onMessage() method. ps. if step3 is skipped, likely you would receive all the expired 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-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ] james strachan updated AMQ-1054: Fix Version/s: 4.1.1 updated fix versions XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0, 4.1.1 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37576 ] james strachan commented on AMQ-1054: - Just to make absolutely sure, I've added the test case into the 4.0 branch too https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.0/activemq-test-atomikos/ and the test case works fine. I wonder if these tests fail on a specific platform only? I wonder could someone try running these test cases on Windows (am an OS X / unix person myself) BTW I tried Java 1.4.2 with the 4.0 branch (which is basically 4.0.2) XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Created: (AMQ-1074) support JDBC master slave on MySQL
support JDBC master slave on MySQL -- Key: AMQ-1074 URL: https://issues.apache.org/activemq/browse/AMQ-1074 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 We need to make a few changes to support MySQL's SQL dialect for JDBC Master Slave... http://incubator.apache.org/activemq/jdbc-master-slave.html For details see this thread... http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369 -- 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-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37580 ] james strachan commented on AMQ-1054: - Hi Guy Just to be sure - are you saying the bug doesn't happen for you on OSX/Unix? i.e. its a windows only bug? XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37581 ] james strachan commented on AMQ-1054: - Shoaib - I wonder could you try using ActiveMQ trunk (or tomorrows nightly snapshot build of 4.2-SNAPSHOT) to see if I've fixed the bug for you on your environment? I think I've nailed the ClassCastException you're seeing - am just not yet sure of the magic incantations to reproduce it so I can know for sure its fixed XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Commented: (AMQ-1074) support JDBC master slave on MySQL
[ https://issues.apache.org/activemq/browse/AMQ-1074?page=comments#action_37583 ] james strachan commented on AMQ-1074: - Patch applied to trunk - which seems to work for me with MySQL Connector/J 5.0.4. support JDBC master slave on MySQL -- Key: AMQ-1074 URL: https://issues.apache.org/activemq/browse/AMQ-1074 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 We need to make a few changes to support MySQL's SQL dialect for JDBC Master Slave... http://incubator.apache.org/activemq/jdbc-master-slave.html For details see this thread... http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369 -- 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-1075) support for FileMessage interface to support in-band and out-of-band file transfer
support for FileMessage interface to support in-band and out-of-band file
transfer
--
Key: AMQ-1075
URL: https://issues.apache.org/activemq/browse/AMQ-1075
Project: ActiveMQ
Issue Type: New Feature
Components: Broker
Reporter: james strachan
Fix For: 4.2.0
Some new API like this...
public class ActiveMQSession {
// send a local file or stream over JMS
public FileMessage createLocalFileMessage(InputStream inputStream) {...}
public FileMessage createLocalFileMessage(File file) {..,}
public FileMessage createLocalFileMessage(URL url) {..,}
// send a remote URL over JMS
public FileMessage createRemoteFileMessage(URL url) {...}
}
with FileMessage like this...
public interface FileMessage extends Message {
// access the remote resource
// or for local resources, force creation of temporary file
// so this resource can be parsed multiple times etc
URL getURL();
InputStream getInputStream();
}
For further discussion see
http://www.nabble.com/support-for-FileMessage--tf2641673.html#a7373916
--
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-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ] james strachan resolved AMQ-1054. - Fix Version/s: 4.2.0 Resolution: Fixed Aha! So the reason the test case was working that I checked into trunk and 4.0 branch was due to the fact that the test was using the VM transport - which tends to avoid mashalling to and from a socket, so not causing the bug. Have patched the test case both in trunk and in the 4.0 branch. The one in the 4.0 branch now does indeed fail with the ClassCastException. The one in trunk passes with flying colours. So this issue is now resolved and will go out as part of the 4.2 release. If we cut a 4.1.x bug fix release this fix can be back ported for that too XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37589 ] james strachan commented on AMQ-1054: - Have backported the test case and fix to 4.1 branch too if we release a new bug fix release of 4.1 before 4.2 XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no 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] Commented: (AMQ-1068) DestinationMap seems to use up lots of RAM if using deep hierarchies
[ https://issues.apache.org/activemq/browse/AMQ-1068?page=comments#action_37564 ] james strachan commented on AMQ-1068: - The fix was done in r478324 on trunk if folks wanna backport DestinationMap seems to use up lots of RAM if using deep hierarchies Key: AMQ-1068 URL: https://issues.apache.org/activemq/browse/AMQ-1068 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.1.0, 4.0.2 Reporter: james strachan Assigned To: 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] Created: (AMQ-1073) support selectors in virtual destinations to allow a message to be dispatched to multiple phyiscal queues if it matches the selector
support selectors in virtual destinations to allow a message to be dispatched to multiple phyiscal queues if it matches the selector Key: AMQ-1073 URL: https://issues.apache.org/activemq/browse/AMQ-1073 Project: ActiveMQ Issue Type: Improvement Components: Broker Reporter: james strachan Assigned To: 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] Created: (AMQ-1068) DestinationMap seems to use up lots of RAM if using deep hierarchies
DestinationMap seems to use up lots of RAM if using deep hierarchies Key: AMQ-1068 URL: https://issues.apache.org/activemq/browse/AMQ-1068 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.1.0, 4.0.2 Reporter: james strachan Assigned To: 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] Resolved: (AMQ-1068) DestinationMap seems to use up lots of RAM if using deep hierarchies
[ https://issues.apache.org/activemq/browse/AMQ-1068?page=all ] james strachan resolved AMQ-1068. - Resolution: Fixed see the test case DestinationMapMemoryTest which used to blow up and create OutOfMemory before the patch DestinationMap seems to use up lots of RAM if using deep hierarchies Key: AMQ-1068 URL: https://issues.apache.org/activemq/browse/AMQ-1068 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.1.0, 4.0.2 Reporter: james strachan Assigned To: 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] Created: (AMQ-1055) support for FileMessage to allow easy transfer of attachments
support for FileMessage to allow easy transfer of attachments - Key: AMQ-1055 URL: https://issues.apache.org/activemq/browse/AMQ-1055 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Fix For: 4.3.0 For more background see... http://weblogs.java.net/blog/guruwons/archive/2006/11/sending_large_f.html http://www.nabble.com/support-for-FileMessage--tf2641673.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] Assigned: (AMQ-1048) Some tools from Command line not works properly
[ https://issues.apache.org/activemq/browse/AMQ-1048?page=all ] james strachan reassigned AMQ-1048: --- Assignee: Adrian Co Some tools from Command line not works properly --- Key: AMQ-1048 URL: https://issues.apache.org/activemq/browse/AMQ-1048 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.1 Environment: Tested in Windows XP Professional and Linux Debian Sarge Reporter: Lucas GPL Assigned To: Adrian Co Priority: Critical Original Estimate: 2 days Remaining Estimate: 2 days Some command line not works properly, just return de prompt Example: query -QQueue=* query --objname Type=Connect,BrokerName=localhost -xQNetworkConnector=* 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] Commented: (AMQ-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus
[ https://issues.apache.org/activemq/browse/AMQ-1053?page=comments#action_37464 ] james strachan commented on AMQ-1053: - MessageTransformer interface is now in SVN along with an implementation, XStreamMessagegeTransformer in activemq-optional which can be used to turn ObjectMessages into XML on the bus. See the XStreamTransformTest for an example of its use allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus Key: AMQ-1053 URL: https://issues.apache.org/activemq/browse/AMQ-1053 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan Fix For: 4.2.0 For example a user may wish to use ObjectMessage in their code - but in deployment use a TextMessage with XStream or JAXB as the marshalling. -- 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-1051) be able to interact with the broker via messaging
[ https://issues.apache.org/activemq/browse/AMQ-1051?page=all ] james strachan resolved AMQ-1051. - Fix Version/s: 4.2.0 Resolution: Fixed Its described here http://activemq.org/site/command-agent.html be able to interact with the broker via messaging - Key: AMQ-1051 URL: https://issues.apache.org/activemq/browse/AMQ-1051 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Fix For: 4.2.0 Send a text message over JMS, XMPP, Stomp, Ajax or REST to communicate with the broker, query queues/topics 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] Resolved: (AMQ-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus
[ https://issues.apache.org/activemq/browse/AMQ-1053?page=all ] james strachan resolved AMQ-1053. - Resolution: Fixed For documentation see here: http://activemq.org/site/message-transformation.html allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus Key: AMQ-1053 URL: https://issues.apache.org/activemq/browse/AMQ-1053 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan Fix For: 4.2.0 For example a user may wish to use ObjectMessage in their code - but in deployment use a TextMessage with XStream or JAXB as the marshalling. -- 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-1050) browse -QTopic=* does not seem to return anything...
browse -QTopic=* does not seem to return anything... Key: AMQ-1050 URL: https://issues.apache.org/activemq/browse/AMQ-1050 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.x Reporter: james strachan Assigned To: Adrian Co Fix For: 4.2.0 I think there's something funny going on in the regex stuff. I tried from the SimpleConsole typing query -QTopic=* and I get nothing. query returns tons of stuff though. I wonder if it might be simpler to have specific arguments for topic and queues? query -topic=* queyr -queue=* to avoid the complex regex of ObjectName 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] Created: (AMQ-1051) be able to interact with the broker via messaging
be able to interact with the broker via messaging - Key: AMQ-1051 URL: https://issues.apache.org/activemq/browse/AMQ-1051 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Send a text message over JMS, XMPP, Stomp, Ajax or REST to communicate with the broker, query queues/topics 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] Commented: (AMQ-1051) be able to interact with the broker via messaging
[ https://issues.apache.org/activemq/browse/AMQ-1051?page=comments#action_37455 ] james strachan commented on AMQ-1051: - Code checked in - could use some documentation. Currently if you can send a message to the Topic *ActiveMQ.Agent* it will be interpreted as an activemq-console command. So the following kinds of commands are available * help * list * query * browse etc. I've tested it with XMPP so you can chat via Jabber to the broker! :) http://incubator.apache.org/activemq/xmpp.html The best way to get started is to run the web console http://incubator.apache.org/activemq/web-console.html be able to interact with the broker via messaging - Key: AMQ-1051 URL: https://issues.apache.org/activemq/browse/AMQ-1051 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: james strachan Send a text message over JMS, XMPP, Stomp, Ajax or REST to communicate with the broker, query queues/topics 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-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus
[ https://issues.apache.org/activemq/browse/AMQ-1053?page=all ] james strachan updated AMQ-1053: Fix Version/s: 4.2.0 allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus Key: AMQ-1053 URL: https://issues.apache.org/activemq/browse/AMQ-1053 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan Fix For: 4.2.0 For example a user may wish to use ObjectMessage in their code - but in deployment use a TextMessage with XStream or JAXB as the marshalling. -- 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-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus
allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus Key: AMQ-1053 URL: https://issues.apache.org/activemq/browse/AMQ-1053 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Assigned To: james strachan For example a user may wish to use ObjectMessage in their code - but in deployment use a TextMessage with XStream or JAXB as the marshalling. -- 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-1036) web-console broken (queue browsing).
[ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]
james strachan reopened AMQ-1036:
-
Could you apply this fix to the 4-1 branch too please?
https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.1/
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.1.0
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-1018) Tomcat JVM hangs when it tried to get ConnectionFactory object
[ https://issues.apache.org/activemq/browse/AMQ-1018?page=all ] james strachan updated AMQ-1018: Fix Version/s: 4.0.3 (was: 4.0.2) Tomcat JVM hangs when it tried to get ConnectionFactory object -- Key: AMQ-1018 URL: https://issues.apache.org/activemq/browse/AMQ-1018 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.1 Environment: Tomcat 5.5.9, Activemq 4.0.1 Reporter: Suvarna Raju Madhey Priority: Critical Fix For: 4.0.3 Attachments: StackTrace I have deployed my application in Tomcat 5.5.9, which uses Activemq 4.0.1. To get ConnectionFactory I have written a method called getConnectionFactory. Following way i am tring to lookup.. Context ctx = new InitialContext(); Context ctx2= (Context) initCtx.lookup(java:comp/env); ConnectionFactory cf = (ConnectionFactory) ctx2.lookup(jms/ConnectionFactory); 3 iterations of start and stop works successfully. But when I start the application 4th time, it executes Context ctx2 = (Context)initCtx.lookup(java:comp/env); then it goes to next line. After that it never returns ConnectionFactory. After I notice that the application hangs.. Please find the stack which i got by running kill -3 tomcat-process-pid -- 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-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] james strachan updated AMQ-847: --- Fix Version/s: 4.0.3 (was: 4.0.2) 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 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-1028) AMQ Stops dispatching messages after a period of time without errors/warnings
[ https://issues.apache.org/activemq/browse/AMQ-1028?page=comments#action_37408 ] james strachan commented on AMQ-1028: - A badly behaved consumer can't bring the entire messaging system down. Dealing with slow consumers on non-persistent messaging is a common problem though - either increase the RAM, enforce persistence or use slow consumer handling... http://incubator.apache.org/activemq/slow-consumer-handling.html AMQ Stops dispatching messages after a period of time without errors/warnings - Key: AMQ-1028 URL: https://issues.apache.org/activemq/browse/AMQ-1028 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.2 Environment: Os: Ubuntu Linux i386 - Java: J2RE SE 1.5.0_08-b03 Reporter: Bas van Beek Priority: Critical Fix For: 4.0.2 The ActiveMQ stand alone server seems to stop dispatching messages to topics after a period of time. New clients can connect... new subscriptions to topics can be made... no errors are shown... messages are just not sent... including to and from the new clients... No errors or warnings can be found in the ActiveMQ.log (even in debug mode) JConsole doesn't show the new messages coming in (EnqueueCount doesn't change) Stomp Protocol is used exclusively -- 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-1017) Build of current trunk with Maven2 fails
[ https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37391 ] james strachan commented on AMQ-1017: - I've tried trashing the local repo too - and it still works fine for me. I'm kinda mystified why its failing for you. Build of current trunk with Maven2 fails Key: AMQ-1017 URL: https://issues.apache.org/activemq/browse/AMQ-1017 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06 Reporter: Bernhard Wellhöfer Priority: Critical Attachments: mvn.log, mvn.log, mvn.log A build of a fresh checkout from https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. See the attached log of the build. -- 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-1017) Build of current trunk with Maven2 fails
[ https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37392 ] james strachan commented on AMQ-1017: - I guess we need someone else with a windows machine to trash their local repo and try again - it could be a windows-only-with-no-local-repo issue Build of current trunk with Maven2 fails Key: AMQ-1017 URL: https://issues.apache.org/activemq/browse/AMQ-1017 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06 Reporter: Bernhard Wellhöfer Priority: Critical Attachments: mvn.log, mvn.log, mvn.log A build of a fresh checkout from https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. See the attached log of the build. -- 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-1034) bad acknowledgement messages when rolling back on a large queue
bad acknowledgement messages when rolling back on a large queue --- Key: AMQ-1034 URL: https://issues.apache.org/activemq/browse/AMQ-1034 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2, 4.1 Reporter: james strachan Assigned To: james strachan See the test case RollbacksWhileConsumingLargeQueueTest for details of how to reproduce -- 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-1034) bad acknowledgement messages when rolling back on a large queue
[ https://issues.apache.org/activemq/browse/AMQ-1034?page=all ] james strachan resolved AMQ-1034. - Fix Version/s: 4.0.3 4.1 Resolution: Fixed hiram fixed this in trunk revision 472345. I've just back ported it to 4.0.x in revision: 472423 bad acknowledgement messages when rolling back on a large queue --- Key: AMQ-1034 URL: https://issues.apache.org/activemq/browse/AMQ-1034 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2, 4.1 Reporter: james strachan Assigned To: james strachan Fix For: 4.0.3, 4.1 See the test case RollbacksWhileConsumingLargeQueueTest for details of how to reproduce -- 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-1036) web-console broken (queue browsing).
[
https://issues.apache.org/activemq/browse/AMQ-1036?page=comments#action_37369 ]
james strachan commented on AMQ-1036:
-
Which version are you using? Its working for me on the 4.1-SNAPSHOT
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
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] Assigned: (AMQ-1015) ActiveMQ web-demo and web-console cannot be run
[ https://issues.apache.org/activemq/browse/AMQ-1015?page=all ] james strachan reassigned AMQ-1015: --- Assignee: james strachan (was: Patrick Villacorta) ActiveMQ web-demo and web-console cannot be run --- Key: AMQ-1015 URL: https://issues.apache.org/activemq/browse/AMQ-1015 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 4.1, 4.0.2 Reporter: Adrian Co Assigned To: james strachan Fix For: 4.1, 4.0.3 Let's update the maven plugin from maven-jetty-plugin to maven-jetty6-plugin for the 4.1.x branch and the 4.0.x branch. The web-console is throwing this exception after: java.lang.NoSuchMethodError: org.mortbay.jetty.webapp.WebAppClassLoader.getUrlClassPath()Ljava/lang/String; at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.configureClassLoader(Jetty6MavenConfiguration.jav a:62) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119) at org.mortbay.jetty.Server.doStart(Server.java:210) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:115) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:318) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:268) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor. java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx ecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja va:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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-1015) ActiveMQ web-demo and web-console cannot be run
[ https://issues.apache.org/activemq/browse/AMQ-1015?page=comments#action_37327 ] james strachan commented on AMQ-1015: - Please keep the maven-jetty-plugin as this is the new version. The maven-jetty6-plugin is old! ActiveMQ web-demo and web-console cannot be run --- Key: AMQ-1015 URL: https://issues.apache.org/activemq/browse/AMQ-1015 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 4.1, 4.0.2 Reporter: Adrian Co Assigned To: Patrick Villacorta Fix For: 4.1, 4.0.3 Let's update the maven plugin from maven-jetty-plugin to maven-jetty6-plugin for the 4.1.x branch and the 4.0.x branch. The web-console is throwing this exception after: java.lang.NoSuchMethodError: org.mortbay.jetty.webapp.WebAppClassLoader.getUrlClassPath()Ljava/lang/String; at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.configureClassLoader(Jetty6MavenConfiguration.jav a:62) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119) at org.mortbay.jetty.Server.doStart(Server.java:210) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:115) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:318) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:268) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor. java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx ecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja va:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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-1015) ActiveMQ web-demo and web-console cannot be run
[ https://issues.apache.org/activemq/browse/AMQ-1015?page=comments#action_37328 ] james strachan commented on AMQ-1015: - I've fixed SVN HEAD so that we use an explicit version of the jetty plugin, along with using maven-jetty-plugin which should fix these issues. I also upgraded to 6.0.1 of Jetty too. We should backport this to 4.0.x too ActiveMQ web-demo and web-console cannot be run --- Key: AMQ-1015 URL: https://issues.apache.org/activemq/browse/AMQ-1015 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 4.1, 4.0.2 Reporter: Adrian Co Assigned To: james strachan Fix For: 4.1, 4.0.3 Let's update the maven plugin from maven-jetty-plugin to maven-jetty6-plugin for the 4.1.x branch and the 4.0.x branch. The web-console is throwing this exception after: java.lang.NoSuchMethodError: org.mortbay.jetty.webapp.WebAppClassLoader.getUrlClassPath()Ljava/lang/String; at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.configureClassLoader(Jetty6MavenConfiguration.jav a:62) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119) at org.mortbay.jetty.Server.doStart(Server.java:210) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:115) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:318) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:268) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor. java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx ecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja va:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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-1015) ActiveMQ web-demo and web-console cannot be run
[ https://issues.apache.org/activemq/browse/AMQ-1015?page=all ] james strachan reassigned AMQ-1015: --- Assignee: Adrian Co (was: james strachan) I've fixed this for 4.1 - wanna backport to 4.0.x? ActiveMQ web-demo and web-console cannot be run --- Key: AMQ-1015 URL: https://issues.apache.org/activemq/browse/AMQ-1015 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 4.1, 4.0.2 Reporter: Adrian Co Assigned To: Adrian Co Fix For: 4.1, 4.0.3 Let's update the maven plugin from maven-jetty-plugin to maven-jetty6-plugin for the 4.1.x branch and the 4.0.x branch. The web-console is throwing this exception after: java.lang.NoSuchMethodError: org.mortbay.jetty.webapp.WebAppClassLoader.getUrlClassPath()Ljava/lang/String; at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.configureClassLoader(Jetty6MavenConfiguration.jav a:62) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119) at org.mortbay.jetty.Server.doStart(Server.java:210) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:115) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:318) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:268) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor. java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx ecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja va:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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-999) Message dispatcher issues (use dedicated dispatching thread for each session)
[ https://issues.apache.org/activemq/browse/AMQ-999?page=all ] james strachan resolved AMQ-999. Fix Version/s: 4.1 Resolution: Fixed Patches applied with thanks Rob! I made a minor change to the patch so that the code still works on Mono 1.0; I used the class AutoResetEvent instead of EventWaitHandle to avoid compile errors in Dispatcher.cs and DispatchingThead.cs - see the TODO notes in those files in case you can think of a cleaner solution. Cheers! 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.1 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] Resolved: (AMQ-996) IConnection requires Start(), Stop() and Close() methods
[ https://issues.apache.org/activemq/browse/AMQ-996?page=all ] james strachan resolved AMQ-996. Fix Version/s: 4.1 Resolution: Fixed Fixed by AMQ-999 IConnection requires Start(), Stop() and Close() methods Key: AMQ-996 URL: https://issues.apache.org/activemq/browse/AMQ-996 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.1 These three methods are needed to bring IConnection closer to the JMS Connection interface, and also provide important capabilities. Start() and Stop() methods should start and stop/join the underlying transport's reader thread. Close() should perform the tasks described in the JMS specification (ie wait for current message to be processed), whereas Dispose should probably concern itself simply with freeing up resources. Both Close() and Dispose() should be able to be called multiple times without throwing an exception. -- 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-995) An unhandled exception in the TcpTransports' reader thread should close the connection (and inform the app)
[ https://issues.apache.org/activemq/browse/AMQ-995?page=all ] james strachan resolved AMQ-995. Fix Version/s: 4.1 Resolution: Fixed Patch applied Rob - thanks again! :) An unhandled exception in the TcpTransports' reader thread should close the connection (and inform the app) --- Key: AMQ-995 URL: https://issues.apache.org/activemq/browse/AMQ-995 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq995-patch.txt, AtomicBoolean.cs If the reader thread throws an exception (e.g. IOException) then the socket should be closed to prevent further messages being sent to the broker. If an exception is thrown during the marshalling of a message then there's no way for the stream to be set to the beginning of the next message, so all communication with the broker should cease at that point. Similarly, if the broker is killed, an IOException will probably be detected in the read thread first. -- 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-988) Thread synchronization error in TcpTransport
[ https://issues.apache.org/activemq/browse/AMQ-988?page=all ] james strachan resolved AMQ-988. Resolution: Fixed Patch applied - thanks! Thread synchronization error in TcpTransport Key: AMQ-988 URL: https://issues.apache.org/activemq/browse/AMQ-988 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq988-patch.txt I have a problem where my C# client application crashes when placed under load. It's taken a while to get to the bottom of it, but I believe I have identified the problem and luckily there's a simple solution. The AMQ .Net client uses a common pattern where a full-duplex TCP/IP connection is established with the broker, and the client uses two threads to concurrently read and write data to/from the underlying socket - one thread reading from a Reader object and the other writing to a Writer object. The TcpTransport.Start() method contains the following:- NetworkStream networkStream = new NetworkStream(socket); socketWriter = new OpenWireBinaryWriter(networkStream); socketReader = new OpenWireBinaryReader(networkStream); This pattern is explicitly allowed in Java and Win32 applications, but .Net is a little vague on the subject. The Microsoft documentation [1] suggests use of the asynchronous read/write calls for multithreaded applications, but that would significantly complicate the C# client which relies on blocking stream behaviour. On the same doc page Microsoft does specifiy that the Socket class is thread-safe, which I take to mean that concurrent read/write calls are permitted, however the same is not true of NetworkStream [2]. Perhaps it would be reasonable to expect NetworkStream to have no internal state other than the Socket it contains, but apparently this is not the case because I've identified that it is a corrupt NetworkStream which is causing my application to crash under load. After some experimentation and a fair amount of load testing, I think the solution is a simple change to the TcpTransport.start() method to use a separate NetworkStream for input and output operations. e.g. :- NetworkStream inputNetworkStream = new NetworkStream(socket); NetworkStream outputNetworkStream = new NetworkStream(socket); socketWriter = new OpenWireBinaryWriter(inputNetworkStream); socketReader = new OpenWireBinaryReader(outputNetworkStream); This works for me and my test client has now been running for 16 hours without crashing (before it would rarely last longer than 10 minutes). Regards Rob Lugt [1] http://msdn2.microsoft.com/en-us/library/system.net.sockets.socket.aspx [2] http://msdn2.microsoft.com/en-us/library/system.net.sockets.networkstream.aspx -- 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-980) lastImageSubscriptionRecoveryPolicy does not work with wildcards
[ https://issues.apache.org/activemq/browse/AMQ-980?page=comments#action_37305 ] james strachan commented on AMQ-980: Now that AMQ-999 is resolved, is this issue now fixed? lastImageSubscriptionRecoveryPolicy does not work with wildcards Key: AMQ-980 URL: https://issues.apache.org/activemq/browse/AMQ-980 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows, JDK 1.5 Reporter: Rob Lugt Fix For: 4.1 The lastImageSubscriptionRecoveryPolicy does not appear to work with wildcards. In the following example, a new consumer only receives one message for the topics covered by the wildcard instead of receiving one message for each topic. config file:- policyEntry topic=PRICES. subscriptionRecoveryPolicy lastImageSubscriptionRecoveryPolicy/ /subscriptionRecoveryPolicy /policyEntry consumer subscription:- GetTopic(PRICES.?consumer.retrocactive=true); -- 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-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages
XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages --- Key: AMQ-1007 URL: https://issues.apache.org/activemq/browse/AMQ-1007 Project: ActiveMQ Issue Type: New Feature Components: Transport Reporter: james strachan Assigned To: james strachan Fix For: 4.1 This is particularly useful for demos or testing things out in development. -- 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-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages
[ https://issues.apache.org/activemq/browse/AMQ-1007?page=all ] james strachan resolved AMQ-1007. - Resolution: Fixed The activemq-xmpp module provides the functionality, for documentation see http://activemq.org/site/xmpp.html XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages --- Key: AMQ-1007 URL: https://issues.apache.org/activemq/browse/AMQ-1007 Project: ActiveMQ Issue Type: New Feature Components: Transport Reporter: james strachan Assigned To: james strachan Fix For: 4.1 This is particularly useful for demos or testing things out in development. -- 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-506) Jabber transport missing
[ https://issues.apache.org/activemq/browse/AMQ-506?page=all ] james strachan resolved AMQ-506. Fix Version/s: 4.1 (was: 4.2) Resolution: Fixed Now back as activemq-xmpp Jabber transport missing Key: AMQ-506 URL: https://issues.apache.org/activemq/browse/AMQ-506 Project: ActiveMQ Issue Type: Improvement Components: Transport Affects Versions: 4.0 M4 Reporter: Guillaume Nodet 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-40) jabber support as client server
[ https://issues.apache.org/activemq/browse/AMQ-40?page=comments#action_37289 ] james strachan commented on AMQ-40: --- FWIW in 4.1 its now via xmpp://host:port For more details see http://activemq.org/site/xmpp.html jabber support as client server - Key: AMQ-40 URL: https://issues.apache.org/activemq/browse/AMQ-40 Project: ActiveMQ Issue Type: New Feature Reporter: james strachan Priority: Minor Fix For: 3.1 we now support a new transport jabber://localhost:61606 which allows a Jabber client to connect to ActiveMQ and talk Jabber (XMPP) to the ActiveMQ broker. This allows any Jabber client in any language to talk natively to ActiveMQ. -- 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-826) LDAP based authorization support
[ https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37285 ] james strachan commented on AMQ-826: Note that * is only allowed on a complete path, not regex. So STOCKS.PRICE.NYSE.* or STOCKS.PRICE.*.IBM but not STOCKS.PRICE.NYSE.*BM Thanks for the clarification on union v intersection. So yes, intersection sounds about right, sorry for my previous confusion :) LDAP based authorization support Key: AMQ-826 URL: https://issues.apache.org/activemq/browse/AMQ-826 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Nikola Goran Cutura Attachments: LdapAuth.zip Patch kindly added by ngcutura - discussion thread... http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494 -- 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-992) MySQL doesn't honor lock in JDBC Master Slave configuration?
[ https://issues.apache.org/activemq/browse/AMQ-992?page=comments#action_37278 ] james strachan commented on AMQ-992: You're the first one to notice this issue. I wonder how else to create an exclusive table lock in MySQL. I wonder if they are even supported? It might be we need to use different SQL for MySQL maybe? MySQL doesn't honor lock in JDBC Master Slave configuration? Key: AMQ-992 URL: https://issues.apache.org/activemq/browse/AMQ-992 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: RHEL 4 MySQL 4.x, 5.x mysql-ab_jdbc_driver Reporter: Steven Lotito Attachments: mysql_obtain_lock.txt I have been attempting to get the new 4.1 JDBC Master Slave configuration working with MySQL. The log from the first broker to start up states: 2006-10-18 09:35:08,558 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker 2006-10-18 09:35:08,559 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] The 2nd broker to start up has an identical message and both brokers listen for connections. The 2nd broker should be waiting for the lock and NOT accepting connections, if I understand http://www.activemq.org/site/jdbc-master-slave.html correctly... Oracle exhibits the expected behavior: When running the exact same configuration (except using an Oracle datasource), the first broker has the same log message as above, while the 2nd broker halts at the Attempting to acquire the exclusive lock to become the Master broker message until I fail the master. Then it becomes the master. Is this a known issue? I was able to replicate it using both MySql 4 and 5 (trying both the MySQL Connector/J 3.1 and MySQL Connector/J 5.0 drivers) -- 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-931) NMS test fails against trunk version of server
[ https://issues.apache.org/activemq/browse/AMQ-931?page=all ] james strachan resolved AMQ-931. Fix Version/s: 4.1 Resolution: Fixed Things are working fine for me with the current trunk. I wonder if the bug has been fixed (we've been applying quite a few patches to NMS recently). Let us know if you still have problems and we can reopen this issue NMS test fails against trunk version of server -- Key: AMQ-931 URL: https://issues.apache.org/activemq/browse/AMQ-931 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Environment: Gentoo Linux EM64T, Mono 1.1.17, AMQ SVN Reporter: Adam Wendt Fix For: 4.1 When running the test case against svn version of broker server the server generates this error: Exception in thread ActiveMQ Transport: tcp:///127.0.0.1:36117 java.lang.IllegalArgumentException: Invalid version: 0, could not load org.apache.activemq.openwire.v0.MarshallerFactory at org.apache.activemq.openwire.OpenWireFormat.setVersion(OpenWireFormat.java:328) at org.apache.activemq.openwire.OpenWireFormat.renegotiateWireFormat(OpenWireFormat.java:568) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:110) 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:129) at java.lang.Thread.run(Thread.java:595) The C# test runs fine against 4.0.1 or 4.0.2RC3 server -- 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-992) MySQL doesn't honor lock in JDBC Master Slave configuration?
[ https://issues.apache.org/activemq/browse/AMQ-992?page=comments#action_37280 ] james strachan commented on AMQ-992: I wonder if some SQL statement like the following works for MysQL... LOCK TABLE foo IN ACCESS EXCLUSIVE MODE; MySQL doesn't honor lock in JDBC Master Slave configuration? Key: AMQ-992 URL: https://issues.apache.org/activemq/browse/AMQ-992 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: RHEL 4 MySQL 4.x, 5.x mysql-ab_jdbc_driver Reporter: Steven Lotito Attachments: mysql_obtain_lock.txt I have been attempting to get the new 4.1 JDBC Master Slave configuration working with MySQL. The log from the first broker to start up states: 2006-10-18 09:35:08,558 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker 2006-10-18 09:35:08,559 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: [EMAIL PROTECTED] The 2nd broker to start up has an identical message and both brokers listen for connections. The 2nd broker should be waiting for the lock and NOT accepting connections, if I understand http://www.activemq.org/site/jdbc-master-slave.html correctly... Oracle exhibits the expected behavior: When running the exact same configuration (except using an Oracle datasource), the first broker has the same log message as above, while the 2nd broker halts at the Attempting to acquire the exclusive lock to become the Master broker message until I fail the master. Then it becomes the master. Is this a known issue? I was able to replicate it using both MySql 4 and 5 (trying both the MySQL Connector/J 3.1 and MySQL Connector/J 5.0 drivers) -- 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-826) LDAP based authorization support
[ https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37281 ] james strachan commented on AMQ-826: 1. union is probably more appropriate. If the user tries to send to 5 destinations and one of them is not available, it should generate an error and fail rather than silently just sending to the ones it can etc 2. Yes. acts as a recursive match to any depth. http://incubator.apache.org/activemq/wildcards.html LDAP based authorization support Key: AMQ-826 URL: https://issues.apache.org/activemq/browse/AMQ-826 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Nikola Goran Cutura Attachments: LdapAuth.zip Patch kindly added by ngcutura - discussion thread... http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494 -- 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-991) ActiveMQ 4.0.1 crashes when using client from trunk.
[
https://issues.apache.org/activemq/browse/AMQ-991?page=comments#action_37263 ]
james strachan commented on AMQ-991:
There was a gremlin in trunk for a little while that made NMS not work with
older ActiveMQ brokers. Though AFAIK this should be resolved now.
ActiveMQ 4.0.1 crashes when using client from trunk.
Key: AMQ-991
URL: https://issues.apache.org/activemq/browse/AMQ-991
Project: ActiveMQ
Issue Type: Bug
Components: NMS (C# client)
Reporter: Pawel Niewiadomski
I tried today to use C# client from trunk agains ActiveMQ 4.0.1 server. This
caused server to die totally. Following error message was shown by server:
{noformat}
Exception in thread ActiveMQ Transport: tcp:///127.0.0.1:1699
java.lang.Illega
lArgumentException: Invalid version: 2, could not load
org.apache.activemq.openwire.v2.MarshallerFactory
at
org.apache.activemq.openwire.OpenWireFormat.setVersion(OpenWireFormat.java:329)
at
org.apache.activemq.openwire.OpenWireFormat.renegociatWireFormat(OpenWireFormat.java:569)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:100)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException:
org.apache.activemq.openwire.v2.MarshallerFactory
at
org.apache.activemq.util.ClassLoading.loadClass(ClassLoading.java:104)
at
org.apache.activemq.openwire.OpenWireFormat.setVersion(OpenWireFormat.java:327)
... 6 more
{noformat}
I then used ActiveMQ 4.0.2 server and it worked. Isn't that client should
automatically negotiate protocol with server? Why server after this error
dies totally? (new client connecting were not handled at all, everything
died).
--
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-998) add support for stomp+ssl
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.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-998) add support for stomp+ssl
[ https://issues.apache.org/activemq/browse/AMQ-998?page=comments#action_37260 ] james strachan commented on AMQ-998: The implementation and test case is now in trunk; just need to get the test case working and document this feature on the wiki... http://incubator.apache.org/activemq/configuring-transports.html 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.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-980) lastImageSubscriptionRecoveryPolicy does not work with wildcards
[ https://issues.apache.org/activemq/browse/AMQ-980?page=comments#action_37248 ] james strachan commented on AMQ-980: Ah cool - thanks for the analysis Rob. As soon as we've the '1 thread per session' change in ActiveMQ.Net we can retest that things are working fine lastImageSubscriptionRecoveryPolicy does not work with wildcards Key: AMQ-980 URL: https://issues.apache.org/activemq/browse/AMQ-980 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows, JDK 1.5 Reporter: Rob Lugt Fix For: 4.1 The lastImageSubscriptionRecoveryPolicy does not appear to work with wildcards. In the following example, a new consumer only receives one message for the topics covered by the wildcard instead of receiving one message for each topic. config file:- policyEntry topic=PRICES. subscriptionRecoveryPolicy lastImageSubscriptionRecoveryPolicy/ /subscriptionRecoveryPolicy /policyEntry consumer subscription:- GetTopic(PRICES.?consumer.retrocactive=true); -- 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-987) suprious exception message when using message streams...
suprious exception message when using message streams... Key: AMQ-987 URL: https://issues.apache.org/activemq/browse/AMQ-987 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Jerome Banks reported this... Oct 17, 2006 11:39:03 AM org.apache.activemq.broker.region.QueueSubscriptionassignGroupToMe WARNING: Failed to set boolean header: * javax.jms.MessageNotWriteableException*: Message body is read-only * javax.jms.MessageNotWriteableException*: Message body is read-only at org.apache.activemq.command.ActiveMQMessage.checkReadOnlyBody(* ActiveMQMessage.java:573*) at org.apache.activemq.command.ActiveMQBytesMessage.initializeWriting(* ActiveMQBytesMessage.java:669*) at org.apache.activemq.command.ActiveMQBytesMessage.setObjectProperty(* ActiveMQBytesMessage.java:736*) at org.apache.activemq.command.ActiveMQMessage.setBooleanProperty(* ActiveMQMessage.java:533*) at org.apache.activemq.broker.region.QueueSubscription.assignGroupToMe(* QueueSubscription.java:137*) at org.apache.activemq.broker.region.QueueSubscription.canDispatch(* QueueSubscription.java:103*) at org.apache.activemq.broker.region.PrefetchSubscription.dispatch(* PrefetchSubscription.java:293*) at org.apache.activemq.broker.region.QueueSubscription.dispatch(* QueueSubscription.java:175*) at org.apache.activemq.broker.region.PrefetchSubscription.add(* PrefetchSubscription.java:64*) at org.apache.activemq.broker.region.Queue.addSubscription(*Queue.java:163*) at org.apache.activemq.broker.region.AbstractRegion.addConsumer(* AbstractRegion.java:189*) at org.apache.activemq.broker.region.RegionBroker.addConsumer(* RegionBroker.java:308*) at org.apache.activemq.broker.BrokerFilter.addConsumer(*BrokerFilter.java:77 *) at org.apache.activemq.advisory.AdvisoryBroker.addConsumer(* AdvisoryBroker.java:77*) at org.apache.activemq.broker.MutableBrokerFilter.addConsumer(* MutableBrokerFilter.java:91*) at org.apache.activemq.broker.BrokerFilter.addConsumer(*BrokerFilter.java:77 *) at org.apache.activemq.broker.MutableBrokerFilter.addConsumer(* MutableBrokerFilter.java:91*) at org.apache.activemq.broker.AbstractConnection.processAddConsumer(* AbstractConnection.java:457*) at org.apache.activemq.command.ConsumerInfo.visit(*ConsumerInfo.java:295*) at org.apache.activemq.broker.AbstractConnection.service(* AbstractConnection.java:226*) at org.apache.activemq.broker.TransportConnection$1.onCommand(* TransportConnection.java:62*) at org.apache.activemq.transport.ResponseCorrelator.onCommand(* ResponseCorrelator.java:91*) at org.apache.activemq.transport.TransportFilter.onCommand(* TransportFilter.java:63*) at org.apache.activemq.transport.vm.VMTransport.oneway(*VMTransport.java:76* ) at org.apache.activemq.transport.MutexTransport.oneway(*MutexTransport.java :44*) at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(* ResponseCorrelator.java:66*) at org.apache.activemq.transport.ResponseCorrelator.request(* ResponseCorrelator.java:71*) at org.apache.activemq.ActiveMQConnection.syncSendPacket(* ActiveMQConnection.java:1137*) at org.apache.activemq.ActiveMQInputStream.init(*ActiveMQInputStream.java :112*) at org.apache.activemq.ActiveMQConnection.doCreateInputStream(* ActiveMQConnection.java:1681*) at org.apache.activemq.ActiveMQConnection.createInputStream(* ActiveMQConnection.java:1663*) at org.apache.activemq.ActiveMQConnection.createInputStream(* ActiveMQConnection.java:1659*) at org.apache.activemq.ActiveMQConnection.createInputStre -- 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-988) Thread synchronization error in TcpTransport
[ https://issues.apache.org/activemq/browse/AMQ-988?page=all ] james strachan resolved AMQ-988. Fix Version/s: 4.1 Resolution: Fixed Great catch Rob! Patch applied with huge thanks Thread synchronization error in TcpTransport Key: AMQ-988 URL: https://issues.apache.org/activemq/browse/AMQ-988 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 I have a problem where my C# client application crashes when placed under load. It's taken a while to get to the bottom of it, but I believe I have identified the problem and luckily there's a simple solution. The AMQ .Net client uses a common pattern where a full-duplex TCP/IP connection is established with the broker, and the client uses two threads to concurrently read and write data to/from the underlying socket - one thread reading from a Reader object and the other writing to a Writer object. The TcpTransport.Start() method contains the following:- NetworkStream networkStream = new NetworkStream(socket); socketWriter = new OpenWireBinaryWriter(networkStream); socketReader = new OpenWireBinaryReader(networkStream); This pattern is explicitly allowed in Java and Win32 applications, but .Net is a little vague on the subject. The Microsoft documentation [1] suggests use of the asynchronous read/write calls for multithreaded applications, but that would significantly complicate the C# client which relies on blocking stream behaviour. On the same doc page Microsoft does specifiy that the Socket class is thread-safe, which I take to mean that concurrent read/write calls are permitted, however the same is not true of NetworkStream [2]. Perhaps it would be reasonable to expect NetworkStream to have no internal state other than the Socket it contains, but apparently this is not the case because I've identified that it is a corrupt NetworkStream which is causing my application to crash under load. After some experimentation and a fair amount of load testing, I think the solution is a simple change to the TcpTransport.start() method to use a separate NetworkStream for input and output operations. e.g. :- NetworkStream inputNetworkStream = new NetworkStream(socket); NetworkStream outputNetworkStream = new NetworkStream(socket); socketWriter = new OpenWireBinaryWriter(inputNetworkStream); socketReader = new OpenWireBinaryReader(outputNetworkStream); This works for me and my test client has now been running for 16 hours without crashing (before it would rarely last longer than 10 minutes). Regards Rob Lugt [1] http://msdn2.microsoft.com/en-us/library/system.net.sockets.socket.aspx [2] http://msdn2.microsoft.com/en-us/library/system.net.sockets.networkstream.aspx -- 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-974) .Net client needs centralised trace facility
[ https://issues.apache.org/activemq/browse/AMQ-974?page=all ] james strachan resolved AMQ-974. Resolution: Fixed Patch applied, thanks again! .Net client needs centralised trace facility Key: AMQ-974 URL: https://issues.apache.org/activemq/browse/AMQ-974 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq974-patch.txt, ITrace.cs, Tracer.cs There are several classes within activemq-dotnet which need to write log/trace information. This data is currently written to an ad-hoc mixture of the Console and System.Diagnostics.Trace. Neither of these detinations are suitable because System.Diagnostics.Trace is not fully supported in the .Net compact framework and the Console is unsuitable for severl reasons - not least of which is that output is discarded in a Windows (i.e. non-console) application. There are two possible solutions to this problem 1) adopt log4net as the strategic logging/tracing platform 2) write our own Tracing interface which can be controlled at run-time to make use of any logging mechanism. Log4net is an attractive proposition because it is powerful, full-featured, reliable and is also an Apache incubator project. However, there is a strong desire to keep activemq-dotnet as clear as possible from any external dependencies. So far this has been successfull and as there is an alternative solution perhaps we should not create a dependency now. Creating a custom Tracing interface is attractive because it is stand-alone and allows the client application to plug-in whichever trace mechanism it requires. There don't seem to be many down sides to this solution, so I'll post a sample impementation shortly. -- 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-985) TcpTransportFactory adds LoggingTransport after WireFormatNegotiator
[ https://issues.apache.org/activemq/browse/AMQ-985?page=all ]
james strachan resolved AMQ-985.
Fix Version/s: 4.1
Resolution: Fixed
Patch applied - thanks again :)
TcpTransportFactory adds LoggingTransport after WireFormatNegotiator
Key: AMQ-985
URL: https://issues.apache.org/activemq/browse/AMQ-985
Project: ActiveMQ
Issue Type: Improvement
Components: NMS (C# client)
Affects Versions: 4.0.2
Environment: Windows
Reporter: Rob Lugt
Assigned To: james strachan
Priority: Minor
Fix For: 4.1
The TcpTransportFactory class will insert a LoggingTransport filter into the
transport chain if the useLogging=true attribute is set. However, it
currently adds the LoggingTransport after the WireFormatNegotiator, which
means that the wire format negotiation packets are excluded from the log
output. This can be simply rectified by adding the LoggingTransport
immediately after the TcpTransport. e.g.
public ITransport CreateTransport(Uri location)
{
// Console.WriteLine(Opening socket to: + host + on port:
+ port);
Socket socket = Connect(location.Host, location.Port);
TcpTransport tcpTransport = new TcpTransport(socket);
ITransport rc = tcpTransport;
// At present the URI is parsed for options by the
ConnectionFactory
if (UseLogging)
{
rc = new LoggingTransport(rc);
}
rc = new WireFormatNegotiator(rc, tcpTransport.Wireformat);
...
--
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-972) NMS Client does not set NMSTimestamp
[ https://issues.apache.org/activemq/browse/AMQ-972?page=all ] james strachan resolved AMQ-972. Fix Version/s: 4.1 Resolution: Fixed Looks great to me - patch applied with thanks! NMS Client does not set NMSTimestamp Key: AMQ-972 URL: https://issues.apache.org/activemq/browse/AMQ-972 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows client Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq972-patch.txt, DateUtils.cs MessageProducer.cs fails to set the Timestamp property on a message regardless if the DisableMessageTimestamp feature property is set or not. -- 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-971) NMSTimestamp returning LocalTime instead of UTC
[ https://issues.apache.org/activemq/browse/AMQ-971?page=all ] james strachan reassigned AMQ-971: -- Assignee: Hiram Chirino NMSTimestamp returning LocalTime instead of UTC --- Key: AMQ-971 URL: https://issues.apache.org/activemq/browse/AMQ-971 Project: ActiveMQ Issue Type: Improvement Components: NMS (C# client) Affects Versions: incubation Environment: Windows Reporter: Rob Lugt Assigned To: Hiram Chirino Priority: Minor The NMSTimestamp property has been changed from long to DateTime - which is a good thing. However, the DateTime is currently being adjusted to localtime before being returned to the client - which is probably not ideal. The DateTime struct does not contain timezone information, therefore the programmer has to make some assumption about what timezone the time is expressed in. A UTC time is more in-keeping with the JMS specification - which specifies that Timestamp is a normal Java time i.e. expressed in GMT. This article from Microsoft also suggests using UTC as a common time where possible: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/datetimecode.asp -- 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-989) .Net Client: allow specification of wireFormat parameters in broker URI
[ https://issues.apache.org/activemq/browse/AMQ-989?page=all ] james strachan resolved AMQ-989. Fix Version/s: 4.1 Resolution: Fixed I think I've faithfully applied your patch for this issue - many thanks. This issue seemed to cut across a few other issues to do with logging; could you double check Ive applied your patch correctly please? .Net Client: allow specification of wireFormat parameters in broker URI --- Key: AMQ-989 URL: https://issues.apache.org/activemq/browse/AMQ-989 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.1 Attachments: amq989.txt Update required to TcpTransportFactory to accept wireFormat connection parameters in the connection URI. This is the only means for .Net client applications to set properties such as tight/loose encoding. Please apply the attached patch. Best Regards Rob Lugt -- 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-966) NMSDestination is null when receiving messages
[ https://issues.apache.org/activemq/browse/AMQ-966?page=all ] james strachan resolved AMQ-966. Fix Version/s: 4.1 Resolution: Fixed yes, it should be the Destination property :) Patch applied with thanks NMSDestination is null when receiving messages -- Key: AMQ-966 URL: https://issues.apache.org/activemq/browse/AMQ-966 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Reporter: Rob Lugt Fix For: 4.1 The NMSDestination property is null when receiving messages via an asynchronous listener. -- 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-952) .Net Client ConnectionFactory requires additional configurable attributes
[ https://issues.apache.org/activemq/browse/AMQ-952?page=comments#action_37226 ] james strachan commented on AMQ-952: I've added API access to the various consumer related configuration options; so you can now do things like ISession session = ... session.Retroactive = true session.CreateConsumer()... etc Also you should be able to use the URI syntax currently... new ActiveMQQueue(Foo.BAR?consumer.retroactive=true) etc .Net Client ConnectionFactory requires additional configurable attributes - Key: AMQ-952 URL: https://issues.apache.org/activemq/browse/AMQ-952 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Reporter: Rob Lugt Priority: Minor The Java Client has a rich set of configuration options, which should also be available on the .Net client. As a mimimum I believe we need:- closeTimeout retroactiveConsumer Is it also worth considering a connectTimeout property - or should this be transport specific? -- 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-952) .Net Client ConnectionFactory requires additional configurable attributes
[ https://issues.apache.org/activemq/browse/AMQ-952?page=comments#action_37227 ] james strachan commented on AMQ-952: Incidentally, while looking at the Connection.Dispose(), we no longer call Dispose() on child sessions as they are iDisposable - by the same logic I guess we should no longer call transport.Dispose() too? .Net Client ConnectionFactory requires additional configurable attributes - Key: AMQ-952 URL: https://issues.apache.org/activemq/browse/AMQ-952 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Reporter: Rob Lugt Priority: Minor The Java Client has a rich set of configuration options, which should also be available on the .Net client. As a mimimum I believe we need:- closeTimeout retroactiveConsumer Is it also worth considering a connectTimeout property - or should this be transport specific? -- 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-952) .Net Client ConnectionFactory requires additional configurable attributes
[ https://issues.apache.org/activemq/browse/AMQ-952?page=comments#action_37228 ] james strachan commented on AMQ-952: So the only things left for this I think are closeTimeout and connectTimeout. For closeTimeout, we currently are not waiting for a receipt to come back from the broker when we send a ShutdownInfo - which seems fine to me. The Java client will do a timeout based request-response up to the closeTimeout - am not sure how useful that is to implement in .Net though. For connectTimeout, in Java we set that as a property on the Socket class when doing a Connect() - I don't see any way to do something similar on .Net. Though the SendTimeout and ReceiveTimeout properties can be set via the URI notation of transport.socket.sendTimeout=1234 etc .Net Client ConnectionFactory requires additional configurable attributes - Key: AMQ-952 URL: https://issues.apache.org/activemq/browse/AMQ-952 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Reporter: Rob Lugt Priority: Minor The Java Client has a rich set of configuration options, which should also be available on the .Net client. As a mimimum I believe we need:- closeTimeout retroactiveConsumer Is it also worth considering a connectTimeout property - or should this be transport specific? -- 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-951) NMS requires the concept of a Connection Exception event to mirror rhe ExceptionListener in JMS.
[ https://issues.apache.org/activemq/browse/AMQ-951?page=all ] james strachan resolved AMQ-951. Fix Version/s: 4.1 Resolution: Fixed I've added an ExceptionListener event on the IConnection which should serve a similar purpose to ExceptionListener in JMS. Does this seem an OK solution to you? NMS requires the concept of a Connection Exception event to mirror rhe ExceptionListener in JMS. Key: AMQ-951 URL: https://issues.apache.org/activemq/browse/AMQ-951 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: incubation Reporter: Rob Lugt Assigned To: Rob Lugt Fix For: 4.1 Applications using NMS have no way of discovering problems with the connection. JMS allws a ExceptionListener to be registered with a Connection, NMS should provide a similar concept. -- 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-980) lastImageSubscriptionRecoveryPolicy does not work with wildcards
[ https://issues.apache.org/activemq/browse/AMQ-980?page=all ] james strachan resolved AMQ-980. Fix Version/s: 4.1 Resolution: Cannot Reproduce I've created a JUnit test case to try reproduce the issue. I've added the test case RetroactiveConsumerTestWithLastImagePolicyWithWildcardTest (in the activemq-core module) which creates a broker without persistence, sends 20 messages to different topics, then creates a retroactive consumer using a wildcard and it receives all 20 messages on each topic. Am wondering how to reproduce your issue - any ideas? Does this issue only show itself in ActiveMQ.Net? lastImageSubscriptionRecoveryPolicy does not work with wildcards Key: AMQ-980 URL: https://issues.apache.org/activemq/browse/AMQ-980 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2 Environment: Windows, JDK 1.5 Reporter: Rob Lugt Fix For: 4.1 The lastImageSubscriptionRecoveryPolicy does not appear to work with wildcards. In the following example, a new consumer only receives one message for the topics covered by the wildcard instead of receiving one message for each topic. config file:- policyEntry topic=PRICES. subscriptionRecoveryPolicy lastImageSubscriptionRecoveryPolicy/ /subscriptionRecoveryPolicy /policyEntry consumer subscription:- GetTopic(PRICES.?consumer.retrocactive=true); -- 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-980) lastImageSubscriptionRecoveryPolicy does not work with wildcards
[ https://issues.apache.org/activemq/browse/AMQ-980?page=comments#action_37231 ] james strachan commented on AMQ-980: BTW I marked this resolved as a 'Cannot Reproduce' for now - if you can figure out how to reproduce we can reopen it lastImageSubscriptionRecoveryPolicy does not work with wildcards Key: AMQ-980 URL: https://issues.apache.org/activemq/browse/AMQ-980 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2 Environment: Windows, JDK 1.5 Reporter: Rob Lugt Fix For: 4.1 The lastImageSubscriptionRecoveryPolicy does not appear to work with wildcards. In the following example, a new consumer only receives one message for the topics covered by the wildcard instead of receiving one message for each topic. config file:- policyEntry topic=PRICES. subscriptionRecoveryPolicy lastImageSubscriptionRecoveryPolicy/ /subscriptionRecoveryPolicy /policyEntry consumer subscription:- GetTopic(PRICES.?consumer.retrocactive=true); -- 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-974) .Net client needs centralised trace facility
[ https://issues.apache.org/activemq/browse/AMQ-974?page=all ] james strachan reassigned AMQ-974: -- Assignee: james strachan .Net client needs centralised trace facility Key: AMQ-974 URL: https://issues.apache.org/activemq/browse/AMQ-974 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Attachments: amq974-patch.txt, ITrace.cs, Tracer.cs There are several classes within activemq-dotnet which need to write log/trace information. This data is currently written to an ad-hoc mixture of the Console and System.Diagnostics.Trace. Neither of these detinations are suitable because System.Diagnostics.Trace is not fully supported in the .Net compact framework and the Console is unsuitable for severl reasons - not least of which is that output is discarded in a Windows (i.e. non-console) application. There are two possible solutions to this problem 1) adopt log4net as the strategic logging/tracing platform 2) write our own Tracing interface which can be controlled at run-time to make use of any logging mechanism. Log4net is an attractive proposition because it is powerful, full-featured, reliable and is also an Apache incubator project. However, there is a strong desire to keep activemq-dotnet as clear as possible from any external dependencies. So far this has been successfull and as there is an alternative solution perhaps we should not create a dependency now. Creating a custom Tracing interface is attractive because it is stand-alone and allows the client application to plug-in whichever trace mechanism it requires. There don't seem to be many down sides to this solution, so I'll post a sample impementation shortly. -- 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-974) .Net client needs centralised trace facility
[ https://issues.apache.org/activemq/browse/AMQ-974?page=all ] james strachan resolved AMQ-974. Fix Version/s: 4.1 Resolution: Fixed Patch applied - many thanks! .Net client needs centralised trace facility Key: AMQ-974 URL: https://issues.apache.org/activemq/browse/AMQ-974 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq974-patch.txt, ITrace.cs, Tracer.cs There are several classes within activemq-dotnet which need to write log/trace information. This data is currently written to an ad-hoc mixture of the Console and System.Diagnostics.Trace. Neither of these detinations are suitable because System.Diagnostics.Trace is not fully supported in the .Net compact framework and the Console is unsuitable for severl reasons - not least of which is that output is discarded in a Windows (i.e. non-console) application. There are two possible solutions to this problem 1) adopt log4net as the strategic logging/tracing platform 2) write our own Tracing interface which can be controlled at run-time to make use of any logging mechanism. Log4net is an attractive proposition because it is powerful, full-featured, reliable and is also an Apache incubator project. However, there is a strong desire to keep activemq-dotnet as clear as possible from any external dependencies. So far this has been successfull and as there is an alternative solution perhaps we should not create a dependency now. Creating a custom Tracing interface is attractive because it is stand-alone and allows the client application to plug-in whichever trace mechanism it requires. There don't seem to be many down sides to this solution, so I'll post a sample impementation shortly. -- 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-973) .Net client sends message acknowledgements as synchronous requests instead of asynchronous oneWay packets
[ https://issues.apache.org/activemq/browse/AMQ-973?page=all ] james strachan reassigned AMQ-973: -- Assignee: james strachan (was: Rob Lugt) .Net client sends message acknowledgements as synchronous requests instead of asynchronous oneWay packets - Key: AMQ-973 URL: https://issues.apache.org/activemq/browse/AMQ-973 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Attachments: amq973-patch.txt The Java client sends message acknowledgements as one-way communications, but the NMS client currently sends these as synchronous requests. This is impacting performance and is (I believe) unnecessary. -- 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-973) .Net client sends message acknowledgements as synchronous requests instead of asynchronous oneWay packets
[ https://issues.apache.org/activemq/browse/AMQ-973?page=all ] james strachan resolved AMQ-973. Fix Version/s: 4.1 Resolution: Fixed Patch applied - many thanks! .Net client sends message acknowledgements as synchronous requests instead of asynchronous oneWay packets - Key: AMQ-973 URL: https://issues.apache.org/activemq/browse/AMQ-973 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Environment: Windows Reporter: Rob Lugt Assigned To: james strachan Fix For: 4.1 Attachments: amq973-patch.txt The Java client sends message acknowledgements as one-way communications, but the NMS client currently sends these as synchronous requests. This is impacting performance and is (I believe) unnecessary. -- 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-826) LDAP based authorization support
[ https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37159 ] james strachan commented on AMQ-826: Hi Nikola Don't worry about the maven stuff, I can try help with that - its mostly to get a unit test running that boots up an embedded ApacheDS, loads it with the necessary test data, then runs the test case. LDAP based authorization support Key: AMQ-826 URL: https://issues.apache.org/activemq/browse/AMQ-826 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Nikola Goran Cutura Attachments: LdapAuth.zip Patch kindly added by ngcutura - discussion thread... http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494 -- 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-950) createConnector=false has no effect on Tiger
[ https://issues.apache.org/activemq/browse/AMQ-950?page=all ]
james strachan resolved AMQ-950.
Resolution: Fixed
Patch applied - many thanks Renaud.
BTW could you double check my version of your patch works - I only create a
connector if result != null and createConnector is true.
createConnector=false has no effect on Tiger
--
Key: AMQ-950
URL: https://issues.apache.org/activemq/browse/AMQ-950
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1
Environment: JDK 1.5.0_08
Reporter: Renaud Bruyeron
Priority: Minor
Fix For: 4.1
On Tiger, activemq always creates a rmi connector on port 1099 no matter what
I do with -Djavax.management... and managementContext/
In particular, setting createConnector=false should prevent AMQ from
setting up its own connector, but it does not.
The problem is in the findMBeanServer() method:
if (result == null createMBeanServer) {
result = createMBeanServer();
}
else {
createConnector(result);
}
result is not null on Tiger with useJmx=true, and createConnector is not
protected by if(createConnector) like it is on the non-Tiger flow.
The fix (I think) is simply to do this:
if (result == null createMBeanServer) {
result = createMBeanServer();
}
else {
if(createConnector){
createConnector(result);
}
}
--
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-947) Improve .Net client to accept URI configuration parameters for connection, consumer and producer
[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ] james strachan resolved AMQ-947. Fix Version/s: 4.1 Resolution: Fixed Patch applied Rob - many thanks! Improve .Net client to accept URI configuration parameters for connection, consumer and producer Key: AMQ-947 URL: https://issues.apache.org/activemq/browse/AMQ-947 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.x Reporter: Rob Lugt Assigned To: Rob Lugt Fix For: 4.1 Attachments: AMQ-947.diff The Java client accepts optional parameters on broker and destination URIs, which allows client programs to configure the client using the standard JMS interface. The .Net client does not currently support parameters (it silently ignores them), but this is not made clear in the documentation. URI parameters are a powerful mechanism which should ideally be rolled out to all clients, but as this is client specific this Jira covers the .Net client only. Idelly the same URI configuration parameters should be used for both the Java and .Net clients. The Java mechanism is based on introspection, so the .Net client should ideally use a similar mechanism. -- 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: (SM-617) make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically confi
make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically configured endpoint POJOs --- Key: SM-617 URL: https://issues.apache.org/activemq/browse/SM-617 Project: ServiceMix Issue Type: Improvement Reporter: james strachan Assigned To: james strachan Fix For: 3.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 started: (SM-617) make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically
[ https://issues.apache.org/activemq/browse/SM-617?page=all ] Work on SM-617 started by james strachan. make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically configured endpoint POJOs --- Key: SM-617 URL: https://issues.apache.org/activemq/browse/SM-617 Project: ServiceMix Issue Type: Improvement Reporter: james strachan Assigned To: james strachan Fix For: 3.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: (SM-617) make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically
[ https://issues.apache.org/activemq/browse/SM-617?page=all ] Work on SM-617 stopped by james strachan. make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically configured endpoint POJOs --- Key: SM-617 URL: https://issues.apache.org/activemq/browse/SM-617 Project: ServiceMix Issue Type: Improvement Reporter: james strachan Assigned To: james strachan Fix For: 3.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] Resolved: (SM-617) make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically conf
[ https://issues.apache.org/activemq/browse/SM-617?page=all ] james strachan resolved SM-617. --- Resolution: Fixed for an example of this base class in action, see the new refactored Saxon component in servicemix-saxon make a new base class, DefaultComponent which combines the Component and Lifecycle functionality and can deal with the SpringComponent behaviour, dealing with statically configured endpoint POJOs --- Key: SM-617 URL: https://issues.apache.org/activemq/browse/SM-617 Project: ServiceMix Issue Type: Improvement Reporter: james strachan Assigned To: james strachan Fix For: 3.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: (SM-618) create a file based servicemix-file service engine with nice support for URIs
create a file based servicemix-file service engine with nice support for URIs - Key: SM-618 URL: https://issues.apache.org/activemq/browse/SM-618 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Reporter: james strachan Assigned To: james strachan Fix For: 3.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-947) Imporve .Net client to accept URI configuration parameters for connection, consumer and producer
[ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37044 ] james strachan commented on AMQ-947: Sounds fine with me. The main thing holding us back on this is figuring out the right .Net way to do this... http://incubator.apache.org/activemq/maven/activemq-core/xref/org/apache/activemq/util/IntrospectionSupport.html I wonder any chance you could try create an introspection/reflection helper class something like that so we could wire in a similar introspection URI handler to the connection / consumer / transport / socket stuff etc? Imporve .Net client to accept URI configuration parameters for connection, consumer and producer Key: AMQ-947 URL: https://issues.apache.org/activemq/browse/AMQ-947 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.x Reporter: Rob Lugt The Java client accepts optional parameters on broker and destination URIs, which allows client programs to configure the client using the standard JMS interface. The .Net client does not currently support parameters (it silently ignores them), but this is not made clear in the documentation. URI parameters are a powerful mechanism which should ideally be rolled out to all clients, but as this is client specific this Jira covers the .Net client only. Idelly the same URI configuration parameters should be used for both the Java and .Net clients. The Java mechanism is based on introspection, so the .Net client should ideally use a similar mechanism. -- 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-947) Imporve .Net client to accept URI configuration parameters for connection, consumer and producer
[ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37047 ] james strachan commented on AMQ-947: Who-hoo!! BTW you should now have sufficient JIRA karma to assign issues to yourself or edit issues if you like etc Imporve .Net client to accept URI configuration parameters for connection, consumer and producer Key: AMQ-947 URL: https://issues.apache.org/activemq/browse/AMQ-947 Project: ActiveMQ Issue Type: New Feature Components: NMS (C# client) Affects Versions: 4.x Reporter: Rob Lugt The Java client accepts optional parameters on broker and destination URIs, which allows client programs to configure the client using the standard JMS interface. The .Net client does not currently support parameters (it silently ignores them), but this is not made clear in the documentation. URI parameters are a powerful mechanism which should ideally be rolled out to all clients, but as this is client specific this Jira covers the .Net client only. Idelly the same URI configuration parameters should be used for both the Java and .Net clients. The Java mechanism is based on introspection, so the .Net client should ideally use a similar mechanism. -- 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-921) When recovering messages on startup - execution of Store.getMessage is executed as many times as many subscribers to this destination there are
[ https://issues.apache.org/activemq/browse/AMQ-921?page=all ] james strachan reassigned AMQ-921: -- Assignee: Hiram Chirino When recovering messages on startup - execution of Store.getMessage is executed as many times as many subscribers to this destination there are --- Key: AMQ-921 URL: https://issues.apache.org/activemq/browse/AMQ-921 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 4.1 Environment: Any Reporter: Nikolai Penkov Assigned To: Hiram Chirino Priority: Minor Fix of issue https://issues.apache.org/activemq/browse/AMQ-878 (when recovering gigantic queues) come to a new performance problem. - When recovering messages on startup - execution of Store.getMessage (from IndirectMessageRefference.incrementReferenceCount) is executed as many times as many subscribers to this destination there are. E.g. 1. Start of broker with a queue A with a lot of messages 2. Queue is recovered from database by creation of IndirectMessageRefferences 3. 2 Subscribers connect to recovered queue with two different message selectors. 4. Messages are loaded from database (IndirectMessageRefference.incrementReferenceCount - destinationStore.getMessage) twice - for 2 subscribers... -- 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-940) JMSXUserId not set when using a JAAS login module
[ https://issues.apache.org/activemq/browse/AMQ-940?page=all ] james strachan resolved AMQ-940. Resolution: Fixed Patch applied - many thanks! JMSXUserId not set when using a JAAS login module - Key: AMQ-940 URL: https://issues.apache.org/activemq/browse/AMQ-940 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: Linux, JDK 1.6 Reporter: Kelly Campbell Assigned To: james strachan Priority: Minor Fix For: 4.1 Attachments: JMSXUserID-jaas.patch The JMSXUserID field is not set when using a JAAS login module. A unit test that fails and a bugfix are attached. -- 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-940) JMSXUserId not set when using a JAAS login module
[ https://issues.apache.org/activemq/browse/AMQ-940?page=all ] james strachan reassigned AMQ-940: -- Assignee: james strachan JMSXUserId not set when using a JAAS login module - Key: AMQ-940 URL: https://issues.apache.org/activemq/browse/AMQ-940 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.1 Environment: Linux, JDK 1.6 Reporter: Kelly Campbell Assigned To: james strachan Priority: Minor Fix For: 4.1 Attachments: JMSXUserID-jaas.patch The JMSXUserID field is not set when using a JAAS login module. A unit test that fails and a bugfix are attached. -- 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
