ActivemQ - starting the broker

[Sonia_08 <si...@gmail.com>]

Hi
i want to upgrate from 4.1.1 to 5.0.0 version of ActiveMq. I have updated
the jars in my Jboss Server. But when i start my jboss, it says
Could not connect to broker URL: tcp:/localhost:55000. Reason:
java.net.ConnectException: Connection refused ]
I changed the port number from 80 to 8080 to 61616 to 55000. Still the
broker hasnt got started. Can anyone help me out with this. The same used to
work with the 4.1.1 verion
Thanks in advance
-- 
View this message in context: http://www.nabble.com/ActivemQ---starting-the-broker-tp16822371s2354p16822371.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActivemQ - starting the broker

[Sonia_08 <si...@gmail.com>]

Hi,
  Thanks for the suggestion. It really helped. And yes, it was a typo. I
somehow missed on '/' :)
  But i have one more query, i want the broker to be a prt of my jboss
server and start up as my jboss server starts. As of now, am starting it
separately from the bin folder, is there any way where in we can start the
broker directly as the jboss server is starting?

Thanks



Fred D wrote:
> 
> 
> Hi,
> 
> I noticed only 1 slash in the URL .... could it be a typo? or just in the
> error message
> 
> It should be:
> "tcp://localhost:55000"
> 
> in the config xml file.
> 
> If this is not it ... try running a standalone broker (right after
> unzipping the binary package) to see if that works as a start.
> 
> Fred
> 

-- 
View this message in context: http://www.nabble.com/ActivemQ---starting-the-broker-tp16822371s2354p16842248.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActivemQ - starting the broker

[Fred D <fr...@ttmsolutions.com>]

Hi,

I noticed only 1 slash in the URL .... could it be a typo? or just in the
error message

It should be:
"tcp://localhost:55000"

in the config xml file.

If this is not it ... try running a standalone broker (right after unzipping
the binary package) to see if that works as a start.

Fred

-----
Goto www.ttmsolutions.com for a free ActiveMQ user guide 
-- 
View this message in context: http://www.nabble.com/ActivemQ---starting-the-broker-tp16822371s2354p16826241.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

RE: STOMP and Failover transport

[Dylan Vanderhoof <Dy...@semaphore.com>]

I believe Ramit Arora and Simon Wistow from this list are also working separatly on failover transport for Net::Stomp and have access to PAUSE for uploading to CPAN.  It might be worth pinging them to avoid duplication of effort and get a One True Module(tm) out for the perl community.

(Speaking as a party who wants a Net::Stomp with failover and doesn't have the cycles to do it.  :P)

-D

> -----Original Message-----
> From: Valerio VALDEZ Paolini [mailto:valerio.paolini@staff.dada.net]
> Sent: Tuesday, April 22, 2008 7:41 AM
> To: users@activemq.apache.org
> Subject: STOMP and Failover transport
>
>
> Hi All,
>
> I'm working on an improved STOMP client written in Perl and I
> need some
> clarifications about the behaviour of the failover transport.
>
> Let's suppose that a client, configured to use two hosts in
> failover A and B,
> opens a TCP connection to broker A, connects, subscribes to
> some destinations
> and then waits for incoming messages.
>
> Let's suppose now that broker A is switched off, is it
> correct that, after
> connecting successfully to broker B, the client re-connects,
> subscribes again
> to all previously subscribed destinations and then tries
> again to receive
> messages?
>
> Is there any case in which a failover shouldn't try to
> restore the situation
> before the transport failure?
>
> Thanks,
>
>         Valerio
>
>
> --
>
> Valerio Paolini - valerio.paolini@staff.dada.net
> The lyf so short, the craft so long to lerne - Geoffrey Chaucer
>

STOMP and Failover transport

[Valerio VALDEZ Paolini <va...@staff.dada.net>]

Hi All,

I'm working on an improved STOMP client written in Perl and I need some 
clarifications about the behaviour of the failover transport.

Let's suppose that a client, configured to use two hosts in failover A and B, 
opens a TCP connection to broker A, connects, subscribes to some destinations 
and then waits for incoming messages.

Let's suppose now that broker A is switched off, is it correct that, after 
connecting successfully to broker B, the client re-connects, subscribes again 
to all previously subscribed destinations and then tries again to receive 
messages?

Is there any case in which a failover shouldn't try to restore the situation 
before the transport failure?

Thanks,

        Valerio


-- 

Valerio Paolini - valerio.paolini@staff.dada.net
The lyf so short, the craft so long to lerne - Geoffrey Chaucer