[jira] [Commented] (AMQ-4439) Stomp 1.1 connections ignore persistent option

2013-04-18 Thread Trey Hyde (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635862#comment-13635862
 ] 

Trey Hyde commented on AMQ-4439:


Thanks for taking a look.  I stripped down my test case and I can't reproduce 
either.  I'll dig more, thanks again.

 Stomp 1.1 connections ignore persistent option
 

 Key: AMQ-4439
 URL: https://issues.apache.org/jira/browse/AMQ-4439
 Project: ActiveMQ
  Issue Type: Bug
  Components: stomp
Affects Versions: 5.7.0
Reporter: Trey Hyde

 Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option 
 on the send call is ignored.  Set accept-version to 1.0 and messages get get 
 set as persistent appropriately. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (AMQ-4439) Stomp 1.1 connections ignore persistent

2013-04-04 Thread Trey Hyde (JIRA) 
Trey Hyde created AMQ-4439:
--

 Summary: Stomp 1.1 connections ignore persistent
 Key: AMQ-4439
 URL: https://issues.apache.org/jira/browse/AMQ-4439
 Project: ActiveMQ
  Issue Type: Bug
  Components: stomp
Affects Versions: 5.7.0
Reporter: Trey Hyde




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMQ-4439) Stomp 1.1 connections ignore persistent option

2013-04-04 Thread Trey Hyde (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trey Hyde updated AMQ-4439:
---

Description: Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the 
persistent:true option on the send call is ignored.  Set accept-version to 1.0 
and messages get get set as persistent appropriately. 
Summary: Stomp 1.1 connections ignore persistent option  (was: Stomp 
1.1 connections ignore persistent)

 Stomp 1.1 connections ignore persistent option
 

 Key: AMQ-4439
 URL: https://issues.apache.org/jira/browse/AMQ-4439
 Project: ActiveMQ
  Issue Type: Bug
  Components: stomp
Affects Versions: 5.7.0
Reporter: Trey Hyde

 Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option 
 on the send call is ignored.  Set accept-version to 1.0 and messages get get 
 set as persistent appropriately. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-4439) Stomp 1.1 connections ignore persistent option

2013-04-04 Thread Trey Hyde (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622985#comment-13622985
 ] 

Trey Hyde commented on AMQ-4439:


Sorry, I'm having some challenges with that.  I don't see an example of another 
test using  ActiveMQQueueBrowser.  Is there some other way I should be 
inspecting the data store in tests to assert messages have the appropriate 
properties?

 Stomp 1.1 connections ignore persistent option
 

 Key: AMQ-4439
 URL: https://issues.apache.org/jira/browse/AMQ-4439
 Project: ActiveMQ
  Issue Type: Bug
  Components: stomp
Affects Versions: 5.7.0
Reporter: Trey Hyde

 Set accept-version to 1.1,1.0, 1.0,1.1 or 1.1 and the persistent:true option 
 on the send call is ignored.  Set accept-version to 1.0 and messages get get 
 set as persistent appropriately. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-2455) Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.

2011-07-21 Thread Trey Hyde (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069069#comment-13069069
 ] 

Trey Hyde commented on AMQ-2455:


I looked at the code here a while back... it only tries to reconnect 10 times 
if there is an issue (I can't comment if that actually works or not). If 
the remote connection is down or restarting or any reason can be contacted in 
the fraction of a second 10 sequential attempts take then it will give up.  
There is no thread/timer that will retry at some later time.   I also couldn't 
find any JMX exposed methods that would allow me to manually attempt a 
reconnect without restarting AMQ.

 Need a facility to retry jms connections to a foreign provider by the 
 ActiveMQ JMS bridge.
 --

 Key: AMQ-2455
 URL: https://issues.apache.org/jira/browse/AMQ-2455
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker
 Environment: Debian Lenny.  ActiveMQ 5.2.  OpenJMS-0.7.7-beta-1
Reporter: Billy Buzzard
Assignee: Rob Davies
 Fix For: 5.4.0

 Attachments: bridge-reconnect.patch, test.zip


 I followed an example 
 (http://www.codeproject.com/KB/docview/jms_to_jms_bridge_activem.aspx?display=Print)
  showing how to set up a bridge between OpenJMS and ActiveMQ.  The bridge 
 seems to work perfectly until I stop then restart OpenJMS while leaving 
 ActiveMQ running.  Once I restart OpenJMS I try sending a message from it to 
 ActiveMQ, but ActiveMQ doesn't receive it until I stop and restart ActiveMQ.  
 I can recreate the exact same problem by starting ActiveMQ first and then 
 OpenJMS.  After a little more reading it looks like failover should fix this 
 problem, but I tried it and it didn't work.  I submitted a question to 
 ActiveMQ and Gary Tully responded and told me there is currently no facility 
 to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.
 Assuming that remote end-points may not be using ActiveMQ then I would think 
 this would be a very important feature to have.
 Here's a link to our conversation: 
 http://www.nabble.com/How-to-configure-failover-for-jmsBridgeConnector-td25909047.html#a25918800
 The conversation also contains an attachment showing me configuration file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-3008) Queue destination bridge does not stay up

2010-10-29 Thread Trey Hyde (JIRA) 
Queue destination bridge does not stay up
-

 Key: AMQ-3008
 URL: https://issues.apache.org/activemq/browse/AMQ-3008
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.4.1, 5.3.2
Reporter: Trey Hyde


I'm not sure of cause of any of these exceptions.  The IllegalStateException 
seems be be due to the direct interaction between the OpenMQ and ActiveMQ jms 
code.   I haven't the faintest why the reconnect code can't connect again in 
the normal circumstance.  The agents that talk directly to OpenMQ do no have 
issues during these times and nothing is logged in the OpenMQ log.


2010-10-29 10:54:44,170 | ERROR | failed to forward message on attempt: 1 
reason: javax.jms.IllegalStateException: [C4064]: Cannot perform operation, 
producer is closed. message: ActiveMQMapMessage {commandId = 3, 
responseRequired = false, messageId = ID:mq1.cdlocal-27338-12
88370972745-6:24434:-1:1:1, originalDestination = null, originalTransactionId = 
null, producerId = ID:mq1.cdlocal-27338-1288370972745-6:24434:-1:1, destination 
= queue://CD.live.search.needsretrieve, transactionId = null, expiration = 0, 
timestamp = 1288374884167, arrival = 
0, brokerInTime = 1288374884167, brokerOutTime = 1288374884167, correlationId = 
null, replyTo = null, persistent = true, type = null, priority = 0, groupID = 
null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = 
null, content = org.apache.activemq.ut
il.byteseque...@224f68dc, marshalledProperties = 
org.apache.activemq.util.byteseque...@b6d551d, dataStructure = null, 
redeliveryCounter = 0, size = 1797, properties = {transformation=jms-map-json}, 
readOnlyProperties = true, readOnlyBody = true, droppable = false} ActiveMQMa
pMessage{ theTable = {} } | org.apache.activemq.network.jms.DestinationBridge | 
ActiveMQ Session: ID:mq1.cdlocal-27338-1288370972745-4:0:2
javax.jms.IllegalStateException: [C4064]: Cannot perform operation, producer is 
closed.
at 
com.sun.messaging.jmq.jmsclient.MessageProducerImpl.checkState(MessageProducerImpl.java:175)
at 
com.sun.messaging.jmq.jmsclient.MessageProducerImpl.send(MessageProducerImpl.java:719)
at 
com.sun.messaging.jmq.jmsclient.QueueSenderImpl.send(QueueSenderImpl.java:145)
at 
org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:80)
at 
org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:129)
at 
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1229)
at 
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)
at 
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)
at 
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
at 
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
2010-10-29 10:54:45,179 | ERROR | failed to forward message on attempt: 2 
reason: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on 
connection creation [search2.cdlocal:6076]. - cause: java.net.ConnectException: 
Connection refused message: ActiveMQMapMessage {co
mmandId = 3, responseRequired = false, messageId = 
ID:mq1.cdlocal-27338-1288370972745-6:24434:-1:1:1, originalDestination = null, 
originalTransactionId = null, producerId = 
ID:mq1.cdlocal-27338-1288370972745-6:24434:-1:1, destination = 
queue://CD.live.search.needsretrieve, t
ransactionId = null, expiration = 0, timestamp = 1288374884167, arrival = 0, 
brokerInTime = 1288374884167, brokerOutTime = 1288374884167, correlationId = 
null, replyTo = null, persistent = true, type = null, priority = 0, groupID = 
null, groupSequence = 0, targetConsumerId =
 null, compressed = false, userID = null, content = 
org.apache.activemq.util.byteseque...@224f68dc, marshalledProperties = 
org.apache.activemq.util.byteseque...@b6d551d, dataStructure = null, 
redeliveryCounter = 0, size = 1797, properties = {transformation=jms-map-json}, 
rea
dOnlyProperties = true, readOnlyBody = true, droppable = false} 
ActiveMQMapMessage{ theTable = {} } | 
org.apache.activemq.network.jms.DestinationBridge | ActiveMQ Session: 
ID:mq1.cdlocal-27338-1288370972745-4:0:2
com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection 
creation [search2.cdlocal:6076]. - cause: java.net.ConnectException: Connection 
refused
at 
com.sun.messaging.jmq.jmsclient.ExceptionHandler.throwConnectionException(ExceptionHandler.java:274)
at 
com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:220)
at 
com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:241)
at 
com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:150)
at

[jira] Commented: (AMQ-2455) Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.

2010-10-26 Thread Trey Hyde (JIRA) 

[ 
https://issues.apache.org/activemq/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62847#action_62847
 ] 

Trey Hyde commented on AMQ-2455:


This issue is certainly not fixed for me in 5.4.1.   Is there any additional 
configuration I need to do? Source and config for my bridge setup to OpenMQ 
is here : http://github.com/centraldesktop/openmq-spring-bean

 Need a facility to retry jms connections to a foreign provider by the 
 ActiveMQ JMS bridge.
 --

 Key: AMQ-2455
 URL: https://issues.apache.org/activemq/browse/AMQ-2455
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker
 Environment: Debian Lenny.  ActiveMQ 5.2.  OpenJMS-0.7.7-beta-1
Reporter: Billy Buzzard
Assignee: Rob Davies
 Fix For: 5.4.0

 Attachments: bridge-reconnect.patch, test.zip


 I followed an example 
 (http://www.codeproject.com/KB/docview/jms_to_jms_bridge_activem.aspx?display=Print)
  showing how to set up a bridge between OpenJMS and ActiveMQ.  The bridge 
 seems to work perfectly until I stop then restart OpenJMS while leaving 
 ActiveMQ running.  Once I restart OpenJMS I try sending a message from it to 
 ActiveMQ, but ActiveMQ doesn't receive it until I stop and restart ActiveMQ.  
 I can recreate the exact same problem by starting ActiveMQ first and then 
 OpenJMS.  After a little more reading it looks like failover should fix this 
 problem, but I tried it and it didn't work.  I submitted a question to 
 ActiveMQ and Gary Tully responded and told me there is currently no facility 
 to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.
 Assuming that remote end-points may not be using ActiveMQ then I would think 
 this would be a very important feature to have.
 Here's a link to our conversation: 
 http://www.nabble.com/How-to-configure-failover-for-jmsBridgeConnector-td25909047.html#a25918800
 The conversation also contains an attachment showing me configuration file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-2480) Stomp Transport Dispatcher Fails on NPE

2010-10-21 Thread Trey Hyde (JIRA) 

[ 
https://issues.apache.org/activemq/browse/AMQ-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62738#action_62738
 ] 

Trey Hyde commented on AMQ-2480:


I have this issue with 5.4.1.  I got it within a few minutes of starting up the 
broker.  I did not have this issue in the ~6month that 5.3.1 was up with the 
same setup.

 Stomp Transport Dispatcher Fails on NPE
 ---

 Key: AMQ-2480
 URL: https://issues.apache.org/activemq/browse/AMQ-2480
 Project: ActiveMQ
  Issue Type: Bug
  Components: Transport
Affects Versions: 5.3.0, 5.4.0
 Environment: Windows XP, JRE6
Reporter: Ben
 Fix For: 5.5.0


 We have been using ActiveMQ 5.2 on Windows for about 6months with a 
 relatively low message throughput (a maximum usage 1 message every 4 seconds, 
 nothing crazy) and it was working perfectly.  We have several clients that 
 connect through either an OpenWire or Stomp connection and communicate 
 through Queues.   
 Several days ago I started testing higher throughput (several 
 messages/second) messaging by publishing to a Queue from an OpenWire 
 connection and consuming the message on a Stomp connection.  At some point 
 there is a failure in the Dispatcher for the Stomp connection and my client 
 stops receiving messages.  The OpenWire connection is unaffected and 
 continues filling the Queue.  I have since upgraded to ActiveMQ 5.3 because 
 there were some issues fixed related to Stomp connection, but still see the 
 same issue.  The only exception is :
 Exception in thread ActiveMQ Connection Dispatcher: /127.0.0.1:3047 
 java.lang.NullPointerException 
 at 
 org.apache.activemq.transport.stomp.LegacyFrameTranslator.convertMessage(LegacyFrameTranslator.java:69)
  
 at 
 org.apache.activemq.transport.stomp.ProtocolConverter.convertMessage(ProtocolConverter.java:594)
  
 at 
 org.apache.activemq.transport.stomp.StompSubscription.onMessageDispatch(StompSubscription.java:92)
  
 at 
 org.apache.activemq.transport.stomp.ProtocolConverter.onActiveMQCommand(ProtocolConverter.java:576)
  
 at 
 org.apache.activemq.transport.stomp.StompTransportFilter.oneway(StompTransportFilter.java:56)
  
 at 
 org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40) 
 at 
 org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1190)
  
 at 
 org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:779)
  
 at 
 org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:815)
  
 at 
 org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
  
 at 
 org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
  
 I thought I would also note that with the nice new Connector page on the 
 admin interface it shows the connection to my Stomp client as connected, and 
 similarly the Queues page lists the Stomp consumer on the Queue, but the 
 pending messages just keeps growing.
 The client library we are using for the Stomp connection is from Codehaus 
 (http://stomp.codehaus.org/C).  Our OpenWire connection is utilizing Spring 
 frameworks JMS library.
 I'm going to continue to look for a test case to reproduce my error. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.