|
Re: Scout+Gemini JPA [message #1086872 is a reply to message #1084916] |
Wed, 14 August 2013 21:23 |
Cesar Henriques Messages: 8 Registered: August 2013 |
Junior Member |
|
|
Hi Guys, I just have solved the issue.
The main problem seems to be related to the order on wich every bundle is started and (I don't know why) some bundles doesn't start automatically.
I have solved the problem adding the following parameters to the launch product
Program argument
-console -clean
VM ARgument
-Xms64m
-Xmx512m
-XX:MaxPermSize=256m
-Dosgi.console.enable.builtin=true
-Dosgi.noShutdown=true
-Declipse.ignoreApp=false
-DGEMINI_DEBUG
and adding a explicit bundle start order in the config.ini
### Eclipse Runtime Configuration File
osgi.noShutdown=true
eclipse.ignoreApp=false
eclipse.product=org.openlex.server.product
osgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@start, org.eclipse.equinox.http.jetty@start, org.eclipse.equinox.http.registry@start, org.eclipse.core.runtime@start, javax.persistence@start, org.apache.derby@start, org.eclipse.persistence.core@start, org.eclipse.persistence.jpa@start, org.eclipse.gemini.jpa@start, org.eclipse.persistence.jpa.jpql@start, myPersistenceUnit@start, myPersistenceDAO@start,
osgi.bundles.defaultStartLevel=4
Regards
|
|
|
|
Powered by
FUDForum. Page generated in 0.04210 seconds