Re: java.io.EOFException when ActiveMQ starts
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* matches to that of activemq's internal hostname naming scheme, then I don't see the WARNING. For my case, my Transport connections were starting as below INFO | Listening for connections at: tcp://divinedragonbox:7029 INFO | Connector openwire started INFO | Listening for connections at: stomp://divinedragonbox:7030 INFO | Connector stomp started INFO | Listening for connections at: ssl://divinedragonbox:7031 So, when I configured my *JMS_X_SITE_CSV_URL=ssl://divinedragonbox:7031*, there were no WARNING generated. I will review and get more details about networkConnectors, but for now, I guess this understanding helps a lot to set this value correctly. Thanks for the help. Appreciate it. On Thu, Oct 13, 2016 at 11:52 AM, Tim Bain [via ActiveMQ] < ml-node+s2283324n4717855...@n4.nabble.com> wrote: > 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 wrong with your SSL configuration as you suggested; there's no > good way in a mailing list discussion to check whether your truststore > trusts your keystore and the certs are being presented properly since > that's all about the binary content and you shouldn't be sharing that > publicly, but you could test the SSL configuration by setting up two > brokers (in a test environment) that each have their JMS_X_SITE_CSV_URL > pointed at each other. If that configuration gives you EOFExceptions, > then > switch to using the tcp transport and see what happens. If you get errors > with the ssl transport but not the tcp one, there's a good chance it's > something wrong with your keys. > > As far as the current configuration (where you have a broker whose only > networkConnection is a static:ssl: one to itself), it's not a useful > configuration (having a networkConnector to yourself serves no purpose), > and you proved early on in this discussion that removing it removes the > WARN log line that you're concerned about. So I disagree with your > statement that "I feel the configuration still seems fine." Either switch > to something that serves the purpose you said you're trying to achieve > (like the discovery: transport instead of the static: transport, or like > listing your cross-site servers if you're going to continue using the > static: transport) or take it out and eliminate the WARN line. > > Tim > > On Wed, Oct 12, 2016 at 10:25 AM, divinedragon <[hidden email] > <http:///user/SendEmail.jtp?type=node=4717855=0>> wrote: > > > 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]" < > > [hidden email] <http:///user/SendEmail.jtp?type=node=4717855=1>> > 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] > > > <http:///user/SendEmail.jtp?type=node=4717847=0>> 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] <http:///user/SendEmail.jtp? > > type=node=4717847=1>> > > > 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
Re: java.io.EOFException when ActiveMQ starts
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] > <http:///user/SendEmail.jtp?type=node=4717847=0>> 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] <http:///user/SendEmail.jtp?type=node=4717847=1>> > 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] > > > <http:///user/SendEmail.jtp?type=node=4717831=0>> 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] <http:///user/SendEmail.jtp? > > 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] > > > > > <http:///user/SendEmail.jtp?type=node=4717827=0>> 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] <http:///user/SendEmail.jtp? > > > > 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] > > > > > > > <http:///user/SendEmail.jtp?type=node=4717820=0>> > 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] <http:///user/SendEmail.jtp? > > > > > > type=node=4717820=1>> > > > > > > > wrote: > > > > > > > > > >
Re: java.io.EOFException when ActiveMQ starts
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]
> <http:///user/SendEmail.jtp?type=node=4717831=0>> 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] <http:///user/SendEmail.jtp?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]
> > > <http:///user/SendEmail.jtp?type=node=4717827=0>> 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] <http:///user/SendEmail.jtp?
> > 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]
> > > > > <http:///user/SendEmail.jtp?type=node=4717820=0>> 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] <http:///user/SendEmail.jtp?
> > > > 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]
> > > > > > > <http:///user/SendEmail.jtp?type=node=4717740=0>>
> 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] <http:///user/SendEmail.jtp?
> > > > > > 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
Re: java.io.EOFException when ActiveMQ starts
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]
> <http:///user/SendEmail.jtp?type=node=4717827=0>> 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] <http:///user/SendEmail.jtp?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]
> > > <http:///user/SendEmail.jtp?type=node=4717820=0>> 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] <http:///user/SendEmail.jtp?
> > 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]
> > > > > <http:///user/SendEmail.jtp?type=node=4717740=0>> 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] <http:///user/SendEmail.jtp?
> > > > 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]
> > > > > > > <http:///user/SendEmail.jtp?type=node=4717710=0>>
> 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
> > > >
Re: java.io.EOFException when ActiveMQ starts
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 <just...@gmail.com> 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]
>> <http:///user/SendEmail.jtp?type=node=4717820=0>> 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] <http:///user/SendEmail.jtp?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]
>> > > <http:///user/SendEmail.jtp?type=node=4717740=0>> 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] <http:///user/SendEmail.jtp?
>> > 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]
>> > > > > <http:///user/SendEmail.jtp?type=node=4717710=0>> 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
>> > > > > <http://activemq.2283324.n4.nabble.com/template/
>> > NamlServlet.jtp?macro=
>> > > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
>>
>> > > > U5OHwtMjEzOTUzNTk3Ng==>
>> > > > > .
>> > > > > NAML
>> > > > > <http://activemq.2283324.n4.nabble.com/template/
>> > > > NamlServlet.jtp?macro=macro_viewer=instant_html%
>> > >
Re: java.io.EOFException when ActiveMQ starts
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]
> <http:///user/SendEmail.jtp?type=node=4717820=0>> 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] <http:///user/SendEmail.jtp?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]
> > > <http:///user/SendEmail.jtp?type=node=4717740=0>> 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] <http:///user/SendEmail.jtp?
> > 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]
> > > > > <http:///user/SendEmail.jtp?type=node=4717710=0>> 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
> > > > > <http://activemq.2283324.n4.nabble.com/template/
> > NamlServlet.jtp?macro=
> > > > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
>
> > > > U5OHwtMjEzOTUzNTk3Ng==>
> > > > > .
> > > > > NAML
> > > > > <http://activemq.2283324.n4.nabble.com/template/
> > > > 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.
> > >
> > >
> > > ---
Re: java.io.EOFException when ActiveMQ starts
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]
> <http:///user/SendEmail.jtp?type=node=4717740=0>> 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] <http:///user/SendEmail.jtp?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]
> > > <http:///user/SendEmail.jtp?type=node=4717710=0>> 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
> > > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=
> > unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNz
> > U5OHwtMjEzOTUzNTk3Ng==>
> > > .
> > > NAML
> > > <http://activemq.2283324.n4.nabble.com/template/
> > 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
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNzU5OHwtMjEzOTUzNTk3Ng==>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/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
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 > 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] > <http:///user/SendEmail.jtp?type=node=4717710=0>> 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 > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=4717598=anVzdGRwa0BnbWFpbC5jb218NDcxNzU5OHwtMjEzOTUzNTk3Ng==> > . > NAML > <http://activemq.2283324.n4.nabble.com/template/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.
Re: java.io.EOFException when ActiveMQ starts
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.
java.io.EOFException when ActiveMQ starts
I am trying to start the ActiveMQ 5.11 and I see a WARNING as below: WARN | Transport Connection to: tcp://127.0.0.1:40890 failed: java.io.EOFException Here is the entire console log for this. Java Runtime: Oracle Corporation 1.7.0_05 /usr/java/jdk1.7.0_05/jre Heap sizes: current=1004928k free=994439k max=1004928kJVM args: -Xmx1G -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=/home/dragon/activemq/conf/login.config -Dcom.sun.management.jmxremote -Djava.io.tmpdir=/home/dragon/activemq/tmp -Dactivemq.classpath=/home/dragon/activemq/conf; -Dactivemq.home=/home/dragon/activemq -Dactivemq.base=/home/dragon/activemq -Dactivemq.conf=/home/dragon/activemq/conf -Dactivemq.data=/home/dragon/activemq/dataExtensions classpath: [/home/dragon/activemq/lib,/home/dragon/activemq/lib/camel,/home/dragon/activemq/lib/optional,/home/dragon/activemq/lib/web,/home/dragon/activemq/lib/extra]ACTIVEMQ_HOME: /home/dragon/activemqACTIVEMQ_BASE: /home/dragon/activemqACTIVEMQ_CONF: /home/dragon/activemq/confACTIVEMQ_DATA: /home/dragon/activemq/dataLoading message broker from: xbean:activemq.xml INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@a842913: startup date [Fri Oct 07 08:14:02 IST 2016]; root of context hierarchy INFO | PListStore:[/home/dragon/activemq/data/divinedragonbox/tmp_storage] started INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/home/dragon/jms_store] INFO | JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:15526/jmxrmi INFO | KahaDB is version 5 INFO | Recovering from the journal ... INFO | Recovery replayed 76 operations from the journal in 0.032 seconds. INFO | Apache ActiveMQ 5.11.1 (divinedragonbox, ID:divinedragonbox-60914-1475824445361-0:1) is starting INFO | Listening for connections at: tcp://divinedragonbox:15511 INFO | Connector openwire started INFO | Listening for connections at: stomp://divinedragonbox:15512 INFO | Connector stomp started INFO | Listening for connections at: ssl://divinedragonbox:15571 INFO | Connector ssl started INFO | Establishing network connection from vm://divinedragonbox?async=false=true to ssl://localhost:15571 INFO | Connector vm://divinedragonbox started INFO | Network Connector DiscoveryNetworkConnector:host1 and host2:BrokerService[divinedragonbox] started INFO | Apache ActiveMQ 5.11.1 (divinedragonbox, ID:divinedragonbox-60914-1475824445361-0:1) started INFO | For help or more information please see: http://activemq.apache.org INFO | divinedragonbox Shutting down INFO | Connector vm://divinedragonbox stopped INFO | divinedragonbox bridge to Unknown stopped WARN | Transport Connection to: tcp://127.0.0.1:40890 failed: java.io.EOFException INFO | ActiveMQ WebConsole available at http://localhost:15521/ INFO | Initializing Spring FrameworkServlet 'dispatcher' INFO | jolokia-agent: No access restrictor found at classpath:/jolokia-access.xml, access to all MBeans is allowed I enabled the TRACE for the messages and I got the following snippets of exceptions in the log file. 2016-10-07 08:15:45,378 | TRACE | Execute[ActiveMQ ForwardingBridge StopTask] runnable: org.apache.activemq.network.DemandForwardingBridgeSupport$4@b3f451d | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ BrokerService[divinedragonbox] Task-42016-10-07 08:15:45,378 | TRACE | Created and running thread[ActiveMQ ForwardingBridge StopTask-5]: Thread[ActiveMQ ForwardingBridge StopTask-5,5,main] | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ BrokerService[divinedragonbox] Task-42016-10-07 08:15:45,379 | DEBUG | Caught exception sending shutdown | org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ ForwardingBridge StopTask-5org.apache.activemq.transport.TransportDisposedIOException: Transport disposed. at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:82)[activemq-broker-5.11.1.jar:5.11.1] at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)[activemq-client-5.11.1.jar:5.11.1] at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)[activemq-client-5.11.1.jar:5.11.1] at org.apache.activemq.network.DemandForwardingBridgeSupport$4.run(DemandForwardingBridgeSupport.java:288)[activemq-broker-5.11.1.jar:5.11.1] at java.lang.Thread.run(Thread.java:722)[:1.7.0_05]2016-10-07 08:15:45,380 | DEBUG | Stopping transport ssl://localhost/127.0.0.1:15571 | org.apache.activemq.transport.tcp.TcpTransport | ActiveMQ BrokerService[divinedragonbox] Task-42016-10-07 08:15:45,381 | DEBUG | Initialized TaskRunnerFactory[ActiveMQ Task] using ExecutorService: null | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ BrokerService[divinedragonbox] Task-42016-10-07 08:15:45,381 | TRACE | Execute[ActiveMQ Task] runnable: org.apache.activemq.transport.tcp.TcpTransport$1@a1848dc | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ BrokerService[divinedragonbox]
