[JBoss JIRA] Created: (JBAS-7628) CombinedVFSCache fills tmp/vfs-nested.tmp for deployments not listed in permanentRoots
by Dietmar Scheidl (JIRA)
CombinedVFSCache fills tmp/vfs-nested.tmp for deployments not listed in permanentRoots
--------------------------------------------------------------------------------------
Key: JBAS-7628
URL: https://jira.jboss.org/jira/browse/JBAS-7628
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.1.0.GA
Reporter: Dietmar Scheidl
Assignee: Ales Justin
Priority: Critical
CombinedVFSCache starts to fill the harddisk with copies of nested libraries from ear-deployment.
This happens only if the location of the deployment is not listed in permanentRoots.
We encounter this behavior by using the jmx-console to deploy the ear-file.
Space is stable for about 30mins. After that any request to the web application (JSF/Richfaces/Seam/EJB3/...) leads to a new copy of all nested libraries into the vfs-nested.tmp folder.
--
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
14 years
[JBoss JIRA] Created: (JBAOP-791) AbstractAopMetaDataDeployer.undeploy() should uninstall the scoped manager bean
by Kabir Khan (JIRA)
AbstractAopMetaDataDeployer.undeploy() should uninstall the scoped manager bean
-------------------------------------------------------------------------------
Key: JBAOP-791
URL: https://jira.jboss.org/jira/browse/JBAOP-791
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.1.Alpha1
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: 2.2.1.GA
When running AS testsuite with jboss-reflect on javassist we get errors like this on shutdown since the beans have not been undeployed and the aop classloader has been removed at this stage
16:25:01,756 WARN [StartStopLifecycleAction] Error during stop for ScopedManager_2_vfs:///Users/kabir/sourcecontrol/jbossas/KABIR_JAVASSIST_REFLECT/subversion/testsuite/output/lib/aop-scopedtest1.sar/aop-scopedtest1.aop/: java.lang.NoClassDefFoundError: Unable to find class org.jboss.aop.domain.ScopedClassLoaderDomain from org.jboss.aop.asintegration.jboss5.ScopedVFSClassLoaderDomain in pool [org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPool@101901517 [class path: ] - dcl:BaseClassLoader@390f34cc{aop-classloader:0.0.0$MODULE} domain: [org.jboss.classpool.plugins.jbosscl.JBossClClassPoolDomain@740ba142 name:DefaultDomain]]
at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactoryImpl.raiseClassNotFound(JavassistTypeInfoFactoryImpl.java:110) [jboss-reflect.jar:2.2.0-SNAPSHOT]
at org.jboss.reflect.plugins.javassist.JavassistTypeInfo.getSuperclass(JavassistTypeInfo.java:236) [jboss-reflect.jar:2.2.0-SNAPSHOT]
at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:398) [jboss-reflect.jar:2.2.0-SNAPSHOT]
at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:366) [jboss-reflect.jar:2.2.0-SNAPSHOT]
at org.jboss.kernel.plugins.config.Configurator.handleMethod(Configurator.java:606) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.config.Configurator.findMethod(Configurator.java:563) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.ungetMethodJoinPoint(AbstractKernelConfigurator.java:153) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.LifecycleAction.uninstallActionInternal(LifecycleAction.java:290) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:175) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.uninstallAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleUninstallAction(SimpleControllerContextAction.java:79) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.uninstall(AccessControllerContextAction.java:131) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:385) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:2078) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1624) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1472) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:756) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:669) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.shutdown(AbstractController.java:270) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.shutdownKernelAndDeployer(AbstractMCServerBase.java:210) [jboss-bootstrap-impl-mc.jar:2.1.0-SNAPSHOT]
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.doShutdown(AbstractMCServerBase.java:168) [jboss-bootstrap-impl-mc.jar:2.1.0-SNAPSHOT]
at org.jboss.bootstrap.impl.base.server.AbstractServer.shutdown(AbstractServer.java:304) [jboss-bootstrap-impl-base.jar:2.1.0-SNAPSHOT]
at org.jboss.Main$ShutdownHook$1.run(Main.java:994) [run.jar:6.0.0-SNAPSHOT (Build SVNTag:JBoss_6.0.0-SNAPSHOT date: 20100513)]
--
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
14 years
[JBoss JIRA] Created: (JBAS-7996) @Startup not working jboss 6.0M2
by Nagin Kothari (JIRA)
@Startup not working jboss 6.0M2
--------------------------------
Key: JBAS-7996
URL: https://jira.jboss.org/jira/browse/JBAS-7996
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Reporter: Nagin Kothari
Assignee: Carlo de Wolf
As per Ejb 3.1 spec when @startup annotation is placed on Singleton bean, then bean @PostConstruct method should be invoked at application start up process and not when client calls its method first time. but in Jboss6.0.0M2 this is not working . @PostConstruct method is not invoked as a part of container start up process, but called at first method call of singleton bean.
--
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
14 years