[jira] [Commented] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio
[
https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403890#comment-13403890
]
R.I.Pienaar commented on AMQ-3897:
--
Thanks for sorting this out! I see it's targeted for 5.7.x, could this be 5.6.x
instead? its just a bug fix and would be awesome to get this working before
5.7.0
> Stomp 1.1 keep alive does not work with stomp+nio
> -
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
>Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12,
> mixed mode)
>Reporter: R.I.Pienaar
>Assignee: Timothy Bish
> Fix For: 5.7.0
>
>
> using the transport:
> {quote}
>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output
> so new lines etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
> charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
> {quote}
> Notice that I send the heart-beat header requesting 3,3 heartbeats
> but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing
> my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio
[
https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
R.I.Pienaar updated AMQ-3897:
-
Description:
using the transport:
{quote}
{quote}
When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so
new lines etc):
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
{quote}
Notice that I send the heart-beat header requesting 3,3 heartbeats but
then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my
code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
was:
using the transport:
{quote}
{quote}
When connecting a stomp 1.1 client I see this using tcpdump:
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
{quote}
Notice that I send the heart-beat header requesting 3,3 heartbeats but
then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my
code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
> Stomp 1.1 keep alive does not work with stomp+nio
> -
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
>Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12,
> mixed mode)
>Reporter: R.I.Pienaar
>
> using the transport:
> {quote}
>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output
> so new lines etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
> charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
> {quote}
> Notice that I send the heart-beat header requesting 3,3 heartbeats
> but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing
> my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio
[
https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
R.I.Pienaar updated AMQ-3897:
-
Description:
using the transport:
{quote}
{quote}
When connecting a stomp 1.1 client I see this using tcpdump:
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
{quote}
Notice that I send the heart-beat header requesting 3,3 heartbeats but
then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my
code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
was:
using the transport:
When connecting a stomp 1.1 client I see this using tcpdump:
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
Notice that I send the heart-beat header requesting 3,3 heartbeats but
then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my
code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
> Stomp 1.1 keep alive does not work with stomp+nio
> -
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
>Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12,
> mixed mode)
>Reporter: R.I.Pienaar
>
> using the transport:
> {quote}
>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump:
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain;
> charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1
> {quote}
> Notice that I send the heart-beat header requesting 3,3 heartbeats
> but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing
> my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio
R.I.Pienaar created AMQ-3897: Summary: Stomp 1.1 keep alive does not work with stomp+nio Key: AMQ-3897 URL: https://issues.apache.org/jira/browse/AMQ-3897 Project: ActiveMQ Issue Type: Bug Components: Broker, stomp Affects Versions: 5.6.0 Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: R.I.Pienaar using the transport: When connecting a stomp 1.1 client I see this using tcpdump: send...> CONNECT .passcode:xxx.host:kvm4.content-length:0.heart-beat:3,3.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0... <...receive CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1 Notice that I send the heart-beat header requesting 3,3 heartbeats but then ActiveMQ replies with 0,0 If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats. It seems stomp+nio does not have heartbeat support for protocol 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3819) high cpu with stomp+nio+ssl and many subscriptions
[
https://issues.apache.org/jira/browse/AMQ-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265744#comment-13265744
]
R.I.Pienaar commented on AMQ-3819:
--
Well done, this has resolved the problem for me. Tested both with my simple
test script and real world workload that first brought up the problem.
> high cpu with stomp+nio+ssl and many subscriptions
> --
>
> Key: AMQ-3819
> URL: https://issues.apache.org/jira/browse/AMQ-3819
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
>Affects Versions: 5.6.0
> Environment: CentOS 6, RC of 5.6.0
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
>Reporter: R.I.Pienaar
> Attachments: StompLoadTest.java, StompNIOSSLLoadTest.java
>
>
> Switching an existing workload from a transport:
> {quote}
> uri="stomp+ssl://0.0.0.0:6165?needClientAuth=true"/>
> {quote}
> to
> {quote}
> uri="stomp+nio+ssl://0.0.0.0:6165?needClientAuth=true"/>
> {quote}
> showed the CPU profile to go from 1-5% to 300% constantly on a 8 core server
> I was able to recreate this using a ruby client @
> http://devco.net/rip/amq_560_stomp_nio_ssl_tester.rb
> The important combinations are:
> * I am connecting to a stomp+nio+ssl port
> * I am creating the subscriptions to the 10 queus and topics
> If I change either of these variables - like just commenting out the loop
> that does those subscriptions - then the CPU load is acceptable.
> I analysed the running VM with VisualVM and found that
> transport.nio.NIOSSLTransport.serviceRead() is the busy thread.
> My activemq.xml is:
> {noformat}
>xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd
> http://activemq.apache.org/camel/schema/spring
> http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";>
> http://activemq.apache.org/schema/core"; brokerName="amq1"
> useJmx="true" persistent="true" schedulePeriodForDestinationPurge="6">
>
>
>
>
>inactiveTimoutBeforeGC="12" />
>
>
>
>
>jmxDomainName="org.apache.activemq"/>
>
>
>
>
>
>groups="admins,everyone"/>
>
>
>
>
>
>
>admin="admins" />
>admin="admins" />
>
>
>
>
>
>
> keyStore="keystore.jks" keyStorePassword="ohshahCu"
> trustStore="truststore.jks" trustStorePassword="ohshahCu"
>/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>uri="stomp+nio://0.0.0.0:6163"/>
>uri="stomp+ssl://0.0.0.0:6164"/>
>uri="stomp+nio+ssl://0.0.0.0:6165?needClientAuth=true"/>
>
>
>
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3819) high cpu with stomp+nio+ssl and many subscriptions
[
https://issues.apache.org/jira/browse/AMQ-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264996#comment-13264996
]
R.I.Pienaar commented on AMQ-3819:
--
Thanks guys, I'll test 'morrow UK time.
> high cpu with stomp+nio+ssl and many subscriptions
> --
>
> Key: AMQ-3819
> URL: https://issues.apache.org/jira/browse/AMQ-3819
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
>Affects Versions: 5.6.0
> Environment: CentOS 6, RC of 5.6.0
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
>Reporter: R.I.Pienaar
> Attachments: StompLoadTest.java, StompNIOSSLLoadTest.java
>
>
> Switching an existing workload from a transport:
> {quote}
> uri="stomp+ssl://0.0.0.0:6165?needClientAuth=true"/>
> {quote}
> to
> {quote}
> uri="stomp+nio+ssl://0.0.0.0:6165?needClientAuth=true"/>
> {quote}
> showed the CPU profile to go from 1-5% to 300% constantly on a 8 core server
> I was able to recreate this using a ruby client @
> http://devco.net/rip/amq_560_stomp_nio_ssl_tester.rb
> The important combinations are:
> * I am connecting to a stomp+nio+ssl port
> * I am creating the subscriptions to the 10 queus and topics
> If I change either of these variables - like just commenting out the loop
> that does those subscriptions - then the CPU load is acceptable.
> I analysed the running VM with VisualVM and found that
> transport.nio.NIOSSLTransport.serviceRead() is the busy thread.
> My activemq.xml is:
> {noformat}
>xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd
> http://activemq.apache.org/camel/schema/spring
> http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";>
> http://activemq.apache.org/schema/core"; brokerName="amq1"
> useJmx="true" persistent="true" schedulePeriodForDestinationPurge="6">
>
>
>
>
>inactiveTimoutBeforeGC="12" />
>
>
>
>
>jmxDomainName="org.apache.activemq"/>
>
>
>
>
>
>groups="admins,everyone"/>
>
>
>
>
>
>
>admin="admins" />
>admin="admins" />
>
>
>
>
>
>
> keyStore="keystore.jks" keyStorePassword="ohshahCu"
> trustStore="truststore.jks" trustStorePassword="ohshahCu"
>/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>uri="stomp+nio://0.0.0.0:6163"/>
>uri="stomp+ssl://0.0.0.0:6164"/>
>uri="stomp+nio+ssl://0.0.0.0:6165?needClientAuth=true"/>
>
>
>
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-3819) high cpu with stomp+nio+ssl and many subscriptions
R.I.Pienaar created AMQ-3819:
Summary: high cpu with stomp+nio+ssl and many subscriptions
Key: AMQ-3819
URL: https://issues.apache.org/jira/browse/AMQ-3819
Project: ActiveMQ
Issue Type: Bug
Components: stomp
Affects Versions: 5.6.0
Environment: CentOS 6, RC of 5.6.0
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
Reporter: R.I.Pienaar
Switching an existing workload from a transport:
{quote}
{quote}
to
{quote}
{quote}
showed the CPU profile to go from 1-5% to 300% constantly on a 8 core server
I was able to recreate this using a ruby client @
http://devco.net/rip/amq_560_stomp_nio_ssl_tester.rb
The important combinations are:
* I am connecting to a stomp+nio+ssl port
* I am creating the subscriptions to the 10 queus and topics
If I change either of these variables - like just commenting out the loop that
does those subscriptions - then the CPU load is acceptable.
I analysed the running VM with VisualVM and found that
transport.nio.NIOSSLTransport.serviceRead() is the busy thread.
My activemq.xml is:
{noformat}
http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.apache.org/schema/core";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd
http://activemq.apache.org/camel/schema/spring
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";>
http://activemq.apache.org/schema/core"; brokerName="amq1"
useJmx="true" persistent="true" schedulePeriodForDestinationPurge="6">
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066440#comment-13066440
]
R.I.Pienaar commented on AMQ-3135:
--
OK, this looks good, the only remaining weirdness is in ConnectionInfo the
clientIP comes out as "/1.2.3.4:56" and not a proper url, but you indicated
that comes from the VM and you cant fix that.
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065775#comment-13065775
]
R.I.Pienaar commented on AMQ-3135:
--
Awesome, I've tested and this looks good at first glance, will take a better in
depth look real soon and let you know
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052528#comment-13052528
]
R.I.Pienaar commented on AMQ-3135:
--
OK, I now get brokerinfo messages:
"BrokerInfo": {
"commandId": 1,
"responseRequired": false,
"brokerId": {
"value": "ID:dev3.xxx.net-36297-1308660607779-0:1"
},
"brokerURL": "tcp://dev3.xxx.net:6166",
"slaveBroker": false,
"masterBroker": false,
"faultTolerantConfiguration": false,
"networkConnection": true,
"duplexConnection": false,
"brokerName": "localhost",
"connectionId": 0,
"networkProperties": ""
}}
This is fine - the brokerURL is great and it even shows the correct protocol
unlike the connection ones.
The issue left is that I can only get this information where there's events -
like a broker connecting/disconnecting. Compare with
ActiveMQ.Advisory.Connection that dumps the current network state when you
first subscribe to it. So for the purpose of mapping networks I still have no
way afaik to ask it to show me its current state for the brokers.
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049753#comment-13049753
]
R.I.Pienaar commented on AMQ-3135:
--
sounds good. Let me know and I'll gladly test the next nightly :)
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049745#comment-13049745
]
R.I.Pienaar commented on AMQ-3135:
--
The end result that I would like to be able to do is to create a view of my
middleware network. In complex networks where nodes have failover connections
and brokers are meshed or have on their own backup connections to other brokers
getting a clear view of how things look now is really complex. I want to make
this better by having the ablity to produce a view of a network now. This is
to aid in debugging but also as a good aid to optimizing network construction
and to identify setup errors.
This should show broker to node and broker to broker connections, perhaps as a
graph. The final output isnt the question.
In order to do produce the source data I need to be able to answer:
- what node is connected to broker a, to identify a noode I need its IPs
- what brokers are connected to broker a, to identify brokers I need their IPs
If the advisories showed the IP in all cases this would let me do it.
The bridge advisories are fine and the client advisories are fine, we just need
a way to identify the machines hence the request for clientIP.
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043257#comment-13043257
]
R.I.Pienaar commented on AMQ-3135:
--
the only other 2 connections:
This is my stomp connection to request this data, i connect from localhost so
this is perfect:
{"ConnectionInfo": {
"commandId": 0,
"responseRequired": true,
"connectionId": {
"value": "ID:dev1.xx.net-46999-1307055165619-4:3"
},
"clientId": "ID:dev1.xx.net-46999-1307055165619-4:3",
"clientIp": "/127.0.0.1:43407",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
this is outbound - but its not what I need, i am on dev1 it shows connections
from dev3 and neither connectioninfo has dev3's ip ad clientip, the ip here is
the IP of dev1 , which I guess is ok for the outbound connection but the
inbound that I showed earlier never shows the IP of the dev3 remote broker
{"ConnectionInfo": {
"commandId": 4,
"responseRequired": false,
"connectionId": {
"value": "ID:dev3.xx.net-56412-1307055435940-3:1"
},
"clientId": "dev3-dev1_localhost_outbound",
"clientIp": "tcp://dev1.xx.net/88.xx.xx.178:6166",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043120#comment-13043120
]
R.I.Pienaar commented on AMQ-3135:
--
Still no joy unfortunately,
{"ConnectionInfo": {
"commandId": 2,
"responseRequired": true,
"connectionId": {
"value": "ID:dev1.xx.net-46999-1307055165619-6:2"
},
"clientId": "dev3-dev1_localhost_inbound_localhost",
"clientIp": "vm://localhost#4",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
this is the incoming connection from dev3, shows localhost.
loglines:
2011-06-02 23:57:16,419 [xx.xx.181:56079] INFO TransportConnection
- Started responder end of duplex bridge
dev3-dev1@ID:dev3.xx.net-56412-1307055435940-0:1
2011-06-02 23:57:16,430 [m://localhost#4] INFO DemandForwardingBridgeSupport
- Network connection between vm://localhost#4 and
tcp:///88.xx.xx.181:56079(localhost) has been established.
dev3 ip is: 88.xx.xx.181 which you can see missreported on the last line here.
This is the 2nd June snapshot
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041133#comment-13041133
]
R.I.Pienaar commented on AMQ-3135:
--
This seems to break the network of broker feature :)
2011-05-30 14:49:21,813 [98.xx.xx:49408] INFO TransportConnection-
Started responder end of duplex bridge
dev3-dev1@ID:dev3.xx.net-59818-1305794003658-0:1
2011-05-30 14:49:21,814 [ctiveMQ Task-11] WARN Service
- Async error occurred: java.lang.NullPointerException
java.lang.NullPointerException
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.createObjectName(ManagedRegionBroker.java:674)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.addProducer(ManagedRegionBroker.java:271)
at
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:93)
at
org.apache.activemq.advisory.AdvisoryBroker.addProducer(AdvisoryBroker.java:133)
at
org.apache.activemq.broker.CompositeDestinationBroker.addProducer(CompositeDestinationBroker.java:56)
at
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:93)
at
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:93)
at
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:93)
at
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:93)
at
org.apache.activemq.security.AuthorizationBroker.addProducer(AuthorizationBroker.java:168)
at
org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:99)
at
org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:507)
at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:105)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:306)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69)
at
org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:121)
at
org.apache.activemq.transport.vm.VMTransport.start(VMTransport.java:136)
at
org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
at
org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
at
org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:896)
at
org.apache.activemq.broker.TransportConnector$1$1.run(TransportConnector.java:217)
at java.lang.Thread.run(Thread.java:636)
2011-05-30 14:49:21,816 [m://localhost#2] INFO DemandForwardingBridgeSupport
- Network connection between vm://localhost#2 and tcp:///88.xx.xx.181:49408
shutdown due to a local error: java.lang.NullPointerException
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036067#comment-13036067
]
R.I.Pienaar commented on AMQ-3135:
--
Testing this and seeing some pretty perplexing results.
Given config:
dev1: no broker connections configured
dev3:
When looking at ActiveMQ.Advisory.Connection on dev1 I get:
{"ConnectionInfo": {
"commandId": 2,
"responseRequired": false,
"connectionId": {
"value": "ID:dev3.xx.net-59818-1305794003658-3:1"
},
"clientId": "dev3-dev1_localhost_outbound",
"clientIp": "dev1.xx.net/88.xx.xx.178:6166",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
{"ConnectionInfo": {
"commandId": 5,
"responseRequired": true,
"connectionId": {
"value": "ID:dev1.xx.net-59417-1305793401904-6:2"
},
"clientId": "dev3-dev1_localhost_inbound_localhost",
"clientIp": "vm://localhost#4",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
Here are the logs:
2011-05-19 09:33:24,231 [xx.xx.181:49049] INFO TransportConnection
- Started responder end of duplex bridge
dev3-dev1@ID:dev3.xx.net-59818-1305794003658-0:1
2011-05-19 09:33:24,262 [m://localhost#4] INFO DemandForwardingBridgeSupport
- Network connection between vm://localhost#4 and
tcp:///88.xx.xx.181:49049(localhost) has been established.
# netstat -an|grep 49049
tcp0 0 :::88.xx.xx.178:6166 :::88.xx.xx.181:49049
ESTABLISHED
The way I read this is that the first one - dev3-dev1_localhost_outbound - is
the connection from dev3 to dev1 initiating the broker to broker connection and
the 2nd one is the back connection from dev1 to dev3.
The issue is that the first one lists as remote ip the ipaddress of dev1 and
not dev3 when it should be dev3? In the logs I do see the correct IPs listed
and you can see its confirmed with netstat that the ip/port combination is the
connection from the other side so the logs are right. Advisories arent.
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035262#comment-13035262
]
R.I.Pienaar commented on AMQ-3135:
--
This is all I get from it on my broker to broker connections:
{"ConnectionInfo": {
"commandId": 5,
"responseRequired": true,
"connectionId": {
"value": "ID:dev1.xx.net-51545-1305632916918-6:2"
},
"clientId": "monitor1-monitor2_localhost_inbound_localhost",
"clientIp": "vm://localhost#4",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
{"ConnectionInfo": {
"commandId": 2,
"responseRequired": false,
"connectionId": {
"value": "ID:dev3.xx.net-44999-1305633014817-3:1"
},
"clientId": "monitor1-monitor2_localhost_outbound",
"clientIp": "vm://localhost#4",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
So in both cases I am only getting vm:// connection info even though they are
remote connections - see the clientId for confirmation.
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
[
https://issues.apache.org/jira/browse/AMQ-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034731#comment-13034731
]
R.I.Pienaar commented on AMQ-3135:
--
I've tried this in the latest 5.6-SNAPSHOT, it works for simple client
connections but the format of the clientIP is a bit odd:
"clientIp": "/127.0.0.1:48334",
would be great if we could toss out the / or just make it tcp://... which
would be in line with the other cases like:
"clientIp": "vm://localhost#6",
In the case of broker to broker comms I see:
"clientId": "monitor1-monitor2_localhost_inbound_localhost",
"clientIp": "vm://localhost#4",
but never ones showing the tcp connection to the remote broker
> ActiveMQ.Advisory.Connection messages should contain client ip/host
> ---
>
> Key: AMQ-3135
> URL: https://issues.apache.org/jira/browse/AMQ-3135
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 5.4.2
> Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
>Reporter: R.I.Pienaar
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: 5.6.0
>
>
> At present a connection advisory message recieved over stomp looks like:
> "ConnectionInfo": {
> "commandId": 0,
> "responseRequired": true,
> "connectionId": {
> "value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
> },
> "clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
> "userName": "",
> "password": "",
> "brokerMasterConnector": false,
> "manageable": false,
> "clientMaster": true,
> "faultTolerant": false,
> "failoverReconnect": false
> }}
> Where monitor1.xx.net is the broker name.
> It would be very useful if these messages also included the IP Address,
> Hostname, Port of the client connecting.
> There other advisories that would also greatly benefit from this like
> ActiveMQ.Advisory.NetworkBridge
> thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
ActiveMQ.Advisory.Connection messages should contain client ip/host
---
Key: AMQ-3135
URL: https://issues.apache.org/jira/browse/AMQ-3135
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.4.2
Environment: CentOS, OpenJDK 6, ActiveMQ 5.4.2
Reporter: R.I.Pienaar
Priority: Minor
At present a connection advisory message recieved over stomp looks like:
"ConnectionInfo": {
"commandId": 0,
"responseRequired": true,
"connectionId": {
"value": "ID:monitor1.xx.net-57901-1294599217160-5:10017"
},
"clientId": "ID:monitor1.xx.net-57901-1294599217160-5:10017",
"userName": "",
"password": "",
"brokerMasterConnector": false,
"manageable": false,
"clientMaster": true,
"faultTolerant": false,
"failoverReconnect": false
}}
Where monitor1.xx.net is the broker name.
It would be very useful if these messages also included the IP Address,
Hostname, Port of the client connecting.
There other advisories that would also greatly benefit from this like
ActiveMQ.Advisory.NetworkBridge
thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
