November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-167) Update installation instructions to fix getRollbackOnly functionality

by Kevin Conner (JIRA)

Update installation instructions to fix getRollbackOnly functionality --------------------------------------------------------------------- Key: JBTM-167 URL: http://jira.jboss.com/jira/browse/JBTM-167 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.2 Reporter: Kevin Conner Assigned To: Kevin Conner Update installation instructions and jars to provide a patch for JBAS-3847. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-140) The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout.

by Kevin Conner (JIRA)

The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout. ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-140 URL: http://jira.jboss.com/jira/browse/JBTM-140 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-98) Adding padding support to Xid for Oracle OCI driver

by Mark Little (JIRA)

Adding padding support to Xid for Oracle OCI driver --------------------------------------------------- Key: JBTM-98 URL: http://jira.jboss.com/jira/browse/JBTM-98 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 Plus add it to qualification drivers for DTF. -- 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back

by Kevin Conner (JIRA)

Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back -------------------------------------------------------------------------------------------------- Key: JBAS-3847 URL: http://jira.jboss.com/jira/browse/JBAS-3847 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Kevin Conner The current implementation of EJBContext.getRollbackOnly will return true if the current transaction context has status Status.STATUS_MARKED_ROLLBACK. If using JBossTS, a transaction timeout results in the transaction being rolled back asynchronously (not just marked for rollback). Code using the getRollbackOnly method as an indicator of the current transaction status will not function as expected. The transaction status undergoes the following transition Status.STATUS_ACTIVE -> Status.STATUS_ROLLING_BACK -> Status.STATUS_ROLLEDBACK. Extending getRollbackOnly to check for Status.STATUS_MARKED_ROLLBACK, Status.STATUS_ROLLING_BACK and Status.STATUS_ROLLEDBACK will allow this code to function as expected. This was opened via salesforce https://na1.salesforce.com/50030000002X6dw. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1138) Delete page feature for dashboard configurator

by Roy Russo (JIRA)

Delete page feature for dashboard configurator ---------------------------------------------- Key: JBPORTAL-1138 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1138 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-874) Use performant order collections in TransactionEntry

by Brian Stansberry (JIRA)

Use performant order collections in TransactionEntry ---------------------------------------------------- Key: JBCACHE-874 URL: http://jira.jboss.com/jira/browse/JBCACHE-874 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 1.4.1.GA, 2.0.0.ALPHA2 If multiple locks are associated with a TransactionEntry, it's highly non-performant, since for each addition the class does a contains() check on a LinkedList. We should replace the LinkedList fields with LinkedHashSet. With that, the contains test can be removed all together, as a 2nd add of the same object to a LinkedHashSet has no impact on the collection ordering. See forum post for profiling info on the current impl. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-977) 403 error when logging in as admin with LDAP

by Kevin Barfield (JIRA)

403 error when logging in as admin with LDAP -------------------------------------------- Key: JBPORTAL-977 URL: http://jira.jboss.com/jira/browse/JBPORTAL-977 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Environment: Portal 2.4 CR3 bundled Reporter: Kevin Barfield Fix For: 2.4 Final A 403 error is shown when logging in as admin using LDAP. Open a new browser, and now you are logged in. Same issue with logout. Logging in as a regular user is fine. Here is the login config: <policy>  <application-policy name="cms"> <authentication> <login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required"/> </authentication> </application-policy> <application-policy name="portal"> <authentication> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial"> com.sun.jndi.ldap.LdapCtxFactory </module-option> <module-option name="java.naming.provider.url"> ldap://localhost/ </module-option> <module-option name="java.naming.security.authentication"> simple </module-option> <module-option name="java.naming.security.principal"> cn=Manager,dc=example,dc=com </module-option> <module-option name="java.naming.security.credentials"> secret </module-option> <module-option name="principalDNPrefix">cn=</module-option> <module-option name="principalDNSuffix"> ,ou=people,dc=example,dc=com </module-option> <module-option name="password-stacking">useFirstPass</module-option> <module-option name="rolesCtxDN"> ou=groups,dc=example,dc=com </module-option> <module-option name="uidAttributeID">member</module-option> <module-option name="matchOnUserDN">true</module-option> <module-option name="roleAttributeID">cn</module-option> <module-option name="roleAttributeIsDN">false </module-option>  </login-module> </authentication> </application-policy> </policy> -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-365) RpcDispatcher without registered membership listener is causing BLOCK timeout

by Vladimir Blagojevic (JIRA)

RpcDispatcher without registered membership listener is causing BLOCK timeout ----------------------------------------------------------------------------- Key: JGRP-365 URL: http://jira.jboss.com/jira/browse/JGRP-365 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic If RpcDispatcher is used *and* membership listener used to construct RpcDispatcher is null then BLOCK event will always timeout whenever FLUSH protocol is in stack. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-309) Upgrade log4j from 1.2.8 to 1.2.13

by Bela Ban (JIRA)

Upgrade log4j from 1.2.8 to 1.2.13 ---------------------------------- Key: JGRP-309 URL: http://jira.jboss.com/jira/browse/JGRP-309 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Need some testing -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-308) Upgrade commons-logging from 1.0.3 to 1.1.0

by Bela Ban (JIRA)

Upgrade commons-logging from 1.0.3 to 1.1.0 ------------------------------------------- Key: JGRP-308 URL: http://jira.jboss.com/jira/browse/JGRP-308 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Needs some testing -- 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, 7 months

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