[JBoss JIRA] Created: (JBREM-596) Lease doesn't work if client has two connections opened when using callbacks
5:25 p.m.
Lease doesn't work if client has two connections opened when using callbacks
----------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: callbacks
Reporter: Clebert Suconic
Assigned To: Tom Elrod
If you have two connections, one of them is using CallBack the Lease is just stopped.
I don't know how to reproduce this with a pure JBossRemoting testcase, but there is a
testcase @ JBossMEssaging (Branch_1_0) which reproduces this really easily.
Download JBossMessaging SVN @ Branch_1, and execute ant crash-tests within /testsuite.
You can look at cruisecontrol results at this URL:
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
and
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
I have added a couple of messages on JBossRemoting code and I could see that with the code
bellow, the lease is stopped. During addCallBAck the client copy calls disconnect and the
lease thread never comes back.
Here is the code:
public void testSimplestDurableSubscription() throws Exception
{
ConnectionFactory cf =
(ConnectionFactory)ic.lookup("ConnectionFactory");
Topic topic = (Topic)ic.lookup("/topic/TopicCrash");
Connection conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
Connection conn2 = cf.createConnection();
conn2.setClientID("client2");
conn2.start();
Session s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
Session s2 = conn2.createSession(true, Session.AUTO_ACKNOWLEDGE);
MessageProducer prod = s.createProducer(topic);
prod.setDeliveryMode(DeliveryMode.PERSISTENT);
MessageConsumer durable = s.createDurableSubscriber(topic, "subs1");
MessageConsumer durable2 = s2.createDurableSubscriber(topic, "subs2");
//conn2.close(); -- do not remote this comment. It was meant to not close the
connection
for (int i=0;i<10;i++)
{
prod.send(s.createTextMessage("k"+i));
}
s.commit();
conn.close();
conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
durable = s.createDurableSubscriber(topic, "subs1");
for (int i=0;i<2;i++)
{
TextMessage tm = (TextMessage)durable.receive(1000);
assertNotNull(tm);
s.commit();
System.out.println(tm.getText());
assertEquals("k" + i, tm.getText());
}
//conn.close();-- do not remote this comment. It was meant to not close the
connection
//System.exit(0); -- this is not needed as there is not tearDown, the client VM
will simply be finished the same way an exit would do, and this is better since it will
keep proper JUNIT report outputs
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:37 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-596) Lease doesn't work if client has two connections opened when using callbacks
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Clebert Suconic updated JBREM-596:
----------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970472#...
Lease doesn't work if client has two connections opened when
using callbacks
----------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Reporter: Clebert Suconic
Assigned To: Tom Elrod
If you have two connections, one of them is using CallBack the Lease is just stopped.
I don't know how to reproduce this with a pure JBossRemoting testcase, but there is a
testcase @ JBossMEssaging (Branch_1_0) which reproduces this really easily.
Download JBossMessaging SVN @ Branch_1, and execute ant crash-tests within /testsuite.
You can look at cruisecontrol results at this URL:
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
and
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
I have added a couple of messages on JBossRemoting code and I could see that with the
code bellow, the lease is stopped. During addCallBAck the client copy calls disconnect and
the lease thread never comes back.
Here is the code:
public void testSimplestDurableSubscription() throws Exception
{
ConnectionFactory cf =
(ConnectionFactory)ic.lookup("ConnectionFactory");
Topic topic = (Topic)ic.lookup("/topic/TopicCrash");
Connection conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
Connection conn2 = cf.createConnection();
conn2.setClientID("client2");
conn2.start();
Session s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
Session s2 = conn2.createSession(true, Session.AUTO_ACKNOWLEDGE);
MessageProducer prod = s.createProducer(topic);
prod.setDeliveryMode(DeliveryMode.PERSISTENT);
MessageConsumer durable = s.createDurableSubscriber(topic, "subs1");
MessageConsumer durable2 = s2.createDurableSubscriber(topic, "subs2");
//conn2.close(); -- do not remote this comment. It was meant to not close the
connection
for (int i=0;i<10;i++)
{
prod.send(s.createTextMessage("k"+i));
}
s.commit();
conn.close();
conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
durable = s.createDurableSubscriber(topic, "subs1");
for (int i=0;i<2;i++)
{
TextMessage tm = (TextMessage)durable.receive(1000);
assertNotNull(tm);
s.commit();
System.out.println(tm.getText());
assertEquals("k" + i, tm.getText());
}
//conn.close();-- do not remote this comment. It was meant to not close the
connection
//System.exit(0); -- this is not needed as there is not tearDown, the client VM
will simply be finished the same way an exit would do, and this is better since it will
keep proper JUNIT report outputs
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:45 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-596) Lease doesn't work if client has two connections opened when using callbacks
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Tom Elrod updated JBREM-596:
-----------------------------
Fix Version/s: 2.2.0.Beta1 (Bluto)
Affects Version/s: 2.0.0.GA (Boon)
Lease doesn't work if client has two connections opened when
using callbacks
----------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you have two connections, one of them is using CallBack the Lease is just stopped.
I don't know how to reproduce this with a pure JBossRemoting testcase, but there is a
testcase @ JBossMEssaging (Branch_1_0) which reproduces this really easily.
Download JBossMessaging SVN @ Branch_1, and execute ant crash-tests within /testsuite.
You can look at cruisecontrol results at this URL:
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
and
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
I have added a couple of messages on JBossRemoting code and I could see that with the
code bellow, the lease is stopped. During addCallBAck the client copy calls disconnect and
the lease thread never comes back.
Here is the code:
public void testSimplestDurableSubscription() throws Exception
{
ConnectionFactory cf =
(ConnectionFactory)ic.lookup("ConnectionFactory");
Topic topic = (Topic)ic.lookup("/topic/TopicCrash");
Connection conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
Connection conn2 = cf.createConnection();
conn2.setClientID("client2");
conn2.start();
Session s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
Session s2 = conn2.createSession(true, Session.AUTO_ACKNOWLEDGE);
MessageProducer prod = s.createProducer(topic);
prod.setDeliveryMode(DeliveryMode.PERSISTENT);
MessageConsumer durable = s.createDurableSubscriber(topic, "subs1");
MessageConsumer durable2 = s2.createDurableSubscriber(topic, "subs2");
//conn2.close(); -- do not remote this comment. It was meant to not close the
connection
for (int i=0;i<10;i++)
{
prod.send(s.createTextMessage("k"+i));
}
s.commit();
conn.close();
conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
durable = s.createDurableSubscriber(topic, "subs1");
for (int i=0;i<2;i++)
{
TextMessage tm = (TextMessage)durable.receive(1000);
assertNotNull(tm);
s.commit();
System.out.println(tm.getText());
assertEquals("k" + i, tm.getText());
}
//conn.close();-- do not remote this comment. It was meant to not close the
connection
//System.exit(0); -- this is not needed as there is not tearDown, the client VM
will simply be finished the same way an exit would do, and this is better since it will
keep proper JUNIT report outputs
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Clebert Suconic updated JBREM-596:
----------------------------------
Summary: Lease stops working if the First Client using the same Locator is closed
(was: Lease doesn't work if client has two connections opened when using callbacks)
Description:
If you use always the same locator (say if you need socket pool working), and if you close
the first Client opened, Lease will stop as Lease is associated with the Client and not
with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
was:
If you have two connections, one of them is using CallBack the Lease is just stopped.
I don't know how to reproduce this with a pure JBossRemoting testcase, but there is a
testcase @ JBossMEssaging (Branch_1_0) which reproduces this really easily.
Download JBossMessaging SVN @ Branch_1, and execute ant crash-tests within /testsuite.
You can look at cruisecontrol results at this URL:
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
and
http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220...
I have added a couple of messages on JBossRemoting code and I could see that with the code
bellow, the lease is stopped. During addCallBAck the client copy calls disconnect and the
lease thread never comes back.
Here is the code:
public void testSimplestDurableSubscription() throws Exception
{
ConnectionFactory cf =
(ConnectionFactory)ic.lookup("ConnectionFactory");
Topic topic = (Topic)ic.lookup("/topic/TopicCrash");
Connection conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
Connection conn2 = cf.createConnection();
conn2.setClientID("client2");
conn2.start();
Session s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
Session s2 = conn2.createSession(true, Session.AUTO_ACKNOWLEDGE);
MessageProducer prod = s.createProducer(topic);
prod.setDeliveryMode(DeliveryMode.PERSISTENT);
MessageConsumer durable = s.createDurableSubscriber(topic, "subs1");
MessageConsumer durable2 = s2.createDurableSubscriber(topic, "subs2");
//conn2.close(); -- do not remote this comment. It was meant to not close the
connection
for (int i=0;i<10;i++)
{
prod.send(s.createTextMessage("k"+i));
}
s.commit();
conn.close();
conn = cf.createConnection();
conn.setClientID("client1");
conn.start();
s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);
durable = s.createDurableSubscriber(topic, "subs1");
for (int i=0;i<2;i++)
{
TextMessage tm = (TextMessage)durable.receive(1000);
assertNotNull(tm);
s.commit();
System.out.println(tm.getText());
assertEquals("k" + i, tm.getText());
}
//conn.close();-- do not remote this comment. It was meant to not close the
connection
//System.exit(0); -- this is not needed as there is not tearDown, the client VM
will simply be finished the same way an exit would do, and this is better since it will
keep proper JUNIT report outputs
}
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:52 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343389 ]
Clebert Suconic commented on JBREM-596:
---------------------------------------
We would need this fix on a 2.0.1.GA (or having a snapsho we could use on JMS)
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:52 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343388 ]
Clebert Suconic commented on JBREM-596:
---------------------------------------
I have updated org.jboss.test.remoting.lease.socket.multiple.SocketLeaseTestClient to have
the appropriate testing scenario
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Clebert Suconic updated JBREM-596:
----------------------------------
Comment: was deleted
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343391 ]
Clebert Suconic commented on JBREM-596:
---------------------------------------
We would need this fix on a 2.0.1.GA (or having a snapshot we could use on Messaging)
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343639 ]
Tom Elrod commented on JBREM-596:
----------------------------------
Have updated code so that client invoker is responsible for handling lease management for
all Clients using that client invoker. The org.jboss.test.remoting.lease.socket.multiple
package test case is passing now.
The main benefit for this (other than fixing original bug) is that instead of having a
thread per Client doing lease ping, will only be one thread per client invoker (regardless
of number of Clients using that client invoker).
This change does raise some issues with regards to some of the more obscure behaviors,
which have been listed in forum post -
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972805#...
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343640 ]
Tom Elrod commented on JBREM-596:
----------------------------------
Clebert, can you verify this fix for messaging?
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Tom Elrod updated JBREM-596:
-----------------------------
Priority: Critical (was: Major)
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Priority: Critical
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343671 ]
Clebert Suconic commented on JBREM-596:
---------------------------------------
After updating libraries ClientCrashTwoConnectionsTest is passing without any failures.
So, the fix is perfect for messaging.
We will need a tagged snapshot or a minor release for messaging now.
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Priority: Critical
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:43 p.m.
New subject: [JBoss JIRA] Resolved: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Tom Elrod resolved JBREM-596.
------------------------------
Resolution: Done
Repository binary - http://repository.jboss.com/jboss/remoting/2.2.0.Alpha1/lib/
CVS tag - remoting_2_2_0_Alpha1
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Priority: Critical
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-596) Lease stops working if the First Client using the same Locator is closed
[ http://jira.jboss.com/jira/browse/JBREM-596?page=all ]
Clebert Suconic closed JBREM-596.
---------------------------------
Lease stops working if the First Client using the same Locator is
closed
------------------------------------------------------------------------
Key: JBREM-596
URL: http://jira.jboss.com/jira/browse/JBREM-596
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Clebert Suconic
Assigned To: Tom Elrod
Priority: Critical
Fix For: 2.2.0.Beta1 (Bluto)
If you use always the same locator (say if you need socket pool working), and if you
close the first Client opened, Lease will stop as Lease is associated with the Client and
not with the Invoker (what is wrong IMO)
Lease should be associated with AbstractInvoker, as the property for Lease will determine
an unique ClientInvoker on InvokerRegistry.
Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7246
days inactive
7258
days old
13 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Tom Elrod (JIRA)