Re: Can I use JMX on an embedded broker without TCP/IP?

Opening a tcp/ip port and associating that to the JMX registry allows for JMX remote access. if you are not concerned with remote access the JMX console can access the local JMX instance as long as you are logged into that box. Chris O. *Chris Odom | Sr Consultant | Media Driver* 512.799.0270

Re: JMS to JMS Bridge

onnector created on the local broker...any ideas. Thanks, *Chris Odom | Sr Consultant | Media Driver* 512.799.0270 | chris.o...@mediadriver.com 810 Hester's Crossing, Suite 165, Round Rock, TX 78681 On Tue, Mar 18, 2014 at 4:40 PM, artnaseef wrote: > The JMS bridge connects into the br

JMS to JMS Bridge

e the default values with the users.properties when you uncomment them out. The bridge can not create any local connections returning errors stating that the username and password can not be null? Any ideas on why this is happening or have I configured the bridge incorrectly? Thanks, *Chris

Re: Reply:Re: What will happen if consumer uses the client acknowledge model but no further explicit acknowledges are made?

SuoNayi, I guess what I was trying to elude to was that there is no dispatch queue per say but just a dispatch count. The queue that the message was dispatch from is the queue for the message, and the metrics are a representation of what the broker has done with those messages in the queue.

Re: What will happen if consumer uses the client acknowledge model but no further explicit acknowledges are made?

SuoNayi Queue's only keep one copy of any message at any given time, that I am aware of. What you are seeing the web console are metrics that the Broker maintains about the Queue. Messages arrive to a Queue the Enqueue count increments. A Consumer reads a message from the Queue the Dispatch

Queue Size wrong

When looking at the Queue size attribute in JConsole for a particular Queue we noticed that the size would not reseed below a certain number 138. The reporting of this number persisted for several hours. When I investigated it I looked at the Queue's operation browseMessages it returned what I

Re: Configuring SSL on default Broker

Never mind this is a bug. Come to find out that even though you set the SslContext with in the activemq-broker.xml it is never used when creating the SslSocketConnector for the Broker, so you see the behavior I am seeing. On Tue, 24 Apr 2012 10:48:57 -0500, Chris Odom wrote: > Further debugg

Re: Configuring SSL on default Broker

ntext bs) { current.set(bs); } The TransportFactory calls setCurrentSslContext twice in which the second call sets the sslcontext to null. On Tue, 24 Apr 2012 09:43:03 -0500, Chris Odom wrote: > Furthering debugging of the issue has revealed that the create > SslSocketConnector's sslCont

Re: Configuring SSL on default Broker

ment is in A-Z order with in the broker element. Thanks Chris O. On Mon, 23 Apr 2012 17:30:52 -0500, Chris Odom wrote: > I am currently trying to setup both a https and ssl transport connector > for the default broker. I am using servicemix deploying a blueprint version > of the activem

Configuring SSL on default Broker

va:636)[10:org.apache.aries.blueprint:0.3.1] ... 15 more Any ideas on why this is happening or why this would occur would be deeply appreciated. -- Thanks, Chris Odom 512:799-0270