On 3/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
From: "Christopher G. Stach II" <[EMAIL PROTECTED]>
> ``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
From: "Christopher G. Stach II" <[EMAIL PROTECTED]>
> ``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
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
>
> [EMAIL PROTECTED] wrote:
>> Suchitha,
>>
>> Thanks for your help. I thought a URL of
TED]
Sent: Monday, March 26, 2007 8:31 PM
To: users@activemq.apache.org
Subject: Re: Problems with VM transport
To follow up on my last mail: I can perhaps avoid the problem by using
distinct brokernames for each webapp; but that would create distinct
embedded brokers perhaps? I need both the
here by the broker is a part of
> servlets web app.
>
>
>
>
> Hope this helps.
> Thanks,
> Suchitha.
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 26, 2007 8:31 PM
> To: users@activ
PROTECTED]
Sent: Monday, March 26, 2007 8:31 PM
To: users@activemq.apache.org
Subject: Re: Problems with VM transport
To follow up on my last mail: I can perhaps avoid the problem by using
distinct brokernames for each webapp; but that would create distinct
embedded brokers perhaps? I need both t
To follow up on my last mail: I can perhaps avoid the problem by
using distinct brokernames for each webapp; but that would
create distinct embedded brokers perhaps? I need both the webapps
to share the same broker so they receive messages published
by each other.
Regards,
/U
-- O
Hi -
I am using the embedded broker in a servlet container. Each webapp in the
servlet
container instantiates a connection factory that refers to broker URL of
vm://localhost?broker.persistent=false
as follows:
(Servlet Container
(WebApp1
[EMAIL PROTECTED] wrote:
Adrian,
Thanks for the note.
> >Startup: vm://localhost
> >During runtime (after an event):
> >failover(vm://localhost,tcp://remote:61616)
> >
> > Would modifying the broker URL of the connection factory cause
p
Adrian,
Thanks for the note.
> >Startup: vm://localhost
> >During runtime (after an event):
> >failover(vm://localhost,tcp://remote:61616)
> >
> > Would modifying the broker URL of the connection factory cause
problems?
> >
[EMAIL PROTECTED] wrote:
Hello...
I have a couple of basic questions on ActiveMQ. I would appreciate any hits as
I am stuck.
I am using ActiveMQ 4.1 with JDK6.
1) When I use an embedded broker with vm transport (vm://localhost)
the instantiation of my Spring SimpleMessageListenerContainer
alw
.
-Original Message-
From: Manish Gulati [mailto:[EMAIL PROTECTED]
Sent: Monday, March 26, 2007 10:08 AM
To: users@activemq.apache.org
Subject: RE: Problems with VM transport
Hi,
For JournalLockedException, include activeio-core-3.0-beta4.jar (you may
have different version of this) in your
copies without reading or saving
in any manner. Thank you.
-Original Message-
From: Christopher G. Stach II [mailto:[EMAIL PROTECTED]
Sent: Monday, March 26, 2007 8:42 AM
To: users@activemq.apache.org
Subject: Re: Problems with VM transport
[EMAIL PROTECTED] wrote:
> Hello...
>
>
[EMAIL PROTECTED] wrote:
> Hello...
>
> I have a couple of basic questions on ActiveMQ. I would appreciate any hits
> as I am stuck.
>
> I am using ActiveMQ 4.1 with JDK6.
>
> 1) When I use an embedded broker with vm transport (vm://localhost)
> the instantiation of my Spring SimpleMessageListe
I can only speak to #3. There is a spelling error the URL should read:
vm://localhost?broker.persistent=false
I am using a Spring SimpleMessageListenerContainer on jdk1.6 on linux
with 4.1.1RC1 without the issue you describe. I am fairly sure it
worked with 4.1 too, with a non-persistent broker
15 matches
Mail list logo