Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Problem Running Greenpages under STS/Eclipse
Problem Running Greenpages under STS/Eclipse [message #647613] Fri, 07 January 2011 11:05 Go to next message
Mike Shorter is currently offline Mike ShorterFriend
Messages: 2
Registered: January 2011
Junior Member
Hello,

I am having problems running Greenpages under STS.

I have successfully build and run Greenpages from the command line. I then deleted the .par file from Virgo, and tried to run it via STS. Here is part of the error log:

[2011-01-07 12:00:13.624] TCP Connection(2)-127.0.0.1 <ME0003I> Dump 'serviceability/dump/2011-01-07-12-00-077' generated
[2011-01-07 12:00:13.629] TCP Connection(2)-127.0.0.1 <DE0002E> Installation of par 'greenpages-solution' version '0.0.0' failed. java.lang.UnsupportedOperationException: Cannot open an input stream for '/opt/java/OSGi/virgo-web-server-2.1.0.RELEASE/work/org.ecli pse.virgo.kernel.deployer_2.1.0.RELEASE/staging/greenpages-s olution-0/bundle/greenpages-solution-0-greenpages.db-solutio n/0.0.0/greenpages.db-solution.jar/META-INF/MANIFEST.MF' as it does not exist
at org.eclipse.virgo.kernel.artifact.fs.internal.FileArtifactFS Entry.getInputStream(FileArtifactFSEntry.java:59)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.loadManifest(ServiceScoper.java:186)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.loadBundleManifests(ServiceScoper.java:175)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.doScope(ServiceScoper.java:156)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.scope(ServiceScoper.java:88)
at org.eclipse.virgo.kernel.install.artifact.internal.PlanScope r.scope(PlanScoper.java:137)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardP lanInstallArtifact.scope(StandardPlanInstallArtifact.java:17 5)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopingTransformer.processScopedPlanInstallArtifact(S copingTransformer.java:50)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopedPlanIdentifyingTreeVisitor.visit(ScopedPlanIden tifyingTreeVisitor.java:32)
at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:165)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopingTransformer.transform(ScopingTransformer.java: 41)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.TransformationStage.doProcessTree(TransformationStage .java:55)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:613)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:192)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(ConvertingMethod.java:174)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:117)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIn trospector.java:54)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntro spector.java:235)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.jav a:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.jav a:250)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer .java:791)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RM IConnectionImpl.java:1447)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMI ConnectionImpl.java:89)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(RMIConnectionImpl.java:1292)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(RMIConnectionImpl.java:1380)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConn ectionImpl.java:812)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:613)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.ja va:322)
at sun.rmi.transport.Transport$1.run(Transport.java:177)
at sun.rmi.transport.Transport$1.run(Transport.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspo rt.java:553)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TC PTransport.java:808)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCP Transport.java:667)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool Executor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo lExecutor.java:603)
at java.lang.Thread.run(Thread.java:732)

[2011-01-07 12:00:13.633] TCP Connection(2)-127.0.0.1 <DE0003E> Install failed for bundle 'greenpages.web-solution' version '0.0.0'.
[2011-01-07 12:00:13.636] TCP Connection(2)-127.0.0.1 <DE0003E> Install failed for bundle 'greenpages-solution-0-greenpages.app-solution' version '0.0.0'.
[2011-01-07 12:00:13.638] TCP Connection(2)-127.0.0.1 <DE0003E> Install failed for bundle 'greenpages-solution-0-greenpages.jpa-solution' version '0.0.0'.
[2011-01-07 12:00:13.640] TCP Connection(2)-127.0.0.1 <DE0003E> Install failed for bundle 'greenpages-solution-0-greenpages.db-solution' version '0.0.0'.
[2011-01-07 12:00:13.642] TCP Connection(2)-127.0.0.1 <DE0003E> Install failed for par 'greenpages-solution' version '0.0.0'.
[2011-01-07 12:00:13.646] fs-watcher <HD0005I> Hot deploy not performed because file 'org.eclipse.virgo.apps.admin-2.1.0.RELEASE.plan' is already deployed.
[2011-01-07 12:00:13.648] fs-watcher <HD0001I> Hot deployer processing 'INITIAL' event for file 'org.eclipse.virgo.apps.repository-2.1.0.RELEASE.par'.
[2011-01-07 12:00:13.650] fs-watcher <HD0005I> Hot deploy not performed because file 'org.eclipse.virgo.apps.repository-2.1.0.RELEASE.par' is already deployed.
[2011-01-07 12:00:13.655] fs-watcher <HD0001I> Hot deployer processing 'INITIAL' event for file 'org.eclipse.virgo.apps.splash-2.1.0.RELEASE.war'.
[2011-01-07 12:00:13.661] fs-watcher <HD0005I> Hot deploy not performed because file 'org.eclipse.virgo.apps.splash-2.1.0.RELEASE.war' is already deployed.

I have noticed that there is a directory structure under /stage directory of the Virgo web server:
stage/
|-- greenpages-solution.par
| |-- greenpages.app-solution.jar
| | |-- greenpages
| | | `-- internal
| | `-- META-INF
| | `-- spring
| |-- greenpages.db-solution.jar
| | `-- META-INF
| | `-- spring
| |-- greenpages.jpa-solution.jar
| | |-- greenpages
| | | `-- jpa
| | `-- META-INF
| | `-- spring
| |-- greenpages.web-solution.war
| | |-- images
| | |-- META-INF
| | |-- styles
| | `-- WEB-INF
| | |-- classes
| | | |-- greenpages
| | | | `-- web
| | | `-- META-INF
| | | `-- spring
| | |-- ftl
| | `-- lib
| `-- META-INF
`-- org.eclipse.virgo.repository.properties

but as you can see, there are no files. Has anyone else had this problem and/or a possible solution?

I am running Eclipse 3.6.1 64 bit/STS 2.5.1 with Virgo 2.1.0.RELEASE and Maven 3.0.1 under Linux (Ubuntu 10.10 AMD 64).

Thanks,

Mike

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #647874 is a reply to message #647613] Mon, 10 January 2011 09:33 Go to previous messageGo to next message
Martin Lippert is currently offline Martin LippertFriend
Messages: 124
Registered: July 2009
Senior Member
Hi Mike!

Hm, looks like a bug in the tooling somehow. We will take a look at this right after the donation of the Virgo tooling to Eclipse. Could you file a bug for this? That would be great!

Thanks,
Martin

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #648175 is a reply to message #647874] Tue, 11 January 2011 15:59 Go to previous messageGo to next message
Eva Troels is currently offline Eva TroelsFriend
Messages: 17
Registered: December 2010
Junior Member
Do you have a workaround / explanation for this?
I am also experiencing these problems and getting nowhere Sad

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #648275 is a reply to message #648175] Wed, 12 January 2011 09:07 Go to previous messageGo to next message
Mike Shorter is currently offline Mike ShorterFriend
Messages: 2
Registered: January 2011
Junior Member
No. I have submitted a bug report on the problem.

Thanks,

MIke

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #663391 is a reply to message #647874] Mon, 04 April 2011 20:13 Go to previous messageGo to next message
Ronald So is currently offline Ronald SoFriend
Messages: 198
Registered: April 2011
Senior Member
Hi guys,

I think I have run into the same problem. I am new to Eclipse Virgo, and I was deploying the greenpages app from the manual. I can get the app to run through command line too, but as soon as I delete the PAR file and try to deploy the app in Eclipse, I got the following stack trace when I start the Virgo Web Server.


[2011-04-04 15:59:59.441] start-signalling-2 <DE0005I> Started par 'org.eclipse.virgo.apps.repository' version '2.1.0.RELEASE'.
[2011-04-04 15:59:59.514] TCP Connection(3)-127.0.0.1 <DE0000I> Installing par 'greenpages' version '2.3.0.RELEASE'.
[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.app-solution' version '0.0.0'.
[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.db-solution' version '0.0.0'.
[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.jpa-solution' version '0.0.0'.
[2011-04-04 16:00:00.110] fs-watcher <HD0001I> Hot deployer processing 'INITIAL' event for file 'org.eclipse.virgo.apps.admin-2.1.0.RELEASE.plan'.
[2011-04-04 16:00:00.295] TCP Connection(3)-127.0.0.1 <ME0003I> Dump 'serviceability\dump\2011-04-04-15-59-546' generated
[2011-04-04 16:00:00.301] TCP Connection(3)-127.0.0.1 <DE0002E> Installation of par 'greenpages' version '2.3.0.RELEASE' failed. java.lang.UnsupportedOperationException: Cannot open an input stream for 'C:\OSGI\virgo-web-server-2.1.0.RELEASE\work\org.eclipse.vir go.kernel.deployer_2.1.0.RELEASE\staging\greenpages-2.3.0.RE LEASE\bundle\greenpages-2.3.0.RELEASE-greenpages.app-solutio n\0.0.0\greenpages.app-solution.jar\META-INF\MANIFEST.MF' as it does not exist
at org.eclipse.virgo.kernel.artifact.fs.internal.FileArtifactFS Entry.getInputStream(FileArtifactFSEntry.java:59)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.loadManifest(ServiceScoper.java:186)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.loadBundleManifests(ServiceScoper.java:175)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.doScope(ServiceScoper.java:156)
at org.eclipse.virgo.kernel.install.artifact.internal.ServiceSc oper.scope(ServiceScoper.java:88)
at org.eclipse.virgo.kernel.install.artifact.internal.PlanScope r.scope(PlanScoper.java:137)
at org.eclipse.virgo.kernel.install.artifact.internal.StandardP lanInstallArtifact.scope(StandardPlanInstallArtifact.java:17 5)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopingTransformer.processScopedPlanInstallArtifact(S copingTransformer.java:50)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopedPlanIdentifyingTreeVisitor.visit(ScopedPlanIden tifyingTreeVisitor.java:32)
at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit( ThreadSafeArrayListTree.java:165)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.ScopingTransformer.transform(ScopingTransformer.java: 41)
at org.eclipse.virgo.kernel.install.pipeline.stage.transform.in ternal.TransformationStage.doProcessTree(TransformationStage .java:55)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.Compensat ingPipeline.doProcessTree(CompensatingPipeline.java:72)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardP ipeline.doProcessTree(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipe lineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.driveInstallPipeline(PipelinedApplicationDe ployer.java:271)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.doInstall(PipelinedApplicationDeployer.java :151)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.install(PipelinedApplicationDeployer.java:1 23)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApp licationDeployer.deploy(PipelinedApplicationDeployer.java:19 0)
at org.eclipse.virgo.kernel.deployer.management.StandardDeploye r.deploy(StandardDeployer.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenRetur n(Unknown Source)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source)
at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke (Unknown Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Un known Source)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unk nown Source)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOper ation.run(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOp eration(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Un known Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unk nown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Is this the same issue? If not, can you suggest what I can do to get around the issue?

Thank you so much in advance.

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #667694 is a reply to message #663391] Sun, 01 May 2011 13:52 Go to previous messageGo to next message
Muammer Yucel is currently offline Muammer YucelFriend
Messages: 1
Registered: May 2011
Junior Member
Try to clean and rebuild greenpages projects and redeploy bundles. I'm not sure but it seems that inappropriate versions of bundles were being deployed:

[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.app-solution' version '0.0.0'.
[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.db-solution' version '0.0.0'.
[2011-04-04 15:59:59.529] TCP Connection(3)-127.0.0.1 <DE0000I> Installing bundle 'greenpages-2.3.0.RELEASE-greenpages.jpa-solution' version '0.0.0'.

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #667710 is a reply to message #667694] Sun, 01 May 2011 15:22 Go to previous messageGo to next message
Eva Troels is currently offline Eva TroelsFriend
Messages: 17
Registered: December 2010
Junior Member
I have a workaround for the particular problem with MANIFEST.MF. If you look in the stage library, you will notice, that the MANIFEST.MF is missing. I usually refresh (F5) the project in question in Eclipse or sometimes just the MANIFEST.MF. After a clean+deploy on the Virgo the MANIFEST.MF shows up as expected in the stage library and the problem goes away.
I'm not sure what is going on - something with timestamps maybe??

/Eva

Report message to a moderator

Re: Problem Running Greenpages under STS/Eclipse [message #1220355 is a reply to message #648275] Wed, 11 December 2013 09:32 Go to previous message
Christian Bonami is currently offline Christian BonamiFriend
Messages: 1
Registered: December 2013
Junior Member
Hi Mike,

I know it's a long time ago, but could you maybe give me the location/number of that bug report ccn Virgo tooling and the META-INF not being found ?
Tried to find it but didn't Sad
And the (annoying) problem is still there ...

Report message to a moderator

Previous Topic:Disabling Security Manager in Virgo
Next Topic:JAX-WS Web Service support
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 02:25:53 GMT 2024

Powered by FUDForum. Page generated in 0.04239 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly