[
https://issues.jboss.org/browse/JBIDE-8461?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8461:
------------------------------------
The reason no java.library.path is being set for EAP 5.1 is because no such native folder
exists. The user can open the launch configuration and add his own overriding for the java
library path by setting the flag in vm arguments. (Open server editor, click "Open
launch configuration", and add the flag to the vm args.)
In the event no flag is set (lib folder not manually set by user), the launch
configuration attempts to set a default. The default is assumed to be at
{serverHome}/bin/native. If that folder does not exist, no native flag is set. The
property being set to the string you mentioned is probably just your system's default
native folder.
Editing AS Launch Configuration -Djava.library.path
---------------------------------------------------
Key: JBIDE-8461
URL:
https://issues.jboss.org/browse/JBIDE-8461
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Environment: Win7 64-bit, 32-bit 1.6 JVM
Reporter: Burr Sutter
Assignee: Rob Stryker
Labels: as_backwards
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: native_lib_editing1.png, native_lib_editing2.png
It seems that you can not make changes to -Djava.library.path on the Launch configuration
properties. In addition, dropping your native libs into this directory are not recognized
when the server is launched - I am trying to add the JBoss Native tc-native1.dll to my
AS6
The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
D:\servers\jboss-6.0.0.Final\bin\native;
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira