April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-1794) Remote ConnectionFactory usage

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1794?page=all ] Jesper Pedersen updated JBAS-1794: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Remote ConnectionFactory usage > ------------------------------ > > Key: JBAS-1794 > URL: http://jira.jboss.com/jira/browse/JBAS-1794 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > > This needs doing properly. It should be applicable to any resource adapter > not hardwired into the jdbc rar. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1434) JMS Message Inflow

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1434?page=all ] Jesper Pedersen updated JBAS-1434: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > JMS Message Inflow > ------------------ > > Key: JBAS-1434 > URL: http://jira.jboss.com/jira/browse/JBAS-1434 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.2 Final > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Fix For: JBossAS-4.2.3.GA > > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672 > The JMS message inflow in the JMS resource adapter needs properly testing. > There are basic tests, but the following are missing: > 1) Complete tests of edge cases for each configuration parameter in the activation spec > 2) Failure tests to confirm the implementation handles error gracefully > 3) Stress tests to make sure there the implementation is stable > 4) Performance tests to optimize the implementation > Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 > style deployments and hence as the default configuration. > This should be possible provided the user has not created their own > container configuration that uses the old JMSContainerInvoker explicitly. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3943) JMS/JCA adapter should provide for security domain authentication in addition to JMS client credential

by Weston Price (JIRA)

JMS/JCA adapter should provide for security domain authentication in addition to JMS client credential ------------------------------------------------------------------------------------------------------ Key: JBAS-3943 URL: http://jira.jboss.com/jira/browse/JBAS-3943 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Current the JCA/JMS adapter does not allow for security domain based authentication. There is nothing in the JCA spec or in the JMS spec that would prohibit this type of authentication. -- 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

18 years, 1 month

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1740) Remote Connection does not get closed in case of sloppy client

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1740?page=all ] Jesper Pedersen updated JBAS-1740: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Remote Connection does not get closed in case of sloppy client > -------------------------------------------------------------- > > Key: JBAS-1740 > URL: http://jira.jboss.com/jira/browse/JBAS-1740 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Jesper Pedersen > Priority: Minor > Fix For: JBossAS-5.1.0.CR1 > > > If the Client that gets a remote Connection (WrapperDataSourceService) does not close it properly (sloppy or crash), it will never be released again. > This can be solved rather easily, the finalize method of the Server part of the proxy should call close. > Thus if the client object gets garbage collected (or the JVM dies), the server object (proxy) will be garbage collected and the finalize method called. > This thing is that a sloppy or crashing client can occupy all available connections, leaving all other applications with no connection to work with. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4200) Last Resource Gambit for non XA MDB

by Weston Price (JIRA)

Last Resource Gambit for non XA MDB ----------------------------------- Key: JBAS-4200 URL: http://jira.jboss.com/jira/browse/JBAS-4200 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Currently non XA MDB's do not support the LRG but rely on the local JMS API for redelivery support. It should be considered if we should provide this. -- 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

18 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4001) JMS/JCA inflow adapter needs to be backported from head to 4.2 and 4.0.5 CP releases

by Weston Price (JIRA)

JMS/JCA inflow adapter needs to be backported from head to 4.2 and 4.0.5 CP releases ------------------------------------------------------------------------------------ Key: JBAS-4001 URL: http://jira.jboss.com/jira/browse/JBAS-4001 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 Reporter: Weston Price Assigned To: Weston Price The JCA/JMS inflow adapter changes in HEAD need to be backported to 4.x releases. Changes made affect transaction processing that will resolve transaction problems for redelivery for BMT and CMT Not support MDB's. -- 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

18 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4010) XATerminator interrface of TxManager is not including error codes in XAExceptions thrown

by Adrian Brock (JIRA)

XATerminator interrface of TxManager is not including error codes in XAExceptions thrown ---------------------------------------------------------------------------------------- Key: JBAS-4010 URL: http://jira.jboss.com/jira/browse/JBAS-4010 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Assigned To: Weston Price Attachments: XAException.diff According to the javadoc for XATerminator, it should include an error code in the XAException thrown: e.g. see http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/XATerminator.htm... This is similar to the fix for the JBossXALocalException done in JBAS-2807 However, our XATerminator impl in TxManager is not including the error code in the thrown XAException. I'm attaching a diff that shows how to fix this for prepare(), i.e. add XA_RBROLLBACK but this also needs doing for the other methods commit/forget/rollback and tests creating to prevent regression. -- 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

18 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4381) Change the JMS resource adapter to better re-use resources internally

by Adrian Brock (JIRA)

Change the JMS resource adapter to better re-use resources internally --------------------------------------------------------------------- Key: JBAS-4381 URL: http://jira.jboss.com/jira/browse/JBAS-4381 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Currently in the JMS resource adapter it always creates a connection for each session. This is mainly because it implements the pooling at the session level, but some of the pooling parameters are specified on the connection, i.e. user/password/client id. Ideally, the pooled sessions should be able to share the same connection if they have the same parameters at the connection level. -- 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

18 years, 1 month

3
3
0 / 0

[JBoss JIRA] Updated: (JBAS-1433) Message Inflow targetting MBeans/POJOs

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1433?page=all ] Jesper Pedersen updated JBAS-1433: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > Message Inflow targetting MBeans/POJOs > -------------------------------------- > > Key: JBAS-1433 > URL: http://jira.jboss.com/jira/browse/JBAS-1433 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48674 > The JCA message inflow could target MBeans or POJOs rather than EJBs. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1485) JMS ResourceAdapter makes unnecessary temporary delete requests

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1485?page=all ] Jesper Pedersen updated JBAS-1485: ---------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > JMS ResourceAdapter makes unnecessary temporary delete requests > --------------------------------------------------------------- > > Key: JBAS-1485 > URL: http://jira.jboss.com/jira/browse/JBAS-1485 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Priority: Optional > Fix For: JBossAS-5.0.1.CR1 > > > The JMS ResourceAdaptor keeps track of temporaries created on a connection > (org.jboss.resource.adapter.jms.JMSSessionFactoryImpl) > and deletes them. > This is because we cannot expect the real JMS implementation to do this > because the connection is pooled and not closed. > However, if the user is deleting the temporaries themselves > (good practice in terms of resource usage), > the JMS ResourceAdapter does not know about this > and tries to repeat the delete at connection.close(); > Solution: > Add some wrapping processing for the temporary queues and topics > so we can trap temporary.delete(). That way we will know we don't > need to do it on close() > IMPORTANT: Invocations like send() or JMSMessage.setJMSReplyTo will > also need to trap these destinations to do the necessary wrapping/unwrapping. > It is also possible to retrieve a temporary destination with Session.createQueue/Topic. -- 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

18 years, 1 month

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 April 2008