On Fri, 2012-08-03 at 00:08 +0200, Jakob Ericsson wrote:
> Hi,
>
> We have a small activemq setup that uses the JMSBridge against a Sonic
> MQ. This works fine in production where we use 5.5.1 version.
>
> I am now testing upgrade to 5.6.0 because there where some bugs I
> wanted fixed (speciall
Hi,
We have a small activemq setup that uses the JMSBridge against a Sonic
MQ. This works fine in production where we use 5.5.1 version.
I am now testing upgrade to 5.6.0 because there where some bugs I
wanted fixed (specially
https://issues.apache.org/jira/browse/AMQ-3137).
But the JMSBridge ou
Hi Tim,
Thank you for your quick reply.
I have tried to invoke session creating in another thread and it works.
Thanks
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CreateSession-failover-timeout-after-a-connection-is-resumed-tp4654721p4654725.html
Sent from
On Thu, 2012-08-02 at 06:29 -0700, Bo wrote:
> I'm using ActiveMQ 5.6.0 and ActiveMQ NMS client.
>
> I connect to the broker using the follow code:
>
> var connectionFactory = new ConnectionFactory(
> "failover:(tcp://localhost:61616)?transport.timeout=5000"
> );
>
> connection = connec
I'm using ActiveMQ 5.6.0 and ActiveMQ NMS client.
I connect to the broker using the follow code:
var connectionFactory = new ConnectionFactory(
"failover:(tcp://localhost:61616)?transport.timeout=5000"
);
connection = connectionFactory.CreateConnection();
connection.Start();
connect
Thanks for replies...
Any message actually never got lost. What I saw was just a few confusing
observations:)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Lost-non-persistent-messages-tp4654526p4654718.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
On trunk, there is a repository in the pom where those dependencies
can be found,
they are used by the console module.
have a peek at:
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-console/pom.xml?hb=true#to49
On 1 August 2012 20:31, Vitaliy Semochkin wrote:
> Hi,
>
> I've proba
just report it against the broker
On 1 August 2012 20:31, Vitaliy Semochkin wrote:
> Hi,
>
> I've probably found a bug in maven-activemq-plugin versoins
> 5.4.0-5.6.0 (5.3.0 is the last version which is not affected).
>
> The problem is 5.4.0-5.6.0 versions of maven-activemq-plugin depend on
> ne
ActiveMQ uses SLF4J logging framework.
It can integrate Log4J. To do so add the jar files slf4j-api and slf4j-log4j12
to your classpath.
The broker should then hopefully initialize logging successfully.
Regards,
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Aug 1, 2012, at 10
