This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Status: 500 Internal Server Error occurs when run the Depot Application Jruby Sample application Steps To Reproduce: 1. Install NB 6.5 Trunk build (09/15/2008) with bundled with GF V3 b24 build 2. Create New Jruby project by select File > New Project > Sample > Ruby > Depot Application 3. Right-click at the Depot Application project, select Properties > change the server to Glassfish V3 and port to 8080 4. Select to run the project BUG: Nothing is displayed on the browser after the run and exception occurs in the log files
Created attachment 69992 [details] messages.log
Created attachment 69993 [details] server.log
The error message shows that the Jruby connector in GlassFish v3 needs to know about where the jruby installation is. So basically netbeans needs to start glassfish v3 and pass -Djruby.home to the directory where jruby installation directory is. Peter Williams may have more info on this as how to start glassfish for rails app deployment. ---------- [#|2008-09-15T17:26:32.562- 0700|SEVERE|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=14;_ThreadName=Thread-3;|Exception while deploying the app java.lang.RuntimeException: JRuby installation not found at C:\sun\glassfishv3-prelude-b24\glassfish\modules\jruby. You may like to do one of the following: - Use updatetool to install JRuby and Rails installation. - Check if the 'jruby.home' Java sysytem property is pointing to your JRuby installation. - If on Unix or Mac, create a symbolic link of your jruby installation to C:\sun\glassfishv3-prelude- b24\glassfish\modules\jruby. - Install JRuby at C:\sun\glassfishv3-prelude-b24\glassfish\modules\jruby - Set 'jruby.home' inside $GLASSFISH_INSTALL/domains/domain1/config/domain.xml to the location of your JRuby directory. Make an entry of <jvm-options>-Djruby.home=...</jvm-options> inside <java-config> element. at org.glassfish.scripting.rails.sniffer.RailsSniffer.setup(RailsSniffer.java:131) at com.sun.enterprise.v3.server.ContainerStarter.startContainer(ContainerStarter.java:101) at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainer(ApplicationLifecycle.java:683) at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:339) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:191) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:290) ---------------
jruby.home is defined correctly. server log is not valid for debug session that this issue is about. The problem appears to be due to jar packaging changes in GlassFish recently. The first promoted build they appear in is B24 (the one this issue is filed against).
pickup half of pcw's issues
I followed these steps and got an error message from Rails... which is expected... since there are additional steps necessary to run the app. Closing as WFM
Comment on attachment 69993 [details] server.log .
Sorry for posting the dot, but I had no other way to know which bug is the attechment, found through google, attached to.
For someone who would get this error with JBoss AS 5.1, "mapped-name is required for UserTransaction of deployment" change @Resource to @Resource(mappedName="java:comp/UserTransaction")