activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "R.I.Pienaar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3135) ActiveMQ.Advisory.Connection messages should contain client ip/host
Date Thu, 02 Jun 2011 23:05:47 GMT

    [ 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

Mime
View raw message