[JBoss JIRA] (JBOSGI-700) Karaf configuration through ConfigAdmin
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-700?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-700.
-----------------------------------
Resolution: Won't Fix
> Karaf configuration through ConfigAdmin
> ---------------------------------------
>
> Key: JBOSGI-700
> URL: https://issues.jboss.org/browse/JBOSGI-700
> Project: JBoss OSGi
> Issue Type: Feature Request
> Reporter: Thomas Diesler
>
> Currently we add these props to standalone.conf
> {code}
> -Dkaraf.home=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.base=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.startRemoteShell=true -Dkaraf.startLocalConsole=false
> {code}
> For this we should have sensible defaults as well as make the SSH port (and possibly other options) configurable through ConfigAdmin
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-701) Provide management view for bundle wiring
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-701?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-701.
-----------------------------------
Resolution: Won't Fix
> Provide management view for bundle wiring
> -----------------------------------------
>
> Key: JBOSGI-701
> URL: https://issues.jboss.org/browse/JBOSGI-701
> Project: JBoss OSGi
> Issue Type: Feature Request
> Environment: Mac OS X 10.7.3
> Reporter: Tim Diekmann
> Labels: Console
>
> The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what?
> {code}
> 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet
> at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294)
> at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
> at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109)
> at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60)
> at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300)
> at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223)
> at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488)
> at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132)
> at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89)
> at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304)
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294)
> at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294)
> at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201)
> at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208)
> at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-667) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-667:
----------------------------------
Component/s: WildFly
> OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository
> ---------------------------------------------------------------------------------------
>
> Key: JBOSGI-667
> URL: https://issues.jboss.org/browse/JBOSGI-667
> Project: JBoss OSGi
> Issue Type: Bug
> Components: WildFly
> Reporter: Igor Shulika
>
> I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare capability in the standalone-osgi.xml file.
>
> Here is my capability configuration.
> <capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0" startlevel="4"/>
>
> Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments" directory the message driven bean starting successfully (see below).
> INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter.
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-536) OSGi implementation does not support framework extensions
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-536?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-536:
----------------------------------
Fix Version/s: JBossOSGi 2.0.1
(was: Awaiting Volunteers)
> OSGi implementation does not support framework extensions
> ---------------------------------------------------------
>
> Key: JBOSGI-536
> URL: https://issues.jboss.org/browse/JBOSGI-536
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Framework
> Affects Versions: JBossOSGi 1.0.0
> Environment: Mac OS X 10.7.3
> Reporter: Tim Diekmann
> Fix For: JBossOSGi 2.0.1
>
>
> Installing a System Framework extension fails in AS 7.1.0.Final.
> {code}
> 10:27:35,179 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jbosgi.bundle.8."com.tibco.tpcl.javax.system.exports"."5.0.300.004".INSTALLED: org.jboss.msc.service.StartException in service jbosgi.bundle.8."com.tibco.tpcl.javax.system.exports"."5.0.300.004".INSTALLED: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
> Caused by: java.lang.UnsupportedOperationException: Framework extension not supported
> at org.jboss.osgi.framework.internal.BundleValidatorR4.validateBundle(BundleValidatorR4.java:141)
> at org.jboss.osgi.framework.internal.UserBundleInstalledService.validateBundle(UserBundleInstalledService.java:93)
> at org.jboss.osgi.framework.internal.UserBundleInstalledService.start(UserBundleInstalledService.java:65)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> {code}
> I tried adding this through the cli, web console, and by adding this manually to the bundles folder and updating the configuration file. Same result.
> Please note that framework extensions support is mandated by the Core specification to be a certified OSGi framework.
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-673) Invalid bundle deployment does not fail in domain
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-673?page=com.atlassian.jira.plugin... ]
Thomas Diesler resolved JBOSGI-673.
-----------------------------------
Resolution: Won't Fix
Won't Fix
> Invalid bundle deployment does not fail in domain
> -------------------------------------------------
>
> Key: JBOSGI-673
> URL: https://issues.jboss.org/browse/JBOSGI-673
> Project: JBoss OSGi
> Issue Type: Bug
> Reporter: Thomas Diesler
> Priority: Minor
>
> Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE!
> on the server I see
> {code}
> 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
> Caused by: java.lang.NumberFormatException: For input string: "bogus"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29]
> at org.osgi.framework.Version.<init>(Version.java:125)
> at org.osgi.framework.Version.parseVersion(Version.java:218)
> at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204)
> at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153)
> at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63)
> {code}
--
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
12 years, 9 months
[JBoss JIRA] (JBOSGI-672) DuplicateServiceException on undertow deployment replace
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-672?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-672:
----------------------------------
Component/s: WildFly
> DuplicateServiceException on undertow deployment replace
> --------------------------------------------------------
>
> Key: JBOSGI-672
> URL: https://issues.jboss.org/browse/JBOSGI-672
> Project: JBoss OSGi
> Issue Type: Bug
> Components: WebApp, WildFly
> Reporter: Thomas Diesler
>
> {code}
> 07:21:52,095 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webapp-v101.wab" (runtime-name: "webapp-v101.wab")
> 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: webapp-v101.wab:1.0.1
> 07:21:52,119 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS018224: Unregister web context: /simple-bundle
> 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011003: Bundle stopped: webapp-v100.wab:1.0.0
> 07:21:52,124 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."webapp-v101.wab".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."webapp-v101.wab".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "webapp-v101.wab"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.undertow.deployment.default-host./simple-bundle.UndertowDeploymentInfoService is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.processDeployment(UndertowDeploymentProcessor.java:235)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.deploy(UndertowDeploymentProcessor.java:102)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> {code}
> http://teamcity.cafe-babe.org/viewLog.html?buildId=5380&tab=buildResultsD...
--
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
12 years, 9 months