[
https://issues.apache.org/jira/browse/TOMEE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125199#comment-13125199
]
Steve Maring commented on TOMEE-32:
-----------------------------------
I noticed in the start scripts in bin that if CATALINA_HOME is not specified it
will be based on the current directory from which execution happens, which
explains the:
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the java.library.path:
<bunch of other stuff>;C:\eclipse-helios;
I have tried explicitly setting CATALINA_HOME at the top of the scripts, but it
does not help.
The Eclipse launch configuration for the server even has this in the VM args:
-Dcatalina.base="C:\workspace-201104\.metadata\.plugins\org.eclipse.wst.server.core\tmp2"
-Dcatalina.home="C:\app\apache-tomee-webprofile-1.0.0-beta-1"
-Dwtp.deploy="C:\workspace-201104\.metadata\.plugins\org.eclipse.wst.server.core\tmp2\wtpwebapps"
-Djava.endorsed.dirs="C:\app\apache-tomee-webprofile-1.0.0-beta-1\endorsed"
but I would be inclined to say that it seems to be getting ignored, because
that is not what the logs are telling me
I should also mention that if I select "Use Tomcat Installation" for the
"Server Locations", instead of the default "Use workspace metadata" that it
seems to start just fine.
I will deem that a valid workaround for now, until I hit a bump that tells me
otherwise.
> 1.0.0-beta-1 does not start in Eclipse with the Apache Tomcat 7 server profile
> ------------------------------------------------------------------------------
>
> Key: TOMEE-32
> URL: https://issues.apache.org/jira/browse/TOMEE-32
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.0.0-beta-1
> Environment: Eclipse Helios
> Reporter: Steve Maring
> Priority: Minor
> Labels: eclipse, startup, tomcat
>
> Usage of start scripts in bin directory, from the command line, work fine.
> When attempting to start the tomee-1.0.0-beta-1 server from within Eclipse,
> as an Apache Tomcat 7 profile, you get error:
> SEVERE: Servlet threw load() exception
> java.lang.ClassNotFoundException: javax.ejb.EJB
> confirmed usage of exact same JDK in both scenarios.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
