-
1. Re: Upgrade to newer Versions of org.ops4j.pax
You mean in the jbosgi distribution? The upcomming 1.2.0 release will not contain any ops4j.pax components any more. In AS7 we now support HttpService and WebApp natively on JBossWeb.
-
2. Re: Upgrade to newer Versions of org.ops4j.pax
Yes I mean in the jbosgi distribution.
With JBoss 7.2 from trunk there is a different problem :-( (I think it is more JBoss specific and not JBoss OSGi).
I deploy the third party bundles on which my bundles depend with the JBoss AS7 Deploment plugin, this was working with 7.1.3.Final.
But with 7.2 from trunk it stops (hangs) when deploying the Apache Commons Logging bundle provided by SpringSource.
When the deployment is disrupted, there is the following message in the logging of the server:
10:01:14,524 ERROR [org.jboss.remoting.remote.connection] (Remoting "a303:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
10:01:14,542 DEBUG [org.jboss.as.protocol] (Remoting "a303:MANAGEMENT" task-2) active-op (1263598696) failed null: org.jboss.remoting3.MessageCancelledException
at org.xnio.streams.BufferPipeInputStream.checkFailure(BufferPipeInputStream.java:280) [xnio-api-3.0.7.GA.jar:3.0.7.GA]
at org.xnio.streams.BufferPipeInputStream.read(BufferPipeInputStream.java:171) [xnio-api-3.0.7.GA.jar:3.0.7.GA]
at org.jboss.remoting3.remote.InboundMessage$3.read(InboundMessage.java:131) [jboss-remoting-3.2.11.GA.jar:3.2.11.GA]
at java.io.DataInputStream.readFully(DataInputStream.java:178) [rt.jar:1.6.0_24]
at org.jboss.as.controller.remote.OperationAttachmentsProxy$ProxiedInputStream$1.handleRequest(OperationAttachmentsProxy.java:151) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:255) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:220) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:114) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:58) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:86) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:436) [jboss-remoting-3.2.11.GA.jar:3.2.11.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
10:01:14,604 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location C:\java\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\content\87\a9232fbce3040716bdd0f9f1a6f7e9aeb68c15\content
10:01:14,613 DEBUG [org.jboss.as.controller.management-operation] (management-handler-thread - 2) Entered VERIFY stage; waiting for service container to settle
10:01:14,614 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "com.springsource.org.apache.commons.logging-1.1.1.jar"
10:01:14,657 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."com.springsource.org.apache.commons.logging-1.1.1.jar".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."com.springsource.org.apache.commons.logging-1.1.1.jar".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "com.springsource.org.apache.commons.logging-1.1.1.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-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_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment content
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:92) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.6.0_24]
at java.util.zip.ZipFile.<init>(ZipFile.java:127) [rt.jar:1.6.0_24]
at java.util.jar.JarFile.<init>(JarFile.java:135) [rt.jar:1.6.0_24]
at java.util.jar.JarFile.<init>(JarFile.java:99) [rt.jar:1.6.0_24]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:97)
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83)
at org.jboss.vfs.VFS.mountZip(VFS.java:408)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:95) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:88) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 6 more
10:01:14,677 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "com.springsource.org.apache.commons.logging-1.1.1.jar" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"com.springsource.org.apache.commons.logging-1.1.1.jar\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"com.springsource.org.apache.commons.logging-1.1.1.jar\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"com.springsource.org.apache.commons.logging-1.1.1.jar\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment content
Caused by: java.util.zip.ZipException: error in opening zip file"}}
10:01:14,680 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment com.springsource.org.apache.commons.logging-1.1.1.jar in 3ms
10:01:14,682 DEBUG [org.jboss.as.protocol] (management-handler-thread - 2) failed to process async request for org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1@ecb69e on channel Channel ID 745d22f7 (inbound) of Remoting connection 00c94ad4 to null: org.jboss.remoting3.NotOpenException: Writes closed
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:108) [jboss-remoting-3.2.11.GA.jar:3.2.11.GA]
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:297) [jboss-remoting-3.2.11.GA.jar:3.2.11.GA]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2.writeMessage(AbstractMessageHandler.java:328) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:113) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
-
3. Re: Upgrade to newer Versions of org.ops4j.pax
Yes, this is a different problem. How can I reproduce this?
-
4. Re: Upgrade to newer Versions of org.ops4j.pax
I attached a simple maven pom file. The call to maven deploy shows the error.
-
5. Re: Upgrade to newer Versions of org.ops4j.pax
This seems to be an IO issue and unrelated to OSGi. What happens when you deploy the thing normally?
-
6. Re: Upgrade to newer Versions of org.ops4j.pax
When I copy it to the deployment folder, the bundle is installed and started.
But in the deployment folder is a file with name com.springsource.org.apache.commons.logging-1.1.1.jar.failed with contend "undefined" as if a deploment fails.
-
7. Re: Upgrade to newer Versions of org.ops4j.pax
That would be a bug. You can create a jira for component osgi and attach the file that you're deploying.
-
9. Re: Upgrade to newer Versions of org.ops4j.pax
For which component should I create a JIRA for the maven deploy problem? I have more dependecies with the same problem.
Best Regards
Peter
-
11. Re: Upgrade to newer Versions of org.ops4j.pax
I don't think this is a problem of the jboss-as-maven-plugin, because it is working with JBoss 7.1.3.Final but not with jboss-as-7.2.0.Alpha1-SNAPSHOT
-
12. Re: Upgrade to newer Versions of org.ops4j.pax
With JBoss 7.2.0-Alpha1-SNAPSHOT following exception is thrown:
11:27:58,696 ERROR [org.eclipse.rap.rwt.osgi] (Thread-67) Unable to start RWT application.: java.lang.IllegalStateException: ServletConfig has not been initialized
at javax.servlet.GenericServlet.getServletContext(GenericServlet.java:197)
at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.createApplication(ApplicationReferenceImpl.java:71)
at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.start(ApplicationReferenceImpl.java:61)
at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.doLaunch(ApplicationLauncherImpl.java:103)
at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:85)
at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:162)
at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launchWithConfiguration(ApplicationLauncherImpl.java:149)
at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.addConfiguration(ApplicationLauncherImpl.java:64)
at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:35)
at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:1)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]
at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:525) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]
at org.jboss.osgi.framework.internal.ServiceManagerPlugin.registerService(ServiceManagerPlugin.java:162) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]
at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:305) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]
at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:394)
at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:188)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:652)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:325)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:228)
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_24]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_24]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [rt.jar:1.6.0_24]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
Few lines before the HttpService ist registered:
1:27:58,695 INFO [org.jboss.as.osgi] (Blueprint Extender: 2) JBAS011913: Register HttpService alias: /servlet_context_finder
But maybe the servlet is not initialized?