[
https://issues.apache.org/jira/browse/KARAF-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392829#comment-17392829
]
Amichai Rothman commented on KARAF-6210:
----------------------------------------
I originally reported simple steps to reproduce on stock karaf, and also
attached the full karaf log when recreating it... I'm really sorry but I'm not
sure what more I can add :-/
It's a race condition, so naturally it isn't 100% reproducible all the time,
and can occur more often on some systems than others (due to threading
differences, cpu speed, disk speed, OS, or sheer random luck). The point is,
it's still happening, and has been for years now, and is quite annoying... at
least we have a workaround (also a bit annoying), but still I think it
shouldn't be doing this at all, obviously there's a bug somewhere. And as I
found out yesterday when upgrading to 4.3.2 - it's still here, and the issue
shouldn't be closed imho.
> NoClassDefFoundError: org/apache/karaf/shell/api/action/Action when starting
> Karaf
> ----------------------------------------------------------------------------------
>
> Key: KARAF-6210
> URL: https://issues.apache.org/jira/browse/KARAF-6210
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.4
> Environment: Stock Karaf 4.2.4 on Windows 10 with latest Oracle JDK 8.
> Reporter: Amichai Rothman
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Attachments: karaf_command_not_found.log
>
>
> When starting karaf using equinox and some bundle in the deploy folder, many
> shell commands (such as bundle:* and others) are not recognized, and the log
> shows NoClassDefFoundError: org/apache/karaf/shell/api/action/Action. Some
> commands don't work, but others (e.g. shell:*) do.
> This happens consistently on Windows 10, but not on Linux, not sure why.
>
> Steps to recreate:
> 1. Extract stock Karaf 4.2.4.
> 2. In etc/config.properties change karaf.framework=felix to
> karaf.framework=equinox.
> 3. Place org.apache.aries.transaction.blueprint-2.2.0.jar (from maven) in
> deploy folder. This is not the only bundle it happens with, just a public one
> I found for this example. From several I tried, some recreated the issue and
> some did not. The bundle is not resolved due to missing dependencies.
> 4. Start Karaf.
> 5. Try to run bundle:list and it'll say command not found. Or look at the
> karaf log and see "java.lang.NoClassDefFoundError:
> org/apache/karaf/shell/api/action/Action". Use shell completion to see that
> some commands are available but others are not.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
