[JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov resolved JBOSGI-771.
-----------------------------------
Resolution: Done
> NPE in FallbackLoader due to absent BundleWiring
> ------------------------------------------------
>
> Key: JBOSGI-771
> URL: https://issues.jboss.org/browse/JBOSGI-771
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
> at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576)
> at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155)
> at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135)
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119)
> at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513)
> at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60)
> at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70)
> at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov updated JBOSGI-771:
----------------------------------
Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/19
> NPE in FallbackLoader due to absent BundleWiring
> ------------------------------------------------
>
> Key: JBOSGI-771
> URL: https://issues.jboss.org/browse/JBOSGI-771
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
> at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576)
> at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155)
> at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135)
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119)
> at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513)
> at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60)
> at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70)
> at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov updated JBOSGI-771:
----------------------------------
Summary: NPE in FallbackLoader due to absent BundleWiring (was: NPE in FallbackLoader)
> NPE in FallbackLoader due to absent BundleWiring
> ------------------------------------------------
>
> Key: JBOSGI-771
> URL: https://issues.jboss.org/browse/JBOSGI-771
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
> at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576)
> at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155)
> at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final]
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135)
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119)
> at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513)
> at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60)
> at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70)
> at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader
by Arcadiy Ivanov (JIRA)
Arcadiy Ivanov created JBOSGI-771:
-------------------------------------
Summary: NPE in FallbackLoader
Key: JBOSGI-771
URL: https://issues.jboss.org/browse/JBOSGI-771
Project: JBoss OSGi
Issue Type: Bug
Components: framework
Affects Versions: JBossOSGi 2.2.0
Reporter: Arcadiy Ivanov
Assignee: Arcadiy Ivanov
Priority: Blocker
Fix For: JBossOSGI 2.3.1
{noformat}
Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0
at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624)
at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576)
at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129)
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155)
at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final]
at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135)
at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119)
at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513)
at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60)
at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70)
at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43)
at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598)
... 8 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov commented on JBOSGI-765:
---------------------------------------
This seems to be a correct behavior under JLS - https://bugs.openjdk.java.net/browse/JDK-6322301
Class.getAnnotations() never throws ClassNotFoundException or TypeNotPresentException but silently strips the annotations altogether.
> HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
> ------------------------------------------------------------------------------------------
>
> Key: JBOSGI-765
> URL: https://issues.jboss.org/browse/JBOSGI-765
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Environment: WildFly 8.1.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Minor
> Fix For: JBossOSGI 2.3.1
>
>
> Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be:
> 1) Successfully installed
> 2) Successfully activated
> 3) All classes within said bundle will be properly loaded
> 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation.
> No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service:
> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml
> if the return type of REST API call is List<X>.
> While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere.
> Marked Minor since workaround exists but I would recommend escalation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov resolved JBOSGI-765.
-----------------------------------
Resolution: Won't Fix
> HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
> ------------------------------------------------------------------------------------------
>
> Key: JBOSGI-765
> URL: https://issues.jboss.org/browse/JBOSGI-765
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Environment: WildFly 8.1.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Minor
> Fix For: JBossOSGI 2.3.1
>
>
> Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be:
> 1) Successfully installed
> 2) Successfully activated
> 3) All classes within said bundle will be properly loaded
> 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation.
> No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service:
> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml
> if the return type of REST API call is List<X>.
> While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere.
> Marked Minor since workaround exists but I would recommend escalation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov updated JBOSGI-765:
----------------------------------
Fix Version/s: JBossOSGI 2.3.1
> HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported
> ------------------------------------------------------------------------------------------
>
> Key: JBOSGI-765
> URL: https://issues.jboss.org/browse/JBOSGI-765
> Project: JBoss OSGi
> Issue Type: Bug
> Components: framework
> Affects Versions: JBossOSGi 2.2.0
> Environment: WildFly 8.1.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Minor
> Fix For: JBossOSGI 2.3.1
>
>
> Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be:
> 1) Successfully installed
> 2) Successfully activated
> 3) All classes within said bundle will be properly loaded
> 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation.
> No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service:
> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml
> if the return type of REST API call is List<X>.
> While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere.
> Marked Minor since workaround exists but I would recommend escalation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start in domain
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov resolved JBOSGI-770.
-----------------------------------
Resolution: Done
> Capability org.jboss.as.osgi.http fails to start in domain
> ----------------------------------------------------------
>
> Key: JBOSGI-770
> URL: https://issues.jboss.org/browse/JBOSGI-770
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: WildFly 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description:
> {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]}
> 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start in domain
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov updated JBOSGI-770:
----------------------------------
Summary: Capability org.jboss.as.osgi.http fails to start in domain (was: Capability org.jboss.as.osgi.http fails to start)
> Capability org.jboss.as.osgi.http fails to start in domain
> ----------------------------------------------------------
>
> Key: JBOSGI-770
> URL: https://issues.jboss.org/browse/JBOSGI-770
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: WildFly 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description:
> {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]}
> 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov updated JBOSGI-770:
----------------------------------
Fix Version/s: JBossOSGI 2.3.1
Git Pull Request: https://github.com/jbosgi/jbosgi/pull/8
> Capability org.jboss.as.osgi.http fails to start
> ------------------------------------------------
>
> Key: JBOSGI-770
> URL: https://issues.jboss.org/browse/JBOSGI-770
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: WildFly 8.2.0.Final
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Blocker
> Fix For: JBossOSGI 2.3.1
>
>
> {noformat}
> 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description:
> {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]}
> 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month