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 be in the connection if i make a
filter but i wanted to do it "by configuration" just to log the user that
connects to a topic/queue)
On Wed, Jun 17, 2015 at 1:23 PM, Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> 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 test this out I am getting the user name in that object on the
> advisory.
>
> On Wed, Jun 17, 2015 at 2:45 AM, ALi <osat...@gmail.com> wrote:
>
> > 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 <osat...@gmail.com> wrote:
> >
> > > this is what i see with this two routes
> > >
> > > <route>
> > > <from
> > >
> >
> uri="activemq:topic:ActiveMQ.Advisory.Consumer.Queue.TEST.Q?mapJmsMessage=false"
> > > />
> > > <convertBodyTo type="java.lang.String"/>
> > > <transform>
> > > <simple>\r\n${date:now:yyyyMMdd-hh-mm-ss} ${in.body}
> > \r\n</simple>
> > > </transform>
> > > <to
> > >
> >
> uri="file://c:/folder/?fileExist=Append&fileName=advisoryConnection-${date:now:yyyyMMdd}.txt"
> > > />
> > > </route>
> > > <route>
> > > <from uri="activemq:topic:ActiveMQ.Advisory.Connection" />
> > > <convertBodyTo type="java.lang.String"/>
> > > <transform>
> > > <simple>\r\n${date:now:yyyyMMdd-hh-mm-ss} ${in.body}
> \r\n</simple>
> > > </transform>
> > > <to
> > >
> >
> uri="file://c:/folder/?fileExist=Append&fileName=advisoryConnection-${date:now:yyyyMMdd}.txt"
> > > />
> > > </route>
> > >
> > >
> > >
> > >
> > > 20150617-08-31-04
> > >
> > > 20150617-08-31-37
> > >
> > > 20150617-08-31-37 ActiveMQMessage {commandId = 0, responseRequired =
> > > false, messageId = ID:COMPUTER-61030-1434522661496-1:1:0:0:11,
> > > originalDestination = null, originalTransactionId = null, producerId =
> > > ID:COMPUTER-61030-1434522661496-1:1:0:0, destination =
> > > topic://ActiveMQ.Advisory.Consumer.Queue.TEST.Q, transactionId = null,
> > > expiration = 0, timestamp = 0, arrival = 0, brokerInTime =
> 1434522697947,
> > > brokerOutTime = 1434522697947, correlationId = null, replyTo = null,
> > > persistent = false, type = Advisory, priority = 0, groupID = null,
> > > groupSequence = 0, targetConsumerId = null, compressed = false, userID
> =
> > > null, content = null, marshalledProperties = null, dataStructure =
> > > ConsumerInfo {commandId = 3, responseRequired = false, consumerId =
> > > ID:COMPUTER-61030-1434522661496-4:1:-1:1, destination = queue://TEST.Q,
> > > prefetchSize = 1000, maximumPendingMessageLimit = 0, browser = false,
> > > dispatchAsync = true, selector = null, subscriptionName = null,
> noLocal =
> > > false, exclusive = false, retroactive = false, priority = 0,
> brokerPath =
> > > null, optimizedAcknowledge = false, noRangeAcks = false,
> > > additionalPredicate = null}, redeliveryCounter = 0, size = 1024,
> > properties
> > > = {consumerCount=1, originBrokerURL=tcp://127.0.0.1:61616,
> > > originBrokerId=ID:COMPUTER-61030-1434522661496-0:1,
> > > originBrokerName=amq-broker}, readOnlyProperties = true, readOnlyBody =
> > > true, droppable = false}
> > >
> > > 20150617-08-33-20 ActiveMQMessage {commandId = 0, responseRequired =
> > > false, messageId = ID:COMPUTER-61030-1434522661496-1:1:0:0:12,
> > > originalDestination = null, originalTransactionId = null, producerId =
> > > ID:COMPUTER-61030-1434522661496-1:1:0:0, destination =
> > > topic://ActiveMQ.Advisory.Consumer.Queue.TEST.Q, transactionId = null,
> > > expiration = 0, timestamp = 0, arrival = 0, brokerInTime =
> 1434522800355,
> > > brokerOutTime = 1434522800355, correlationId = null, replyTo = null,
> > > persistent = false, type = Advisory, priority = 0, groupID = null,
> > > groupSequence = 0, targetConsumerId = null, compressed = false, userID
> =
> > > null, content = null, marshalledProperties = null, dataStructure =
> > > RemoveInfo {commandId = 0, responseRequired = false, objectId =
> > > ID:COMPUTER-61030-1434522661496-4:1:-1:1, lastDeliveredSequenceId = 0},
> > > redeliveryCounter = 0, size = 1024, properties = {consumerCount=0,
> > > originBrokerURL=tcp://127.0.0.1:61616,
> > > originBrokerId=ID:COMPUTER-61030-1434522661496-0:1,
> > > originBrokerName=amq-broker}, readOnlyProperties = true, readOnlyBody =
> > > true, droppable = false}
> > >
> > > 20150617-08-33-20
> > >
> > >
> > >
> > >
> > > it seems that connection messages arent "printable"????
> > >
> > >
> > >
> > >
> > > On Tue, Jun 16, 2015 at 4:00 PM, Christopher Shannon <
> > > christopher.l.shan...@gmail.com> wrote:
> > >
> > >> No problem, let me know if you have any more questions.
> > >>
> > >> Chris
> > >>
> > >> On Tue, Jun 16, 2015 at 9:13 AM, ALi <osat...@gmail.com> wrote:
> > >>
> > >> > Thank you very nice explanation I will try in this manner
> > >> >
> > >>
> > >
> > >
> >
>
