Follow up:

When i shutdown the framework before undeploy, it works fine.
I would assume that JBoss discards the old classloader / creates a new
classloader when i redeploy the ear, especially since we use the
classloader-per-ear configuration (not the JBoss default).

Regards,
Peter.


2009/5/6 Peter Doornbosch <[email protected]>

> Hi,
>
> I'm running Felix (1.6.0) embedded in an ear that is deployed in JBoss. Was
> quite easy, works like charm, compliments for you guys!
>
> Now i'm running in an issue that i don't understand when i hot-deploy the
> ear.
> Here is the case.
> When I autostart Felix with only the shell bundle and the remote shell
> bundle, everything works fine. Hot deploy of the ear works without problem
> (although i should add that during undeploy of the ear, felix is not
> shutdown (shutted-down? shutdowned? ;-)), which for example leads to a
> bindexception when the remote shell is started - but apart from that it
> works fine).
>
> But... When I autostart Felix with these bundles and the fileinstall
> bundle, the hot deploy results in the following error (note that the initial
> startup works fine):
>
> java.lang.NoClassDefFoundError: org/apache/felix/framework/FilterImpl
>     at org.apache.felix.framework.Felix.addServiceListener(Felix.java:2434)
>     at
> org.apache.felix.framework.BundleContextImpl.addServiceListener(BundleContextImpl.java:203)
>     at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:270)
>     at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:235)
>     at org.apache.felix.fileinstall.FileInstall.start(FileInstall.java:51)
>
> And the same for the other two bundles, e.g.
>
> java.lang.NoClassDefFoundError: org/apache/felix/framework/FilterImpl
>     at org.apache.felix.framework.Felix.addServiceListener(Felix.java:2434)
>     at
> org.apache.felix.framework.BundleContextImpl.addServiceListener(BundleContextImpl.java:203)
>     at org.apache.felix.shell.impl.Activator.start(Activator.java:66)
>
> I don't have a clue, something weird is happening here.
> Maybe it is related to the fact that felix is not properly shutdown before
> the redeploy? (i will try to test that scenario right away)
> Any ideas?
>
> Regards
> Peter
>
>

Reply via email to