Thanks Tim for making things clear. I tried out with the two brokers with
each pointing to other broker in *JMS_X_SITE_CSV_URL* and both the brokers
came up without any warning. This rules out the issue for any SSL.
For the self configuration, I figured that if the value in
*JMS_X_SITE_CSV_URL* ma
I've never tried configuring a broker with a static networkConnector
connected to itself (why would I, it's a useless configuration), but it
wouldn't surprise me if the broker rejected that self-connection, which
could result in the EOFException you saw. It's also possible that there's
something w
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 gene
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
dyn
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://activem
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
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 reall
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 ba
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
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
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
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:
> Wha
And alternatively, is the broker(s) to which that URI connects up and
healthy? Is there any relevant info in its/their logs?
On Oct 10, 2016 7:25 AM, "Tim Bain" 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 t
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" wrote:
> Ok. So, removing the does get rid of the WARN entry.
> But, then I don't want to remove it. What is the confi
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] <
ml-node+s2283324n4717710...@n4.nabble.com> wrote:
> Does the behavior change if you comment out your
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
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
It looks like the broker is failing to make the connection described in
your networkConnectors section of activemq.xml. Can you show us that
config snippet? And do you have any reason to believe that connection
might be failing?
Tim
On Oct 7, 2016 2:44 AM, "divinedragon" wrote:
I am trying to
18 matches
Mail list logo
