[EJB3] - Quartz bean fails at deployment on JBoss 5.1
by sven.loe
sven.loe [http://community.jboss.org/people/sven.loe] created the discussion
"Quartz bean fails at deployment on JBoss 5.1"
To view the discussion, visit: http://community.jboss.org/message/641906#641906
--------------------------------------------------------------
Hello,
I am trying to deploy a app on JBoss 5.1 Final. It has 2 MDBs that need to be called by quartz according to crontab. At deployment time I get the following error message:
08:34:10,809 INFO [EJBContainer] STARTED EJB: ch.mobi.evn.business.application.AttestationEventsTimerBean ejbName: AttestationEventsTimerBean
08:34:10,872 ERROR [TimerImpl] Error invoking ejbTimeout
javax.ejb.EJBException: No method has been annotated with @Timeout
at org.jboss.ejb3.mdb.MessagingContainer.callTimeout(MessagingContainer.java:304)
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerBridge.callTimeout(TimedObjectInvokerBridge.java:44)
at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
08:34:10,872 ERROR [TimerImpl] Error invoking ejbTimeout
javax.ejb.EJBException: No method has been annotated with @Timeout
at org.jboss.ejb3.mdb.MessagingContainer.callTimeout(MessagingContainer.java:304)
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerBridge.callTimeout(TimedObjectInvokerBridge.java:44)
at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
08:34:10,872 ERROR [TimerImpl] Error invoking ejbTimeout
javax.ejb.EJBException: No method has been annotated with @Timeout
at org.jboss.ejb3.mdb.MessagingContainer.callTimeout(MessagingContainer.java:304)
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerBridge.callTimeout(TimedObjectInvokerBridge.java:44)
at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
The source of the Bean looks like that:
@MessageDriven(activationConfig =
{@ActivationConfigProperty(propertyName = "cronTrigger", propertyValue = "0 5 * ? * MON-FRI *")})
@ResourceAdapter("quartz-ra.rar")
public class AttestationEventsTimerBean implements Job {
private static final Logger logger = Logger.getLogger(AttestationEventsTimerBean.class);
@Override
public void execute(JobExecutionContext jobExecutionContext) throws JobExecutionException {
SimpleDateFormat formatter = new SimpleDateFormat("HH:mm:ss");
logger.info("Process attestations: "+formatter.format(new Date()));
try {
this.attestationService.processLocalAttestations();
}
catch (AttestationException e) {
logger.error("AttestationTimeout failed.", e);
}
}
private AttestationService attestationService;
@EJB
public void setAttesationService(AttestationService attestationService) {
this.attestationService = attestationService;
}
}
It is done like in the examples in the JBoss docs. If I delete the @ResourceAdapter annotation I get an exception that MDB the messagetype is unknown. An MDB has no @Timeout annotations so what is going on here? Has somebody an idea?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/641906#641906]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[Beginner's Corner] - Configuring IdentityLoginModule in JBoss AS
by Greg Allen
Greg Allen [http://community.jboss.org/people/oeuftete] created the discussion
"Configuring IdentityLoginModule in JBoss AS"
To view the discussion, visit: http://community.jboss.org/message/642357#642357
--------------------------------------------------------------
I have a web application that I am trying to access in JBoss using the IdentityLoginModule. It seems like it should be straightforward, but I am having problems.
I have added the following <application-policy> in login-config.xml:
<application-policy name="demo">
<authentication>
<login-module code="org.jboss.security.auth.spi.IdentityLoginModule"
flag="required">
<module-option name="principal">bfranklin</module-option>
<module-option name="roles">user</module-option>
</login-module>
</authentication>
</application-policy>
>From my understanding, any successful login with this policy should result in the user being logged in as the user "bfranklin".
Now I log into my application as "mtwain". I would have expected the actual login to be "bfranklin" when the application main page loads, but it ends up being "mtwain". The application retrieves the logged in user via GetRemoteUser and displays it on that page. And it displays "mtwain".
I have confirmed that the getIdentity method is in fact returning "bfranklin".
Am I missing something here? Is there somethine else that needs to be configured?
Thanks,
-- Greg
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/642357#642357]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
[jBPM] - Deadlocks in the JBPM4_EXECUTION
by sacrm2011
sacrm2011 [http://community.jboss.org/people/sacrm2011] created the discussion
"Deadlocks in the JBPM4_EXECUTION"
To view the discussion, visit: http://community.jboss.org/message/642318#642318
--------------------------------------------------------------
Hello
I'm having some problems with jBPM4.4.
My application is currently running on a 3-node cluster using an oracle database 11.2.0.2.0 and am using JBPM 4.4 as an orchestrator of the flow of navigation of the application.
At the beginning my application had some problems with competition but not as severe as today, since the load has been increase significantly.
I'm getting a lot of error messages in my logs:
"2011-12-15 11:00:26,933 ERROR [org.hibernate.util.JDBCExceptionReporter] - ORA-00060: deadlock detected while waiting for resource
2011-12-15 11:00:26,934 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] - Could not synchronize database state with session
org.hibernate.exception.LockAcquisitionException: could not delete: [org.jbpm.pvm.internal.model.ExecutionImpl#20376624]
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:110)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2569)
at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2725)
at org.hibernate.action.EntityDeleteAction.execute(EntityDeleteAction.java:97)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:172)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at org.jbpm.pvm.internal.tx.HibernateSessionResource.prepare(HibernateSessionResource.java:56)
at org.jbpm.pvm.internal.tx.StandardTransaction.commit(StandardTransaction.java:107)
at org.jbpm.pvm.internal.tx.StandardTransaction.complete(StandardTransaction.java:64)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:57)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:56)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.signalExecutionById(ExecutionServiceImpl.java:89)
(...) "
Looking in database logs found several sql statements/threads that I suspect are causing the deadlocks:
Query 1:
"delete from where JBPM4_EXECUTION DBID_ =: = 1 and DBVERSION_: 2;"
Query 2:
"update JBPM4_EXECUTION set
DBVERSION_=:1, ACTIVITYNAME_=:2, PROCDEFID_=:3, HASVARS_=:4, NAME_=:5, KEY_=:6, ID_=:7, STATE_=:8, SUSPHISTSTATE_=:9,
PRIORITY_=:10, HISACTINST_=:11, PARENT_=:12, INSTANCE_=:13, SUPEREXEC_=:14, SUBPROCINST_=:15
where DBID_=:16 and DBVERSION_=:17; "
Is this a concurrencial problem/limitation of jbpm or something else?
Any help would be greatly appreciated!
Best regards
Afonso T.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/642318#642318]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months