From issues at jboss.org Tue Jan 21 10:48:30 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Tue, 21 Jan 2014 10:48:30 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5132) Two XXE security issues in Seam remoting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny moved WFK2-382 to JBSEAM-5132: -------------------------------------------- Project: Seam 2 (was: JBoss WFK 2) Key: JBSEAM-5132 (was: WFK2-382) Workflow: GIT Pull Request workflow (was: CDW v1) Affects Version/s: 2.3.1.Final (was: 2.4.0.GA) Component/s: Remoting (was: Seam 2) Security: (was: JBoss Internal) Fix Version/s: 2.3.2.CR1 (was: 2.5.0.ER1) Target Release: (was: 2.5.0.GA) > Two XXE security issues in Seam remoting > ---------------------------------------- > > Key: JBSEAM-5132 > URL: https://issues.jboss.org/browse/JBSEAM-5132 > Project: Seam 2 > Issue Type: Bug > Components: Remoting > Affects Versions: 2.3.1.Final > Reporter: David Jorm > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > WFK 2.4.0 is affected by two Seam security flaws: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447 > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448 > A WFK tracking bug in BZ is here: > https://bugzilla.redhat.com/show_bug.cgi?id=1052099 > These flaws are embargoed, and we need to produce patches for our products before pushing the fixes upstream. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 21 10:50:28 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Tue, 21 Jan 2014 10:50:28 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5132) Two XXE security issues in Seam remoting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny updated JBSEAM-5132: ---------------------------------- Description: Seam remoting is impacted by 2 XXE security flaws: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448 was: WFK 2.4.0 is affected by two Seam security flaws: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448 A WFK tracking bug in BZ is here: https://bugzilla.redhat.com/show_bug.cgi?id=1052099 These flaws are embargoed, and we need to produce patches for our products before pushing the fixes upstream. > Two XXE security issues in Seam remoting > ---------------------------------------- > > Key: JBSEAM-5132 > URL: https://issues.jboss.org/browse/JBSEAM-5132 > Project: Seam 2 > Issue Type: Bug > Components: Remoting > Affects Versions: 2.3.1.Final > Reporter: David Jorm > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > Seam remoting is impacted by 2 XXE security flaws: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447 > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Jan 21 10:50:29 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Tue, 21 Jan 2014 10:50:29 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5132) Two XXE security issues in Seam remoting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12937596#comment-12937596 ] Marek Novotny commented on JBSEAM-5132: --------------------------------------- fix is committed as https://github.com/seam2/jboss-seam/commit/090aa6252affc978a96c388e3fc2c1c2688d9bb5 > Two XXE security issues in Seam remoting > ---------------------------------------- > > Key: JBSEAM-5132 > URL: https://issues.jboss.org/browse/JBSEAM-5132 > Project: Seam 2 > Issue Type: Bug > Components: Remoting > Affects Versions: 2.3.1.Final > Reporter: David Jorm > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > Seam remoting is impacted by 2 XXE security flaws: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6447 > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-6448 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Jan 22 17:28:28 2014 From: issues at jboss.org (yangju (JIRA)) Date: Wed, 22 Jan 2014 17:28:28 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (SOLDER-339) Catch attempts to use BeanManager during application initialization under Weld 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SOLDER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938053#comment-12938053 ] yangju commented on SOLDER-339: ------------------------------- org.jboss.weld.nonPortableMode=true does not seem to work in Wildfly CR1 with Solder 3.2.0.Final and Solder 3.1.0.Final. Even I set this flag as system property in standalone.conf.bat (windows), the deployment still throws errors: Exception 0 : org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default at injection point [BackedAnnotatedField] @Inject private org.jboss.solder.servlet.http.CookieParamProducer.request at org.jboss.solder.servlet.http.CookieParamProducer.request(CookieParamProducer.java:0) Possible dependencies: - WELD|AbstractSyntheticBean|epen-login-1.4.30-SNAPSHOT.war/WEB-INF/lib/solder-impl-3.2.0.Final.jar|HttpServletRequest, - Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()] at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:369) at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:282) at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:133) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:507) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Is there any other work around? Thanks. > Catch attempts to use BeanManager during application initialization under Weld 2.0 > ---------------------------------------------------------------------------------- > > Key: SOLDER-339 > URL: https://issues.jboss.org/browse/SOLDER-339 > Project: Solder > Issue Type: Bug > Affects Versions: 3.1.0.Final > Environment: JBoss 7.1.1 w/ Weld 2.0.0.Beta2 > Reporter: Ken H > > The exception prevents application from starting. > org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerInitialized(BeanManagerProxy.java:148) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:78) > at org.jboss.solder.exception.control.HandlerMethodImpl.getBean(HandlerMethodImpl.java:154) > at org.jboss.solder.exception.control.HandlerMethodImpl.(HandlerMethodImpl.java:138) > at org.jboss.solder.exception.control.extension.CatchExtension.findHandlers(CatchExtension.java:102) > at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:268) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:264) > at org.jboss.weld.annotated.runtime.InvokableAnnotatedMethod.invokeOnInstance(InvokableAnnotatedMethod.java:82) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:97) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:276) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:134) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:263) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:238) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:242) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:173) > at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:47) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:134) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:69) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) > at org.jboss.weld.bootstrap.events.ProcessManagedBeanImpl.fire(ProcessManagedBeanImpl.java:30) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessBean(ContainerLifecycleEvents.java:154) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:145) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:133) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:309) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:265) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:446) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:92) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:77) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 23 04:14:29 2014 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Thu, 23 Jan 2014 04:14:29 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (SOLDER-339) Catch attempts to use BeanManager during application initialization under Weld 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SOLDER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938143#comment-12938143 ] Martin Kouba commented on SOLDER-339: ------------------------------------- Well, non-portable mode only solves the issue with invoking some specific methods (e.g. getBeans()) on BeanManager during application initialization (which is forbidden in CDI 1.1). > Catch attempts to use BeanManager during application initialization under Weld 2.0 > ---------------------------------------------------------------------------------- > > Key: SOLDER-339 > URL: https://issues.jboss.org/browse/SOLDER-339 > Project: Solder > Issue Type: Bug > Affects Versions: 3.1.0.Final > Environment: JBoss 7.1.1 w/ Weld 2.0.0.Beta2 > Reporter: Ken H > > The exception prevents application from starting. > org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerInitialized(BeanManagerProxy.java:148) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:78) > at org.jboss.solder.exception.control.HandlerMethodImpl.getBean(HandlerMethodImpl.java:154) > at org.jboss.solder.exception.control.HandlerMethodImpl.(HandlerMethodImpl.java:138) > at org.jboss.solder.exception.control.extension.CatchExtension.findHandlers(CatchExtension.java:102) > at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:268) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:264) > at org.jboss.weld.annotated.runtime.InvokableAnnotatedMethod.invokeOnInstance(InvokableAnnotatedMethod.java:82) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:97) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:276) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:134) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:263) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:238) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:242) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:173) > at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:47) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:134) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:69) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) > at org.jboss.weld.bootstrap.events.ProcessManagedBeanImpl.fire(ProcessManagedBeanImpl.java:30) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessBean(ContainerLifecycleEvents.java:154) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:145) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:133) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:309) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:265) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:446) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:92) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:77) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Jan 23 04:14:29 2014 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Thu, 23 Jan 2014 04:14:29 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (SOLDER-339) Catch attempts to use BeanManager during application initialization under Weld 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SOLDER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938143#comment-12938143 ] Martin Kouba edited comment on SOLDER-339 at 1/23/14 4:13 AM: -------------------------------------------------------------- Weld 2 non-portable mode only solves the issue with invoking some specific methods (e.g. getBeans()) on BeanManager during application initialization (which is forbidden in CDI 1.1). was (Author: mkouba): Well, non-portable mode only solves the issue with invoking some specific methods (e.g. getBeans()) on BeanManager during application initialization (which is forbidden in CDI 1.1). > Catch attempts to use BeanManager during application initialization under Weld 2.0 > ---------------------------------------------------------------------------------- > > Key: SOLDER-339 > URL: https://issues.jboss.org/browse/SOLDER-339 > Project: Solder > Issue Type: Bug > Affects Versions: 3.1.0.Final > Environment: JBoss 7.1.1 w/ Weld 2.0.0.Beta2 > Reporter: Ken H > > The exception prevents application from starting. > org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerInitialized(BeanManagerProxy.java:148) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:78) > at org.jboss.solder.exception.control.HandlerMethodImpl.getBean(HandlerMethodImpl.java:154) > at org.jboss.solder.exception.control.HandlerMethodImpl.(HandlerMethodImpl.java:138) > at org.jboss.solder.exception.control.extension.CatchExtension.findHandlers(CatchExtension.java:102) > at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:268) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:264) > at org.jboss.weld.annotated.runtime.InvokableAnnotatedMethod.invokeOnInstance(InvokableAnnotatedMethod.java:82) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:97) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:276) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:134) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:263) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:238) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:242) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:173) > at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:47) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:134) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:69) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) > at org.jboss.weld.bootstrap.events.ProcessManagedBeanImpl.fire(ProcessManagedBeanImpl.java:30) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessBean(ContainerLifecycleEvents.java:154) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:145) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:133) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:309) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:265) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:446) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:92) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:77) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira