November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (RELOADED-8) Create a JSR-250 compliant injection framework on top of VDF

by Carlo de Wolf (JIRA)

Create a JSR-250 compliant injection framework on top of VDF ------------------------------------------------------------ Key: RELOADED-8 URL: https://jira.jboss.org/jira/browse/RELOADED-8 Project: JBoss Reloaded Issue Type: Feature Request Components: injection Affects Versions: injection-0.1.0 Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

12 years

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-7882) Wrong provider code base for security provider included in packed ear

by Petr H (JIRA)

Wrong provider code base for security provider included in packed ear --------------------------------------------------------------------- Key: JBAS-7882 URL: https://jira.jboss.org/jira/browse/JBAS-7882 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: JBossAS-6.0.0.M2, JBossAS-5.1.0.GA Environment: Any OS, JDK 5 and 6, JBoss AS 5.1.0 and 6.0.0.M2 Reporter: Petr H We've got applications which uses the IAIK JCE provider (http://jce.iaik.tugraz.at/sic/Products/Core-Crypto-Toolkits/JCA-JCE) whose library is included directly in our application. On JBoss AS 5 and later, we can't use this provider as usually. The new VFS mechanism seems to break the path determination to the IAIK provider library (needed to determine provider code base) - it still points into the ear/war structure inside the server deploy directory but as all this is packed into one ear file, the provider verification.fails because of unsigned ear/war and thus the following exception is thrown: 2010-04-01 15:04:20,890 ERROR [STDERR] (http-0.0.0.0-8180-1) java.lang.SecurityException: JCE cannot authenticate the provider IAIK 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.Cipher.getInstance(DashoA13*..) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.Cipher.getInstance(DashoA13*..) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at iaik.test.ControllerServlet.service(ControllerServlet.java:123) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:905) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:592) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2036) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at java.lang.Thread.run(Thread.java:619) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) Caused by: java.util.jar.JarException: Cannot parse jar:file:/opt/jboss-5.1.0.GA/server/test1/deploy/IAIKTest.ear!/IAIKTestWeb.war 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_c.a(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_b.b(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_b.a(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) ... 24 more This works when one of tho three mentioned workarounds is used. The most interesting of course is the third workaround for which the code base corectly points to the temporary IAIK library instance in the java.io.tmpdir: 2010-04-01 15:09:51,291 INFO [STDOUT] (http-0.0.0.0-8180-1) Provider code base: file:/tmp/nestedjar2481829661547119990.tmp I'll attach a simple testcase ear (IAIKTest.ear) which contains an evaluation version of IAIK provider library (thanks for permission to the IAIK authors) and a simple servlet (including source) which demonstrates the problem. All you need to do is to have the unrestricted JCE policy files installed in your JRE and then just put the IAIKTest.ear into the deploy directory, start the JBoss instance and access the test servlet URL in browser, for example: http://localhost:8080/IAIKTestWeb/ControllerServlet On init (which happens on start) it will register the IAIK provider On service (after you access it in browser) it will attempt to get some cipher instance and here it fails. I'll also attach two log files covering the problem: - server-default.log with default server setup where the issue occurs - server-forceVfsJar.log with jboss.vfs.forceVfsJar=true where the issue doesn't occur Also I think this is more generic problem because we had similar issues, where some jar or resource location was pointing to the packed ear/war structure inside the deploy directory instead of those VFS temporary locations, with our own code (when attemting to obtain full path) and had to perform some modifications in order to make it working. The same set of workarounds could resolve these issues as well. -- 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

12 years

17
51
0 / 0

[JBoss JIRA] Created: (JASSIST-126) create OSGi bundle information

by Mark Struberg (JIRA)

create OSGi bundle information ------------------------------ Key: JASSIST-126 URL: https://jira.jboss.org/browse/JASSIST-126 Project: Javassist Issue Type: Feature Request Affects Versions: 3.12.0.GA Reporter: Mark Struberg Assignee: Shigeru Chiba Fix For: 3.13.0.GA Create OSGi bundle information for javassist at build time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
9
0 / 0

[JBoss JIRA] Created: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

by Flavia Rainone (JIRA)

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(). The correct is to create the advisor by calling AspectManager.instance(WovenClass.class).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2033) EjbReferenceResolver can't resolve service bean references

by Carlo de Wolf (JIRA)

EjbReferenceResolver can't resolve service bean references ---------------------------------------------------------- Key: EJBTHREE-2033 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2033 Project: EJB 3.0 Issue Type: Bug Components: common Affects Versions: 1.1.22 Reporter: Carlo de Wolf Assignee: Carlo de Wolf org.jboss.ejb3.common.resolvers.spi.UnresolvableReferenceException: Could not resolve reference [EJB Reference: beanInterface 'org.jboss.ejb3.test.interceptors2.StatusRemote', beanName '', mappedName 'null'] in AbstractVFSDeploymentContext@790495753{file:///home/carlo/work/ejb3/testsuite/target/test-lib/interceptors2-test.jar} at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.resolveEjb(ScopedEJBReferenceResolver.java:88) -- 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

12 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8318) Deployment fails for a war containing CXF jar with error: mapped-name is required for cxf.

by Pierre Demyan (JIRA)

Deployment fails for a war containing CXF jar with error: mapped-name is required for cxf. ------------------------------------------------------------------------------------------ Key: JBAS-8318 URL: https://jira.jboss.org/browse/JBAS-8318 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.M4 Environment: OS: Windows XP SP2 JDK: 1.6.0_18 JBoss configuration: all CXF version: 2.2.9 Reporter: Pierre Demyan Assignee: Remy Maucherat The following exception is thrown when including cxf-2.2.9.jar in a war: 11:13:31,769 ERROR [StandardContext] Context [/test] startup failed due to previous errors: java.lang.RuntimeException: mapped-name is required for cxf of deployment test.war at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXmlResourceEnvRefs(WebResourceHandler.java:288) [:6.0.0.20100721-M4] at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXml(WebResourceHandler.java:326) [:6.0.0.201007 21-M4] at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:593) [:6. 0.0.20100721-M4] at org.jboss.web.tomcat.service.WebCtxLoader.start(WebCtxLoader.java:157) [:6.0.0.20100721-M4] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3737) [:6.0.0.20100721-M4] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) [:6. 0.0.20100721-M4] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145) [:6.0.0.2010 0721-M4] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) [:6.0.0.20100721-M4] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:116) [:6.0.0.20100721-M4] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.20100721-M4] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_18] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_18] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_18] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_18] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.Alpha10] at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installActio n(StartStopLifecycleAction.java:53) [:2.2.0.Alpha10] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2. 2.0.Alpha10] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContext Action.java:62) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java: 71) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:5 1) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dep endency.jar:2.2.0.Alpha10] at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.A lpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2 .2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependenc y.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.system.ServiceController.doChange(ServiceController.java:671) [:6.0.0.20100721-M4 (Build SVNTag:JBo ss_6.0.0.20100721-M4 date: 20100723)] at org.jboss.system.ServiceController.start(ServiceController.java:443) [:6.0.0.20100721-M4 (Build SVNTag:JBoss_ 6.0.0.20100721-M4 date: 20100723)] at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:189) [:6.0.0.20100721-M4] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:102) [:6.0.0.20100721-M4] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:49) [:6.0.0.20100721-M4] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer .java:62) [:2.2.0.Alpha6] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Al pha6] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alp ha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.Alp ha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha6] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dep endency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2 .2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependenc y.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha6] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6. 0.0.20100721-M4] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContex t.java:130) [:0.1.0.Alpha1] at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:148) [:0.1.0.Alpha1] at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [: 0.1.0.Alpha1] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-ker nel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-ker nel.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContext Action.java:62) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java: 71) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:5 1) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dep endency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2 .2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependenc y.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependen cy.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2 .0.Alpha10] at org.jboss.profileservice.dependency.ProfileServiceController.activate(ProfileServiceController.java:188) [:0. 1.0.Alpha1] at org.jboss.profileservice.AbstractProfileService.activateProfile(AbstractProfileService.java:170) [:0.1.0.Alph a1] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.j ava:117) [:0.1.0.Alpha1] at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java :89) [:0.1.0.Alpha1] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java :97) [:0.1.0.Alpha1] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootst rap.java:130) [:6.0.0.20100721-M4] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootst rap.java:56) [:6.0.0.20100721-M4] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap -impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-boots trap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:619) [:1.6.0_18] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-8384) Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error.

by Ken Britton (JIRA)

Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error. --------------------------------------------------------------------------------------------------------------------- Key: JBAS-8384 URL: https://jira.jboss.org/browse/JBAS-8384 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M4 Environment: Mac OS 10.6.4, Java6 Reporter: Ken Britton If a @Stateful session bean has an injected @Stateless session bean it cannot be passivated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-8198) DomainController discovery system

by Brian Stansberry (JIRA)

DomainController discovery system --------------------------------- Key: JBAS-8198 URL: https://jira.jboss.org/browse/JBAS-8198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Mechanism(s) by which a ServerManager finds a DomainController so it can begin the process of integrating into the domain. Task includes the host.xml schema elements to configure this, the domain object model classes behind those elements, and the actual implementation of discovery from both the ServerManager and DomainController sides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

7
14
0 / 0

[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

Ability to rollback AS version updates -------------------------------------- Key: JBAS-8139 URL: https://jira.jboss.org/browse/JBAS-8139 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> A fixpack installer that handles version rollbacks would be fantastic. >> Of course it needs to remain flexible to work with JBoss installs that >> have been manually modified. Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8635) MailResourceAdapter mail check triggered only once

by Martin Clauss (JIRA)

MailResourceAdapter mail check triggered only once -------------------------------------------------- Key: JBAS-8635 URL: https://jira.jboss.org/browse/JBAS-8635 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: 6.0.0.M5 Environment: Win7, JBoss 6.0.0.M5, Java 1.6.0_21 Ubuntu lucid, JBoss 6.0.0.M5, Java 1.6.0_18 Reporter: Martin Clauss Assignee: Jesper Pedersen Mail check is performed correctly only once (after first timeout of pollingInterval) and then never again... 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss.ejb:service=EJBTimerService; Required: Described 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and supplies: 18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jndi:null 18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Class:org.jboss.resource.adapter.mail.inflow.MailListener 18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3) to KernelDeployment of: CTAEJB3.jar 18:43:13,741 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: com.contactulater.ba.MailBean ejbName: MailBean ****snip**** 18:44:13,749 INFO [STDOUT] DEBUG: JavaMail version 1.4.2 18:44:13,760 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.providers 18:44:13,761 INFO [STDOUT] DEBUG: Tables of loaded providers 18:44:13,761 INFO [STDOUT] DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider ***snip*** 18:44:13,763 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map 18:44:13,771 INFO [STDOUT] DEBUG: setDebug: JavaMail version 1.4.2 18:44:13,771 INFO [STDOUT] DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc] 18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.fetchsize: 16384 18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.statuscachetimeout: 1000 18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.appendbuffersize: -1 18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.minidletime: 10 18:44:13,774 INFO [STDOUT] DEBUG: trying to connect to host "127.0.0.1", port 143, isSSL false 18:44:13,799 INFO [STDOUT] * OK **** Cyrus IMAP4 v2.2.13-Debian-2.2.13-19 server ready 18:44:13,800 INFO [STDOUT] A0 CAPABILITY 18:44:13,820 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS 18:44:13,821 INFO [STDOUT] A0 OK Completed 18:44:13,821 INFO [STDOUT] DEBUG: protocolConnect login, host=127.0.0.1, user=jbossra, password=<non-null> 18:44:13,844 INFO [STDOUT] A1 OK User logged in 18:44:13,845 INFO [STDOUT] A2 CAPABILITY 18:44:13,868 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE LOGINDISABLED 18:44:13,869 INFO [STDOUT] A2 OK Completed 18:44:13,870 INFO [STDOUT] A3 LIST "" INBOX 18:44:13,889 INFO [STDOUT] * LIST (\HasChildren) "." "INBOX" 18:44:13,890 INFO [STDOUT] A3 OK Completed (0.000 secs 4 calls) 18:44:13,891 INFO [STDOUT] DEBUG: connection available -- size: 1 18:44:13,891 INFO [STDOUT] A4 SELECT INBOX 18:44:13,973 INFO [STDOUT] * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) 18:44:13,973 INFO [STDOUT] * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] 18:44:13,973 INFO [STDOUT] * 2 EXISTS 18:44:13,974 INFO [STDOUT] * 0 RECENT 18:44:13,974 INFO [STDOUT] * OK [UIDVALIDITY 1288029487] 18:44:13,974 INFO [STDOUT] * OK [UIDNEXT 4] 18:44:13,974 INFO [STDOUT] A4 OK [READ-WRITE] Completed 18:44:13,974 INFO [STDOUT] A5 SEARCH UNSEEN ALL 18:44:13,993 INFO [STDOUT] * SEARCH 18:44:13,993 INFO [STDOUT] A5 OK Completed (0 msgs in 0.000 secs) 18:44:13,993 INFO [STDOUT] A6 CLOSE 18:44:14,138 INFO [STDOUT] A6 OK Completed 18:44:14,138 INFO [STDOUT] DEBUG: added an Authenticated connection -- size: 1 18:44:14,138 INFO [STDOUT] IMAP DEBUG: IMAPProtocol noop 18:44:14,138 INFO [STDOUT] A7 NOOP 18:44:14,156 INFO [STDOUT] A7 OK Completed 18:44:14,156 INFO [STDOUT] A8 LOGOUT 18:44:14,175 INFO [STDOUT] * BYE LOGOUT received 18:44:14,175 INFO [STDOUT] A8 OK Completed 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore connection dead 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup, force false 18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup done MDB implementation: @MessageDriven(activationConfig={ @ActivationConfigProperty(propertyName="mailServer", propertyValue="127.0.0.1"), @ActivationConfigProperty(propertyName="mailFolder", propertyValue="INBOX"), @ActivationConfigProperty(propertyName="storeProtocol", propertyValue="imap"), @ActivationConfigProperty(propertyName="userName", propertyValue="jbossra"), @ActivationConfigProperty(propertyName="password", propertyValue="****"), @ActivationConfigProperty(propertyName="debug", propertyValue="true"), @ActivationConfigProperty(propertyName="starttls", propertyValue="false"), @ActivationConfigProperty(propertyName="pollingInterval", propertyValue="60000") }) @ResourceAdapter("mail-ra.rar") public class MailBean implements MailListener { public void onMessage(Message message) { // Process the message try { System.out.println("Message received:"+message.getSubject()); } catch (MessagingException e) { e.printStackTrace(); } } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

6
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010