Hi Ivan,
You can't do that. It'd be against the EJB specifications. See below:
5.4.14 Message Acknowledgment for JMS Message-Driven Beans
JMS message-driven beans should not attempt to use the JMS API for message
acknowledgment. Message
acknowledgment is automatically handled by the container.
Hi Lou,
My two cents on this. The activemq team possibly chose http/ftp over raw tcp
sockets to get around
1. firewall/proxy setups that may be possible between an ActiveMQ broker and
the file server. Using pre-defined ports can allow you to control the traffic.
2. A higher level protocol like
You will need to start the connection for receiving messages. After setting
up your receiver, call connection.start();
consumer = session.createConsumer(destination);
connection.start();
Message message1 = consumer.receive(1000);
Read the jms api/a good book.
I believe activemq is supposed to be
The code below is the problem in your Consumer class...
consumer.setMessageListener(this);
Message message1 = consumer.receive(1000);
With jms, you can receive messages synchronously (using the receive methods)
or asynchronously (using the MessageListener, w
I believe that's the pub-sub behavior. A message on a topic should be sent to
all registered subscribers. If you need the message to be processed only
once, your should use queues instead.
Regards
Sachin
-Original Message-
From: Manish1985 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July
Hi Kalana,
Check for a code/configuration that sets the client id, either on the
ActiveMQConnectionFactory or on an ActiveMQConnection. The client id should
be unique among the connected clients (as per the JMS Spec).
I believe the issue at the AMQ site was related to InvalidClientIdException,
This bug is supposed to have been fixed in SUN VM 1.5.0_12.
http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=ee6ec97669ab91923bde6c
d8c041?bug_id=6460501
Would we still expect the ActiveMQ5.0 + Sun JDK 1.5.0_12 memory leak?
-Original Message-
From: ttmdev [mailto:[EMAIL PROTECTED]
