Unable to Launch Roo Shell 1.2 RELEASE - error on load please see attached log

Printable View

Jan 16th, 2012, 11:35 AM
dudeRK

1 Attachment(s)

Unable to Launch Roo Shell 1.2 RELEASE - error on load please see attached log

I cannot load the Roo shell as it gives some kind of error loading, I just downloaded spring-roo-1.2.0.RELEASE and I get the errors below (full log is attached to this post)

Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
Downloaded 0% of favorites.jsonDownloaded 100% of favorites.jsonDownloaded 100% of favorites.jsonDownloaded 100% of favorites.json
@ibmkhd: Introducing Spring Roo, Part 4: Rapid application development in cloud with Spring Roo and Cloud Foundry: Rapid ... http://t.co/eRT1bE6H
roo> Downloaded 100% of favorites.json
[org.springframework.roo.felix [45]] [org.springframework.roo.felix.pgp.PgpServiceImpl] The activate method has thrown an exception
org.apache.felix.log.LogException: java.lang.IllegalArgumentException: java.io.IOException: unknown object in stream: 0
at org.springframework.roo.felix.pgp.PgpServiceImpl.g etTrustedKeys(PgpServiceImpl.java:152)
at org.springframework.roo.felix.pgp.PgpServiceImpl.t rust(PgpServiceImpl.java:168)
at org.springframework.roo.felix.pgp.PgpServiceImpl.t rustDefaultKeys(PgpServiceImpl.java:110)
at org.springframework.roo.felix.pgp.PgpServiceImpl.t rustDefaultKeysIfRequired(PgpServiceImpl.java:93)
at org.springframework.roo.felix.pgp.PgpServiceImpl.a ctivate(PgpServiceImpl.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.felix.scr.impl.helper.BaseMethod.invoke Method(BaseMethod.java:227)
at org.apache.felix.scr.impl.helper.BaseMethod.access $500(BaseMethod.java:38)
at org.apache.felix.scr.impl.helper.BaseMethod$Resolv ed.invoke(BaseMethod.java:591)
at org.apache.felix.scr.impl.helper.BaseMethod.invoke (BaseMethod.java:472)
at org.apache.felix.scr.impl.helper.ActivateMethod.in voke(ActivateMethod.java:146)
at org.apache.felix.scr.impl.manager.ImmediateCompone ntManager.createImplementationObject(ImmediateComp onentManager.java:226)
at org.apache.felix.scr.impl.manager.ImmediateCompone ntManager.createComponent(ImmediateComponentManage r.java:118)
at org.apache.felix.scr.impl.manager.DelayedComponent Manager.createRealComponent(DelayedComponentManage r.java:95)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager$Registered.getService(AbstractComponentMa nager.java:1148)
at org.apache.felix.scr.impl.manager.DelayedComponent Manager.getService(DelayedComponentManager.java:88 )
at org.apache.felix.framework.ServiceRegistrationImpl .getFactoryUnchecked(ServiceRegistrationImpl.java: 310)
at org.apache.felix.framework.ServiceRegistrationImpl .getService(ServiceRegistrationImpl.java:221)
at org.apache.felix.framework.ServiceRegistry.getServ ice(ServiceRegistry.java:297)
at org.apache.felix.framework.Felix.getService(Felix. java:3139)
at org.apache.felix.framework.BundleContextImpl.getSe rvice(BundleContextImpl.java:411)
at org.apache.felix.scr.impl.manager.DependencyManage r.getService(DependencyManager.java:785)
at org.apache.felix.scr.impl.manager.DependencyManage r$1.getInstance(DependencyManager.java:1039)
at org.apache.felix.scr.impl.helper.BindMethod.getPar ameters(BindMethod.java:564)
at org.apache.felix.scr.impl.helper.BaseMethod.invoke Method(BaseMethod.java:226)
at org.apache.felix.scr.impl.helper.BaseMethod.access $500(BaseMethod.java:38)
at org.apache.felix.scr.impl.helper.BaseMethod$Resolv ed.invoke(BaseMethod.java:591)
at org.apache.felix.scr.impl.helper.BaseMethod$NotRes olved.invoke(BaseMethod.java:548)
at org.apache.felix.scr.impl.helper.BaseMethod.invoke (BaseMethod.java:472)
at org.apache.felix.scr.impl.manager.DependencyManage r.invokeBindMethod(DependencyManager.java:1028)
at org.apache.felix.scr.impl.manager.DependencyManage r.bind(DependencyManager.java:944)
at org.apache.felix.scr.impl.manager.DependencyManage r.open(DependencyManager.java:868)
at org.apache.felix.scr.impl.manager.ImmediateCompone ntManager.createImplementationObject(ImmediateComp onentManager.java:200)
at org.apache.felix.scr.impl.manager.ImmediateCompone ntManager.createComponent(ImmediateComponentManage r.java:118)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager$Unsatisfied.activate(AbstractComponentMan ager.java:997)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.activateInternal(AbstractComponentManager .java:333)
at org.apache.felix.scr.impl.manager.DependencyManage r.serviceAdded(DependencyManager.java:283)
at org.apache.felix.scr.impl.manager.DependencyManage r.serviceChanged(DependencyManager.java:170)
at org.apache.felix.framework.util.EventDispatcher.in vokeServiceListenerCallback(EventDispatcher.java:8 71)
at org.apache.felix.framework.util.EventDispatcher.fi reEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fi reServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent( Felix.java:3890)
at org.apache.felix.framework.Felix.access$000(Felix. java:79)
at org.apache.felix.framework.Felix$2.serviceChanged( Felix.java:728)
at org.apache.felix.framework.ServiceRegistry.registe rService(ServiceRegistry.java:107)
at org.apache.felix.framework.Felix.registerService(F elix.java:2979)
at org.apache.felix.framework.BundleContextImpl.regis terService(BundleContextImpl.java:313)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.registerService(AbstractComponentManager. java:449)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.registerComponentService(AbstractComponen tManager.java:460)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager$Unsatisfied.activate(AbstractComponentMan ager.java:1009)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.activateInternal(AbstractComponentManager .java:333)
at org.apache.felix.scr.impl.manager.DependencyManage r.serviceAdded(DependencyManager.java:283)
at org.apache.felix.scr.impl.manager.DependencyManage r.serviceChanged(DependencyManager.java:170)
at org.apache.felix.framework.util.EventDispatcher.in vokeServiceListenerCallback(EventDispatcher.java:8 71)
at org.apache.felix.framework.util.EventDispatcher.fi reEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fi reServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent( Felix.java:3890)
at org.apache.felix.framework.Felix.access$000(Felix. java:79)
at org.apache.felix.framework.Felix$2.serviceChanged( Felix.java:728)
at org.apache.felix.framework.ServiceRegistry.registe rService(ServiceRegistry.java:107)
at org.apache.felix.framework.Felix.registerService(F elix.java:2979)
at org.apache.felix.framework.BundleContextImpl.regis terService(BundleContextImpl.java:313)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.registerService(AbstractComponentManager. java:449)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.registerComponentService(AbstractComponen tManager.java:460)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager$Unsatisfied.activate(AbstractComponentMan ager.java:1009)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.activateInternal(AbstractComponentManager .java:333)
at org.apache.felix.scr.impl.manager.AbstractComponen tManager.enable(AbstractComponentManager.java:157)
at org.apache.felix.scr.impl.config.ConfiguredCompone ntHolder.enableComponents(ConfiguredComponentHolde r.java:256)
at org.apache.felix.scr.impl.BundleComponentActivator .loadDescriptor(BundleComponentActivator.java:253)
at org.apache.felix.scr.impl.BundleComponentActivator .initialize(BundleComponentActivator.java:147)
at org.apache.felix.scr.impl.BundleComponentActivator .<init>(BundleComponentActivator.java:111)
at org.apache.felix.scr.impl.Activator.loadComponents (Activator.java:285)
at org.apache.felix.scr.impl.Activator.bundleChanged( Activator.java:203)
at org.apache.felix.framework.util.EventDispatcher.in vokeBundleListenerCallback(EventDispatcher.java:80 7)
at org.apache.felix.framework.util.EventDispatcher.fi reEventImmediately(EventDispatcher.java:729)
at org.apache.felix.framework.util.EventDispatcher.fi reBundleEvent(EventDispatcher.java:610)
at org.apache.felix.framework.Felix.fireBundleEvent(F elix.java:3879)
at org.apache.felix.framework.Felix.startBundle(Felix .java:1850)
at org.apache.felix.framework.Felix.setActiveStartLev el(Felix.java:1192)
at org.apache.felix.framework.StartLevelImpl.run(Star tLevelImpl.java:266)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: unknown object in stream: 0
at org.bouncycastle.openpgp.PGPObjectFactory.nextObje ct(Unknown Source)
at org.bouncycastle.openpgp.PGPPublicKeyRingCollectio n.<init>(Unknown Source)
at org.springframework.roo.felix.pgp.PgpServiceImpl.g etTrustedKeys(PgpServiceImpl.java:142)
... 83 more

roo>
[org.springframework.roo.felix [45]] [org.springframework.roo.felix.pgp.PgpServiceImpl] Failed creating the component instance; see log for reason

roo>
[org.springframework.roo.felix [45]] [org.springframework.roo.felix.HttpPgpUrlStreamHand lerServiceImpl] Cannot create component instance due to failure to bind reference pgpService
Feb 7th, 2012, 10:01 PM
drinks.sobe

1 Attachment(s)

I had the same error just now ...

Code:

/ _, _/ /_/ / /_/ / /_/ |_|\____/\____/ 1.2.0.RELEASE [rev 39eb957] Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER. @ibmkhd: Introducing Spring Roo, Part 4: Rapid application development in cloud with Spring Roo and Cloud Foundry: Rapid ... http://t.co/eRT1bE6H [org.springframework.roo.felix [45]] [org.springframework.roo.felix.pgp.PgpServiceImpl] The activate method has thrown an exception org.apache.felix.log.LogException: java.lang.IllegalArgumentException: java.io.IOException: unknown object in stream: 0 at org.springframework.roo.felix.pgp.PgpServiceImpl.getTrustedKeys(PgpServiceImpl.java:152) at org.springframework.roo.felix.pgp.PgpServiceImpl.trust(PgpServiceImpl.java:168) at org.springframework.roo.felix.pgp.PgpServiceImpl.trustDefaultKeys(PgpServiceImpl.java:110)

I'm on Windows XP 32-bit with java 6 update 30

Attachment 4636
Feb 7th, 2012, 10:24 PM
drinks.sobe

Looks like it might be the key server ... http://keyserver.ubuntu.com/pks/lookup?op=get&search=

Response is...

Error handling request
Error handling request: No keys found
Feb 8th, 2012, 03:36 AM
sracenta

Seems like your roo source folder counter some problem.
When i face same kinda problem couple of days ago, i extract roo from zip file to another location.
link new location in STS setting.
make changes in maven settings to update dependacy automatic, and it will work fine
Feb 8th, 2012, 08:45 AM
dudeRK

everything worked for me after deleting the pgp key that roo downloads and puts in the Users folder on windows

so I setup roo to run in an outside shell as STS 2.8.1 seems to be very slow if running Roo within STS
Feb 8th, 2012, 09:20 AM
drinks.sobe

@dudRK

That worked, thanks for the tip!
After deleting the ".spring_roo_pgp.bpg" file in the Users folder, Roo was able to start with no exceptions.

/cheers
Feb 8th, 2012, 12:40 PM
drinks.sobe

I was able to reproduce this startup error again.

Roo was working fine in the command line shell until after I imported my multi-module maven project into STS 2.8.1.

My project has 4 modules and one of them is using DBRE with Oracle.
I followed the steps from other threads on how to get this working, basically had to install/start a 3 osgi bundles (com.springsource.javax.resource-1.5.0.jar, com.springsource.javax.transaction-1.1.0.jar, and the newly wrapped com.oracle.roo.jdbc.ojdbc6-11.2.0.3.0001.jar)
I was able to use DBRE from command-line Roo shell and rev gen the entities.

I exited out the Roo shell on the command line then created a new STS workspace.
Imported my multi-maven project (which has 4 modules), which launched 4 Roo shells ?!?
After everything loaded and finished building and validating in STS, I closed the 4 Roo shells inside of STS.
I then went back to the command line and started the Roo shell and this is when the startup error happened.

Code:

/ /_/ / / / / / / / / _, _/ /_/ / /_/ / /_/ |_|\____/\____/ 1.2.0.RELEASE [rev 39eb957] Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER. [org.springframework.roo.felix [45]] [org.springframework.roo.felix.pgp.PgpServiceImpl] The activate method has thrown an exception org.apache.felix.log.LogException: java.lang.IllegalArgumentException: java.io.IOException: invalid header encountered at org.springframework.roo.felix.pgp.PgpServiceImpl.getTrustedKeys(PgpServiceImpl.java:152) at org.springframework.roo.felix.pgp.PgpServiceImpl.trust(PgpServiceImpl.java:168)

I noticed that the Roo Home directory creates separate folders for bundle cache ... "sts-cache-[module name]" ... I had 4 of them in my Roo Home directory. When I compared them with the main cache directory I noticed the sts-cache's were missing the 3 osgi bundles I had loaded from the command line Roo Shell.

cache folder = 74 bundles
sts cache folders = 71 bundles

Is this what is corrupting the ".spring_roo_pgp.bpg" file??

Anybody have a workaround for this?
I was thinking about adding the 3 osgi jars to the Roo Home bundle directory and have Roo install/start them. Then maybe when the STS Roo shells launch they will have the all the bundles as the command line Roo shell.
Feb 8th, 2012, 03:21 PM
drinks.sobe

Quote:

Originally Posted by drinks.sobe

I was thinking about adding the 3 osgi jars to the Roo Home bundle directory and have Roo install/start them. Then maybe when the STS Roo shells launch they will have the all the bundles as the command line Roo shell.

This seemed to do the trick. :cool:

Just remember to clear out the caches and delete the sts-caches-* so that Roo can rebuild them.
Dec 7th, 2012, 05:43 AM
stevehartley

STS Roo cache directory contents

I think there is a more general problem here.

I'm running roo version 1.2.2.RELEASE [rev 7d75659]. When I run it from the command line, there are more bundles available than when I point STS at the same installation and run roo from within STS (version 3.1.0)

If I delete the sts-cache folders and .sts-cache-*-version I still only get a subset of all the bundles that the standalone version loads. Interestingly, executing from within STS shows osgi version 4.0.3 whereas from the command line it is 3.2.2. I was expecting these to be the same...

Surely this is a bug with roo - the osgi bundles loaded should be the same whether roo is executed from the command line or from within STS [for the same roo installation]?

Can anyone help or should I raise a bug with roo?

Steve

Quote:

Originally Posted by drinks.sobe

This seemed to do the trick. :cool:

Just remember to clear out the caches and delete the sts-caches-* so that Roo can rebuild them.