Re: ActiveMQ NMS and Failure Recovery

[Jim Gomes]

It seems like you reinvented the wheel a little bit there, but I'm glad you
got it to work for you.

Cheers!


On Wed, Oct 12, 2016, 8:36 AM magmasystems 
wrote:

> Thanks Jim and Tim. I managed to hook up a poor-man's recover mechanism.
> Our
> application uses a framework that sits over the various low-level messaging
> APIs, such ActiveMQ NMS, Tibco EMS .NET client, and the .NET RabbitMQ
> client. So we actually have thin "proxy objects" sitting on top of the
> native MessageConsumers and MessageProducers. When we detect a broker
> failure, we instantiate a new connection and new sessions, and we recreate
> the MessageConsumers and MessageProducers that the application was using.
> Not the most elegant solution, but it was accomplished in a few lines of
> code and seems to work.
>
> The most difficult thing to do (which is not too difficult, and only
> involved finding the correct combination of BindingFlags to use) is to copy
> the listener from the old MessageConsumer to the new MessageConsumer.
>
> var handler = typeof(MessageConsumer).GetField("listener",
> BindingFlags.DeclaredOnly | BindingFlags.Instance | BindingFlags.NonPublic
> |
> BindingFlags.GetField).GetValue(nativeMessageConsumer);
> newMessageConsumer.Listener += handler;
>
> So
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-NMS-and-Failure-Recovery-tp4717704p4717848.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

Oh ok. Anyhow, I feel the configuration still seems fine.  It still doesnt
explain the WARNING entry.

On Oct 12, 2016 8:53 PM, "Tim Bain [via ActiveMQ]" <
ml-node+s2283324n4717847...@n4.nabble.com> wrote:

> Unfortunately the use of the term "discovery" is misleading.  The term is
> used as a generic superset over the discovery transport (which allows
> dynamic discovery at runtime) and the static transport (which allows
> static
> discovery at configuration time based on what's in your config file, but
> no
> dynamic discovery at runtime; the phrase "hard code" from the page you
> linked to is the relevant one).  It doesn't inherently mean you get
> dynamic
> discovery; you need to use the discovery transport for that.
>
> On Oct 12, 2016 7:25 AM, "divinedragon" <[hidden email]
> > wrote:
>
> > I was referring to this(static discovery section).
> >
> > http://activemq.apache.org/networks-of-brokers.html
> >
> >
> > On Wed, Oct 12, 2016 at 6:44 PM, Tim Bain [via ActiveMQ] <
> > [hidden email] >
> wrote:
> >
> > > I don't see anywhere that you're using the discovery transport (
> > > http://activemq.apache.org/discovery-transport-reference.html); am I
> > just
> > > not seeing it?  Automatic broker discovery isn't the default behavior;
> > you
> > > have to use the discovery transport if you want that behavior.
> > >
> > > On Oct 12, 2016 7:08 AM, "divinedragon" <[hidden email]
> > > > wrote:
> > >
> > > > I wanted to configure automatic broker discovery. As of now, I just
> > have
> > > > one broker(localhost) and that is what I configured. Isn't it how
> that
> > > > should be configured?
> > > >
> > > > On Wed, Oct 12, 2016 at 6:02 PM, Tim Bain [via ActiveMQ] <
> > > > [hidden email]  > type=node=4717831=1>>
> > > wrote:
> > > >
> > > > > OK.  And is it really pointing to localhost   (i.e. this broker is
> > > > > connecting to itself)?  I've never tried that myself, but I can't
> > > imagine
> > > > > that resulting in good behavior...  How come that URI isn't to
> some
> > > other
> > > > > (cross-site) host?
> > > > >
> > > > > Tim
> > > > >
> > > > > On Oct 12, 2016 1:04 AM, "divinedragon" <[hidden email]
> > > > > > wrote:
> > > > >
> > > > > > Oh my bad. Sorry about the type. The value is this.
> > > > > >
> > > > > > JMS_X_SITE_CSV_URL=ssl://localhost:7031/
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> > > > > > [hidden email]  > > > type=node=4717827=1>>
> > > > > wrote:
> > > > > >
> > > > > > > It looks like you're using the tcp transport to connect to an
> SSL
> > > > > > > endpoint;
> > > > > > > shouldn't you either use the ssl transport or port 7029?
> > > > > > >
> > > > > > > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > > > > > >
> wrote:
> > > > > > >
> > > > > > > > I don't suppose the value is incorrect. Here are all the
> values
> > > in
> > > > > the
> > > > > > > > properties file.
> > > > > > > >
> > > > > > > > JMS_PORT=7029
> > > > > > > > JMS_STOMP_PORT=7030
> > > > > > > > JMS_SSL_PORT=7031
> > > > > > > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > > > > > > [hidden email]  > > > > > type=node=4717820=1>>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for
> your
> > > > > > process?
> > > > > > > > Is
> > > > > > > > > it a valid URI?  Could something be wrong with that
> variable?
> > > > > > > > >
> > > > > > > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > > > > > >
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Ok. So, removing the  does get rid of
> > the
> > > > > WARN
> > > > > > > > entry.
> > > > > > > > > > But, then I don't want to remove it. What is the
> > > configuration
> > > > > > issue
> > > > > > > > > with
> > > > > > > > > > the ???
> > > > > > > > > >
> > > > > > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via
> ActiveMQ] <
> > > > > > > > > > [hidden email]  > > > > > > > type=node=4717740=1>>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Does the behavior change if you comment out your
> > > > > > > 
> > > > > > > > > > > element?  I can't think of a reason why a problem
> there
> > > would
> > > > > > > cause
> > > > > > > > > the
> > > > > > > > > > > broker to shut down, but since that's the first place
> the
> > > > > > shutdown
> > > > > > > > > > > manifests in the logs, let's see if there really is a
> > link
> > > > > > between
> > > > > > > 

Re: ActiveMQ NMS and Failure Recovery

[magmasystems]

Thanks Jim and Tim. I managed to hook up a poor-man's recover mechanism. Our
application uses a framework that sits over the various low-level messaging
APIs, such ActiveMQ NMS, Tibco EMS .NET client, and the .NET RabbitMQ
client. So we actually have thin "proxy objects" sitting on top of the
native MessageConsumers and MessageProducers. When we detect a broker
failure, we instantiate a new connection and new sessions, and we recreate
the MessageConsumers and MessageProducers that the application was using.
Not the most elegant solution, but it was accomplished in a few lines of
code and seems to work.

The most difficult thing to do (which is not too difficult, and only
involved finding the correct combination of BindingFlags to use) is to copy
the listener from the old MessageConsumer to the new MessageConsumer. 

var handler = typeof(MessageConsumer).GetField("listener",
BindingFlags.DeclaredOnly | BindingFlags.Instance | BindingFlags.NonPublic |
BindingFlags.GetField).GetValue(nativeMessageConsumer);
newMessageConsumer.Listener += handler;

So



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-NMS-and-Failure-Recovery-tp4717704p4717848.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: java.io.EOFException when ActiveMQ starts

[Tim Bain]

Unfortunately the use of the term "discovery" is misleading.  The term is
used as a generic superset over the discovery transport (which allows
dynamic discovery at runtime) and the static transport (which allows static
discovery at configuration time based on what's in your config file, but no
dynamic discovery at runtime; the phrase "hard code" from the page you
linked to is the relevant one).  It doesn't inherently mean you get dynamic
discovery; you need to use the discovery transport for that.

On Oct 12, 2016 7:25 AM, "divinedragon"  wrote:

> I was referring to this(static discovery section).
>
> http://activemq.apache.org/networks-of-brokers.html
>
>
> On Wed, Oct 12, 2016 at 6:44 PM, Tim Bain [via ActiveMQ] <
> ml-node+s2283324n4717831...@n4.nabble.com> wrote:
>
> > I don't see anywhere that you're using the discovery transport (
> > http://activemq.apache.org/discovery-transport-reference.html); am I
> just
> > not seeing it?  Automatic broker discovery isn't the default behavior;
> you
> > have to use the discovery transport if you want that behavior.
> >
> > On Oct 12, 2016 7:08 AM, "divinedragon" <[hidden email]
> > > wrote:
> >
> > > I wanted to configure automatic broker discovery. As of now, I just
> have
> > > one broker(localhost) and that is what I configured. Isn't it how that
> > > should be configured?
> > >
> > > On Wed, Oct 12, 2016 at 6:02 PM, Tim Bain [via ActiveMQ] <
> > > [hidden email]  type=node=4717831=1>>
> > wrote:
> > >
> > > > OK.  And is it really pointing to localhost   (i.e. this broker is
> > > > connecting to itself)?  I've never tried that myself, but I can't
> > imagine
> > > > that resulting in good behavior...  How come that URI isn't to some
> > other
> > > > (cross-site) host?
> > > >
> > > > Tim
> > > >
> > > > On Oct 12, 2016 1:04 AM, "divinedragon" <[hidden email]
> > > > > wrote:
> > > >
> > > > > Oh my bad. Sorry about the type. The value is this.
> > > > >
> > > > > JMS_X_SITE_CSV_URL=ssl://localhost:7031/
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> > > > > [hidden email]  > > type=node=4717827=1>>
> > > > wrote:
> > > > >
> > > > > > It looks like you're using the tcp transport to connect to an SSL
> > > > > > endpoint;
> > > > > > shouldn't you either use the ssl transport or port 7029?
> > > > > >
> > > > > > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > > > > > wrote:
> > > > > >
> > > > > > > I don't suppose the value is incorrect. Here are all the values
> > in
> > > > the
> > > > > > > properties file.
> > > > > > >
> > > > > > > JMS_PORT=7029
> > > > > > > JMS_STOMP_PORT=7030
> > > > > > > JMS_SSL_PORT=7031
> > > > > > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > > > > > [hidden email]  > > > > type=node=4717820=1>>
> > > > > > wrote:
> > > > > > >
> > > > > > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
> > > > > process?
> > > > > > > Is
> > > > > > > > it a valid URI?  Could something be wrong with that variable?
> > > > > > > >
> > > > > > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > > > > >
> > wrote:
> > > > > > > >
> > > > > > > > > Ok. So, removing the  does get rid of
> the
> > > > WARN
> > > > > > > entry.
> > > > > > > > > But, then I don't want to remove it. What is the
> > configuration
> > > > > issue
> > > > > > > > with
> > > > > > > > > the ???
> > > > > > > > >
> > > > > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > > > > > > [hidden email]  > > > > > > type=node=4717740=1>>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Does the behavior change if you comment out your
> > > > > > 
> > > > > > > > > > element?  I can't think of a reason why a problem there
> > would
> > > > > > cause
> > > > > > > > the
> > > > > > > > > > broker to shut down, but since that's the first place the
> > > > > shutdown
> > > > > > > > > > manifests in the logs, let's see if there really is a
> link
> > > > > between
> > > > > > > the
> > > > > > > > > two
> > > > > > > > > > or if it's a red herring.
> > > > > > > > > >
> > > > > > > > > > Tim
> > > > > > > > > >
> > > > > > > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden
> > email]
> > > > > > > > > > >
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > My activemq.xml is configured like below.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > 

Re: ActiveMQ NMS and Failure Recovery

[Jim Gomes]

Another technique to try when hitting a breakpoint is to not freeze all of
your threads. Let the NMS worker threads continue running in the background
so they are able to respond to the KeepAlive requests from the broker.
Otherwise, your client will be kicked off from the broker. Visual Studio
supports the ability to let background threads continue to run and only
break certain threads for debugging.

However, even though you client gets kicked off, it should go into failover
mode and attempt to reconnect once you start running your application
again. It will need a certain amount of time in order to accomplish this,
so hitting Step Over line-by-line debugging won't give it enough time to
reconnect. You don't have to try to reestablish all of the connections
inside of your exception handler. That would be redundant to what the
failover code already does. It just needs processor time in order to do it.

This seems like a debugging issue, and not really a bug in the client.

On Wed, Oct 12, 2016, 6:16 AM Tim Bain  wrote:

> As Jim said, the failover transport should ensure that your client
> reconnects even if the broker disconnects the client due to a
> breakpoint-induced timeout.  If you're able to isolate specific steps or
> sequences of events that result in that not happening, or to gather more
> detailed information about the symptoms of the failed reconnect, it might
> be possible for someone to figure out what's causing the behavior and fix
> it.  As always when debugging something with no obvious cause, the more
> detail you can provide, the better the odds of someone figuring out what
> the problem is.
>
> Also: tell your developers to stop getting coffee while they're debugging!
> The clock is ticking when you hit your first breakpoint, because as you've
> seen, there's a pretty narrow timeout window before the broker declares
> your client dead and disconnects you.  Do your thing and then detach, as
> quickly as you can.
>
> One technique I use (which might or might not be available in Visual
> Studio; I use Eclipse) is to use custom code in the condition of
> conditional breakpoints that will add a custom log line (to see the value
> of a variable, for example) but then always return false (i.e. don't stop
> at this breakpoint), which lets me add custom logging anywhere I want it
> without causing timeouts.  Obviously there are some technology differences
> between our setups, so YMMV.
>
> Tim
>
> On Oct 10, 2016 8:32 AM, "magmasystems" 
> wrote:
>
> > Thanks, Jim. I neglected to add that we are using the failover URI in
> > production. The main problem seems to be around surviving debugging. For
> > instance, I someone is debugging a service, and goes away for a cup of
> > coffee for a few minutes, they will invariably find that the broker has
> > send
> > an NMSException.
> >
> > The pseudo-code for what we are trying to do is below. Let's assume that
> > the
> > developer is working on his own laptop, with a locally-installed single
> > instance of ActiveMQ.
> >
> > // When initially creating a connection, we set the NMS
> > ExceptionListener handler
> > this.TheConnection.ExceptionListener += this.OnConnectionException;
> >
> > // This will get called when we get a break in the connection
> > public virtual void OnConnectionException(Exception exception)
> > {
> >   if (exception is NMSException)
> >   this.TryExceptionRepair(exception as NMSException);
> > }
> >
> > private void TryExceptionRepair(NMSException nmsException)
> > {
> >// This is where we want to try to re-establish connections,
> > sessions, etc
> > }
> >
> >
> > Let's say that we have a single Connection, a single Session that is
> > associated with the connection, and a number of MessageConsumers and
> > MessageProducers that were created by that Session.
> >
> > Is there a well-known pattern for re-establishing the environment when
> the
> > connection is broker?
> >
> > Also, any advice regarding the URI is welcome.
> >
> > Thanks,
> >
> > Marc
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> > nabble.com/ActiveMQ-NMS-and-Failure-Recovery-tp4717704p4717707.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
>

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

I was referring to this(static discovery section).

http://activemq.apache.org/networks-of-brokers.html


On Wed, Oct 12, 2016 at 6:44 PM, Tim Bain [via ActiveMQ] <
ml-node+s2283324n4717831...@n4.nabble.com> wrote:

> I don't see anywhere that you're using the discovery transport (
> http://activemq.apache.org/discovery-transport-reference.html); am I just
> not seeing it?  Automatic broker discovery isn't the default behavior; you
> have to use the discovery transport if you want that behavior.
>
> On Oct 12, 2016 7:08 AM, "divinedragon" <[hidden email]
> > wrote:
>
> > I wanted to configure automatic broker discovery. As of now, I just have
> > one broker(localhost) and that is what I configured. Isn't it how that
> > should be configured?
> >
> > On Wed, Oct 12, 2016 at 6:02 PM, Tim Bain [via ActiveMQ] <
> > [hidden email] >
> wrote:
> >
> > > OK.  And is it really pointing to localhost   (i.e. this broker is
> > > connecting to itself)?  I've never tried that myself, but I can't
> imagine
> > > that resulting in good behavior...  How come that URI isn't to some
> other
> > > (cross-site) host?
> > >
> > > Tim
> > >
> > > On Oct 12, 2016 1:04 AM, "divinedragon" <[hidden email]
> > > > wrote:
> > >
> > > > Oh my bad. Sorry about the type. The value is this.
> > > >
> > > > JMS_X_SITE_CSV_URL=ssl://localhost:7031/
> > > >
> > > >
> > > >
> > > > On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> > > > [hidden email]  > type=node=4717827=1>>
> > > wrote:
> > > >
> > > > > It looks like you're using the tcp transport to connect to an SSL
> > > > > endpoint;
> > > > > shouldn't you either use the ssl transport or port 7029?
> > > > >
> > > > > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > > > > wrote:
> > > > >
> > > > > > I don't suppose the value is incorrect. Here are all the values
> in
> > > the
> > > > > > properties file.
> > > > > >
> > > > > > JMS_PORT=7029
> > > > > > JMS_STOMP_PORT=7030
> > > > > > JMS_SSL_PORT=7031
> > > > > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > > > > >
> > > > > >
> > > > > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > > > > [hidden email]  > > > type=node=4717820=1>>
> > > > > wrote:
> > > > > >
> > > > > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
> > > > process?
> > > > > > Is
> > > > > > > it a valid URI?  Could something be wrong with that variable?
> > > > > > >
> > > > > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > > > >
> wrote:
> > > > > > >
> > > > > > > > Ok. So, removing the  does get rid of the
> > > WARN
> > > > > > entry.
> > > > > > > > But, then I don't want to remove it. What is the
> configuration
> > > > issue
> > > > > > > with
> > > > > > > > the ???
> > > > > > > >
> > > > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > > > > > [hidden email]  > > > > > type=node=4717740=1>>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Does the behavior change if you comment out your
> > > > > 
> > > > > > > > > element?  I can't think of a reason why a problem there
> would
> > > > > cause
> > > > > > > the
> > > > > > > > > broker to shut down, but since that's the first place the
> > > > shutdown
> > > > > > > > > manifests in the logs, let's see if there really is a link
> > > > between
> > > > > > the
> > > > > > > > two
> > > > > > > > > or if it's a red herring.
> > > > > > > > >
> > > > > > > > > Tim
> > > > > > > > >
> > > > > > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden
> email]
> > > > > > > > > >
> > > wrote:
> > > > > > > > >
> > > > > > > > > > My activemq.xml is configured like below.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > View this message in context: http://activemq.2283324.n4.
>
> > > > > > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > > > > > starts-tp4717598p4717709.html
> > > > > > > > > > Sent from the ActiveMQ - User mailing list archive at
> > > > > Nabble.com.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > If you reply to this email, your message will be added to
> the
> > > > > > > discussion
> > > > > > > > > below:
> > > > > > > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > > > > > > EOFException-when-ActiveMQ-
> > > > > > > > > starts-tp4717598p4717710.html
> > > > > > > > > To unsubscribe from java.io.EOFException when ActiveMQ
> > starts,
> > > > > click
> > > > > > > here
> > > > > > > > > 

Re: java.io.EOFException when ActiveMQ starts

[Tim Bain]

I don't see anywhere that you're using the discovery transport (
http://activemq.apache.org/discovery-transport-reference.html); am I just
not seeing it?  Automatic broker discovery isn't the default behavior; you
have to use the discovery transport if you want that behavior.

On Oct 12, 2016 7:08 AM, "divinedragon"  wrote:

> I wanted to configure automatic broker discovery. As of now, I just have
> one broker(localhost) and that is what I configured. Isn't it how that
> should be configured?
>
> On Wed, Oct 12, 2016 at 6:02 PM, Tim Bain [via ActiveMQ] <
> ml-node+s2283324n4717827...@n4.nabble.com> wrote:
>
> > OK.  And is it really pointing to localhost   (i.e. this broker is
> > connecting to itself)?  I've never tried that myself, but I can't imagine
> > that resulting in good behavior...  How come that URI isn't to some other
> > (cross-site) host?
> >
> > Tim
> >
> > On Oct 12, 2016 1:04 AM, "divinedragon" <[hidden email]
> > > wrote:
> >
> > > Oh my bad. Sorry about the type. The value is this.
> > >
> > > JMS_X_SITE_CSV_URL=ssl://localhost:7031/
> > >
> > >
> > >
> > > On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> > > [hidden email]  type=node=4717827=1>>
> > wrote:
> > >
> > > > It looks like you're using the tcp transport to connect to an SSL
> > > > endpoint;
> > > > shouldn't you either use the ssl transport or port 7029?
> > > >
> > > > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > > > wrote:
> > > >
> > > > > I don't suppose the value is incorrect. Here are all the values in
> > the
> > > > > properties file.
> > > > >
> > > > > JMS_PORT=7029
> > > > > JMS_STOMP_PORT=7030
> > > > > JMS_SSL_PORT=7031
> > > > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > > > >
> > > > >
> > > > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > > > [hidden email]  > > type=node=4717820=1>>
> > > > wrote:
> > > > >
> > > > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
> > > process?
> > > > > Is
> > > > > > it a valid URI?  Could something be wrong with that variable?
> > > > > >
> > > > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > > > wrote:
> > > > > >
> > > > > > > Ok. So, removing the  does get rid of the
> > WARN
> > > > > entry.
> > > > > > > But, then I don't want to remove it. What is the configuration
> > > issue
> > > > > > with
> > > > > > > the ???
> > > > > > >
> > > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > > > > [hidden email]  > > > > type=node=4717740=1>>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Does the behavior change if you comment out your
> > > > 
> > > > > > > > element?  I can't think of a reason why a problem there would
> > > > cause
> > > > > > the
> > > > > > > > broker to shut down, but since that's the first place the
> > > shutdown
> > > > > > > > manifests in the logs, let's see if there really is a link
> > > between
> > > > > the
> > > > > > > two
> > > > > > > > or if it's a red herring.
> > > > > > > >
> > > > > > > > Tim
> > > > > > > >
> > > > > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > > > > > >
> > wrote:
> > > > > > > >
> > > > > > > > > My activemq.xml is configured like below.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > View this message in context: http://activemq.2283324.n4.
> > > > > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > > > > starts-tp4717598p4717709.html
> > > > > > > > > Sent from the ActiveMQ - User mailing list archive at
> > > > Nabble.com.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > If you reply to this email, your message will be added to the
> > > > > > discussion
> > > > > > > > below:
> > > > > > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > > > > > EOFException-when-ActiveMQ-
> > > > > > > > starts-tp4717598p4717710.html
> > > > > > > > To unsubscribe from java.io.EOFException when ActiveMQ
> starts,
> > > > click
> > > > > > here
> > > > > > > >  > > > > NamlServlet.jtp?macro=
> > > > > > > unsubscribe_by_code=4717598=
> > > anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > > >
> > > > > > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > > > > > .
> > > > > > > > NAML
> > > > > > > >  > > > > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > > > > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > > > > > nabble.view.web.template.NodeNamespace=
> > > 

Re: ActiveMQ NMS and Failure Recovery

[Tim Bain]

As Jim said, the failover transport should ensure that your client
reconnects even if the broker disconnects the client due to a
breakpoint-induced timeout.  If you're able to isolate specific steps or
sequences of events that result in that not happening, or to gather more
detailed information about the symptoms of the failed reconnect, it might
be possible for someone to figure out what's causing the behavior and fix
it.  As always when debugging something with no obvious cause, the more
detail you can provide, the better the odds of someone figuring out what
the problem is.

Also: tell your developers to stop getting coffee while they're debugging!
The clock is ticking when you hit your first breakpoint, because as you've
seen, there's a pretty narrow timeout window before the broker declares
your client dead and disconnects you.  Do your thing and then detach, as
quickly as you can.

One technique I use (which might or might not be available in Visual
Studio; I use Eclipse) is to use custom code in the condition of
conditional breakpoints that will add a custom log line (to see the value
of a variable, for example) but then always return false (i.e. don't stop
at this breakpoint), which lets me add custom logging anywhere I want it
without causing timeouts.  Obviously there are some technology differences
between our setups, so YMMV.

Tim

On Oct 10, 2016 8:32 AM, "magmasystems" 
wrote:

> Thanks, Jim. I neglected to add that we are using the failover URI in
> production. The main problem seems to be around surviving debugging. For
> instance, I someone is debugging a service, and goes away for a cup of
> coffee for a few minutes, they will invariably find that the broker has
> send
> an NMSException.
>
> The pseudo-code for what we are trying to do is below. Let's assume that
> the
> developer is working on his own laptop, with a locally-installed single
> instance of ActiveMQ.
>
> // When initially creating a connection, we set the NMS
> ExceptionListener handler
> this.TheConnection.ExceptionListener += this.OnConnectionException;
>
> // This will get called when we get a break in the connection
> public virtual void OnConnectionException(Exception exception)
> {
>   if (exception is NMSException)
>   this.TryExceptionRepair(exception as NMSException);
> }
>
> private void TryExceptionRepair(NMSException nmsException)
> {
>// This is where we want to try to re-establish connections,
> sessions, etc
> }
>
>
> Let's say that we have a single Connection, a single Session that is
> associated with the connection, and a number of MessageConsumers and
> MessageProducers that were created by that Session.
>
> Is there a well-known pattern for re-establishing the environment when the
> connection is broker?
>
> Also, any advice regarding the URI is welcome.
>
> Thanks,
>
> Marc
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/ActiveMQ-NMS-and-Failure-Recovery-tp4717704p4717707.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

I wanted to configure automatic broker discovery. As of now, I just have
one broker(localhost) and that is what I configured. Isn't it how that
should be configured?

On Wed, Oct 12, 2016 at 6:02 PM, Tim Bain [via ActiveMQ] <
ml-node+s2283324n4717827...@n4.nabble.com> wrote:

> OK.  And is it really pointing to localhost   (i.e. this broker is
> connecting to itself)?  I've never tried that myself, but I can't imagine
> that resulting in good behavior...  How come that URI isn't to some other
> (cross-site) host?
>
> Tim
>
> On Oct 12, 2016 1:04 AM, "divinedragon" <[hidden email]
> > wrote:
>
> > Oh my bad. Sorry about the type. The value is this.
> >
> > JMS_X_SITE_CSV_URL=ssl://localhost:7031/
> >
> >
> >
> > On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> > [hidden email] >
> wrote:
> >
> > > It looks like you're using the tcp transport to connect to an SSL
> > > endpoint;
> > > shouldn't you either use the ssl transport or port 7029?
> > >
> > > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > > wrote:
> > >
> > > > I don't suppose the value is incorrect. Here are all the values in
> the
> > > > properties file.
> > > >
> > > > JMS_PORT=7029
> > > > JMS_STOMP_PORT=7030
> > > > JMS_SSL_PORT=7031
> > > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > > >
> > > >
> > > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > > [hidden email]  > type=node=4717820=1>>
> > > wrote:
> > > >
> > > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
> > process?
> > > > Is
> > > > > it a valid URI?  Could something be wrong with that variable?
> > > > >
> > > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > > wrote:
> > > > >
> > > > > > Ok. So, removing the  does get rid of the
> WARN
> > > > entry.
> > > > > > But, then I don't want to remove it. What is the configuration
> > issue
> > > > > with
> > > > > > the ???
> > > > > >
> > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > > > [hidden email]  > > > type=node=4717740=1>>
> > > > > wrote:
> > > > > >
> > > > > > > Does the behavior change if you comment out your
> > > 
> > > > > > > element?  I can't think of a reason why a problem there would
> > > cause
> > > > > the
> > > > > > > broker to shut down, but since that's the first place the
> > shutdown
> > > > > > > manifests in the logs, let's see if there really is a link
> > between
> > > > the
> > > > > > two
> > > > > > > or if it's a red herring.
> > > > > > >
> > > > > > > Tim
> > > > > > >
> > > > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > > > > >
> wrote:
> > > > > > >
> > > > > > > > My activemq.xml is configured like below.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > View this message in context: http://activemq.2283324.n4.
> > > > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > > > starts-tp4717598p4717709.html
> > > > > > > > Sent from the ActiveMQ - User mailing list archive at
> > > Nabble.com.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > If you reply to this email, your message will be added to the
> > > > > discussion
> > > > > > > below:
> > > > > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > > > > EOFException-when-ActiveMQ-
> > > > > > > starts-tp4717598p4717710.html
> > > > > > > To unsubscribe from java.io.EOFException when ActiveMQ starts,
> > > click
> > > > > here
> > > > > > >  > > > NamlServlet.jtp?macro=
> > > > > > unsubscribe_by_code=4717598=
> > anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > >
> > > > > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > > > > .
> > > > > > > NAML
> > > > > > >  > > > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > > > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > > > > nabble.view.web.template.NodeNamespace=
> > > > > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > > > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > View this message in context: http://activemq.2283324.n4.
> > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > starts-tp4717598p4717733.html
> > > > > > Sent from the ActiveMQ - User mailing list archive at
> Nabble.com.
> > > > >
> > > > >
> > > > > --
> > > > > If you reply to this email, your message will be added to the
> 

Re: java.io.EOFException when ActiveMQ starts

[Tim Bain]

OK.  And is it really pointing to localhost   (i.e. this broker is
connecting to itself)?  I've never tried that myself, but I can't imagine
that resulting in good behavior...  How come that URI isn't to some other
(cross-site) host?

Tim

On Oct 12, 2016 1:04 AM, "divinedragon"  wrote:

> Oh my bad. Sorry about the type. The value is this.
>
> JMS_X_SITE_CSV_URL=ssl://localhost:7031/
>
>
>
> On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> ml-node+s2283324n4717820...@n4.nabble.com> wrote:
>
> > It looks like you're using the tcp transport to connect to an SSL
> > endpoint;
> > shouldn't you either use the ssl transport or port 7029?
> >
> > On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > > wrote:
> >
> > > I don't suppose the value is incorrect. Here are all the values in the
> > > properties file.
> > >
> > > JMS_PORT=7029
> > > JMS_STOMP_PORT=7030
> > > JMS_SSL_PORT=7031
> > > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> > >
> > >
> > > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > > [hidden email]  type=node=4717820=1>>
> > wrote:
> > >
> > > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
> process?
> > > Is
> > > > it a valid URI?  Could something be wrong with that variable?
> > > >
> > > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > > wrote:
> > > >
> > > > > Ok. So, removing the  does get rid of the WARN
> > > entry.
> > > > > But, then I don't want to remove it. What is the configuration
> issue
> > > > with
> > > > > the ???
> > > > >
> > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > > [hidden email]  > > type=node=4717740=1>>
> > > > wrote:
> > > > >
> > > > > > Does the behavior change if you comment out your
> > 
> > > > > > element?  I can't think of a reason why a problem there would
> > cause
> > > > the
> > > > > > broker to shut down, but since that's the first place the
> shutdown
> > > > > > manifests in the logs, let's see if there really is a link
> between
> > > the
> > > > > two
> > > > > > or if it's a red herring.
> > > > > >
> > > > > > Tim
> > > > > >
> > > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > > > > wrote:
> > > > > >
> > > > > > > My activemq.xml is configured like below.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > View this message in context: http://activemq.2283324.n4.
> > > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > > starts-tp4717598p4717709.html
> > > > > > > Sent from the ActiveMQ - User mailing list archive at
> > Nabble.com.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > If you reply to this email, your message will be added to the
> > > > discussion
> > > > > > below:
> > > > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > > > EOFException-when-ActiveMQ-
> > > > > > starts-tp4717598p4717710.html
> > > > > > To unsubscribe from java.io.EOFException when ActiveMQ starts,
> > click
> > > > here
> > > > > >  > > NamlServlet.jtp?macro=
> > > > > unsubscribe_by_code=4717598=
> anVzdGRwa0BnbWFpbC5jb218NDcxNz
> >
> > > > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > > > .
> > > > > > NAML
> > > > > >  > > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > > > nabble.view.web.template.NodeNamespace=
> > > > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context: http://activemq.2283324.n4.
> > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > starts-tp4717598p4717733.html
> > > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > > >
> > > >
> > > > --
> > > > If you reply to this email, your message will be added to the
> > discussion
> > > > below:
> > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > EOFException-when-ActiveMQ-
> > > > starts-tp4717598p4717740.html
> > > > To unsubscribe from java.io.EOFException when ActiveMQ starts, click
> > here
> > > >  NamlServlet.jtp?macro=
> > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > .
> > > > NAML
> > > >  > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > 

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

Another information to add here, I don't know if it could give some
indication. For the SSL transfer, I am using my own self signed
certificate(keystore and truststore using keytool) which I have configured
via the  section as below.





Could this be a problem?

On Wed, Oct 12, 2016 at 12:34 PM, Deepak Shakya  wrote:

> Oh my bad. Sorry about the type. The value is this.
>
> JMS_X_SITE_CSV_URL=ssl://localhost:7031/
>
>
>
> On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
> ml-node+s2283324n4717820...@n4.nabble.com> wrote:
>
>> It looks like you're using the tcp transport to connect to an SSL
>> endpoint;
>> shouldn't you either use the ssl transport or port 7029?
>>
>> On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
>> > wrote:
>>
>> > I don't suppose the value is incorrect. Here are all the values in the
>> > properties file.
>> >
>> > JMS_PORT=7029
>> > JMS_STOMP_PORT=7030
>> > JMS_SSL_PORT=7031
>> > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
>> >
>> >
>> > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
>> > [hidden email] >
>> wrote:
>> >
>> > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your
>> process?
>> > Is
>> > > it a valid URI?  Could something be wrong with that variable?
>> > >
>> > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
>> > > > wrote:
>> > >
>> > > > Ok. So, removing the  does get rid of the WARN
>> > entry.
>> > > > But, then I don't want to remove it. What is the configuration
>> issue
>> > > with
>> > > > the ???
>> > > >
>> > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
>> > > > [hidden email] > > type=node=4717740=1>>
>> > > wrote:
>> > > >
>> > > > > Does the behavior change if you comment out your
>> 
>> > > > > element?  I can't think of a reason why a problem there would
>> cause
>> > > the
>> > > > > broker to shut down, but since that's the first place the
>> shutdown
>> > > > > manifests in the logs, let's see if there really is a link
>> between
>> > the
>> > > > two
>> > > > > or if it's a red herring.
>> > > > >
>> > > > > Tim
>> > > > >
>> > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
>> > > > > > wrote:
>> > > > >
>> > > > > > My activemq.xml is configured like below.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > View this message in context: http://activemq.2283324.n4.
>> > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
>> > > > > > starts-tp4717598p4717709.html
>> > > > > > Sent from the ActiveMQ - User mailing list archive at
>> Nabble.com.
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > If you reply to this email, your message will be added to the
>> > > discussion
>> > > > > below:
>> > > > > http://activemq.2283324.n4.nabble.com/java-io-
>> > > > EOFException-when-ActiveMQ-
>> > > > > starts-tp4717598p4717710.html
>> > > > > To unsubscribe from java.io.EOFException when ActiveMQ starts,
>> click
>> > > here
>> > > > > > > NamlServlet.jtp?macro=
>> > > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
>>
>> > > > U5OHwtMjEzOTUzNTk3Ng==>
>> > > > > .
>> > > > > NAML
>> > > > > > > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
>> > > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
>> > > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
>> > > > nabble.view.web.template.NodeNamespace=
>> > > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
>> > > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > View this message in context: http://activemq.2283324.n4.
>> > > > nabble.com/java-io-EOFException-when-ActiveMQ-
>> > > > starts-tp4717598p4717733.html
>> > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> > >
>> > >
>> > > --
>> > > If you reply to this email, your message will be added to the
>> discussion
>> > > below:
>> > > http://activemq.2283324.n4.nabble.com/java-io-
>> > EOFException-when-ActiveMQ-
>> > > starts-tp4717598p4717740.html
>> > > To unsubscribe from java.io.EOFException when ActiveMQ starts, click
>> here
>> > > > jtp?macro=
>> > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
>> > U5OHwtMjEzOTUzNTk3Ng==>
>> > > .
>> > > NAML
>> > > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
>> > 21nabble%3Aemail.naml=nabble.naml.namespaces.
>> > BasicNamespace-nabble.view.web.template.NabbleNamespace-
>> > 

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

Oh my bad. Sorry about the type. The value is this.

JMS_X_SITE_CSV_URL=ssl://localhost:7031/



On Wed, Oct 12, 2016 at 12:23 PM, Tim Bain [via ActiveMQ] <
ml-node+s2283324n4717820...@n4.nabble.com> wrote:

> It looks like you're using the tcp transport to connect to an SSL
> endpoint;
> shouldn't you either use the ssl transport or port 7029?
>
> On Oct 12, 2016 12:38 AM, "divinedragon" <[hidden email]
> > wrote:
>
> > I don't suppose the value is incorrect. Here are all the values in the
> > properties file.
> >
> > JMS_PORT=7029
> > JMS_STOMP_PORT=7030
> > JMS_SSL_PORT=7031
> > JMS_X_SITE_CSV_URL=tcp://localhost:7031/
> >
> >
> > On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> > [hidden email] >
> wrote:
> >
> > > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your process?
> > Is
> > > it a valid URI?  Could something be wrong with that variable?
> > >
> > > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > > wrote:
> > >
> > > > Ok. So, removing the  does get rid of the WARN
> > entry.
> > > > But, then I don't want to remove it. What is the configuration issue
> > > with
> > > > the ???
> > > >
> > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > > [hidden email]  > type=node=4717740=1>>
> > > wrote:
> > > >
> > > > > Does the behavior change if you comment out your
> 
> > > > > element?  I can't think of a reason why a problem there would
> cause
> > > the
> > > > > broker to shut down, but since that's the first place the shutdown
> > > > > manifests in the logs, let's see if there really is a link between
> > the
> > > > two
> > > > > or if it's a red herring.
> > > > >
> > > > > Tim
> > > > >
> > > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > > > wrote:
> > > > >
> > > > > > My activemq.xml is configured like below.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > View this message in context: http://activemq.2283324.n4.
> > > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > > starts-tp4717598p4717709.html
> > > > > > Sent from the ActiveMQ - User mailing list archive at
> Nabble.com.
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > If you reply to this email, your message will be added to the
> > > discussion
> > > > > below:
> > > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > > EOFException-when-ActiveMQ-
> > > > > starts-tp4717598p4717710.html
> > > > > To unsubscribe from java.io.EOFException when ActiveMQ starts,
> click
> > > here
> > > > >  > NamlServlet.jtp?macro=
> > > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
>
> > > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > > .
> > > > > NAML
> > > > >  > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > > nabble.view.web.template.NodeNamespace=
> > > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context: http://activemq.2283324.n4.
> > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > starts-tp4717598p4717733.html
> > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > >
> > >
> > > --
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://activemq.2283324.n4.nabble.com/java-io-
> > EOFException-when-ActiveMQ-
> > > starts-tp4717598p4717740.html
> > > To unsubscribe from java.io.EOFException when ActiveMQ starts, click
> here
> > >  > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > U5OHwtMjEzOTUzNTk3Ng==>
> > > .
> > > NAML
> > >  > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > nabble.view.web.template.NodeNamespace=
> > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > >
> >
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> > nabble.com/java-io-EOFException-when-ActiveMQ-
> > starts-tp4717598p4717819.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> 

Re: java.io.EOFException when ActiveMQ starts

[Tim Bain]

It looks like you're using the tcp transport to connect to an SSL endpoint;
shouldn't you either use the ssl transport or port 7029?

On Oct 12, 2016 12:38 AM, "divinedragon"  wrote:

> I don't suppose the value is incorrect. Here are all the values in the
> properties file.
>
> JMS_PORT=7029
> JMS_STOMP_PORT=7030
> JMS_SSL_PORT=7031
> JMS_X_SITE_CSV_URL=tcp://localhost:7031/
>
>
> On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
> ml-node+s2283324n4717740...@n4.nabble.com> wrote:
>
> > What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your process?
> Is
> > it a valid URI?  Could something be wrong with that variable?
> >
> > On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > > wrote:
> >
> > > Ok. So, removing the  does get rid of the WARN
> entry.
> > > But, then I don't want to remove it. What is the configuration issue
> > with
> > > the ???
> > >
> > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > > [hidden email]  type=node=4717740=1>>
> > wrote:
> > >
> > > > Does the behavior change if you comment out your 
> > > > element?  I can't think of a reason why a problem there would cause
> > the
> > > > broker to shut down, but since that's the first place the shutdown
> > > > manifests in the logs, let's see if there really is a link between
> the
> > > two
> > > > or if it's a red herring.
> > > >
> > > > Tim
> > > >
> > > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > > wrote:
> > > >
> > > > > My activemq.xml is configured like below.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context: http://activemq.2283324.n4.
> > > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > > starts-tp4717598p4717709.html
> > > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > > > >
> > > >
> > > >
> > > > --
> > > > If you reply to this email, your message will be added to the
> > discussion
> > > > below:
> > > > http://activemq.2283324.n4.nabble.com/java-io-
> > > EOFException-when-ActiveMQ-
> > > > starts-tp4717598p4717710.html
> > > > To unsubscribe from java.io.EOFException when ActiveMQ starts, click
> > here
> > > >  NamlServlet.jtp?macro=
> > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > .
> > > > NAML
> > > >  > > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > > nabble.view.web.template.NodeNamespace=
> > > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context: http://activemq.2283324.n4.
> > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > starts-tp4717598p4717733.html
> > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://activemq.2283324.n4.nabble.com/java-io-
> EOFException-when-ActiveMQ-
> > starts-tp4717598p4717740.html
> > To unsubscribe from java.io.EOFException when ActiveMQ starts, click here
> >  unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> U5OHwtMjEzOTUzNTk3Ng==>
> > .
> > NAML
> >  NamlServlet.jtp?macro=macro_viewer=instant_html%
> 21nabble%3Aemail.naml=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/java-io-EOFException-when-ActiveMQ-
> starts-tp4717598p4717819.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: java.io.EOFException when ActiveMQ starts

[divinedragon]

I don't suppose the value is incorrect. Here are all the values in the
properties file.

JMS_PORT=7029
JMS_STOMP_PORT=7030
JMS_SSL_PORT=7031
JMS_X_SITE_CSV_URL=tcp://localhost:7031/


On Mon, Oct 10, 2016 at 6:49 PM, Tim Bain [via ActiveMQ] <
ml-node+s2283324n4717740...@n4.nabble.com> wrote:

> What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your process?  Is
> it a valid URI?  Could something be wrong with that variable?
>
> On Oct 10, 2016 2:49 AM, "divinedragon" <[hidden email]
> > wrote:
>
> > Ok. So, removing the  does get rid of the WARN entry.
> > But, then I don't want to remove it. What is the configuration issue
> with
> > the ???
> >
> > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
> > [hidden email] >
> wrote:
> >
> > > Does the behavior change if you comment out your 
> > > element?  I can't think of a reason why a problem there would cause
> the
> > > broker to shut down, but since that's the first place the shutdown
> > > manifests in the logs, let's see if there really is a link between the
> > two
> > > or if it's a red herring.
> > >
> > > Tim
> > >
> > > On Sun, Oct 9, 2016 at 10:48 PM, divinedragon <[hidden email]
> > > > wrote:
> > >
> > > > My activemq.xml is configured like below.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context: http://activemq.2283324.n4.
> > > > nabble.com/java-io-EOFException-when-ActiveMQ-
> > > > starts-tp4717598p4717709.html
> > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> > > >
> > >
> > >
> > > --
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://activemq.2283324.n4.nabble.com/java-io-
> > EOFException-when-ActiveMQ-
> > > starts-tp4717598p4717710.html
> > > To unsubscribe from java.io.EOFException when ActiveMQ starts, click
> here
> > >  > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > U5OHwtMjEzOTUzNTk3Ng==>
> > > .
> > > NAML
> > >  > NamlServlet.jtp?macro=macro_viewer=instant_html%
> > 21nabble%3Aemail.naml=nabble.naml.namespaces.
> > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > nabble.view.web.template.NodeNamespace=
> > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > >
> >
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> > nabble.com/java-io-EOFException-when-ActiveMQ-
> > starts-tp4717598p4717733.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/java-io-EOFException-when-ActiveMQ-
> starts-tp4717598p4717740.html
> To unsubscribe from java.io.EOFException when ActiveMQ starts, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/java-io-EOFException-when-ActiveMQ-starts-tp4717598p4717819.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.