<[EMAIL PROTECTED]> wrote:
>> Are you positive you are using exactly the same jars on the client
>> side and broker?
>
> Bear in mind with multicast discovery, someone on your network could
> be running a different version of ActiveMQ...
>
>
>>
>> On 17/01/
a
good idea to interrupt a thread that is sending in AMQ?
James.Strachan wrote:
>
> Are you positive you are using exactly the same jars on the client
> side and broker?
>
> On 17/01/2008, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
>>
>> Thanks for the reply, but
Thanks for the reply, but I dont think thats our issue. We are still on 4.1.1
and dont use persistent messaging at all.
Thanks for the input though...
dmarks wrote:
>
> "Has anyone seen this before or know why it might be happening?"
>
> We have seen this happenand think it may be related
I dont think so, I doubt youll get much help there.does it ALWAYS happen
or just sometimes? The reason I mention that is that we have gotten this
exception before with a spring based JMS listeners trying to connect to a
TCP AMQ broker URL and both were AMQ 4.1.1 out of the box. However, it was
Hi,
We have been hit with this exception on our sending of messages:
Exception in thread "ActiveMQ Transport: tcp:///127.0.0.1:29406"
java.lang.NegativeArraySizeException
at
org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.tightUnmarshalByteSequence(BaseDataStreamM
arshaller.java:
of the time that thread will be spent on the
> SocketInputStream.socketRead0() call. But that's just wall time not
> CPU time. The method is blocking/idle waiting for IO from the socket.
>
> Regards,
> Hiram
>
>
> On Dec 19, 2007 9:58 AM, TOPPER_HARLEY <[EMAIL PRO
07, at 10:57 AM, TOPPER_HARLEY wrote:
>
>>
>> Hi,
>> Im running an eclipse RCP application that uses AMQ4.1.1 for
>> receiving data
>> from temp queues(request/response) and topics (for updates). We are
>> having
>> trouble with CPU on client side and
profile, AMQ was still
93% of the application. This may not be so b
Does anyone know what to try from here?
Thanks
/Tom
rajdavies wrote:
>
> This looks like it might be a bug - but ActiveMQ 5.0 is now available
> - please give it a try ;)
> On Dec 19, 2007, at 10:57 AM, TOPPER_
Hi,
Im running an eclipse RCP application that uses AMQ4.1.1 for receiving data
from temp queues(request/response) and topics (for updates). We are having
trouble with CPU on client side and from using YourKit profiler to monitor
this over about 16 hours I see that AMQ is 100% of the time. Accordi
Hi,
Using AMQ4.1.1 with standalone server with embedded broker. Client apps have
Spring message listeners. If we have client and server running ok and then
server is shutdown, along with the broker inside it, any client that is left
open cannot cleanly shutdown as it hangs trying to close its mess
gt; BTW does the same thing occur in ActiveMQ 5.x? IIRC there's now a
> timeout on closing things down avoiding this block
>
> On 16/11/2007, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>> Using AMQ4.1.1 with standalone server with embedded broker. Clien
Container?
/Tom
James.Strachan wrote:
>
> On 12/11/2007, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
>> >"It could just be the socket has been dropped.":
>> Is socket dropping a common occurence or simply related to the quality of
>> the network one is
to enable
you to help please let me know
/Tom
James.Strachan wrote:
>
> Without more information on how you are using the JMS client its hard
> to know really. It could just be the socket has been dropped.
>
> You night wanna enable failover...
> http://activemq.apache.org/how-can
Hi,
Using AMQ4.1, non persistent, non transactional, I am running an embedded
broker with Spring and am often getting an exception when trying to send a
message:
java.io.IOException: The transport is not running.
at
org.apache.activemq.transport.TransportSupport.checkStarted(TransportS
Hi,
Are you using Spring? Can you use an
org.apache.activemq.xbean.BrokerFactoryBean?
This will create and start the broker and just leave it there in the VM. You
can create a connection and then close it as you want but it will not
shutdown the broker. (Broker stays alive until VM dies or until
Hi all,
This is a follow on from the thread "Temp queue vs topic with message
selectors?", where I was having difficulty with temp queues.
See also : https://issues.apache.org/activemq/browse/AMQ-1375 AMQ-1375
Anyway, following some investigation I have encountered a situation where
temp que
Hi James,
Could you describe what this problem is & how to reproduce? What
version are you using? Are you hitting RAM exhaustion?
http://activemq.apache.org/my-producer-blocks.html
The issue is pretty much identical to that described here:
https://issues.apache.org/activemq/browse/AMQ-1375 AMQ-13
Hi all,
We are currently using temp queues for dispatching data to a number of
clients. In this way each client gets only his own data, request response
style. However we are having lots of trouble with the temp queues and the
broker blocking. We also have topics to dispatch updates to all clients
Hi all,
We are using temp queues for our communication, one per client. We have an
issue that when the client JVM is killed using say "kill -9" in unix that
the connection and temp queue that this client created remain in the broker,
possibly with some data on it. Both seem to remain there indefi
[quote]"Error creating bean with name
'org.apache.activemq.xbean.XBeanBrokerService' defined in class path
resource [activemq.xml]: Error setting property values; nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid property '-'
of bean class [org.apache.activemq.xbe
20 matches
Mail list logo
