Dear Members
I have apache-activemq-5.2.0 and apache-activemq-5.3.0
I have a weird behavior with http://localhost:8161/admin/queueGraph.jsp
When I start the activemq version 5.2.0 and then I produce Messages with my
java app and when I enter to such link I can see in the Queue Graph the
values a
On Tue, Mar 30, 2010 at 11:17 PM, Bruce Snyder wrote:
> On Tue, Mar 30, 2010 at 10:52 PM, foucault wrote:
>>
>>
>>> so in short, as of updating to 5.3.1 the admin console never shows up,
>>> netstat doesn't show anything running on port 8161, although the logs tell
>>> me it has been launched. a
On Tue, Mar 30, 2010 at 10:52 PM, foucault wrote:
>
>
>> so in short, as of updating to 5.3.1 the admin console never shows up,
>> netstat doesn't show anything running on port 8161, although the logs tell
>> me it has been launched. anyone else encounter this problem?
>
> I just double-checked t
> so in short, as of updating to 5.3.1 the admin console never shows up,
> netstat doesn't show anything running on port 8161, although the logs tell
> me it has been launched. anyone else encounter this problem?
I just double-checked this with the 5.3.1 binary tarball from the
release and the
On Tue, Mar 30, 2010 at 6:02 PM, foucault wrote:
>
> First thing, activemq and its admin panel work fine out of the box (default
> config), also both work fine in my dev environment with our re-based config.
>
> production has load blancing, as pretty much the only diffrence, and that is
> where t
Solved the problem. This was a bug in release 5.3.0. Upgraded to 5.3.1 to
fix.
--
View this message in context:
http://old.nabble.com/Duplicate-message-add-attempt-rejected-tp28084188p28086403.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
First thing, activemq and its admin panel work fine out of the box (default
config), also both work fine in my dev environment with our re-based config.
production has load blancing, as pretty much the only diffrence, and that is
where the admin panel is not working.
logs showing everything work
On Tue, 2010-03-30 at 12:31 -0400, Gabe Westmaas wrote:
> Below is a slightly edited version of a tcp dump on the activemq side of a
> transaction between an NMS 1.2 client and ActiveMQ 5.3.
>
> MESSAGE
> message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:-1:1:14
>
> BEGIN
> transaction:ID:IAD2
Well I can spend this time and help you but I'm not that fluent with java and
junit so if you can suggest how to start would be great.
Thanks for this link!
M.
Have a look at the ruby jmx4r example at the bottom of this blog entry as a
starting point on a simple way to code jmx calls :
http:/
Below is a slightly edited version of a tcp dump on the activemq side of a
transaction between an NMS 1.2 client and ActiveMQ 5.3.
MESSAGE
message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:-1:1:14
BEGIN
transaction:ID:IAD2DEPLOY01-56247-634052078212143799-1:885:1
message-id:ID:arch3.bmdc-35562
Note that I have also tried this with a networkconnection on only brokerA,
connecting to brokerB, with duplex="true". I get the same duplicate message
error.
--
View this message in context:
http://old.nabble.com/Duplicate-message-add-attempt-rejected-tp28084188p28084393.html
Sent from the Acti
I'm having trouble networking two brokers together. What I want to do is
make the two brokers function as virtually one. One broker is at one site,
another at a different location. Thus, I need a bi-directional connection.
That is, if I publish to a topic on brokerA I want subscribers to get t
Have a look at the ruby jmx4r example at the bottom of this blog entry as a
starting point on a simple way to code jmx calls :
http://pavelgolubeff.ya.ru/replies.xml?item_no=1583&ncrnd=3263
It may also be worth investing some time in a junit test case for your
scenario, as that would speed up find
... or maybe there is a way to remove such "zombie queue" without stopping
the MQ server?
M.
lucious wrote:
>
> Hi I filed this bug AMQ-2657 which is really annoying to me and sometimes
> it takes me the whole day to look at "zombie" temp-queue (no consumers but
> messagecount increasing) and
Sweet, thanks for the heads-up. Gonna try that when I get a chance to
upgrade.
Gary Tully wrote:
>
> belated but I think 5.4 will help, or a current snapshot, details in
> https://issues.apache.org/activemq/browse/AMQ-2670
>
--
View this message in context:
http://old.nabble.com/XAResourceR
belated but I think 5.4 will help, or a current snapshot, details in
https://issues.apache.org/activemq/browse/AMQ-2670
On 18 December 2009 16:28, jp.belanger wrote:
>
> From what I can see from my use, is the fact that the XARessource not being
> Serializable, the Recovery engine of JBoss fails
Hi I filed this bug AMQ-2657 which is really annoying to me and sometimes it
takes me the whole day to look at "zombie" temp-queue (no consumers but
messagecount increasing) and perform purge() on such queue. Waiting for fix
I'd like to ask if it's possible to create simple app to check temp-queue
Hi Kai,
the problem is a workaround for 5.3.1 that now instructs camel and camel web
console to use tcp connector to talk to the broker.
Just add something like
in webapps/camel/WEB-INF/appl
Hello Garry,
The problem is not with the clients using the failover transport, but on the
remote broker that is using static network connector. For brokers discovery
I cannot use failover but static and this network connector is not behaving
the same way as the failover transport which "connect to
Hi,
this should work
curl -d "body=message" http://localhost:8161/demo/message/myqueue
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Tue, Mar 30, 2010
Hi,
I'm new to ActiveMQ and am trying to POST a message to a queue. I'm using
Poster (the Firefox add-on) and notice that although the message makes it to
the queue it has no body. Attempts to retrieve the message using HTTP GET
results in a HTTP 500 internal error message. Using the admin interf
Some steps to help diagnose:
1) enable debug logging for both the client and broker.
org.apache.activemq=DEBUG in the log4j.properties
You should see the client failover transport detect the connection
failure and start retrying
2) A thread dump of the client should also show threads waiting f
Hello Mike,
I have the same problem. I tested and re-tested and it is not working. Have
you found any solution?
I'm currently running it in a Windows environment. The client seems to be
fine, it is the broker that's the issue.
Mike
--
View this message in context:
http://old.nabble.com/Maste
Hello,
I changed the port from 61616 to 23000 in activemq.xml:
When I then start activemq.bat it starts normally but does go throught the
"Initializing Spring root WebApplicationContext" process. It just stops.
When going to 61616 again, it works.
It does not work
24 matches
Mail list logo
