You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "bill richard (JIRA)" <ji...@apache.org> on 2008/01/04 06:12:44 UTC
[jira] Created: (AMQ-1536) Dural-subScriber can not receive
message!
Dural-subScriber can not receive message!
-----------------------------------------
Key: AMQ-1536
URL: https://issues.apache.org/activemq/browse/AMQ-1536
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.0.0
Reporter: bill richard
Fix For: 5.1.0
situation like this:
TopicSession session = null;
TopicConnection connection = null;
try {
ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("", "", "tcp://10.61.0.200:61616?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false&wireFormat.maxInactivityDuration=0");
connection = connectionFactory.createTopicConnection("","");
connection.setClientID("xxxxxxxxxxxxxx");
connection.start();
session = connection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
Topic userReceiver = session.createTopic("test_unsubscribe_topic");
TopicSubscriber ts=session.createDurableSubscriber(userReceiver,"sub_123");
ts.setMessageListener(new MessageListener(){
public void onMessage(Message msg){
System.out.prinltn("Receie:"+msg+" Date:"+new Date());
);
Thread.sleep(about 2 hours);
then send one message to topic test_unsubscribe_topic
made a connection with argument maxInactivityDuration=0 , then made a dural-subscribe to a topic use that connection,if there is no message on this topic for a long time,then when one message was send to that topic,the subscriber will not got the message.
If you shut down your subscriber program ,then restart it ,it reports a "already connected exception".
Also i changed AMQ 5.0 source code according to issue 1525,
Maybe this is because the socket the subscriber use is in half-open state.
hope these helps!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1536) Dural-subScriber can not receive
message!
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1536:
-------------------------------
Assignee: Rob Davies
> Dural-subScriber can not receive message!
> -----------------------------------------
>
> Key: AMQ-1536
> URL: https://issues.apache.org/activemq/browse/AMQ-1536
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: bill richard
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> situation like this:
> TopicSession session = null;
> TopicConnection connection = null;
> try {
> ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("", "", "tcp://10.61.0.200:61616?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false&wireFormat.maxInactivityDuration=0");
> connection = connectionFactory.createTopicConnection("","");
> connection.setClientID("xxxxxxxxxxxxxx");
> connection.start();
> session = connection.createTopicSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
> Topic userReceiver = session.createTopic("test_unsubscribe_topic");
> TopicSubscriber ts=session.createDurableSubscriber(userReceiver,"sub_123");
> ts.setMessageListener(new MessageListener(){
> public void onMessage(Message msg){
> System.out.prinltn("Receie:"+msg+" Date:"+new Date());
> );
> Thread.sleep(about 2 hours);
> then send one message to topic test_unsubscribe_topic
>
> made a connection with argument maxInactivityDuration=0 , then made a dural-subscribe to a topic use that connection,if there is no message on this topic for a long time,then when one message was send to that topic,the subscriber will not got the message.
> If you shut down your subscriber program ,then restart it ,it reports a "already connected exception".
> Also i changed AMQ 5.0 source code according to issue 1525,
> Maybe this is because the socket the subscriber use is in half-open state.
> hope these helps!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1536) Dural-subScriber can not receive
message!
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1536.
-----------------------------
Resolution: Fixed
use failover:// url (now the default)
> Dural-subScriber can not receive message!
> -----------------------------------------
>
> Key: AMQ-1536
> URL: https://issues.apache.org/activemq/browse/AMQ-1536
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: bill richard
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> situation like this:
> TopicSession session = null;
> TopicConnection connection = null;
> try {
> ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("", "", "tcp://10.61.0.200:61616?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false&wireFormat.maxInactivityDuration=0");
> connection = connectionFactory.createTopicConnection("","");
> connection.setClientID("xxxxxxxxxxxxxx");
> connection.start();
> session = connection.createTopicSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
> Topic userReceiver = session.createTopic("test_unsubscribe_topic");
> TopicSubscriber ts=session.createDurableSubscriber(userReceiver,"sub_123");
> ts.setMessageListener(new MessageListener(){
> public void onMessage(Message msg){
> System.out.prinltn("Receie:"+msg+" Date:"+new Date());
> );
> Thread.sleep(about 2 hours);
> then send one message to topic test_unsubscribe_topic
>
> made a connection with argument maxInactivityDuration=0 , then made a dural-subscribe to a topic use that connection,if there is no message on this topic for a long time,then when one message was send to that topic,the subscriber will not got the message.
> If you shut down your subscriber program ,then restart it ,it reports a "already connected exception".
> Also i changed AMQ 5.0 source code according to issue 1525,
> Maybe this is because the socket the subscriber use is in half-open state.
> hope these helps!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.