On 2/10/07, MqUser <[EMAIL PROTECTED]> wrote:
If one want to send a message and not move forward (be blocked) until
confirmation arrives that the call completed on the other side, can that be
done with activemq?
By default if you are sending persistent messages, the send() method
will block un
If one want to send a message and not move forward (be blocked) until
confirmation arrives that the call completed on the other side, can that be
done with activemq?
--
View this message in context:
http://www.nabble.com/Are-all-producer-message-calls-Asynchronous--tf3204489s2354.html#a8898440
S
On 2/9/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
I create the publisher first and then the subsciber
You must create the subscriber first to get the messages. For topics
messages are only delivered to the available consumers at the time the
broker receives the message.
For dur
Hi,
I am facing a problem, while jgroups transport scheme is using.
I am getting following error message.
Caught: javax.jms.JMSException: Could not connect to broker URL:
jgroups:default. Reason: java.io.IOException: Transport scheme NOT
recognized: [jgroups]
javax.jms.JMSException: Could not c
Some more info:
- My Producer's delivery mode is PERSISTANT
- I have no consumers who would have taken the messages (and I can see htem
when restarting the Master)
- attached is my config - but its basically just the given example.
spiderman2 wrote:
>
> I've gotten the slave to succesfully wai
I create the publisher first and then the subsciber
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 12:50 PM
To: users@activemq.apache.org
Subject: Re: durable subscriptions not working
Do you create the subscriber first before running
Just as a follow up, setting the failover to false results in an out of
memory error quite quickly if where you are bridging to is not up.
in the log i see
09/02/2007 17:16:58.880 [Thread-23] INFO Establishing network connection
between from vm://pccapp?network=true to tcp://localhost:62001
09/
I've gotten the slave to succesfully wait on the db lock. Then it claims it
when I shut the master down :)
The bad part: I've placed 100 message in the Master's queue before shutdown.
Used Jconsole to verify they're there. When the Slave gets the lock and
becomes broker, Jconsole shows that it ha
Do you create the subscriber first before running the publisher?
On 2/9/07, Suchitha Koneru (sukoneru) <[EMAIL PROTECTED]> wrote:
Hello active mq users ,
I have Java 1.5.09 , Tomcat 5.5 .
I am using the following active mq jars activemq-core-4.0.1.jar ,
backport-util-concurrent-
James.Strachan wrote:
>
> You could always make your own custom RAR.
>
> But really there is meant to be a way of isolating RAR, WAR, EAR class
> loaders to avoid exactly these kinds of problems. It might be worth
> asking on the JBoss forums on how to solve this problem generally as
> I'm sure
Hello active mq users ,
I have Java 1.5.09 , Tomcat 5.5 .
I am using the following active mq jars activemq-core-4.0.1.jar ,
backport-util-concurrent-2.1.jar , geronimo-j2ee-
management_1.0_spec-1.0.jar, geronimo-jms_1.1_spec-1.0.jar ,
incubator-activemq-4.0.2.jar
I have two clas
On 2/9/07, Sandeep Chayapathi <[EMAIL PROTECTED]> wrote:
Hi all,
We too have the same problem. Using the stable AMQ 4.1 & stomp, I can
duplicate this problem.
1. Create a durable subscriber, via stomp protocol
2. Publish messages to the topic
3. stop the subscrber
4. stop the producer
5. start
Yes - so fingers crossed once you've got your classpath sorted it should be fine
On 2/9/07, spiderman2 <[EMAIL PROTECTED]> wrote:
You are right! Thanks! I'm fairly sure this is the problem. I had the
datasource commented out! AH!
Now I am pointing the #oracle-ds as in the example. My only next
You are right! Thanks! I'm fairly sure this is the problem. I had the
datasource commented out! AH!
Now I am pointing the #oracle-ds as in the example. My only next issue is
adding the 'oracle.jdbc.driver.OracleDriver' to my classpath. I didn't
realize this wasn't included in the distrubution and
Hi all,
We too have the same problem. Using the stable AMQ 4.1 & stomp, I can
duplicate this problem.
1. Create a durable subscriber, via stomp protocol
2. Publish messages to the topic
3. stop the subscrber
4. stop the producer
5. start the subscriber, using the same client id and "subcription"
Hi,
I have a basic configuration for a Message Driven POJO in Spring(2.0) with
Jencks(2.0). This setup works fine if there are no exceptions thrown from
MDP. MDP stop receiving any message as soon as an exception is thrown. If I
restart the listner app it starts receiving again. Am I missing anyth
That looks like the problem then :)
If you post the complete XML config you're using we can point out the
mistake. You basically need to refer to the #oracle-ds in your
like the example does...
On 2/9/07, spiderman2 <[EMAIL PROTECTED]> wrote:
I've now tried running the Master and Sl
I've now tried running the Master and Slave on different hosts, as the JDBC
Master-Slave example intends. I see the same thing.
James, it seems you are right in that they don't seem to be using the same
DB. They are both configured to use:
HOWEVER, from the logs I'll
Note that with JDBC Master/Slave you don't network them together -
with JDBC Master/Slave there is no direct master-slave communication.
Nor should they be aware of each other, as the slave does not start
listening on any sockets until it becomes the master (for JDBC
master/slave).
Could you show
19 matches
Mail list logo
