[JBoss JIRA] Created: (JBAS-4598) TimerHandle failed to retrieve timer after JBoss restart
by Linoux Linoux (JIRA)
TimerHandle failed to retrieve timer after JBoss restart
--------------------------------------------------------
Key: JBAS-4598
URL: http://jira.jboss.com/jira/browse/JBAS-4598
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows XP / PostgreSQL
Reporter: Linoux Linoux
Creating a timer, store the associated TimerHandle in DB.
Restart JBoss server, try to get the Timer using the stored TimerHandle : javax.ejb.NoSuchObjectLocalException is thrown.
----------------------------------------------------------
//In a Stateless Session :
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void createTimer() throws OgpException {
TimerService ts = ctx.getTimerService();
Timer newTimer = ts.createTimer(getTimerStartDate(), DateUtil.MILLIS_IN_DAY, testAge);
conf.setTestCleanTimerHandle(newTimer.getHandle());
// Store conf in DB
}
private Timer getCurrentTimer(DbConfiguration conf) throws OgpException {
if (conf.getTestCleanTimerHandle() == null)
return null;
try {
return conf.getTestCleanTimerHandle().getTimer();
} catch (NoSuchObjectLocalException e) {
log.warn("Can't retrieve timer : it could be caused by the application redeployment", e);
return null;
}
}
----------------------------------------------------------
Using this code, call to getCurrentTimer after calling createTimer works fine, but after a JBoss restart, call to getCurrentTimer ends with a NoSuchObjectLocalException :
javax.ejb.NoSuchObjectLocalException: Timer not available: [target=jboss.j2ee:service=EJB3,ear=ogp-app.ear,jar=ogp-ejb.jar,name=AdminCleanDbSessionBean]
at org.jboss.ejb.txtimer.TimerHandleImpl.getTimer(TimerHandleImpl.java:203)
at com.sts.ogp.ejb.admin.AdminCleanDbSessionBean.getCurrentTimer(AdminCleanDbSessionBean.java:157)
[...]
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-7324) javax.ejb.EJBAccessException does not contain information about what roles are required anymore
by Marco Schulze (JIRA)
javax.ejb.EJBAccessException does not contain information about what roles are required anymore
-----------------------------------------------------------------------------------------------
Key: JBAS-7324
URL: https://jira.jboss.org/jira/browse/JBAS-7324
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.3.GA
Reporter: Marco Schulze
Assignee: Carlo de Wolf
The SecurityException thrown when accessing EJB2 beans without sufficient permissions contained the information what roles exactly were required. The exception message contained sth. like this: "requiredRoles=[org.nightlabs.jfire.store.seeProductType], principalRoles=[_Guest_]"
This was an easily parseable text and we used it to show the user a nice error message with detailed information about what rights he should request from his boss or his administrator.
Unfortunately, after we switched to EJB3, the now thrown EJBAccessException does not contain this information anymore. It simply says "Authorization failure" without any details.
Please extend org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor to pass the required information (in a parseable form in the exception message).
Reference to our issue (with a stack trace and maybe other useful information): https://www.jfire.org/modules/bugs/view.php?id=1292
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 7 months
[JBoss JIRA] Reopened: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA
by Dimitris Andreadis (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ]
Dimitris Andreadis reopened JBAS-6722:
--------------------------------------
re-open and re-resolve just to see if it goes away from the open issue list in jira!!!
> Hot deployment broken with JBoss 5.0.1.GA
> -----------------------------------------
>
> Key: JBAS-6722
> URL: https://jira.jboss.org/jira/browse/JBAS-6722
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Component
> Environment: JBoss 5.0.1 GA
> JDK 5 update 16
> Seam trunk
> Reporter: Jozef Hartinger
> Assignee: Ales Justin
> Priority: Critical
> Fix For: JBossAS-5.2.0.Beta1
>
>
> Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but:
> a) deployment of XHTML template
> modified facelet templates are not being picked up
> b) deployment of action Java Bean
> I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component.
> All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 7 months