Re: Wire format negotiation timeout

raffic, there are people sniffing out your ports. they connect to this > port, dont know how to respond to activemq, and they get booted off with > the timeout. > > If you have a publically accessible broker you will see this "error". > > > jaya_srini wrote: &g

Re: Wire format negotiation timeout

org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172) at java.lang.Thread.run(Thread.java:619) Any input greatly appreciated! thanks jaya jaya_srini wrote: > > Hi > > can someone answer my email below? > > Basically > > What could be som

Prefetch limit for durable topics and Pending Queues

Hi can someone confirm what is the default prefetch limit for durable topics? Is it 100 or 1000? I was seeing 100 on one page http://activemq.apache.org/what-is-the-prefetch-limit-for.html and 1000 on the other. http://activemq.apache.org/version-5-performance-tuning.html Also, can someone e

Transport Connector question

Hi The default XML configuration of ActiveMQ (5.1) has all the transport connectors enabled If we are only using tcp, do the others need to be enabled? Will there be any issues if all are enabled but we only use the tcp? My connection URL to th

Re: Wire format negotiation timeout

negotiation timeouts and I would like to understand why this happens. Could it be related to network connectivity issues? thank you jaya jaya_srini wrote: > > Thanks Joe! > > No. we only see this if I send higher than certain number of requests > (after about 1000 - 2000 conc

Re: JMS Threading Restriction

hi I had a follow up question on this... If I publish a message within onMessage() then are the following true? 1) if the message is published within onMessage() in the same thread i.e.the JMS provider owns the onMessage thread and the publish happens in that same thread, then the message can b

Re: Async exception with no exception listener: java.io.EOFException

t I was wondering if there were other impacts if we set the "useDatabaseLock" to false? thanks! jaya jaya_srini wrote: > > Hi Rob > > I moved to 5.1 release but now I can't even start the broker :( using my > activemq.xml config for 5.0.0. After a couple of m

Re: Async exception with no exception listener: java.io.EOFException

apter - Failed to stop broker rajdavies wrote: > > > On 16 Jun 2008, at 23:12, jaya_srini wrote: > >> >> hi all >> >> I saw several posts regarding the async exception (listed below) in >> logs >> with ActiveMQ 5.0.0. We are also seeing this excep

Re: Async exception with no exception listener: java.io.EOFException

Thank You! Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we shouldn't need to change any of our previous configuration we did with 5.0, correct? (e.g. connect Url parameters, wireformat parameters etc) rajdavies wrote: > > > On 16 Jun 2008, at 23:

Re: Async exception with no exception listener: java.io.EOFException

Thank You! Is 5.1 backwards compatible with 5.0 configurattion? i.e if we get 5.1, we shouldn't need to change any of our previous configuration we did with 5.0, correct? (e.g. connect Url parameters, wireformat parameters etc) rajdavies wrote: > > > On 16 Jun 2008, at 23:

Async exception with no exception listener: java.io.EOFException

hi all I saw several posts regarding the async exception (listed below) in logs with ActiveMQ 5.0.0. We are also seeing this exception randomly in the logs, the bad part is it breaks the connection between Broker and the client even tho the broker is up and running and there are no network connec

Re: Database connection between ActiveMQ and broker

Filed this issue about a week ago per this email thread. https://issues.apache.org/activemq/browse/AMQ-1780 Can someone give an ETA on this? This is a production problem for us currently jaya_srini wrote: > > Ah..ok. Got it. > > I'll raise a new JIRA issue then. &

Re: org.mortbay.jetty Exceptions in the log

Just wanted to add that this is not interfering with message send or receive i.e we are still able to send and receive messages.It would be nice to know why these exceptions are happening? thanks! jaya jaya_srini wrote: > > Hi there > > We are seeing the following exceptions in t

org.mortbay.jetty Exceptions in the log

Hi there We are seeing the following exceptions in the logs with ActiveMQ 5.0.0. Can someone explain what these are and how it can be resolved? thanks! 2008-06-10 08:11:08,042 [btpool0-44 ] WARN log - handle failed java.io.IOException: Closed at org.mortba

Re: Database connection between ActiveMQ and broker

. > > Mario > > On Fri, Jun 6, 2008 at 6:23 PM, jaya_srini <[EMAIL PROTECTED]> wrote: >> >> Hi Mario >> >> We are using only one Broker and we are still seeing this issue i.e >> Broker >> not automatically reconnecting to the database >&

Re: Database connection between ActiveMQ and broker

the > https://issues.apache.org/activemq/browse/AMQ-1350 issue that is about > the behaviour when encountering an unexpected loss of the lock. > > Mario > > On Thu, Jun 5, 2008 at 11:28 PM, jaya_srini <[EMAIL PROTECTED]> wrote: >> >> Hi Hiram >> >>

Re: Database connection between ActiveMQ and broker

gt; where it left off the next time it runs. If it fails every time, the > old acked messages are not going to get propertly deleted out of your > database. > > On Mon, May 19, 2008 at 11:49 AM, jaya_srini <[EMAIL PROTECTED]> > wrote: >> >> Hello >> >>

Re: Wire format negotiation timeout

gt; never does within the alloted timeout. The default timeout value is 15 > seconds (see > http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/WireFormatNegotiator.html > > WireFormatNegotiator.htm ). > > Do you see the problem with a lighter conne

Wire format negotiation timeout

Hello We are using ActiveMQ 5.0 and we see these messages in the logs when the broker is hit with multiple requests (in our case > 1000 concurrent requests). Each request creates a new connection, sends a message to the topic and closes the connection. There is also a durable consumer that gets c

Re: Database connection between ActiveMQ and broker

Forgot to ask this in my previous post...after the connection is restablished will the broker be able to continue without a restart or will we need to restart the broker every time there is a network issue like this? thanks jaya jaya_srini wrote: > > Hello > > We are using Ac

Database connection between ActiveMQ and broker

Hello We are using ActiveMQ 5.0.0 and the JDBCPersistenceAdapter. From time to time we see the following message in the logs [Q Cleanup Timer] WARN JDBCPersistenceAdapter - Old message cleanup failed due to: com.jnetdirect.jsql.x: DBComms.transmit exception:[java.net.SocketException: C

Re: Question about Producer Consumer usage

messages as the link suggests below http://activemq.apache.org/how-do-i-use-jms-efficiently.html jaya_srini wrote: > > Hi Hiram > > I followed what was said in this link in the ActiveMQ page > > http://activemq.apache.org/how-do-i-use-jms-efficiently.html > > Also from ou

Re: Question about Producer Consumer usage

Hiram Chirino wrote: > > Looks like you have multiple threads concurrently sending messages > using only 1 session. The JMS spec explicitly states that this is not > allowed. Sessions should only be used by 1 thread at a time. > > On Tue, May 13, 2008 at 1:45 PM, jaya_srini

Re: Question about Producer Consumer usage

m, on why the > transport thread is inside the socketRead0 method, and not data is being > received from the server > > when taking thread dumps, always take two of them, otherwise you don't > have a reference in time > Filip > > > > > jaya_srini wrote: &

Re: Question about Producer Consumer usage

here's the link http://www.nabble.com/file/p17221085/thread_dump.txt thanks Jaya Filip Hanik - Dev Lists wrote: > > paste it into the email or provide a link to it, > attachment dont make it to the user list > > Filip > > jaya_srini wrote: >> Hi Fili

Re: Question about Producer Consumer usage

r all threads > > Filip > > jaya_srini wrote: >> thanks for the response, Filip! >> >> Thread dump below is what we got on the client side. I'll try and see if >> I >> can get a better dump. So what would be the resolution for this? Will >> enablin

Re: Question about Producer Consumer usage

e thread dump? > > thanks > Filip > > jaya_srini wrote: >> So Sorry! :( >> >> I just thought I would explain our scenario in more details. >> >> >> jaya_srini wrote: >> >>> Hello >>> >>> Apologies for all the questions bu

Re: Question about Producer Consumer usage

So Sorry! :( I just thought I would explain our scenario in more details. jaya_srini wrote: > > Hello > > Apologies for all the questions but I am a newbie to ActiveMQ and I would > really like to better understand how the ActiveMQ broker works and was > wondering if someo

Question about Producer Consumer usage

Hello Apologies for all the questions but I am a newbie to ActiveMQ and I would really like to better understand how the ActiveMQ broker works and was wondering if someone can explain how it would work for the scenario below: I am using single session with 1 producer and 1 consumer (durable Topi

Re: Need Help with blocking Producer!

be sent at a time on the same session. > so if you have multiple threads using the same session, it will send the > requests, one at a time > > you are probably sending messages synchronously, as opposed to async, > which is why you see the blocking threads > > Filip > &g

Re: TransportListener question

async send to be true using the setUseAsyncSend() API? Or will this parameter be ignored if the transport is failover? jaya_srini wrote: > > Well, that's the problem. When we use jms.useAsyncSend in the connection > URI with the failover transpoert we can't even start the JMS

Re: TransportListener question

e to connect successfully but then we lose the features we wanted with failover. The connection URI looks like this failover:(tcp://localhost:61616?jms.useAsyncSend=true&wireFormat.maxInactivityDuration=-1) thanks jaya James.Strachan wrote: > > 2008/5/9 jaya_srini <[EMAIL PROT

Re: TransportListener question

really great for us! jaya James.Strachan wrote: > > 2008/5/9 jaya_srini <[EMAIL PROTECTED]>: >> >> Hi >> >> >> Is TransportListener only meant to be used with Failover Transport? > > Yeah - as if you're not using failover, the JMS conne

TransportListener question

Hi Is TransportListener only meant to be used with Failover Transport? i.e if I use it with tcp transport (without failover) will I be notified if the broker shuts down and comes back up? The reason we can't use failover is because we would also like to use Async Sends which is not possible with

Re: Need Help with blocking Producer!

he element has a bunch of sub element that you can setup > to control other needs > > Filip > > jaya_srini wrote: >> hi >> >> We are using ActiveMQ 5.0 release and observing the following on >> production. >> After a certain number of messages are se

Re: Need Help with blocking Producer!

appreciated! jaya_srini wrote: > > hi > > We are using ActiveMQ 5.0 release and observing the following on > production. After a certain number of messages are sent the Activemq send > blocks. The thread dump produced the following > > daemon prio=6 tid=0x3793f40

Need Help with blocking Producer!

hi We are using ActiveMQ 5.0 release and observing the following on production. After a certain number of messages are sent the Activemq send blocks. The thread dump produced the following daemon prio=6 tid=0x3793f400 nid=0x1f28 waiting for monitor entry [0x38aff000..0x38affc98] java.lang.Th

Re: ActiveMq 5.0.0 and Windows 2003 Server

Thank you! that's what I needed to know. jaya semog wrote: > > Don't know if it is suppoted, but I have run it on that platform > without problems. > > > > On 4/18/08, jaya_srini <[EMAIL PROTECTED]> wrote: >> >> Hello >> >>

ActiveMq 5.0.0 and Windows 2003 Server

Hello Is ActiveMq 5.0.0 release supported on a Windows 2003 server? thanks jaya -- View this message in context: http://www.nabble.com/ActiveMq-5.0.0-and-Windows-2003-Server-tp16764015s2354p16764015.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMq persistence delivery mode

Please ignore. There was a bug in my code. I was publishing multiple messages. Really sorry for the bother. thanks jaya jaya_srini wrote: > > hi > > I am observing the following behaviour with ActiveMq 5.0 release and I was > wondering if someone can tell me if this is ex

ActiveMq persistence delivery mode

hi I am observing the following behaviour with ActiveMq 5.0 release and I was wondering if someone can tell me if this is expected or a bug I have a single broker with one producer and a durable subscriber. All on one machine. I am using a single Topic for publish and subscribe. The session is

Not all consumers receiving the message

Hi I am new to ActiveMQ and I am hoping someone can help me troubleshoot the behaviour I am seeing. I have ActiveMq 5.0 standalone broker running on my machine. One the same machine I also have a Tomcat Service that creates a durable subscriber (say Consumer 1) and is listening for any messages

ActiveMq and Table Creation

Hi I am new to ActiveMq so apologies in advance if this has been posted before. We are using ActiveMq 5.0 . We noticed that it tries to create the ActiveMQ tables on startup even if they already exists. Is there an option to tell the persistence adapter to create it only if it doesn't exist? I