[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms
[
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38434
]
Kay Stanke commented on AMQCPP-60:
--
I upgraded to the latest trunk version and the persistence flag is now showing
up in the stacktrace.
Still no progress in seeing the message text ...
Nathan could you comment on the AMQ-1141 issue as it looks like the improvement
AMQ-748 broke the interoperability between stomp and jms. Could putting the
request-id of stomp into the correlation-id of the ActiveMQTextMessage be a fix
for that?
message information is lost from stomp message to jms
-
Key: AMQCPP-60
URL: https://issues.apache.org/activemq/browse/AMQCPP-60
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Stomp
Affects Versions: 1.1
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
Reporter: Kay Stanke
Assigned To: Nathan Mittler
Priority: Critical
Fix For: 2.0
As my producer is a cpp server program i downloaded and compiled activemq-cpp
1.0. I managed to make activemq-cpp compile and link as shared lib / dll
under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls
8.1 I use the jms to jms bridge to forward the messages. For other reasons
(see AMQ-1141) the forward fails. I can see in the dumped message:
message: ActiveMQTextMessage {commandId = 3, responseRequired = false,
messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-2844-1170064566619-5:0:-1:1,
destination = queue://TEST.FOO,
transactionId = null, expiration = 0,
timestamp = 1170064774288,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false,
userID = null, content = [EMAIL PROTECTED],
marshalledProperties = [EMAIL PROTECTED], dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {request-id=2},
readOnlyProperties = true,
readOnlyBody = true, droppable = false, text = null}
i'm missing the persistence as i used pProducer-setDeliveryMode(
DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the
message text as well. I created the message with: pMessage =
pSession-createTextMessage(messageText); with an nonempty string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms
[
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38438
]
Kay Stanke commented on AMQCPP-60:
--
Nathan,
meanwhile i patched the file FrameTranslator.java from the activemq-core.jar to
see what message arrives if the error is not happening.
I replace a line in copyStandardHeadersFromFrameToMessage
from
msg.setJMSCorrelationID((String)
headers.remove(Stomp.Headers.Send.CORRELATION_ID));
to
msg.setJMSCorrelationID((String)
headers.remove(Stomp.Headers.Connect.REQUEST_ID));
to see what message is actually sent over the bridge. I definitively only get
my message forwarded as i dumped the message content which is an xml document.
Can you exclude that the request-id is sent on every stomp message? At least i
did not send a connect message explicitely as i use the CMS interface only.
With my patch all of my information seems to be transmitted correctly, so i
guess the initial issue is resolved.
message information is lost from stomp message to jms
-
Key: AMQCPP-60
URL: https://issues.apache.org/activemq/browse/AMQCPP-60
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Stomp
Affects Versions: 1.1
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
Reporter: Kay Stanke
Assigned To: Nathan Mittler
Priority: Critical
Fix For: 2.0
As my producer is a cpp server program i downloaded and compiled activemq-cpp
1.0. I managed to make activemq-cpp compile and link as shared lib / dll
under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls
8.1 I use the jms to jms bridge to forward the messages. For other reasons
(see AMQ-1141) the forward fails. I can see in the dumped message:
message: ActiveMQTextMessage {commandId = 3, responseRequired = false,
messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-2844-1170064566619-5:0:-1:1,
destination = queue://TEST.FOO,
transactionId = null, expiration = 0,
timestamp = 1170064774288,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false,
userID = null, content = [EMAIL PROTECTED],
marshalledProperties = [EMAIL PROTECTED], dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {request-id=2},
readOnlyProperties = true,
readOnlyBody = true, droppable = false, text = null}
i'm missing the persistence as i used pProducer-setDeliveryMode(
DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the
message text as well. I created the message with: pMessage =
pSession-createTextMessage(messageText); with an nonempty string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1141) JMS to JMS Bridge fails if message was generated from activemq-cpp 1.0 client
[
https://issues.apache.org/activemq/browse/AMQ-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38439
]
Kay Stanke commented on AMQ-1141:
-
The patch i applied was in file
org.apache.activemq.command.ActiveMQTempDestination in the method
setPhysicalName.
There was a number format exception raised as the string was not properly
checked. Basically the patch is just some check against null and length of
seqStr before parsing and catching of any NumberFormatException.
I would think that this could not cause an unintended sending of a connect
message. I am wondering if the request-id is really only send for connect
messages as i see it in any message going over the bridge even if i can
validate that the message contains my own content.
As i commented on AMQCPP-60 i patched
replace a line in copyStandardHeadersFromFrameToMessage from
msg.setJMSCorrelationID((String)
headers.remove(Stomp.Headers.Send.CORRELATION_ID));
to
msg.setJMSCorrelationID((String)
headers.remove(Stomp.Headers.Connect.REQUEST_ID));
in org.apache.activemq.transport.stomp.FrameTranslator.java (inner class
helper).
From my understanding this class is relevant if messages have to be converted
in and from the activemq format.
JMS to JMS Bridge fails if message was generated from activemq-cpp 1.0 client
-
Key: AMQ-1141
URL: https://issues.apache.org/activemq/browse/AMQ-1141
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 4.1.0
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6, ActiveMQ-CPP 1.0
Reporter: Kay Stanke
Attachments: activemq.xml
I'm using a jms to jms bridge from activemq to bea wls 8.1 My activemq
version is a patched 4.1 with the fix for issue AMQ-1110 to decouple me from
the release of activemq 4.2.
As my producer is a cpp server program i downloaded and compiled activemq-cpp
1.0. I managed to make activemq-cpp compile and link as shared lib / dll
under vc 7.1 (Visual Studio .NET 2003).
By sending a textmessage to the activemq-queue releated to the jms bridge the
message is not forwarded and i get the following stacktrace:
ERROR DestinationBridge - failed to forward message on attempt:
1
reason: weblogic.jms.common.MessageFormatException: Illegal property name,
'request-id'
message: ActiveMQTextMessage {commandId = 3, responseRequired = false,
messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-2844-1170064566619-5:0:-1:1,
destination = queue://TEST.FOO,
transactionId = null, expiration = 0,
timestamp = 1170064774288,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false,
userID = null, content = [EMAIL PROTECTED],
marshalledProperties = [EMAIL PROTECTED], dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {request-id=2},
readOnlyProperties = true,
readOnlyBody = true, droppable = false, text = null}
weblogic.jms.common.MessageFormatException: Illegal property name,
'request-id'
at weblogic.jms.common.MessageImpl.setObjectProperty(MessageImpl.java:1032)
at weblogic.jms.common.MessageImpl.init(MessageImpl.java:281)
at weblogic.jms.common.TextMessageImpl.init(TextMessageImpl.java:47)
at weblogic.jms.common.TextMessageImpl.init(TextMessageImpl.java:39)
at weblogic.jms.client.JMSProducer.convertMessage(JMSProducer.java:558)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:331)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:152)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:215)
at
org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:87)
at
org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:134)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:840)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:96)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:165)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
This issue seems to be related to AMQ-748
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-63) asynchronous send
[ https://issues.apache.org/activemq/browse/AMQCPP-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38440 ] Timothy Bish commented on AMQCPP-63: I've taken an hour and implemented the Async send functionality. Its not a perfect solution so I think we will refactor it at some point in the future. To use the new functionality you simple need to add useAsyncSend to the Broker URL as you would on the Java client. All Sessions created on that connection will be in Async Mode, so if you need a mix of Async and Non-Async Sessions you will need a separate connection that omits the useAsyncSend flag. asynchronous send - Key: AMQCPP-63 URL: https://issues.apache.org/activemq/browse/AMQCPP-63 Project: ActiveMQ C++ Client Issue Type: New Feature Components: CMS Impl, Openwire, Stomp Affects Versions: 1.1, 2.0 Environment: Sun Solaris/any Reporter: L:esha Masterov Assigned To: Timothy Bish Priority: Minor Fix For: 2.0 Please allow for asynchronous send in the C++ client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQCPP-63) asynchronous send
[ https://issues.apache.org/activemq/browse/AMQCPP-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-63. Resolution: Fixed Implemented in Trunk asynchronous send - Key: AMQCPP-63 URL: https://issues.apache.org/activemq/browse/AMQCPP-63 Project: ActiveMQ C++ Client Issue Type: New Feature Components: CMS Impl, Openwire, Stomp Affects Versions: 1.1, 2.0 Environment: Sun Solaris/any Reporter: L:esha Masterov Assigned To: Timothy Bish Priority: Minor Fix For: 2.0 Please allow for asynchronous send in the C++ client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQCPP-66) Refactor the Async send to happen in an Async Transport instead of in ActiveMQSession
Refactor the Async send to happen in an Async Transport instead of in ActiveMQSession - Key: AMQCPP-66 URL: https://issues.apache.org/activemq/browse/AMQCPP-66 Project: ActiveMQ C++ Client Issue Type: Improvement Affects Versions: 1.1, 2.0 Reporter: Timothy Bish Assigned To: Timothy Bish Priority: Minor Fix For: 2.1 We should re-factor the code that implements the Async Send feature to use an TransportFilter dervied class that handles the async send stuff. This would reduce the overhead as right now, each session creates a thread for sends, where this class would only need one thread and everyone would just make use of it. We need this issue to get done first I think so that we can cleanly implement this. https://issues.apache.org/activemq/browse/AMQCPP-65 One other thing we might want to think about here is the lifetime of objects that are sent when in async mode. Currently all messages are cloned and deleted by the session. We may want to think about changing the CMS API to require that objects are owned by us once you pass them to a send call. Then we can control the lifetime and delete it when we are done with it without having to clone the message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Svn repo moved
The svn repo has been moved to https://svn.apache.org/repos/asf/activemq/ You should be able to update using a svn switch --relocate ... -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Website Up!
http://activemq.apache.org/ is live :-) No we need to remove the Incubator stuff from it :-) -Brian
[jira] Commented: (AMQCPP-60) message information is lost from stomp message to jms
[
https://issues.apache.org/activemq/browse/AMQCPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38443
]
Nathan Mittler commented on AMQCPP-60:
--
I think I found it ... as you had indicated, we were sending the request-id
with all messages (supposed to only send on connect message). This is fixed in
trunk. Give it a shot.
message information is lost from stomp message to jms
-
Key: AMQCPP-60
URL: https://issues.apache.org/activemq/browse/AMQCPP-60
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Stomp
Affects Versions: 1.1
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6, ActiveMQ-CPP 1.0, ActiveMQ 4.1 patched with Fix for AMQ-1110
Reporter: Kay Stanke
Assigned To: Nathan Mittler
Priority: Critical
Fix For: 2.0
As my producer is a cpp server program i downloaded and compiled activemq-cpp
1.0. I managed to make activemq-cpp compile and link as shared lib / dll
under vc 7.1 (Visual Studio .NET 2003). My consumer is located on a bea wls
8.1 I use the jms to jms bridge to forward the messages. For other reasons
(see AMQ-1141) the forward fails. I can see in the dumped message:
message: ActiveMQTextMessage {commandId = 3, responseRequired = false,
messageId = ID:KStanke-2844-1170064566619-5:0:-1:1:1,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-2844-1170064566619-5:0:-1:1,
destination = queue://TEST.FOO,
transactionId = null, expiration = 0,
timestamp = 1170064774288,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false,
userID = null, content = [EMAIL PROTECTED],
marshalledProperties = [EMAIL PROTECTED], dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {request-id=2},
readOnlyProperties = true,
readOnlyBody = true, droppable = false, text = null}
i'm missing the persistence as i used pProducer-setDeliveryMode(
DeliveryMode::PERSISTANT ); As my message is a text message i'm missing the
message text as well. I created the message with: pMessage =
pSession-createTextMessage(messageText); with an nonempty string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQCPP-62) Broken CLIENT_ACKNOWLEDGE
[ https://issues.apache.org/activemq/browse/AMQCPP-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38444 ] Nathan Mittler commented on AMQCPP-62: -- I've made a fix to the validation of received ack messages. Give the latest trunk a whirl. Broken CLIENT_ACKNOWLEDGE - Key: AMQCPP-62 URL: https://issues.apache.org/activemq/browse/AMQCPP-62 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.0, 1.1 Environment: Windows XP SP2 Visual C++ 8 Reporter: Manuel Vivo Assigned To: Nathan Mittler Fix For: 2.0 Attachments: test-1-0.zip, test-1-1.zip We've been trying to use the CLIENT_ACKNOWLEDGE mode without success. As a test, we've modified the example code in the distribution so it uses CLIENT_ACKNOWLEDGE, and it gives an error. I'm attaching the modified C++ code, and the output. We're using the release versions of ActiveMQ (4.1.0) and ActiveMQ CPP (1.0) We've tried also with the latest snapshot of ActiveMQ (apache-activemq-4.2-incubator-20070120.082020-21.zip) and the version 1.1 of ActiveMQ CPP, downloaded with svn co https://svn.apache.org/repos/asf/incubator/activemq/activemq-cpp/tags/activemq-cpp-1.1 It doesn't work either, but the error message is different. I'm attaching the modified code and the related output also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
