[EMAIL PROTECTED] wrote:
Ideally, I would like to alert the user when the broker/connection goes
down, and when it comes back up.
Have you tried to test this scenario? I believe you should get some
exception when connection is broken.
--
Oleg
Thanks, that is a helpful link. FWIW, I've managed to sweep my issues
under the carpet for the moment by reducing the stack size of a thread
via ulimit... now my test program can have thousands of threads without
issue.
Timothy Bish wrote:
I think you may want to go read Sun's JMS tutorial
ht
rajdavies wrote:
>
>
> On 17 Feb 2008, at 01:45, Bijou wrote:
>
>>
>> Hello,
>>
>> We are getting the following error message. Could this be a
>> permissions
>> issue? The broker is on a Unix box, in a WebSphere environment. It
>> has been
>> working in the past, so we are not sure what i
Thanks Rob. We have confirmed that the broker is running and there is no
firewall issue. Sometimes we can fix the problem by recycling the JVM, but
eventually we end up with the same error message again:
Could not connect to broker URL: tcp://eagle4c:61616?
> socket.tcpNoDelay=true.
> Reason: ja
I think you may want to go read Sun's JMS tutorial
http://java.sun.com/products/jms/tutorial/
Every session as per the JMS spec has its own thread, but every session
can have multiple consumers listening to different destinations. So
there should be no need to create 300 sessions. Just create
On Feb 19, 2008 10:38 AM, wha <[EMAIL PROTECTED]> wrote:
>
> Well I don't know what to say, it doesn't work for me when I do
> advisorySupport="false"
>
> If you want to try it. Here's my BrokerA activemq.xml
>
> http://activemq.org/config/1.0";
> brokerName="brokerA"
> dataDirect
I don't know if it applies to your problem but you could setup a Camel
routing on the broker so that the 10'000 queues are forwarded into a
few, so that each client would only have to listen to 10 or so queues
(like one per broker).
Mario
On 2/19/08, Ben Chobot <[EMAIL PROTECTED]> wrote:
> Hey ev
Hey everybody. I'm playing around with the CMS client for ActiveMQ 5,
and I'm having some threading issues. It seems that every time I start a
session, I get a new thread to handle that session. Clearly, this won't
scale to lots of sessions, and in fact my OS won't let me create more
than 300 t
thx much.
ragards
yolcuabbas
rajdavies wrote:
>
> failover depends on the InactivityMonitor - but also socket death too
> - which might take a while to percolate through.
>
> cheers,
>
> Rob
> On 19 Feb 2008, at 07:27, yolcuabbas wrote:
>
>>
>> Hi,
>>
>> thanks for prompt reply. We can no
Does anyone have a simple example of how to use the new amq script? I am
looking at using the jquery adapter, but when I try to address the
amq.AddListener function, I am told it does not exits. I have been trying to
"decyper" the chat example, but it is a bit above my head.
I am looking for an
We do rely on advisories being present for networks to function
correctly at present I'm afraid
cheers,
Rob
On 19 Feb 2008, at 17:38, wha wrote:
Well I don't know what to say, it doesn't work for me when I do
advisorySupport="false"
If you want to try it. Here's my BrokerA activemq.xml
h
could you try a 5.1 snapshot release ?
On 19 Feb 2008, at 16:50, Zanderfax wrote:
5.0.0.zip from the downloads page.
rajdavies wrote:
Zanderfax wrote:
I have been trying to download the windows binary zip file from
several
of the mirrors and the backup site. When the download finishe
Well I don't know what to say, it doesn't work for me when I do
advisorySupport="false"
If you want to try it. Here's my BrokerA activemq.xml
http://activemq.org/config/1.0";
brokerName="brokerA"
dataDirectory="${activemq.base}/data"
useJmx="true"
advisorySu
Can someone describe the use case for when you would set the
wireFormat.maxInactivityDuration=0 parameter on the broker transport, e.g.,
versus on the consumer/producer, e.g.,
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("failover:(tcp://brokerhost:61616)?wi
The default setting for advisorySupport is 'true' and I don't think that the
forwarding of messages has any dependencies on advisorySupport.
Joe
www.ttmsolutions.com
wha wrote:
>
>
>
> bsnyder wrote:
>>
>>
>> Disable the all transport connectors (i.e., comment them out) and
>> remove th
5.0.0.zip from the downloads page.
rajdavies wrote:
>
>
>
> Zanderfax wrote:
>>
>> I have been trying to download the windows binary zip file from several
>> of the mirrors and the backup site. When the download finishes, the zip
>> will not open.
>>
>> Is anyone else having this issue?
>>
bsnyder wrote:
>
>
> Disable the all transport connectors (i.e., comment them out) and
> remove the discoverUri from the openwire connectors. I also advise
> running the brokers on the same machine in order to rule out your
> network. In order to do this, you'll need to change the following:
>
I am using activemq-all-5.1-SNAPSHOT.jar and still get this error:
2008-02-19 11:44:25,768 (ActiveMQConnection.java:1453) WARN
org.apache.activemq.ActiveMQConnection - Async exception with no exception
listener: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too lo
JIRA AMQ-1202 was marked as resolved on 5.0.0. But the downloaded src does
not show the changes mentioned by Kevin, i.e. comment out code on onStarted
and onStopped methods. Wonder it is fixed another way or it didn't make it
to 5.0.0? I need to patch it to 4.1.1 for the memory leak, can you poi
I created a BrokerFilter implementation that gathers some data when messages
are passed around. Now that data I want to send to each new consummer added
if the destination matches some criteria. So after calling
super.addConsumer() i want to build a ActiveMQBytesMessage and send it to
that consumm
On 19 Feb 2008, at 10:04, YMC wrote:
Hi Guys,
We're interested in knowing if the brokers from the 4.x and 5.x
families
designed to interoperate?
Cheers,
YMC
--
View this message in context:
http://www.nabble.com/ActiveMQ-4---5-interoperability--tp15560507s2354p15560507.html
Sent from the
Hi Guys,
We're interested in knowing if the brokers from the 4.x and 5.x families
designed to interoperate?
Cheers,
YMC
--
View this message in context:
http://www.nabble.com/ActiveMQ-4---5-interoperability--tp15560507s2354p15560507.html
Sent from the ActiveMQ - User mailing list archive at
failover depends on the InactivityMonitor - but also socket death too
- which might take a while to percolate through.
cheers,
Rob
On 19 Feb 2008, at 07:27, yolcuabbas wrote:
Hi,
thanks for prompt reply. We can not upgrade easyl, because we use
amq 4.1.1
in production :( is it true, tha
23 matches
Mail list logo