[Mark Aufdencamp]

Hi,

I’m running MyEclipse 9.1 on OS X (10.6.8) with the Apple supplied Java 6 JDK (1.6.0_26). I’m attempting to run Geronimo 2.2.1 as an Application Server. It will run fine from the command line when started with:

./bin/geronimo.sh start

It will not run from inside MyEclipse and fails with the following initial error message from Geronimo:

Module 7/75 org.apache.geronimo.framework/plugin/2.2.1/car 2011-09-26 22:21:52,410 ERROR [AbstractEncryption] Unable to decrypt
java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES
at javax.crypto.Cipher.getInstance(DashoA13*..)

I will try this on a Windows 7 Workstation and validate that it is an OS X issue if necessary. This same behavior/error occurs with JEE 5 and G 2.1.7 on OS X. The proper JDK JAVA_HOME and PATH have been configured in the G ./bin/setenv.sh script as well as the same JVM being selected inside MyEclipse.

Could someone provide the required App Server Connection information for running MyEclipse 9.1 and Geronimo 2.2.1 on OS X?

Thanks

Mark Aufdencamp
Mark@Aufdencamp.com

[support-joy]

Mark,

Sorry to hear you are running into this issue. I have verified this works fine on Windows with a small modification in the configuration file. Please clarify if you have set the flag schedulerSupport to “false” in activemq.xml? Based on the existing issue as reported here – https://issues.apache.org/jira/browse/GERONIMO-5635
Please modify activemq.xml in [Geronimo installation dir]\var\activemq\conf\activemq.xml
and set flag schedulerSupport to “false”
as shown here

 <broker xmlns="http://activemq.apache.org/schema/core" brokerName="${activemq.brokerName}" tmpDataDirectory="${activemq.data}/tmp_storage" useShutdownHook="false" start="false" schedulerSupport="false"> 

Next setup Geronimo app server. Ensure the JDK is set to 1.5 or higher. Let me know how this works for you.

[Mark Aufdencamp]

Adding, schedulerSupport=”false”, to the activemq.xml file DID NOT resolve this issue.

[support-tony]

Sorry that didn’t work for you, Mark

I’ve raised a bug for this, as I can replicate in on a Mac. In the meantime, I managed to start the server by doing the following:

Go to the Geronimo server connector configuration and open the JDK page. Under the Optional Java VM Arguments, add:

-Xmx256m -XX:MaxPermSize=128m 
-javaagent:<geronimo-home>/bin/jpa.jar 
-Djava.ext.dirs=<geronimo-home>/lib/ext:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext

Change <geronimo-home> to the location of your Geronimo installation. You can also increase those memory parameters, if necessary, but they are what geronimo.sh uses by default.

Let us know how that works for you.

[Mark Aufdencamp]

Thanks Tony. That worked!

[support-tony]

No problem, Mark. Thanks for letting us know it worked.

[Author]

Posts