Using security inflow according to chapter 16 "Security Inflow" of the spec Java™ EE Connector Architecture Specification Version 1.6 we get the exception error message:

javax.resource.spi.work.WorkCompletedException: IJ000252: SecurityContext setup failed since CallbackSecurity was null

We noticed, that allways when an new work instance of the resource adapter is started, the callbackSecurity seems to be null, even when this work instance dosn't use security settings at all.

In the JBoss logging we found:

2013-07-18 12:37:47,457 TRACE [org.jboss.jca.core.workmanager.WorkWrapper] (default-threads - 4) Cancel work: WorkWrapper@3052ab[workManger=org.jboss.as.connector.services.workmanager.NamedWorkManager@1093bde[id=default name=default specCompliant=true shortRunningExecutor=org.jboss.as.threads.ManagedQueueExecutorService@1398f3a longRunningExecutor=org.jboss.as.threads.ManagedQueueExecutorService@1ea5ab4 xaTerminator=org.jboss.jca.core.tx.jbossts.XATerminatorImpl@e8e481 validatedWork=[net.fsc.jca.beanconnect.in.comm.ConnectionWorkWithCtx, net.fsc.jca.beanconnect.in.comm.ActivationWorkWithCtx, net.fsc.jca.beanconnect.in.comm.ListenerWorkWithCtx] callbackSecurity=null

Is there any configuration missing for setting up this callbackSecurity ?