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 (it doesn't > really add much value). Why not just run the broker stand alone? > > The RAR is only really necessary for wiring MDBs to ActiveMQ. > > > On 3/6/07, nicpillinger <[EMAIL PROTECTED]> wrote: >> >> I've deployed the RAR file by dropping in the autodeploy directory. What >> next? I cant find any info what I need to do to confgure ActiveMQ as an >> embedded broker or how connect to ActiveMQ when it's embedded in Sun App >> Server. Can I still create JMS resources through the Sun App Server admin >> tool? >> >> Looking at the Sun App Server log it looks like it's listening on 7676, >> but >> connecting to that throws and error? I thought the default should be >> 61616? >> >> FWIW I'm trying to embed ActiveMQ in Sun App Server so I can use the >> apache >> nms libraries to attach my .net client to some JMS topics in Sun App >> Server >> (9). >> >> Help appreciated. >> cheers >> Nic >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/Embedding-ActiveMQ-in-Sun-App-Server-9-tf3355741s2354.html#a9332615 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Embedding-ActiveMQ-in-Sun-App-Server-9-tf3355741s2354.html#a9335654 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
