Re: advisory messages username logging

2015-06-17 Thread ALi
i am unable to see username neither with stomp with ws neither with tcp . i am putting this rule to camel so i can see it in file . and no solution :( \r\n${date:now:MMdd-hh-mm-ss} ${in.body} ::${headers} \r\n \r\n${date:now:MMdd-h

Re: advisory messages username logging

2015-06-17 Thread Christopher Shannon
What do your STOMP headers look like? If you use the header property called "login", then the use name should be set in the ConnectionInfo on the advisory. I just double checked this and ran a test using STOMP over WS and I did indeed get an advisory message with the user name property set. On W

Re: advisory messages username logging

2015-06-17 Thread ALi
i think yes ... because if i dont put user i am unable to get access (using web socket in the demo application) so it must be set or perhaps the ws doesnt set user? that is why i am asking when connecting ... the connectioninfo is not in the advisory of connection (perhaps it must b

Re: advisory messages username logging

2015-06-17 Thread Christopher Shannon
If the user name has been set it would be under the dataStructure field inside the ConnectionInfo object. Just like in your previous message you can see a ConsumerInfo object when listening for new consumers. Are you sure you are setting the user name/credentials when making a connection? When I

Re: advisory messages username logging

2015-06-16 Thread ALi
it seems that the headers are set with no message .. but in the headers i dont see the username (guest) only headers of the message On Wed, Jun 17, 2015 at 8:37 AM, ALi wrote: > this is what i see with this two routes > > > uri="activemq:topic:ActiveMQ.Advisory.Consumer.Queue.TEST.Q?mapJms

Re: advisory messages username logging

2015-06-16 Thread ALi
this is what i see with this two routes \r\n${date:now:MMdd-hh-mm-ss} ${in.body} \r\n \r\n${date:now:MMdd-hh-mm-ss} ${in.body} \r\n 20150617-08-31-04 20150617-08-31-37 20150617-08-31-37 ActiveMQMessage {commandId = 0, responseRe

Re: advisory messages username logging

2015-06-16 Thread Christopher Shannon
No problem, let me know if you have any more questions. Chris On Tue, Jun 16, 2015 at 9:13 AM, ALi wrote: > Thank you very nice explanation I will try in this manner >

Re: advisory messages username logging

2015-06-16 Thread ALi
Thank you very nice explanation I will try in this manner

Re: advisory messages username logging

2015-06-16 Thread Christopher Shannon
The advisory topic "ActiveMQ.Advisory.Consumer.Queue.TEST.Q" will send messages alerting you of new consumers and you will receive a "ConsumerInfo" object which won't contain the user name. That will contain a reference to the consumerId instead, since the connection was already created. The cons

Re: advisory messages username logging

2015-06-16 Thread ALi
i dont know where i am connecting with stomp and ws . this is what this log shows: (using camel to print message) \r\n${date:now:MMdd-hh-mm-ss} ${in.header.user} ${in.body} ${in.headers} \r\n 20150616-01-16-27 ActiveMQMessage {commandId = 0, responseRequ

Re: advisory messages username logging

2015-06-16 Thread Christopher Shannon
Advisory messages delivered to ActiveMQ.Advisory.Connection will contain a ConnectionInfo object as part of the data structure field of the message. That object will contain the user name used for the new connection. Passwords will always be cleared, however. On Tue, Jun 16, 2015 at 5:41 AM, ALi