activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher G. Stach II" <>
Subject Re: Problems with VM transport
Date Wed, 28 Mar 2007 01:56:57 GMT
Adrian Co wrote:
> Yeah. tcp would refer to an external broker. Can you post the complete
> stack trace?
> BTW, can you try using broker.useJmx=false instead of just useJmx=false?
> Is the exception occu
> wrote:
>> Suchitha,
>> Thanks for your help. I thought a URL of the form "tcp://<host>..."
>> refers to
>> an external broker, not an embedded one? Am I mistaken?
>> I need to run the broker within the servlet container VM, not as a
>> separate process.

``tcp'' can refer to _any_ broker, local or remote, that has a TCP
transportConnector.  If you run a vm broker in one webapp and expect
another webapp to talk to it, you just might run into classloader problems.

Christopher G. Stach II

View raw message