August 2006 - jboss-jira - Jboss List Archives

[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.Alpha1 (was: 1.0.2) Assignee: Ron Sigal (was: Tim Fox) Priority: Critical (was: Blocker) > 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 > Priority: Critical > Fix For: 1.2.0.Alpha1 > > 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-207) HTTP invoker configuration and testing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-207?page=all ] Ovidiu Feodorov updated JBMESSAGING-207: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.2) Assignee: Ron Sigal (was: Ovidiu Feodorov) Priority: Critical (was: Blocker) > HTTP invoker configuration and testing > -------------------------------------- > > Key: JBMESSAGING-207 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-207 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Assigned To: Ron Sigal > Priority: Critical > Fix For: 1.2.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Provide a HTTP invoker initial configuration and a working example. > Add the example to docs/examples so it can be used as an integration test. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3115) Extend ValidConnectionChecker semantics to include non JDBC based resources

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3115?page=all ] Weston Price resolved JBAS-3115. -------------------------------- Fix Version/s: JBossAS-4.0.5.CR1 Resolution: Done Covered by background validation and validating connection factory implementation. > Extend ValidConnectionChecker semantics to include non JDBC based resources > --------------------------------------------------------------------------- > > Key: JBAS-3115 > URL: http://jira.jboss.com/jira/browse/JBAS-3115 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Weston Price > Assigned To: Weston Price > Priority: Optional > Fix For: JBossAS-4.0.5.CR1 > > > The valid connection checker implementation should be extended to include non JDBC based resources. This will require DTD changes to allow for this, but I think it is worth doing. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-459) Get rid of derelict SVN branches and tags

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-459?page=all ] Ovidiu Feodorov deleted JBMESSAGING-459: ---------------------------------------- > Get rid of derelict SVN branches and tags > ----------------------------------------- > > Key: JBMESSAGING-459 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-459 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > > There are a lot of unused branches and tags in the new SVN repository. These are migration artifacts and must be removed. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-459) Get rid of derelict branches and tags

by Ovidiu Feodorov (JIRA)

Get rid of derelict branches and tags ------------------------------------- Key: JBMESSAGING-459 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-459 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov There are a lot of unused branches and tags in the new SVN repository. These are migration artifacts and must be removed. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Reopened: (JBPM-325) task priority not set properly

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-325?page=all ] Ronald van Kuijk reopened JBPM-325: ----------------------------------- According to http://www.jboss.org/index.html?module=bb&op=viewtopic&t=68317 this bug is not fixed if persistency is involved. Should be checked > task priority not set properly > ------------------------------ > > Key: JBPM-325 > URL: http://jira.jboss.com/jira/browse/JBPM-325 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3452) Problem indicated by IllegalStateException: createBeanClassInstanceCommand == null

by Lamon Gray (JIRA)

Problem indicated by IllegalStateException: createBeanClassInstanceCommand == null ---------------------------------------------------------------------------------- Key: JBAS-3452 URL: http://jira.jboss.com/jira/browse/JBAS-3452 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Reporter: Lamon Gray We have encountered a problem indicated by IllegalStateException: createBeanClassInstanceCommand == null. this seems to be solved by a patch associated to the jira entry JBAS-3341. JBAS-3341 indicates that the patch is applied to v 4.0.5 CR1. We are running 4.0.4 GA. We would like this patch applied to 4.0.4 GA. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-456) Migrate jboss-head/jms subdirectory content to standalone SVN repository

by Ovidiu Feodorov (JIRA)

Migrate jboss-head/jms subdirectory content to standalone SVN repository ------------------------------------------------------------------------ Key: JBMESSAGING-456 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-456 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha1 Transfer the CVS jboss-head/jms subdirectory content into a standalone SVN repository, making sure no history is lost. Need to coordinate with the IT on that. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-457) Modify the build system to use jbossbuild

by Ovidiu Feodorov (JIRA)

Modify the build system to use jbossbuild ----------------------------------------- Key: JBMESSAGING-457 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-457 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha1 -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-2225) FCI.getTargets() should be Immutable

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2225?page=all ] Brian Stansberry resolved JBAS-2225. ------------------------------------ Resolution: Done ImmutableArrayList now uses delegation to the original array list, and added a writeReplace() impl that returns the original list, so what gets serialized is unchanged from before. > FCI.getTargets() should be Immutable > ------------------------------------ > > Key: JBAS-2225 > URL: http://jira.jboss.com/jira/browse/JBAS-2225 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.5.CR1 > > > The targets returned from the FamilyClusterInfoImpl.getTargets() should not be modified, > otherwise you can cause ConcurrentModificationException. > To better trap people introducing errors in this area, make a subclass of ArrayList > called ImmutableArrayList and return an implementation of this class from getTargets. -- 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

17 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006