[jboss-jira] [JBoss JIRA] Commented: (JBAS-3420) Fix org.jboss.test.timer.test.SecureTimerUnitTestCase in HEAD

[Anil Saldhana (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3420?page=comments#action_12339975 ] 
            
Anil Saldhana commented on JBAS-3420:
-------------------------------------

This seems to be a consistent ejb timer issue in HEAD.  Also when the following test is run:
org.jboss.test.security.test.SecurityProxyUnitTestCase


You should see the following in the log files:
================================================================================
2006-07-24 13:29:27,000 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionInterceptor] start called in CachedConnectionInterceptor 
2006-07-24 13:29:27,000 WARN  [org.jboss.ejb.StatefulSessionContainer] Could not restore ejb timers 
javax.management.RuntimeMBeanException 
        at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) 
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165) 
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) 
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 
.....
Caused by: java.lang.SecurityException: Invalid authentication attempt, principal=null 
        at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubjec
t(BaseConnectionManager2.java:587)
        at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC
onnection(BaseConnectionManager2.java:393)
        at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio
nManagerProxy.allocateConnection(BaseConnectionManager2.java:838)
        at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
        at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.selectTimers(GeneralPurposeDatabasePersistencePlugin.java:207)
==================================================================================

I would like to know if there is any associated timer issues before I look at seeing why there is no security context associated with
the getConnection call.   


> Fix org.jboss.test.timer.test.SecureTimerUnitTestCase in HEAD
> -------------------------------------------------------------
>
>                 Key: JBAS-3420
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3420
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Security, Scheduling/Timers
>            Reporter: Anil Saldhana
>         Assigned To: Carlo de Wolf
>             Fix For: JBossAS-5.0.0.Beta
>
>
> There is some vagaries associated with this test when run as a collection, part of the target "tests-security-basic-unit" against a jboss instance in the all config.
> Here the testcase consistently throws failures/errors.
> Now if this testcase is run standalone as 
> $>ant -Dtest=org.jboss.test.timer.test.SecureTimerUnitTestCase one-test
> The first time there are a couple of errors but when this test is again run, the testcase passes.
> From the log files, I see:
> =====================================================================================================
> (1:31:47 PM) anil_aol: Caused by: java.lang.SecurityException: Invalid authentication attempt, principal=null 
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:587) 
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:393) 
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:838)
>         at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88) 
>         at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.selectTimers(GeneralPurposeDatabasePersistencePlugin.java:207)^M
>         at org.jboss.ejb.txtimer.DatabasePersistencePolicy.listTimerHandles(DatabasePersistencePolicy.java:164) 
> ......
> * Nested Exception (Underlying Cause) ---------------
> java.sql.SQLException: Could not retrieve datasource via JNDI url 'java:DefaultDS' java.lang.SecurityException: Invalid authentication attempt, principal=null
>         at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:166)
>         at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:111)
>         at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:1431)
>         at org.quartz.impl.jdbcjobstore.JobStoreCMT.doRecoverMisfires(JobStoreCMT.java:1335)
>         at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2449)
> =============================================================================================
> Please verify that this is not a Quart integration layer issue.

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