[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-2735) Error: libapr-1.dll was not found starting JBossAS in JBoss IDE

[hmr_mueller (JIRA)]

Error: libapr-1.dll was not found starting JBossAS in JBoss IDE
---------------------------------------------------------------

                 Key: JBIDE-2735
                 URL: https://jira.jboss.org/jira/browse/JBIDE-2735
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: JBossAS
    Affects Versions: 2.1.2
         Environment: Eclipse: 3.3.1.1
OS: Windows 
JBoss AS 4.2.2GA JBossWeb native
            Reporter: hmr_mueller


When starting the JBossAS 4.2.2GA with JBoss Web native configured from within a JBoss Server configured with the Eclipse IDE (JBoss Tools), I'm getting the error '... libapr-1.dll was not found ..' as a popup. After closing the popup for 3 times the server starts, but does so with errors when starting the Tomcat https connector. When running the run.bat script from the command line everything works fine.
Tomcat is configured to used the AprLifecycleListener and a https connector for APR (OpenSSL style configuration).
The server launch configuration in eclipse contains the $JBOSS_HOME\bin\native directory in the -Djava.library.path variable

The problem seems to be that the libtcnative-1.dll is loading the libapr-1.dll dynamically but since the Path environment variable does not contain the $JBOSS_HOME\bin\native directory the library is not found (setting this is done by the run.bat script).
If I put the native directory in the Path variable, the server starts up correctly, so just defining the java.library.path in the launch configuration does not suffice.
The problem can be fixed I think, if instead of setting the java.library.path the launch configuration extends the environment (Tab Environment) to contain the native directory in the Path environment variable and changing the class 
org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType to add this to the 'VMRunnerConfiguration' in the 'actualLaunch' method.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira