[Rick Ross]

We have been having some difficulties launching Resin 3.0.14 Pro from within Eclipse using MyEclipseIDE. The license key is apparently seen by some part of Resin as it starts up, but none of the Pro features like caching and clustering can be used. Further, the config file lines that would govern these features cause problems when starting up in MyEclipseIDE.

The exact same Resin Pro with the same config file and JDK starts perfectly as standalone. It is only when launching from inside MyEclipseIDE that we have observed this problem. We have confirmed it on multiple machines, and it has been easy to reproduce.

1 – Do a fresh install of Eclipse 3.1.1 and MyEclipseIDE 4.01.

2 – Download and unzip a fresh copy of Resin Pro from caucho.com/ Install your license file and confirm that standalone startup is operating correctly.

3 – Configure Resin as an appserver in MyEclipseIDE and try to launch it. We immediatly get an rror from line 98 of the config file complaining about use of the “cluster” directive with a non-Pro version of Resin.

Scott or Riyad, please feel free to contact me if you need a license file for testing. We know the Caucho guys pretty well and could probably get you set up quickly.

Thanks,
Rick Ross
rick@javalobby.org

[Riyad Kalla]

Rick,
If you could send a demo pro license file to support@genuitec.com ATTN Riyad (with a link to this post and instructions on where the file goes) and I’ll get on this ASAP. Scott mentioned that it might be the difference between an optional argument that might be causing the startup issue, either way we’ll get it figured out. Do you know how to explicitly tell Resin Pro where the license file is located?

In the mean time as a temporary workaround, if your team needs to they can connect to the (externally launched) remote server and still get all the debugging features offered when you launch from within MYEclipse: http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/remotedebugging/index.html

[Riyad Kalla]

Rick,
Thank you for the prompt email, the problem is our connector forgets to add the pro.jar file to the classpath to run the Pro version, we are fixing that as I type this. Additionally to fix the setup on your machine all you should need to do is navigate to: Window > Preferences > MyEclipse > Application Servers > Resin 3 > Paths, click “Add” next to “Append to Classpath” and navigate to your <resin dir>/lib directory and add the pro.jar file, then click OK and restart your server.

[Rick Ross]

Wow! I am so impressed with the way you guys handle things, Riyad! Really awesome, and thank you for the quick fix.

Rick

[Author]

Posts