On 3/9/07, AsaUK <[EMAIL PROTECTED]> wrote:
I am using activemq-rar-4.1-SNAPSHOT.rar Maybe that is not recent enough.
Still I am not too worried about that one as I can easily upgrade at a later
date or just build the source.
I think you are right with the null pointer, not a top error though.
I am using activemq-rar-4.1-SNAPSHOT.rar Maybe that is not recent enough.
Still I am not too worried about that one as I can easily upgrade at a later
date or just build the source.
I think you are right with the null pointer, not a top error though. I will
try and get that working.
The external
On 3/9/07, AsaUK <[EMAIL PROTECTED]> wrote:
Hi James,
I am working along with Nic on this one. I have uploaded the rar file fine
with the only parameter set being BrokerXmlConfig as
"broker:(tcp://localhost:61616)" I can then connect to the appserver jms
from an outside client using 4.0.x (can
Hi James,
I am working along with Nic on this one. I have uploaded the rar file fine
with the only parameter set being BrokerXmlConfig as
"broker:(tcp://localhost:61616)" I can then connect to the appserver jms
from an outside client using 4.0.x (can't use 4.1 as the rar does not have
openwire v
On 3/9/07, nicpillinger <[EMAIL PROTECTED]> wrote:
If we deploy the activemq resource adaptor how do we configure the embedded
broker?
How do we actually get the broker running and listening on 61616 from inside
the app server?
Its described on this page
http://activemq.apache.org/resource-adap
If we deploy the activemq resource adaptor how do we configure the embedded
broker?
How do we actually get the broker running and listening on 61616 from inside
the app server?
Once it's actually running what's the process for getting a normal mdb wired
up to listen to a queue/topic on the embedde
On 3/6/07, nicpillinger <[EMAIL PROTECTED]> wrote:
Another reason for embedding is the latency - surely if I run it standalone
the messages created within the app server have to do an extra network hop
to reach activeMQ before being distributed to the clients?
If the broker is on the same mach
On 3/6/07, nicpillinger <[EMAIL PROTECTED]> wrote:
Thanks,
I really want to wire up MDBs as well. Is it possible to have MDBs running
in the App Server subscribed to the same topic as external activeMQ clients?
Sure!
ActiveMQ can communicate with many different languages, platforms and
protoc
Another reason for embedding is the latency - surely if I run it standalone
the messages created within the app server have to do an extra network hop
to reach activeMQ before being distributed to the clients?
James.Strachan wrote:
>
> BTW you don't have to run the broker inside any app server
Thanks,
I really want to wire up MDBs as well. Is it possible to have MDBs running
in the App Server subscribed to the same topic as external activeMQ clients?
James.Strachan wrote:
>
> BTW other options are...
>
> Deploy the Web Console with an embedded broker (i.e. just deploy the
> WAR whi
10 matches
Mail list logo
