October 2009 - jboss-jira - Jboss List Archives

[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

2
2
0 / 0

[JBoss JIRA] Created: (JBMETA-212) rar annotation processing

by Jeff Zhang (JIRA)

rar annotation processing ------------------------- Key: JBMETA-212 URL: https://jira.jboss.org/jira/browse/JBMETA-212 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.2.Beta1 Reporter: Jeff Zhang Assignee: Jeff Zhang handle jca 1.6 annotation -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2247) Add support to monitoring through JMX

by Edson Tirelli (JIRA)

Add support to monitoring through JMX ------------------------------------- Key: JBRULES-2247 URL: https://jira.jboss.org/jira/browse/JBRULES-2247 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 Add JMX support to enable monitoring of existing instances. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6378) Fix Remoting documentation in AS5 Administration And Configuration Guide

by Ron Sigal (JIRA)

Fix Remoting documentation in AS5 Administration And Configuration Guide ------------------------------------------------------------------------ Key: JBAS-6378 URL: https://jira.jboss.org/jira/browse/JBAS-6378 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Ron Sigal Priority: Minor Fix For: JBossAS-5.1.0.Beta1 Section 11.1. "Summary of JBoss Remoting Features" is somewhat out of date, and Section 11.2. "JBoss Remoting Configuration in the JBoss Application Server" is wrong. It's still unclear whether Remoting 3 will be ready for AS 5.1.0. If not, then I would be happy to fix the doc, if I knew where it is. If Remoting 3 ships in time, then I'm sure someone from Remoting can supply the appropriate information. -- 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

3
13
0 / 0

[JBoss JIRA] Updated: (JBRULES-135) Group Rules in outline view

by Guilhem DELEBECQUE (JIRA)

[ https://jira.jboss.org/jira/browse/JBRULES-135?page=com.atlassian.jira.pl... ] Guilhem DELEBECQUE updated JBRULES-135: --------------------------------------- Attachment: JRULES-135.patch Thanks for trying this patch > Group Rules in outline view > --------------------------- > > Key: JBRULES-135 > URL: https://jira.jboss.org/jira/browse/JBRULES-135 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-eclipse > Reporter: Mark Proctor > Assignee: Kris Verlaenen > Fix For: FUTURE > > Attachments: Group By.jpg, Initial View.jpg, JRULES-135.patch, Only Showed.jpg, SortBy.jpg > > > When rules are placed into AgendaGroups we should show this in a tree. default agenda group is MAIN. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-446) bean-deployer xsds don't contain web references

by Wolfgang Knauf (JIRA)

bean-deployer xsds don't contain web references ----------------------------------------------- Key: JBMICROCONT-446 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-446 Project: JBoss Microcontainer Issue Type: Bug Reporter: Wolfgang Knauf bean-deployer_2_0.xsd: <xsd:redefine schemaLocation="jboss-beans-common_2_0.xsd"> =>should point. <xsd:redefine schemaLocation="http://www.jboss.org/j2ee/schema/jboss-beans-common_2_0.xsd"> The comment for a sample instance should also contain a schema location attribute: <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:bean-deployer:2.0" xsi:schemaLocation="urn:jboss:bean-deployer:2.0 http://www.jboss.org/j2ee/schema/bean-deployer_2_0.xsd"> ================== bean-deployer_1_0.xsd: The comment for a sample instance should point to the web schema location: <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:bean-deployer http://www.jboss.org/j2ee/schema/bean-deployer_1_0.xsd" xmlns="urn:jboss:bean-deployer"> ================= policy_1_0.xsd: <xsd:import namespace="urn:jboss:bean-deployer:2.0"/> should be: <xsd:import namespace="urn:jboss:bean-deployer:2.0" schemaLocation="http://www.jboss.org/j2ee/schema/bean-deployer_1_0.xsd"/> ================= bean-deployer_2_0.xsd raises validation errors in Eclipse: -rcase-RecurseLax.2: There is not a complete functional mapping between the particles. -src-redefine.6.2.2: Group 'valueGroup' does not properly restrict the group it redefines; constraint violated: 'rcase-RecurseLax.2'. According to the forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4187426), this might also be a bug of the validator, but I don't have enough xsd knowledge to create a Xerces bugreport. -- 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

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-7325) Set reportLevel to low

by Jesper Pedersen (JIRA)

Set reportLevel to low ---------------------- Key: JBAS-7325 URL: https://jira.jboss.org/jira/browse/JBAS-7325 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Shelly McGowan Set the reportLevel attribute to "low" such that all warnings are reported. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2287) Add Drag/Drop File support in audit View

by Guilhem DELEBECQUE (JIRA)

Add Drag/Drop File support in audit View ---------------------------------------- Key: JBRULES-2287 URL: https://jira.jboss.org/jira/browse/JBRULES-2287 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.0.1.FINAL Environment: Eclipse Plugin Reporter: Guilhem DELEBECQUE Assignee: Mark Proctor Priority: Minor In eclipse, the audit view force to select the log file with a Dialog Box. Could we add Drop file support on the Audit view in order to load the file if present in the workspace -- 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

2
2
0 / 0

[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

1
1
0 / 0

[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

1
0
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 October 2009