[
https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin...
]
Daniel Chapman commented on JBOSGI-625:
---------------------------------------
K I've found a way to recreate the issue consistently - found this while trying to get
infinispan capabilities added to OSGI SubSystem.
So with a clean 7.1.3.Final EAP 6.0.1 Runtime environment - edit Standalone-full.xml osgi
subsystem for following capabilities:
<capability name="javax.servlet.api:v25"/>
<capability name="javax.transaction.api"/>
<capability name="org.apache.felix.log"
startlevel="1"/>
<capability name="org.jboss.osgi.logging"
startlevel="1"/>
<capability name="org.apache.felix.configadmin"
startlevel="1"/>
<capability name="org.jboss.as.osgi.configadmin"
startlevel="1"/>
<capability name="org.jboss.marshalling"/>
<capability name="org.jboss.marshalling.river"/>
<capability name="org.jgroups"/>
<capability name="sun.jdk"/>
<capability name="javax.cache:cache-api:0.5"/>
<capability
name="org.apache.aries:org.apache.aries.util:1.0.0"/>
<capability
name="org.apache.aries.proxy:org.apache.aries.proxy:1.0.0"/>
<capability
name="org.apache.aries.blueprint:org.apache.aries.blueprint:1.0.0"/>
<capability
name="org.infinispan:infinispan-core:5.1.8.Final-redhat-1"/>
Start server - go into OSGI Console and start all the bundles. Successfully puts the
checkmark next to all of them. Server restart looks good and all bundles still in started
state.
Now stop server, add capability:
<capability
name="org.infinispan:infinispan-cdi:5.1.8.Final"/>
Note: I chose 5.1.8.Final because that is what ships in modules dir of eap 6.0.1.
Server starts with bundle in installed state. Go into console - start the bundle, all
hell breaks loose. Primary error is with missing javax.cache [0.4,1):
Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve
HostBundleRevision[org.infinispan.cdi:5.1.8.Final]: missing requirement
AbstractPackageRequirement[atts={osgi.wiring.package=javax.cache,
version=[0.4,1)},[org.infinispan.cdi:5.1.8.Final]]
Which as you could see before I was able to have javax.cache started successfully before
adding infinispan-cdi capability.
Now here's the recreate part... restart server. Blueprint disappeared. Looks
installed, but not listed and not startable on console. Even after you remove the
infinisipan-cdi capability. At one point I could see blueprint in the console without
checkmark, but in trying to start it nothing happens, no log msgs. Just refreshes
console.
I am able to fix this by blowing away the standalone/data and standalone/tmp directory...
haven't done further research into which one causes problem.
So this issue is with funky starting/stopping and not being able to recover properly. But
I wouldn't mind if I could get some help on enabling infinispan-cdi while we're at
it.
Dan C.
Start level not valid message
-----------------------------
Key: JBOSGI-625
URL:
https://issues.jboss.org/browse/JBOSGI-625
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.1.1
Environment: Jboss as 7.1.2.Final
JDK6
EAP 6.0.0
Reporter: Daniel Chapman
Assignee: Thomas Diesler
Priority: Minor
When I set org.jboss.osgi.framework to DEBUG, I get messages like the following:
11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10)
Starting bundle: org.apache.aries.blueprint:1.0.0
11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start
level [2] not valid for: org.apache.aries.blueprint:1.0.0
I'd like more information on this message. I've seen it during various startup
configurations in messing with my capabilities and it seems to matter little when fixing
real issue.
What I'm doing above is clicking the Start Bundle button in the osgi console. It
prints these two messages as DEBUG, nothing else is printed, and net result is console
refreshes and no changes have been made to the status of the bundle.
So is this message really relevant, if so - then why DEBUG only. Second - what do I do
when I got to start a module, nothing is printed to logs (except above) and the bundle
doesn't actually start?
Thanks!
--
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