July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5453) Make DeleteWorkDirOnContextDestroy=true the default setting

by Mike Millson (JIRA)

Make DeleteWorkDirOnContextDestroy=true the default setting ----------------------------------------------------------- Key: JBAS-5453 URL: http://jira.jboss.com/jira/browse/JBAS-5453 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Mike Millson Assigned To: Remy Maucherat JBAS-3358 added the DeleteWorkDirOnContextDestroy property to handle use cases that require the work directory not be deleted on context destroy. This includes cases where it is desired to persist session data between restarts/redeploys and cases where customers do not precompile JSPs and no not want previously compiled JSPs to be recompiled after a restart/redeploy. However, this default setting is causing issues with enterprise users deploying applications that have gone through long quality assurance and user acceptance testing cycles. JSP files will at times necessarily be created earlier than the compilation time of JSPs from older versions of the application that are running in production. Also, sometimes it is necessary to roll back an older version of an application in an emergency. The current default setting causes stale JSPs to be served. Also, enterprise uders often run a clustered configuration, where the concept of saving the session locally in the work directory likely does not apply. Precompiling JSPs is ultimately the best solution; however, many users are still not doing this. My guess is there are more users relying on stale JSPs not being served than session persistence across restarts. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4769) TransactionLocal cannot be locked when transaction is marked rollback only

by Dimitris Andreadis (JIRA)

TransactionLocal cannot be locked when transaction is marked rollback only -------------------------------------------------------------------------- Key: JBAS-4769 URL: http://jira.jboss.com/jira/browse/JBAS-4769 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager Reporter: Dimitris Andreadis Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3 Apply JBAS-4675 fix to trunk. -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1439) Add SystemProperties substitution inside annotations ( ActivationConfigProperty MDB for instance)

by olivier merlin (JIRA)

Add SystemProperties substitution inside annotations ( ActivationConfigProperty MDB for instance) ------------------------------------------------------------------------------------------------- Key: EJBTHREE-1439 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1439 Project: EJB 3.0 Issue Type: Feature Request Components: injection Affects Versions: AS 5.0.0.Beta4 Environment: Linux Redhat 4 Update 4 Reporter: olivier merlin Priority: Minor In deployement descriptor, when you use the system properties tokens ${token}, the tokens are resolved at the deployement level. In order to get rid off deployment descriptor and proceed only with anotations in code, it would be nice to have the same functionality. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1440) JCA MDB annotations behavior on swiftMQ not coherent with deployment descriptor behavior

by olivier merlin (JIRA)

JCA MDB annotations behavior on swiftMQ not coherent with deployment descriptor behavior ----------------------------------------------------------------------------------------- Key: EJBTHREE-1440 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1440 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 5.0.0.CR1 Environment: Redhat 4 Update 4 (Nathan) Reporter: olivier merlin Priority: Minor The JCA MDB with swiftMQ works fine with annotations. As soon as i switch with deployment descriptor it doen not work although the "generated" ActivationConfigProperties are the same than the code with annotations. There is so no equivalence between DD and annotations which can be problematic. I describe with a lot of details the problem in a forum (see above) -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-314) Remove InstanceAnnotation

by Kabir Khan (JIRA)

Remove InstanceAnnotation ------------------------- Key: JBMICROCONT-314 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-314 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMC.2.0.0.CR1 AOP proxy is more clever now -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMDR-27) Remove InstanceAnnotation

by Kabir Khan (JIRA)

Remove InstanceAnnotation ------------------------- Key: JBMDR-27 URL: https://jira.jboss.org/jira/browse/JBMDR-27 Project: JBoss MetaData Repository Issue Type: Feature Request Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMDR-2.0.0.CR1 No longer used, aop proxy factory is more intelligent now -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5200) Error starting web service (stateless EJB) on startup (but hot deploy works fine)

by Scott Dickerson (JIRA)

Error starting web service (stateless EJB) on startup (but hot deploy works fine) --------------------------------------------------------------------------------- Key: JBAS-5200 URL: http://jira.jboss.com/jira/browse/JBAS-5200 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta3 Environment: windows xp; jboss-5.0.0Beta3 Reporter: Scott Dickerson Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta4 Attachments: server.log Starting jboss with the iam-sample.jar in the deploy folder I get the following exception, but if I completely remove the web service and deploy it once jboss is running, the web service is deployed and responds to client properly. I've attached the service and boot logs for both situations. 2008-02-01 11:28:50,034 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: com.mckesson.onestaff.iam.sample.service.GreeterBean ejbName: Greeter 2008-02-01 11:28:50,253 DEBUG [org.jboss.ejb.txtimer.EJBTimerServiceImpl] createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@1ea6afc 2008-02-01 11:28:50,300 DEBUG [org.jboss.ejb.txtimer.EJBTimerServiceImpl] removeTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@1ea6afc 2008-02-01 11:28:50,300 INFO [org.jboss.ejb3.EJBContainer] STOPPED EJB: com.mckesson.onestaff.iam.sample.service.GreeterBean ejbName: Greeter 2008-02-01 11:28:50,300 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=iam-sample.jar,name=Greeter,service=EJB3 state=Create java.lang.NullPointerException at org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:452) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node

by Brian Stansberry (JIRA)

Use InvocationContext to avoid multiple searches for a node ----------------------------------------------------------- Key: JBCACHE-811 URL: http://jira.jboss.com/jira/browse/JBCACHE-811 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani When an interceptor finds a node, why not throw it in the InvocationContext or something similar and pass it through the stack that way? Subsequent calls to find the node can check the context first before walking the cache tree. Saves redundant walking of the tree. We'd need to think very carefully about this, as it exposes 2 paths to access a node -- from a thread's context and from the tree. Need to ensure concurrent threads always access the same node object for a given Fqn. (Side thought -- perhaps disable this for weak isolation levels where the locking behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn). -- 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, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (JBAS-5714) Leaked heuristic outcome in XAExceptionUnitTestCase

by Adrian Brock (JIRA)

Leaked heuristic outcome in XAExceptionUnitTestCase --------------------------------------------------- Key: JBAS-5714 URL: http://jira.jboss.com/jira/browse/JBAS-5714 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR2 XAExceptionUnitTestCase is leaking a heuristic record into the transaction manager's log because TestManagedConnection is deliberately throwing an XAException but not setting the errorCode. It should be set to XA_RBROLLBACK -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1436) Integrate jboss-metadata (removed "determine" logic from Object Model) with EJB3 Core

by Andrew Lee Rubinger (JIRA)

Integrate jboss-metadata (removed "determine" logic from Object Model) with EJB3 Core ------------------------------------------------------------------------------------- Key: EJBTHREE-1436 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1436 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Critical Current SNAPSHOT of jboss-metadata (targeted for 1.0.0.Beta29) must be integrated w/ EJB3 Core before EJB3 Proxy may be brought in. -- 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, 2 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008