> > > OH - here's an example of what gets printed to the logs when it works
> > > >
> > > >
> > > >
> > > > and the message that seems to break it
> > > >
> > > >
> > > >
> > > > --
> >
hen it works
> > >
> > >
> > >
> > > and the message that seems to break it
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://activemq.2283324.n4.nabble.com/JMS-goes-in-sometime
dw wrote:
>
> > OH - here's an example of what gets printed to the logs when it works
> >
> >
> >
> > and the message that seems to break it
> >
> >
> >
> > --
> > View this message in context:
> > http://a
On Thu, 2012-02-23 at 19:38 -0800, davidw wrote:
> OH - here's an example of what gets printed to the logs when it works
>
>
>
> and the message that seems to break it
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com
OH - here's an example of what gets printed to the logs when it works
and the message that seems to break it
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-goes-in-sometimes-STOMP-comes-out-but-not-always-tp4416098p4416114.html
Sent from the ActiveMQ -
on
{
if (connection == null)
connection = connectionFactory.createConnection();
return connection;
}
}
Cheers,
-- David
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-goes-in-sometimes-STOMP-comes-out-but-not-always-tp4416098p4416098.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
