I am working on eclipse kepler rcp. I am using osgi bundles. when i startup the application I am always getting the following message
Enabling components of bundle com.p2pframework.main did not complete in 30000 ms
!ENTRY org.eclipse.equinox.ds 2 0 2014-03-10 00:03:09.774 !MESSAGE
[SCR - WorkThread] Timeout occurred! Thread was blocked on processing
[QueuedJob] WorkPerformer:
org.eclipse.equinox.internal.ds.SCRManager#104e583; actionType 1
Related
I've recently set up my mac for code reviewing using p4v for file syncing/ changelists and ccollab for the review platform. Versions are:
MacOS - 10.15.7
Perforce - P4V/MACOSX1015X86_64/2020.1/1966006
ccollab client - 13_1_13100
Via the coollabgui app, I have the SCM verified and connected with no errors. I am unable to add pending changelists for review, but I can add submitted changelists. What's more is I'm able to submit files for review by manually uploading them through the web client. The big headache comes when I attempt to use the smartbear custom tool that installation builds into P4V. Attempting to right-click and add any changelist results in the following error:
No SCM Configuration could be determined
Cannot run program "p4" (in directory "/Applications/ccollab_client/ccollabgui.app"): error=2, No such file or director
I have reviewed the following other topics on the smartbear forums and found no solutions:
https://community.smartbear.com/t5/Collaborator/quot-No-SCM-could-be-determined-quot-p4-plugin-does-...
https://community.smartbear.com/t5/Collaborator/Config-p4-plugin-on-Mac/m-p/44317
Any ideas? It's looking like this could be a potential bug.
latest log info is:
!SESSION 2020-11-30 09:13:08.279 -----------------------------------------------
eclipse.buildId=unknown
java.version=11
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
!ENTRY com.smartbear.collaborator.ui.standalone 4 0 2020-11-30 09:13:09.284
!MESSAGE Collaborator Enterprise version 13.1.13100
!ENTRY com.smartbear.collaborator 1 0 2020-11-30 09:13:11.024
!MESSAGE INFO: Mon Nov 30 09:13:11 EST 2020: com.smartbear.util.PoolThreadFactory
Thread CommandRunner-1325903125-1 created by thread ModalContext
!ENTRY com.smartbear.collaborator 1 0 2020-11-30 09:13:11.035
!MESSAGE INFO: Mon Nov 30 09:13:11 EST 2020: com.smartbear.util.PoolThreadFactory
Thread CommandRunner-1325903125-2 created by thread ModalContext
!ENTRY com.smartbear.collaborator 1 0 2020-11-30 09:13:11.060
!MESSAGE INFO: Mon Nov 30 09:13:11 EST 2020: com.smartbear.util.PoolThreadFactory
Thread CommandRunner-1325903125-3 created by thread ModalContext
!SESSION 2020-11-30 09:13:26.372 -----------------------------------------------
eclipse.buildId=unknown
java.version=11
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
!ENTRY com.smartbear.collaborator.ui.standalone 4 0 2020-11-30 09:13:27.238
!MESSAGE Collaborator Enterprise version 13.1.13100
!ENTRY com.smartbear.collaborator.ui 4 0 2020-11-30 09:13:28.388
!MESSAGE No SCM Configuration could be determined
!STACK 0
com.smartbear.scm.ScmConfigurationException: Cannot run program "p4" (in directory "/Applications/ccollab_client/ccollabgui.app"): error=2, No such file or directory
at com.smartbear.scm.impl.newp4.P4System.getClientConfiguration(P4System.java:135)
at com.smartbear.scm.impl.newp4.P4System.getClientConfiguration(P4System.java:85)
at com.smartbear.scm.impl.perforce.PerforceSystem.getClientConfiguration(PerforceSystem.java:119)
at com.smartbear.scm.ScmUtils.requireScm(ScmUtils.java:591)
at com.smartbear.collaborator.ui.standalone.wizards.StandaloneScmConfigAddToReviewWizard$1.run(StandaloneScmConfigAddToReviewWizard.java:82)
at com.smartbear.collaborator.ui.wizards.ProgressWizardDialog$AsyncWorkerThread.run(ProgressWizardDialog.java:231)
Caused by: com.smartbear.cmdline.ScmCommunicationException: Cannot run program "p4" (in directory "/Applications/ccollab_client/ccollabgui.app"): error=2, No such file or directory
at com.smartbear.scm.cmd.impl.ScmCmdRunner.run(ScmCmdRunner.java:32)
at com.smartbear.scm.impl.newp4.cli.P4CliConn.executeTextCmd(P4CliConn.java:147)
at com.smartbear.scm.impl.newp4.cli.P4CliConn.<init>(P4CliConn.java:80)
at com.smartbear.scm.impl.newp4.P4System.getClientConfiguration(P4System.java:120)
... 5 more
Caused by: java.io.IOException: Cannot run program "p4" (in directory "/Applications/ccollab_client/ccollabgui.app"): error=2, No such file or directory
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
at com.smartbear.scm.cmd.impl.CommandRunner.run(CommandRunner.java:70)
at com.smartbear.scm.cmd.impl.AutoDebugCommandRunner.run(AutoDebugCommandRunner.java:48)
at com.smartbear.scm.cmd.impl.ScmCmdRunner.run(ScmCmdRunner.java:27)
... 8 more
Caused by: java.io.IOException: error=2, No such file or directory
at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:340)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:271)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
... 12 more
Just heard back from the smartbear community and got it fixed. In case someone else tries googling their way to success and needs the answer, it was this for me:
In the P4v client, select "Tools | Manage custom Tools | SmartBear - Add to Review" and click "Edit".
In the "Arguments" field, add the "--p4 your_current_path_to_p4" option after "--scm perforce".
Note: Don't change any other options.
Click "OK", restart the P4v client, and try to reproduce the issue.
I can't reproduce the tutorial to deploy this application on wildfly.
I downloaded the wildfly and started wildfly-19.1.0.Final/bin/standalone.sh
And when I execute from project directory mvn clean wildfly:deploy I get this error
15:12:55,016 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.module.service."deployment.app-authz-jee-vanilla.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.app-authz-jee-vanilla.war".main: WFLYSRV0179: Failed to load module: deployment.app-authz-jee-vanilla.war
at org.jboss.as.server#11.1.1.Final//org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:116)
at org.jboss.msc#1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads#2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads#2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: org.jboss.modules.ModuleNotFoundException: org.keycloak.keycloak-authz-client
at org.jboss.modules.Module.addPaths(Module.java:1266)
at org.jboss.modules.Module.link(Module.java:1622)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:299)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:283)
at org.jboss.as.server#11.1.1.Final//org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:93)
... 8 more
15:12:55,021 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "app-authz-jee-vanilla.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.app-authz-jee-vanilla.war\".main" => "WFLYSRV0179: Failed to load module: deployment.app-authz-jee-vanilla.war
Caused by: org.jboss.modules.ModuleNotFoundException: org.keycloak.keycloak-authz-client"}}
15:12:55,022 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "app-authz-jee-vanilla.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.app-authz-jee-vanilla.war\".main" => "WFLYSRV0179: Failed to load module: deployment.app-authz-jee-vanilla.war
Caused by: org.jboss.modules.ModuleNotFoundException: org.keycloak.keycloak-authz-client"}}
15:12:55,034 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment app-authz-jee-vanilla.war (runtime-name: app-authz-jee-vanilla.war) in 11ms
I tried running on docker wildfly and other example applications and worked. I don't have any experience in java. What can I do to have this app up and running?
With the command wildfly-19.1.0.Final/bin/standalone.sh, you are running keycloak on Wildfly.
Please use a different Wildfly server to host your servlet application. To communicate with the Keycloak running on the other server, you need "Keycloak OpenID Connect Client Adapter" installed into your Wildfly server which runs the servlet application.
You may use this guide to install the keycloak adapter into the wildly server. After you install this adapter into the new Wildfly, org.keycloak.keycloak-authz-client module will be available on this Wildfly.
However still there is a blocker for the latest java version [above java 11].
In my case, the WildFly not started 100% successfully. In the 'standalone.xml' file's end, there are some ports which maybe not available to you. Check for the logs, disable/move conflicting ports.
We're setting up a new staging server (running Ubuntu), and are encountering errors when starting WildFly. The main one seens to be
java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
which then causes many errors about missing dependencies.
We have set up our (liquibase) database on another server, which we can ssh into internally. We've scoured StackOverflow as well, and attempted to add
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=**true**"
to our standalone.conf, standalone.bat, and standalone.conf.bat (for the sake of having tried everything!). We also saw that this should've been fixed in WildFly 7.1.1, we're running 9 ourselves (to emulate the live server).
We tried manually installing the dependencies but there are so many - and honestly we think that's just not the main issue.
We're also running nginx and Redis, we saw in the server.log (see below) that the error happens after "Started Hibernate Redis cache" but the error itself seems to be specific to WildFly.
A chunk of server.log is below:
2019-04-03 10:52:38,252 INFO [com.company.ejb.util.config.ConfigRetriever] (ServerService Thread Pool -- 56) Successfully found and read the config file at /opt/wildfly/config.yml
2019-04-03 10:52:38,300 INFO [com.company.ejb.entity.cache.RedisRegionFactory] (ServerService Thread Pool -- 56) Started Hibernate Redis cache
2019-04-03 10:52:46,896 INFO [org.jboss.weld.Event] (MSC service thread 1-2) WELD-000411: Observer method [BackedAnnotatedMethod] com.sun.jersey.server.impl.cdi.CDIExtension.processAnnotatedType(#Observes ProcessAnnotatedType<Object>) receives events for all annotated types. Consider restricting events using #WithAnnotations or a generic type with bounds.
2019-04-03 10:52:47,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."DoThePublish.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."DoThePublish.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:161)
at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:151)
at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:417)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.createSubcontext(InitialContext.java:298)
at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:425)
[...]
2019-04-03 10:52:47,078 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "DoThePublish.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"DoThePublish. ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"DoThePublish.ear\".WeldStartService: Failed to
start service
Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:161)
at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:151)
at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:417)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.createSubcontext(InitialContext.java:298)
at org.jboss.as.naming.NamingContext.createSubcontext(NamingContext.java:425)
[...]
"}}
2019-04-03 10:52:47,178 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) WFLYSRV0010: Deployed "DoThePublish.ear" (runtime-name : "DoThePublish.ear")
2019-04-03 10:52:47,186 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."DoThePublish.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."DoThePublish.ear".WeldStartService: Failed to start service
2019-04-03 10:52:47,581 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2019-04-03 10:52:47,582 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2019-04-03 10:52:47,582 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 42472ms - Started 4599 of 5108 services (362 services failed or missing dependencies, 209 services are lazy, passive or on-demand)
Then following that there's a bunch of missing dependencies (there's looaaaads of these):
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".component.AbstractEntityMainSB.CREATE (missing) dependents: [service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".component.AbstractEntityMainSB.START]
service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".component.AbstractEntityMainSB.START (missing) dependents: [service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".moduleDeploymentRuntimeInformationStart, service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".deploymentCompleteService]
service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".component.AbstractEntityMainSB.VIEW."com.company.ejb.session.AbstractEntityMainSBL".LOCAL (missing) dependents: [service jboss.deployment.subunit."DoThePublish.ear"."CoreEjb.jar".component.AbstractEntityMainSB.START]
We've tried comparing the setup to the existing production (live) server, but there has been a big turnaround in the dev team so no-one knows exactly how they're set up. There are no setup instructions so we're trying things as we go along - perhaps the previous server encountered these same issues but we've no idea.
We are wanting to fix this exception to hopefully be able to start wildfly (and thus our website) without issues (or at least move on to the next error...) Any help is greatly appreciated!
So after a bunch of trying, we figured it out. The line we tried to implement needed to be changed a bit:
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true"
So we removed the 'set' and removed the asterisks and stuff. In our case it was the .conf file that needed the line, I believe for different types of implementations it might be the .bat or .conf.bat - sorry I can't help further with that.
Hope this helps someone else!
I recently got this same error on startup of JBOSS EAP 7.2 and Wildfly 12. In my case, it's an old Hibernate Java application. The mapping of entities in the hibernate.cfg.xml. My problem was that someone put the name attribute in the <session-factory name="">, and that particular application goes up two contexts! On the startup of the second context, I get the error:
java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
Removing the name from the session-factory solved the problem.
When trying to run Appcelerator Studio getting this error
Ive tried to reinstall Studio with all libraries and caches, nothing works.
OSX 10.10.4 (14E46)
Java 8 Update 60
An error has occurred.
See the log file
~/Appcelerator_Studio_Workspace/.metadata/.log.
!SESSION 2015-08-20 19:53:03.688 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.9.0-ea
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=ru_RU
Framework arguments: -keyring /Users/user/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/user/.eclipse_keyring -consoleLog -showlocation
!ENTRY org.eclipse.core.resources 2 10035 2015-08-20 19:53:05.671
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.core.net 1 0 2015-08-20 19:53:06.419
!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
!ENTRY org.eclipse.osgi 4 0 2015-08-20 19:53:17.256
!MESSAGE Application error
!STACK 1
java.lang.NoClassDefFoundError: org/w3c/dom/stylesheets/StyleSheetList
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:759)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 44 more
!ENTRY org.eclipse.core.jobs 2 2 2015-08-20 19:53:17.680
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.usage.internal.DefaultAnalyticsEventHandler$1
To fix this issue you need to switch JavaVirtualMachines from jdk1.9.0.jdk to jdk1.7.0_80.jdk or 1.6.0.jdk
/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/
I googled this for hours but I couldn't find anything useful.
I have developed some OSGi bundles and now I want to run them outside of the Eclipse IDE in the equinox container, but it always throws an exception:
!SESSION 2011-01-03 14:26:58.958 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_CH
Framework arguments: -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true -console;
Command-line arguments: -consoleLog -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true -console;
!ENTRY org.eclipse.osgi 4 0 2011-01-03 14:26:59.567
!MESSAGE Error starting bundle: initial#reference:file:javax.transaction_1.1.1.v201006150915.jar/
!STACK 0
org.osgi.framework.BundleException: A fragment bundle cannot be started: javax.transaction_1.1.1.v201006150915 [49]
at org.eclipse.osgi.framework.internal.core.BundleFragment.startWorker(BundleFragment.java:228)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startBundle(EclipseStarter.java:1133)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startBundles(EclipseStarter.java:1126)
at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:646)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:301)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at org.eclipse.core.runtime.adaptor.EclipseStarter.main(EclipseStarter.java:150)
init dd core...
!ENTRY org.eclipse.osgi 4 0 2011-01-03 14:26:59.773
!MESSAGE Bundle javax.transaction_1.1.1.v201006150915 [49] is not active.
(the "init dd core..." text comes properly from my project.)
I have the following file structure:
+configuration
+config.ini
+ch.thobens.dd.commands_1.0.0.jar
+ch.thobens.dd.common.items_1.0.0.jar
+ch.thobens.dd.core_1.0.0.jar
+ch.thobens.dd.game_1.0.0.jar
+javax.transaction_1.1.1.v201006150915.jar
+org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar
+org.eclipse.core.jobs_3.5.0.v20100515.jar
+org.eclipse.core.runtime.compatibility.auth_3.2.200.v20100517.jar
+org.eclipse.core.runtime.compatibility.registry_3.3.0.v20100520/runtime_registry_compatibility.jar
+org.eclipse.core.runtime_3.6.0.v20100505.jar
+org.eclipse.equinox.app_1.3.0.v20100512.jar
+org.eclipse.equinox.common_3.6.0.v20100503.jar
+org.eclipse.equinox.preferences_3.3.0.v20100503.jar
+org.eclipse.equinox.registry_3.5.0.v20100503.jar
+org.eclipse.osgi.services_3.2.100.v20100503.jar
+org.eclipse.osgi_3.6.0.v20100517.jar
and my config.ini file has the following contents:
osgi.bundles=javax.transaction_1.1.1.v201006150915.jar#start, org.eclipse.core.contenttype_3.4.100.v20100505-1235.jar#start, org.eclipse.core.jobs_3.5.0.v20100515.jar#start, org.eclipse.core.runtime.compatibility.auth_3.2.200.v20100517.jar#start,org.eclipse.core.runtime.compatibility.registry_3.3.0.v20100520/runtime_registry_compatibility.jar#start, org.eclipse.core.runtime_3.6.0.v20100505.jar#start, org.eclipse.equinox.app_1.3.0.v20100512.jar#start, org.eclipse.equinox.common_3.6.0.v20100503.jar#2:start, org.eclipse.equinox.preferences_3.3.0.v20100503.jar#start, org.eclipse.equinox.registry_3.5.0.v20100503.jar#start, org.eclipse.osgi.services_3.2.100.v20100503.jar#start, ch.thobens.dd.commands_1.0.0.jar#start, ch.thobens.dd.common.items_1.0.0.jar#start, ch.thobens.dd.core_1.0.0.jar#start, ch.thobens.dd.game_1.0.0.jar#1:start
eclipse.ignoreApp=true
osgi.noShutdown=true
The bundles that are listed here are the same bundles that are selected if I select "Add required Plug-ins" in the run configuration. If I run these bundles from the Eclipse PDE, it works fine.
Additionally, there is no difference between running the command
java -jar org.eclipse.osgi_3.6.0.v20100517.jar -consoleLog -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true
and when I use the equinox launcher (via eclipse.exe).
Thanks for any help
I found the solution (through the eclipse product exporter):
The javax.transaction_1.1.1.v201006150915.jar is not an OSGi bundle itself, it's an OSGi framework extension.
I had to change the config.ini file:
Remove the entry for the
javax_transaction bundle in the
property osgi.bundles
added the following line:
osgi.framework.extensions=javax.transaction_1.1.1.v201006150915.jar