[jira] Commented: (AMQCPP-157) Interoperability issues between C++ and .NET

2007-12-14 Thread Robert Winslow (JIRA)
[ https://issues.apache.org/activemq/browse/AMQCPP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40853 ] Robert Winslow commented on AMQCPP-157: --- My computer lab at home has all the hardware needed for testing this.

[jira] Commented: (AMQCPP-157) Interoperability issues between C++ and .NET

2007-12-14 Thread Robert Winslow (JIRA)
[ https://issues.apache.org/activemq/browse/AMQCPP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40852 ] Robert Winslow commented on AMQCPP-157: --- Guys it might not be clear from my wall of text however, I did retest

[jira] Created: (AMQ-1520) release 5.0.0 depends on SNAPSHOT version of activeio

2007-12-14 Thread Petr Kozelka (JIRA)
release 5.0.0 depends on SNAPSHOT version of activeio - Key: AMQ-1520 URL: https://issues.apache.org/activemq/browse/AMQ-1520 Project: ActiveMQ Issue Type: Bug Reporter: Petr Ko

[jira] Created: (AMQCPP-158) libtool release and version-info arguments need to be set correctly

2007-12-14 Thread Daniel Pocock (JIRA)
libtool release and version-info arguments need to be set correctly --- Key: AMQCPP-158 URL: https://issues.apache.org/activemq/browse/AMQCPP-158 Project: ActiveMQ C++ Client Is

[jira] Created: (AMQ-1519) Broker Should be started async to avoid a slave broker from blocking the startup of J2EE server (like JBoss)

2007-12-14 Thread Hiram Chirino (JIRA)
Broker Should be started async to avoid a slave broker from blocking the startup of J2EE server (like JBoss) Key: AMQ-1519 URL: https://issues.apache.org/

Re: Getting WARN: Local transaction had not been commited. Commiting now.

2007-12-14 Thread Hiram Chirino
What that means is that the XA transaction was not started by the container. And a local transaction was being used. Which was also not terminated by the container. So ActiveMQ is going to commit if for since the onMessage() did not produce an exception. You will need to look into you MDB conta

Re: Message transforming on broker

2007-12-14 Thread Hiram Chirino
I personally think that a STOMP client should request a transformation strategy. For example on a subscribe, he could do SUBSCRIBE destination: /queue/foo transformation: jms-json ack: client And on the reverse side, The send could look like: SEND destination:/queue/a transformation: jms-json

Re: jndi.properties setting in activemq

2007-12-14 Thread Hiram Chirino
Hi, just make sure that the directory holding the jndi.properties file is the first directory on the classpath of your application. On Dec 14, 2007 11:26 AM, activemqnewbie <[EMAIL PROTECTED]> wrote: > > Hi, > Am using jndi.properties in activemq. > Though i have changed my jndi.properties,my cl

jndi.properties setting in activemq

2007-12-14 Thread activemqnewbie
Hi, Am using jndi.properties in activemq. Though i have changed my jndi.properties,my class is still reading values from the cached jndi.property. I checked for any other instances of jndi.property file but couldn't find any in my sys. Also tried setting new jndi.property file in class path. Appr

[jira] Created: (AMQ-1518) NetworkConnector is leaking a thread if broker disconnects

2007-12-14 Thread Rob Davies (JIRA)
NetworkConnector is leaking a thread if broker disconnects -- Key: AMQ-1518 URL: https://issues.apache.org/activemq/browse/AMQ-1518 Project: ActiveMQ Issue Type: Bug Component

Re: Message transforming on broker

2007-12-14 Thread Dejan Bosanac
And now to continue :) sorry about this ... > I was thinking recently if there should be a configurable support for > message transforming on the broker level. For example, one use case > would be to do XML/Object transformation of all messages > received/transmitted through the Stomp protoc

Re: why i can not send this message out?

2007-12-14 Thread bill richard
in what kinds of situation,AMQ will block on MessageProducer.send()? when the derbyDB is full? I m now in this trouble. Any help will be great! bill richard wrote: > > i just find that it was not because of this message.after i reboot the > message center,it works. > but i still can not figure

Message transforming on broker

2007-12-14 Thread Dejan Bosanac
I was thinking recently if there should be a configurable support for message transforming on the broker level. For example, one use case would be to do XML/Object transformation of all messages received/transmitted through the Stomp protocol. I guess now that Camel is integrated in AMQ -- Dejan