java.io.EOFException when ActiveMQ starts

2016-10-07 Thread divinedragon
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

Re: java.io.EOFException when ActiveMQ starts

2016-10-09 Thread divinedragon
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

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
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>> wrot

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
4n4717820...@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] >> &l

Re: java.io.EOFException when ActiveMQ starts

2016-10-14 Thread divinedragon
e 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, divi

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
> 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, "di

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
( > 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 emai

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
gt; 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 v

Re: java.io.EOFException when ActiveMQ starts

2016-10-10 Thread divinedragon
; 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://a

Re: java.io.EOFException when ActiveMQ starts

2016-10-12 Thread divinedragon
e 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:///use