November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-96) Improve AuthorizationContext error reporting

by Anil Saldhana (JIRA)

Improve AuthorizationContext error reporting -------------------------------------------- Key: SECURITY-96 URL: http://jira.jboss.com/jira/browse/SECURITY-96 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA AuthorizationException needs to provide additional details such as any runtime exceptions experienced. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-490) Advisor.resolveAnnotation() and hasAnnotation() should check the MetaData in all cases

by Kabir Khan (JIRA)

Advisor.resolveAnnotation() and hasAnnotation() should check the MetaData in all cases -------------------------------------------------------------------------------------- Key: JBAOP-490 URL: http://jira.jboss.com/jira/browse/JBAOP-490 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR1 Done for all the methods that take java.lang.reflect, I don't think this is necessary for the CtClass, CtMethod, CtField, CtConstructor flavours yet, since they are called at weaving time using a temp class advisor -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1165) Fix remoting configuration under ServiceContainer

by Clebert Suconic (JIRA)

Fix remoting configuration under ServiceContainer ------------------------------------------------- Key: JBMESSAGING-1165 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1165 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.0.SP1, 1.4.0.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.4.0.SP2 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5000) org.jboss.test.jca.test.PSCacheUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.jca.test.PSCacheUnitTestCase ------------------------------------------- Key: JBAS-5000 URL: http://jira.jboss.com/jira/browse/JBAS-5000 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5004) Mbeans declared in a DataSource descriptor should be started before the DataSource

by Marcus Moyses (JIRA)

Mbeans declared in a DataSource descriptor should be started before the DataSource ---------------------------------------------------------------------------------- Key: JBAS-5004 URL: http://jira.jboss.com/jira/browse/JBAS-5004 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Marcus Moyses Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.3.GA A mbean declared inside a datasource descriptor should be started before the datasource and the datasource recorded as dependent on the mbean. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-485) Better toString method on the EJB proxy

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-485?page=all ] Carlo de Wolf updated EJBTHREE-485: ----------------------------------- Fix Version/s: HEAD (was: AS 5.0.0.Beta3) > Better toString method on the EJB proxy > --------------------------------------- > > Key: EJBTHREE-485 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-485 > Project: EJB 3.0 > Issue Type: Feature Request > Environment: n/a > Reporter: Andrew > Assigned To: Carlo de Wolf > Priority: Minor > Fix For: HEAD > > Time Spent: 2 hours > > The EJB instance toString method returns "$Proxy###" instead of a class name. It would be nice to know what interface the proxy implements. So if I have a "MySessionBean" with interface "MySession", it would be nice to know when printing the object that the object implements MySession. > This is especially relavent when using JBoss Seam. When there are annotation problems and the EJB interface, it prints out the cryptic proxy name that does not let the developer determine which been has the problem. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1007) BMTInterceptor refers to wrong spec

by Carlo de Wolf (JIRA)

BMTInterceptor refers to wrong spec ----------------------------------- Key: EJBTHREE-1007 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1007 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Minor Fix For: EJB 3.0 RC11 - FD 11:52:15,234 ERROR [BMTInterceptor] Application error: BMT stateless bean TesterBean should complete transactions before returning (ejb1.1 spec, 11.6.1) -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1349) NotNode and ExistsImprovements

by Mark Proctor (JIRA)

NotNode and ExistsImprovements ------------------------------ Key: JBRULES-1349 URL: http://jira.jboss.com/jira/browse/JBRULES-1349 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.4, 4.1.0 -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1071) Possible problem in concurrent signalling from multiple threads

by Jiri Pechanec (JIRA)

Possible problem in concurrent signalling from multiple threads --------------------------------------------------------------- Key: JBPM-1071 URL: http://jira.jboss.com/jira/browse/JBPM-1071 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux MySQL 5.0.22 Reporter: Jiri Pechanec Assigned To: Tom Baeyens Priority: Critical Attachments: expl.tar.gz Attached is a simple test case that 1) Deploys process definition with two nodes 2) Starts the process instance that will go to the wait state on first node 3) Starts 20 threads that tries concurrently signal the same process instance 4) The second node writes a record to the database The test case needs to be executed multiple times to see the incorrect behaviour. This is an example of run output Isol 8 Action 1 Action 2 Action 2 Action 2 Action 2 Action 2 1 Action 2 1 Action 2 1 Action 2 1 Signalist 5 Signalist 6 Signalist 8 Signalist 12 Signalist 7 Signalist 13 Signalist 14 Signalist 15 Signalist 9 Signalist 16 Signalist 17 Signalist 18 Signalist 4 Success 7 Failure 13 Explanation of the outcome 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created) 3 threads successfully executed the signal operation but no real action was performed 13 threads attempted to execute the signal operation but ended with an exception -- 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, 5 months

6
24
0 / 0

[JBoss JIRA] Created: (JBAS-4293) Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation

by Vladimir Piskarev (JIRA)

Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4293 URL: http://jira.jboss.com/jira/browse/JBAS-4293 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Vladimir Piskarev Assigned To: Scott M Stark According to 18.3.9 of EJB 2.1 spec "the container should not throw the java.rmi.RemoteException or javax.ejb.EJBException if the container performs a transaction rollback because the instance has invoked the setRollbackOnly method on its EJBContext object. In this case, the container must rollback the transaction and pass the business method result or the application exception thrown by the business method to the client.". Also 17.6.2.8 says "If the container initiated the transaction immediately before dispatching the business method to the instance (as opposed to the transaction being inherited from the caller), the container must note that the instance has invoked the setRollbackOnly method. When the business method invocation completes, the container must roll back rather than commit the transaction. If the business method has returned normally or with an application exception, the container must pass the method result or the application exception to the client after the container performed the rollback.". However, if exception-on-rollback is true, JBoss EJB Container throws the TransactionRolledbackException when the transaction should be rolled back because of the setRollbackOnly invocation. This clearly violates the EJB spec requirements mentioned above. It seems that the TxInterceptorCMT.checkTransactionStatus method should not throw the exception when the transaction status is STATUS_MARKED_ROLLBACK. -- 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, 5 months

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