activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uma...@comcast.net
Subject Re: Problems with VM transport
Date Wed, 28 Mar 2007 05:51:36 GMT

    From: "Christopher G. Stach II" <cgs@ldsys.net>
    > ``tcp'' can refer to _any_ broker, local or remote, that has a TCP 
    > transportConnector. 

I understand; it is also my understanding that TCP transport connector
may be used only if the broker running as a distinct process - either
on the localhost or remotely. I am referring to such a broker as "external
broker" as opposed to one that uses "VM" transport and is hence 'embedded'
inside the (J)VM which defines it. Is this terminology correct?

I just saw Suchitha's response where she says that embedded brokers
may also use TCP connector. Is that possible at all?


    > If you run a vm broker in one webapp and expect
    >another webapp to talk to it, you just might run into classloader problems.

Does this mean that distinct webapps in a servlet container wishing to share
a broker may not use an embedded ("VM") broker?

Thanks,

/U





 -------------- Original message ----------------------
From: "Christopher G. Stach II" <cgs@ldsys.net>
> 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
> > 
> > uma_rk@comcast.net 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
> 


Mime
View raw message