December 2007 - jboss-jira - Jboss List Archives

[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

16 years, 10 months

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

16 years, 10 months

2
4
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

16 years, 10 months

2
1
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

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-885) Detect "in-the-same-VM" condition

by David Lloyd (JIRA)

Detect "in-the-same-VM" condition --------------------------------- Key: JBREM-885 URL: http://jira.jboss.com/jira/browse/JBREM-885 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Part of the session creation process should include asking the protocol if the proposed URI is in the same or a different VM. If same, use "local" protocol instead. -- 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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1488) Session Invalidation issue when Tomcat SSO is turned on

by Sohil Shah (JIRA)

Session Invalidation issue when Tomcat SSO is turned on ------------------------------------------------------- Key: JBPORTAL-1488 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1488 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.6.CR2, 2.4.1 SP1 Reporter: Sohil Shah Assigned To: Sohil Shah Priority: Minor Fix For: 2.6 Final, 2.4.2 Final It turns out that when Tomcat SSO is turned on, when a user's session is invalidated, as the portal server iterates through all the active war sessions and invalidates them, the main portal session is invalidated as well. The code calls session.invalidate on the main portal session after that and gets and IllegalStateException because the session is already invalidated. This exception needs to be handled smoothly so that user does not see a failure upon logout Note: This issue surfaces only when Tomcat SSO is actiavted. -- 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

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1730) IdentityServiceControllerImpl : unregister existing MBean service before to re register them

by Antoine Herzog (JIRA)

IdentityServiceControllerImpl : unregister existing MBean service before to re register them -------------------------------------------------------------------------------------------- Key: JBPORTAL-1730 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.1 Final Reporter: Antoine Herzog Priority: Optional Fix For: 2.6.3 Final In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController") the Identity Beans are registered as JMX MBeans. When redeploying the service, an exception is thrown, as the services are yet deployed. javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered. Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java // Unregister the former service is if it is yet there. // This to avoid the exception when redeploying this service if (getServer().isRegistered( new ObjectName(module.getServiceName()))) { getServer().unregisterMBean( new ObjectName(module.getServiceName())); } Thanks, -- 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

16 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1551) Improve file upload sample to show how to correctly build a file upload portlet

by Julien Viet (JIRA)

Improve file upload sample to show how to correctly build a file upload portlet ------------------------------------------------------------------------------- Key: JBPORTAL-1551 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1551 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Julien Viet Fix For: 2.6.2 Final, 2.8 Final Retrieving portlet parameters the correct way is not done (cf CharsetPortlet and CMSPortlet bug JBPORTAL-1550 that was not correctly using them). -- 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

16 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1724) portlet lib for clustering tests

by Prabhat Jha (JIRA)

portlet lib for clustering tests -------------------------------- Key: JBPORTAL-1724 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1724 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet, Portal QA Affects Versions: 2.6.2 Final Reporter: Prabhat Jha Assigned To: Julien Viet Fix For: 2.6.3 Final For clustering tests, from portlet modules, we need portal-portlet-lib.jar portal-portlet-test-framework-lib.jar test-info.war In thirdparty/jboss-portal/portlet, test jars are not available. We need to make this available. I think better place will be to put all test related binaries in test module or build them in portlet module but upload to repository under test module. -- 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

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1477) Custom render modes should be documented

by Andrew Oliver (JIRA)

Custom render modes should be documented ---------------------------------------- Key: JBPORTAL-1477 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1477 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR1, 2.4.1 SP1 Reporter: Andrew Oliver Assigned To: Julien Viet It appears via: The blanket statement of support is based on: http://jira.jboss.com/jira/browse/JBPTL-20 and http://www.jbossworld.com/jbwv_2006/integration_and_presentation/LAPRUN_J... and http://labs.jboss.com/portal/authors/articles/portal/magicbullet/ That custom render modes are supported. However the documentation is completely vague on support just saying the spec allows for custom modes and saying nothing about portals support for them. The doc also does not say HOW to define them. From these 3 I gather: Basically the last url states: "Some vendors define custom portlet modes that your portlets can implement. Support for custom portlet modes is briefly defined in the specification, and is as simple as adding a custom-portlet-mode node to the portlet descriptor and any other vendor-specific modifications to the descriptor or the portlet class." I suspect you define it in the portlet descriptor, the vendor specific descriptor and portal configuration and it should work. However I think the documentation should explicitly state support or non-support (I think it is the former) and in the case of the former demonstrate how (which I think matches the above)... -- 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

16 years, 10 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007