November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ] Ovidiu Feodorov updated JBMESSAGING-287: ---------------------------------------- Fix Version/s: 1.0.2.CR1 (was: 1.2.0.Beta1) > RemotingTest.testConnectionListener() invalid > --------------------------------------------- > > Key: JBMESSAGING-287 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.0.2.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid. > After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove it. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-92) Integrate and enable multiplex transport

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-92?page=all ] Ovidiu Feodorov updated JBMESSAGING-92: --------------------------------------- Fix Version/s: 1.2.0.Beta2 (was: 1.2.0.Beta1) > Integrate and enable multiplex transport > ---------------------------------------- > > Key: JBMESSAGING-92 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-92 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Remoting > Reporter: Ovidiu Feodorov > Assigned To: Ron Sigal > Fix For: 1.2.0.Beta2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Replace "Connector per Consumer" solution with a Remoting UIL2-like transport > The ConsumerInterceptor creates a new Connector instance per each Consumer, and associates maintains a reference to it as transitory metadata, so it can shut it down when the Consumer closes. > The Connector is necessary as a callback server for asynchronous notifications. The MessageCallbackHandler instance is registered to it. Maintaining an instance per Consumer is necessary to avoid port conflicts. > This is a temporary solution until JBoss Remoting gets an UIL2-like transport. > As long as we maintain a server socket per consumer, it won't be possbile to receive asynchronous notifications over firewalls. > until multiplex performance is better it should not be the default tranport but should be available nevertheless -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-264) Provide a mechanism to forward messages from one destination to another automatically

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-264?page=all ] Ovidiu Feodorov updated JBMESSAGING-264: ---------------------------------------- Fix Version/s: 1.2.0.Beta2 (was: 1.2.0.Beta1) > Provide a mechanism to forward messages from one destination to another automatically > ------------------------------------------------------------------------------------- > > Key: JBMESSAGING-264 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-264 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Chris DeLashmutt > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Beta2 > > > I have had requests for this feature many times. Basically, people seem to want to be able to have a component in messaging that will automatically forward messages to another destination. This destination could be in the same messaging server or some remote destination. I'm thinking that the process must either be a daemon or an MDB, and since JBossMsg will also be available standalone I'm thinking we make it an MBean. Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet (to make the pop and the push transactional). -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-127) Delayed delivery, redelivery count and pluggable expiration behavior

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-127?page=all ] Ovidiu Feodorov updated JBMESSAGING-127: ---------------------------------------- Fix Version/s: 1.2.0.Beta2 (was: 1.2.0.Beta1) > Delayed delivery, redelivery count and pluggable expiration behavior > -------------------------------------------------------------------- > > Key: JBMESSAGING-127 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-127 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core, JMS Facade > Reporter: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta2 > > Original Estimate: 1 week, 2 days > Remaining Estimate: 1 week, 2 days > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-127) Delayed delivery, redelivery count and pluggable expiration behavior

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-127?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-127: --------------------------------------------- Partially completed. > Delayed delivery, redelivery count and pluggable expiration behavior > -------------------------------------------------------------------- > > Key: JBMESSAGING-127 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-127 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core, JMS Facade > Reporter: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta1 > > Original Estimate: 1 week, 2 days > Remaining Estimate: 1 week, 2 days > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Ovidiu Feodorov updated JBMESSAGING-407: ---------------------------------------- Priority: Blocker (was: Critical) > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Juha Lindfors > Priority: Blocker > Fix For: 1.0.2.CR1 > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Time Spent: 4 days, 4 hours, 30 minutes > Remaining Estimate: 3 hours, 30 minutes > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-146) String index out of range: -1

by Ryszard Kozmik (JIRA)

String index out of range: -1 ------------------------------ Key: JBFORUMS-146 URL: http://jira.jboss.com/jira/browse/JBFORUMS-146 Project: JBoss Forums Issue Type: Bug Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor Fix For: 1.0.0 Beta Update comment for attachment and Add poll answer cause portlet to hang with String index out of range: -1 error message. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-147) Finish attachments implementation

by Ryszard Kozmik (JIRA)

Finish attachments implementation --------------------------------- Key: JBFORUMS-147 URL: http://jira.jboss.com/jira/browse/JBFORUMS-147 Project: JBoss Forums Issue Type: Sub-task Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta Attachments implementation is not fully functional while creating new post. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-148) Finish polls implementation

by Ryszard Kozmik (JIRA)

Finish polls implementation --------------------------- Key: JBFORUMS-148 URL: http://jira.jboss.com/jira/browse/JBFORUMS-148 Project: JBoss Forums Issue Type: Sub-task Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta Most functionality of Polls is not ready. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBCACHE-344) JBoss Cache IDE Eclipse-Plugin

by Gurkan Erdogdu (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-344?page=all ] Gurkan Erdogdu closed JBCACHE-344. ---------------------------------- Fix Version/s: 1.4.0.GA (was: 2.0.0.GA) Resolution: Done I am closing this jira issue. > JBoss Cache IDE Eclipse-Plugin > ------------------------------ > > Key: JBCACHE-344 > URL: http://jira.jboss.com/jira/browse/JBCACHE-344 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gurkan Erdogdu > Assigned To: Gurkan Erdogdu > Fix For: 1.4.0.GA > > > I have created the JBoss Cache IDE prototype as an Eclipse plugin. We follow discussions about the IDE further from this jira issue. -- 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

19 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006