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&node=4717855&i=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&node=4717855&i=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&node=4717847&i=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&node=4717847&i=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&node=4717831&i=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&node=4717831&i=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&node=4717827&i=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&node=4717827&i=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&node=4717820&i=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&node=4717820&i=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&node=4717740&i=0>> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Ok. So, removing the <networkConnectors> does get > rid > > of > > > > the > > > > > > > WARN > > > > > > > > > > entry. > > > > > > > > > > > > But, then I don't want to remove it. What is the > > > > > configuration > > > > > > > > issue > > > > > > > > > > > with > > > > > > > > > > > > the <networkConnectors>??? > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via > > > ActiveMQ] < > > > > > > > > > > > > [hidden email] <http:///user/SendEmail.jtp? > > > > > > > > > > type=node&node=4717740&i=1>> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Does the behavior change if you comment out your > > > > > > > > > <networkConnectors> > > > > > > > > > > > > > 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&node=4717710&i=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&node=4717598&code= > > > > > > > > anVzdGRwa0BnbWFpbC5jb218NDcxNz > > > > > > > > > > > > > > > > > > > > > U5OHwtMjEzOTUzNTk3Ng==> > > > > > > > > > > > > > . > > > > > > > > > > > > > NAML > > > > > > > > > > > > > <http://activemq.2283324.n4.nabble.com/template/ > > > > > > > > > > > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > > > > > > > > > > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > > > > > > > > > > > BasicNamespace-nabble.view. > > web.template.NabbleNamespace- > > > > > > > > > > > > > > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > > > > > > > > > > > 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&node=4717598&code= > > > > > > anVzdGRwa0BnbWFpbC5jb218NDcxNz > > > > > > > > > > > > > > > > > U5OHwtMjEzOTUzNTk3Ng==> > > > > > > > > > > > . > > > > > > > > > > > NAML > > > > > > > > > > > <http://activemq.2283324.n4.nabble.com/template/ > > > > > > > > > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > > > > > > > > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > > > > > > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace- > > > > > > > > > > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > > > > > > > > > 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 > > > > > > > > > below: > > > > > > > > > http://activemq.2283324.n4.nabble.com/java-io- > > > > > > > > EOFException-when-ActiveMQ- > > > > > > > > > starts-tp4717598p4717820.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&node=4717598&code= > > > > anVzdGRwa0BnbWFpbC5jb218NDcxNz > > > > > > > > > > > > > U5OHwtMjEzOTUzNTk3Ng==> > > > > > > > > > . > > > > > > > > > NAML > > > > > > > > > <http://activemq.2283324.n4.nabble.com/template/ > > > > > > > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > > > > > > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > > > > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace- > > > > > > > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > > > > > > > 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-tp4717598p4717821.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-tp4717598p4717827.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&node=4717598&code= > > anVzdGRwa0BnbWFpbC5jb218NDcxNz > > > > > > > > > U5OHwtMjEzOTUzNTk3Ng==> > > > > > > > . > > > > > > > NAML > > > > > > > <http://activemq.2283324.n4.nabble.com/template/ > > > > > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > > > > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace- > > > > > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > > > > > 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-tp4717598p4717829.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-tp4717598p4717831.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&node=4717598&code=anVzdGRwa0BnbWFpbC5jb218NDcxNz > > > > > U5OHwtMjEzOTUzNTk3Ng==> > > > > > . > > > > > NAML > > > > > <http://activemq.2283324.n4.nabble.com/template/ > > > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > > > BasicNamespace-nabble.view.web.template.NabbleNamespace- > > > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > > > 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-tp4717598p4717832.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-tp4717598p4717847.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&node=4717598&code=anVzdGRwa0BnbWFpbC5jb218NDcxNz > > U5OHwtMjEzOTUzNTk3Ng==> > > > . > > > NAML > > > <http://activemq.2283324.n4.nabble.com/template/ > > NamlServlet.jtp?macro=macro_viewer&id=instant_html% > > 21nabble%3Aemail.naml&base=nabble.naml.namespaces. > > BasicNamespace-nabble.view.web.template.NabbleNamespace- > > nabble.view.web.template.NodeNamespace&breadcrumbs= > > 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-tp4717598p4717850.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-tp4717598p4717855.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&node=4717598&code=anVzdGRwa0BnbWFpbC5jb218NDcxNzU5OHwtMjEzOTUzNTk3Ng==> > . > NAML > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=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-tp4717598p4717901.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
