11:07 a.m.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have two
options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one module in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-2695:
-----------------------------
Description:
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have two
options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
was:
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have two
options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one module in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
Also this error message is basically wrong:
{noformat}
22:53:34,678 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread
1-6) The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
{noformat}
since the library doesn't actually *have* to be on java.library.path.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2695:
-------------------------------------
Ah ok. I don't know where else it can be located (personally, I do install the Fedora
package, and it works fine).
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
where does the lib/name1-name2/libxxx.so, name1? name2?
module which module?
Did you look to
http://downloads.jboss.org/jbossnative//2.0.10.GA/jbossweb-native-2.0.10.jar
at least the jbossweb code could load libraries from those location.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
Whichever module actually executes System.loadLibrary() should contain the libraries. The
module does not need to do anything special to load from the module lib directory as
System.loadLibrary() will automatically look there first.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
"System.loadLibrary() will automatically look there first."
What? How? and there is where?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
There are few technical reasons why having
product/lib/${platform}-${arch}/native.so would create some issues.
1. Libraries with dependencies won't load because operating
system library loader will look for libraries only
on PATH,LD_LIBRARY_PATH,DYLD_LIBRARY_PATH which is
usually reflected in java.library.path
2. From distribution PoV it makes sense only if you
distribute the entire product as platform specific
Eg. similar to what Eclipse does.
3. Most contemporary linux distributions already provide
tomcat-native as installable package. Since it is
stored inside system library it will load without any
additional configuration (like Remy noted)
It is usually optimized at compile time to a given platform.
If we ship something this would have to be generic so it
can work on any linux.
Also linux distributions are much better in applying security
fixes then we are.
To solve #1 (dependency loading) jbossweb would have to go
trough list of dependencies and load them in reverse order
by using System.load and then call System.loadLibrary
Luckily only libapr-1.so is a dependency. Again APR could either
be provided by us or used from os distribution, so we are
basically again at #3.
Same would have to be done for any other native component.
The logical solution is to setup LD_LIBRARY_PATH (java.library.path)
before loading JVM in which case the dependencies are handled
by operating system library loader. If you have to set it up, then
the actual location where the libraries are stored is irrelevant
since this is handled by the application bootstrap code.
Enterprise distribution also contains additional modules so if we
ship that the way you propose it would mean that we would have to
load the isapi_redirect.dll or mod jk from
C:\jboss\jboss-as7\whatever-product\lib\windows-i386\x.dll
Since this is certainly not appropriate we would have to have
multiple root directories which would request fix directory names.
Other solution is to split the way how we distribute native enterprise
packages. We would need to embed some binaries inside AS and some
in a separate package (which would mean some libraries would have to
be separate). Then there is a problem how to make .rpm out of that.
Bottom line.
It makes sense if you ship everything as a bundle (both java and native code)
usually as a platform specific distribution.
In theory this could be done by merging java distribution and
*all* native distributions into a single package, which means the
native package becomes product mandatory.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk edited comment on AS7-2695 at 11/25/11 7:38 AM:
------------------------------------------------------------
There are few technical reasons why having
product/lib/${platform}-${arch}/native.so would create some issues.
1. Libraries with dependencies won't load because operating
system library loader will look for libraries only
on PATH,LD_LIBRARY_PATH,DYLD_LIBRARY_PATH which is
usually reflected in java.library.path
2. From distribution PoV it makes sense only if you
distribute the entire product as platform specific
Eg. similar to what Eclipse does.
3. Most contemporary linux distributions already provide
tomcat-native as installable package. Since it is
stored inside system library it will load without any
additional configuration (like Remy noted)
It is usually optimized at compile time to a given platform.
If we ship something this would have to be generic so it
can work on any linux.
Also linux distributions are much better in applying security
fixes then we are.
To solve #1 (dependency loading) jbossweb would have to go
trough list of dependencies and load them in reverse order
by using System.load and then call System.loadLibrary
Only libapr-1.so is a dependency, but on enterprise edition
we ship openssl as well as its own list of dependencies so the
can increase to about 10 libraries which have to be loaded in
correct order. Again APR/OpenSSL could either
be provided by us or used from os distribution, so we are
basically again at #3.
Same would have to be done for any other native component.
The logical solution is to setup LD_LIBRARY_PATH (java.library.path)
before loading JVM in which case the dependencies are handled
by operating system library loader. If you have to set it up, then
the actual location where the libraries are stored is irrelevant
since this is handled by the application bootstrap code.
Enterprise distribution also contains additional modules so if we
ship that the way you propose it would mean that we would have to
load the isapi_redirect.dll or mod jk from
C:\jboss\jboss-as7\whatever-product\lib\windows-i386\x.dll
Since this is certainly not appropriate we would have to have
multiple root directories which would request fix directory names.
Other solution is to split the way how we distribute native enterprise
packages. We would need to embed some binaries inside AS and some
in a separate package (which would mean some libraries would have to
be separate). Then there is a problem how to make .rpm out of that.
Bottom line.
It makes sense if you ship everything as a bundle (both java and native code)
usually as a platform specific distribution.
In theory this could be done by merging java distribution and
*all* native distributions into a single package, which means the
native package becomes product mandatory.
was (Author: mladen.turk):
There are few technical reasons why having
product/lib/${platform}-${arch}/native.so would create some issues.
1. Libraries with dependencies won't load because operating
system library loader will look for libraries only
on PATH,LD_LIBRARY_PATH,DYLD_LIBRARY_PATH which is
usually reflected in java.library.path
2. From distribution PoV it makes sense only if you
distribute the entire product as platform specific
Eg. similar to what Eclipse does.
3. Most contemporary linux distributions already provide
tomcat-native as installable package. Since it is
stored inside system library it will load without any
additional configuration (like Remy noted)
It is usually optimized at compile time to a given platform.
If we ship something this would have to be generic so it
can work on any linux.
Also linux distributions are much better in applying security
fixes then we are.
To solve #1 (dependency loading) jbossweb would have to go
trough list of dependencies and load them in reverse order
by using System.load and then call System.loadLibrary
Luckily only libapr-1.so is a dependency. Again APR could either
be provided by us or used from os distribution, so we are
basically again at #3.
Same would have to be done for any other native component.
The logical solution is to setup LD_LIBRARY_PATH (java.library.path)
before loading JVM in which case the dependencies are handled
by operating system library loader. If you have to set it up, then
the actual location where the libraries are stored is irrelevant
since this is handled by the application bootstrap code.
Enterprise distribution also contains additional modules so if we
ship that the way you propose it would mean that we would have to
load the isapi_redirect.dll or mod jk from
C:\jboss\jboss-as7\whatever-product\lib\windows-i386\x.dll
Since this is certainly not appropriate we would have to have
multiple root directories which would request fix directory names.
Other solution is to split the way how we distribute native enterprise
packages. We would need to embed some binaries inside AS and some
in a separate package (which would mean some libraries would have to
be separate). Then there is a problem how to make .rpm out of that.
Bottom line.
It makes sense if you ship everything as a bundle (both java and native code)
usually as a platform specific distribution.
In theory this could be done by merging java distribution and
*all* native distributions into a single package, which means the
native package becomes product mandatory.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
Look in
http://anonsvn.jboss.org/repos/jbossweb/trunk/java/org/apache/tomcat/jni/...
That is the order we use in different platforms.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
I know that technology for dependency loading exists.
I even wrote that LibraryLoader :)
Currently it uses META-INF/lib/... and it requires the physical
file system (extracted .jar) So in theory this could be also
specified inside Library.properties to create layout definable.
eg. adding
windows.prefix.i386=lib/windows-i386
windows.prefix.amd64=lib/windows-amd64
...
As long as the Library.java allows the load from the
LD_LIBRARY_PATH, and uses this as a fallback
this can be basically any layout you wish.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:51 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
{quote}
"System.loadLibrary() will automatically look there first."
What? How? and there is where?
{quote}
System.loadLibrary() always uses the caller's class loader first to locate native
libs. "There" is the "lib" directory in the module which executes
that method.
{quote}
There are few technical reasons why having
product/lib/${platform}-${arch}/native.so would create some issues.
{quote}
For #1, correct, you should either link statically or rely upon the operating system to
provide dependencies.
For #2, you have it backwards - by having arch-specific directories we allow a single
distribution which works on any operating system.
For #3, I don't see this as any different than an OS distributing Java JARs. We
don't use the OS for this case, so we shouldn't use the OS for the JNI case
either, especially given that a JNI library is so tightly bound to its JAR counterpart.
If you want to do it this way then you certainly can, but we don't normally support
the distribution of some components separately from the AS because it's a bit of a
pain from the user's perspective. If we can find a way to get around that then fine.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.CR1
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:21 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
The names are coming from
https://github.com/jbossas/jboss-modules/blob/master/src/main/java/org/jb...
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
By the way, just for reference, what David is describing is already done by HornetQ, and
their native library for the AIO journal. This already works just fine, and in fact, both
the i686 and X86_64 versions of the libraries are present.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:03 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
Use the package from the org
(http://www.jboss.org/jbossweb/downloads/jboss-native-2-0-10)
For windows the dll needs to be copied to
AS7_HOME/modules/org/jboss/as/web/main/lib/win-i686/libtcnative-1.dll
I tested winxp 32 bits and Linux 32 bits for moment they both work.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:11 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
OK, looked in that deeper, and its just changing top directory from
<jboss-as>/bin/native
to
<jboss-as>/modules/org/jboss/as/web/main/lib/${os}-${arch}
and completely relying on org.apache.tomcat.jni.LibraryLoader to
correctly load dependencies in reverse order.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
Yes the whole loading logic is based on the correct "reverse" order.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
What does ${os}-${arch} expand into?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-2695:
-----------------------------
Forum Reference: http://community.jboss.org/message/633044#633044
The OS and Arch strings are described here:
http://community.jboss.org/message/633044#633044
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:51 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
Thanks David!
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
I put the latest jboss-native into the jboss web module, using the naming convention
outline here, but I don't see anything in the log telling its using the native
connector?
Is there anything that is supposed to spit out?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:25 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
Something like:
5:31:31,343 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-1)
Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
Note the Apr in the Protocol.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
What if you have multiple modules using the same native
component? Since the .os/.dll can be loaded only once per VM
instance second invocation will always fail because JNI methods
have already been bound to a different class loader.
Next what if multiple native components have the same dependency.
Static linkage of dependencies means that dependency fix would
cause fixing all components using it.
Anyhow, setting LD_LIBRARY_PATH to a whatever location you have
installed jboss-native/native before starting AS works equally well,
so I see no reason why would this be something mandatory.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:18 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
Well, since everybody seems to be 'module' oriented
why not creating a separate module for all native components
a. Native component can be loaded only once per VM
b. In that case they could be shared among different modules
c. It would solve module redeployment cause they would
be loaded by parent class loader.
d. User could safely deploy his native component into
that module and be sure it'll be loaded by a correct
classloader
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
Jean-Frederic - you said you tested this successfully on linux. I get the following after
putting the native libraries in:
<jboss-as>/modules/org/jboss/as/web/main/lib/$<os>-$<arch>
I also noticed in my boot.log that os was Linux, and arch was amd64, so I tried
linux-x86_64, Linux-amd64, and linux-amd64, but none of them worked for me. I did notice
that linux-x86_64 is working for HornetQ though, but so far no luck in this getting picked
up. I also looked at the schema for jboss web, and native-true is the default for the
configuration, so I shouldn't need to do anything in the configuration xml.
What was your setup that worked?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller edited comment on AS7-2695 at 12/14/11 9:49 AM:
--------------------------------------------------------------
Jean-Frederic - you said you tested this successfully on linux. I get the following after
putting the native libraries in:
<jboss-as>/modules/org/jboss/as/web/main/lib/$<os>-$<arch>
07:24:39,236 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread
1-3) The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
I also noticed in my boot.log that os was Linux, and arch was amd64, so I tried
linux-x86_64, Linux-amd64, and linux-amd64, but none of them worked for me. I did notice
that linux-x86_64 is working for HornetQ though, but so far no luck in this getting picked
up. I also looked at the schema for jboss web, and native-true is the default for the
configuration, so I shouldn't need to do anything in the configuration xml.
What was your setup that worked?
was (Author: andy.miller):
Jean-Frederic - you said you tested this successfully on linux. I get the following
after putting the native libraries in:
<jboss-as>/modules/org/jboss/as/web/main/lib/$<os>-$<arch>
I also noticed in my boot.log that os was Linux, and arch was amd64, so I tried
linux-x86_64, Linux-amd64, and linux-amd64, but none of them worked for me. I did notice
that linux-x86_64 is working for HornetQ though, but so far no luck in this getting picked
up. I also looked at the schema for jboss web, and native-true is the default for the
configuration, so I shouldn't need to do anything in the configuration xml.
What was your setup that worked?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
I tested 32 bits...
I still working on an artifact that will contain the most used boxes.
I think linux-x86_64 should be the good one.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere updated AS7-2695:
-------------------------------------
Attachment: jbossweb-native.jar.jar
jar to explode in main of the web subsytem module.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Andrig Miller commented on AS7-2695:
------------------------------------
I just tried the jar, but still getting the same results. It's not picking this up.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
When adding:
+++
<logger category="org.apache.catalina.core">
<level name="DEBUG"/>
</logger>
+++
I have
+++
Caused by: java.lang.UnsatisfiedLinkError:
/home/jfclere/jboss-as-7.1.0.CR1-SNAPSHOT/modules/org/jboss/as/web/main/lib/linux-x86_64/libtcnative-1.so:
libssl.so.0.9.8: cannot open shared object file: No such file or directory, no
libtcnative-1 in java.library.path (LibraryLoader.load()): Can't find:
/home/jfclere/jboss-as-7.1.0.CR1-SNAPSHOT/standalone/tmp/bin/META-INF/lib/linux2/x64/libapr-1.so
(/home/jfclere/JAVA/jdk1.6.0_29/jre/lib/amd64/server:/home/jfclere/JAVA/jdk1.6.0_29/jre/lib/amd64:/home/jfclere/JAVA/jdk1.6.0_29/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib)
+++
It seems SSL is broken for moment.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
{quote}
What if you have multiple modules using the same native
component? Since the .os/.dll can be loaded only once per VM
instance second invocation will always fail because JNI methods
have already been bound to a different class loader.
Next what if multiple native components have the same dependency.
Static linkage of dependencies means that dependency fix would
cause fixing all components using it.
Anyhow, setting LD_LIBRARY_PATH to a whatever location you have
installed jboss-native/native before starting AS works equally well,
so I see no reason why would this be something mandatory.
Well, since everybody seems to be 'module' oriented
why not creating a separate module for all native components
a. Native component can be loaded only once per VM
b. In that case they could be shared among different modules
c. It would solve module redeployment cause they would
be loaded by parent class loader.
d. User could safely deploy his native component into
that module and be sure it'll be loaded by a correct
classloader
{quote}
What are you talking about? Modules can't be redeployed. Modules are loaded once per
VM, that's it. Anyway, there are no parent class loaders in AS 7. None of this makes
any sense... I think you must have some wrong assumption.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
{quote}
What are you talking about? Modules can't be redeployed. Modules are loaded once per
VM, that's it. Anyway, there are no parent class loaders in AS 7. None of this makes
any sense... I think you must have some wrong assumption.
{quote}
OK, my bad, wrong assumption.
So if they are fixed why is so important to have them inside module/lib directory?
This is not technical reason, its just convention you are imposing.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:36 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
Because the user then doesn't have to do any setup or configuration of system
properties or environment variables. All native code will automatically be loaded using a
single standard layout. And we can have a single distribution which covers all platforms
without special configuration steps. Either the library is there and it's loaded, or
it's not and it's skipped. And this same approach works for all other native code
too.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
What do you meany by: "Either the library is there and it's loaded, or it's
not and it's skipped"
Loaded by whom and when?
I still do not understand what are you talking about.
AS works out of box on my Fedora using tomcat-native rpm
without any setup.
Are you saying we should refuse to load anything outside module/lib?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2695:
------------------------------------------
Pff macosx is weird... It looks to lib"NAME".jnilib, why? :-(
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
Of course not. But only a small minority of people will run AS from an RPM. Most people
will unzip it or repackage it their own way. By shipping the JNI libraries with the Java
code, it will always work regardless of where it was installed. There's no reason to
treat JNI code any different from Java classes in terms of distribution.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2695:
-------------------------------------
I don't run AS 7 from a RPM, but tomcat-native is installed using the Fedora's
RPM, and it works extremely well.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:14 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
What about if you're not running on Fedora?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2695:
-------------------------------------
Heretics should be burnt at the stake, don't you know that ? :)
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
hahaha
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
{quote}
There's no reason to treat JNI code any different from Java classes in terms of
distribution.
{quote}
That's your opinion.
I would always prefer to use vendor provided native components.
We already have that supported so its just making sure .so files are
at the correct place; our is module/META-INF/lib/os/arch
So you can equally well modify your NativeLibraryResourceLoader since
I wrote that back in 2008 ;)
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-2695:
-----------------------------------
Jean-Frederic,
Since 10.4 you can use .dylib files instead of jnilib if you choose. Darwin/Mach
doesn't use ELF, so they actually have 2 different library formats. Historically
.dylib had some kind of limitation that prevented it from working in JNI (which is exactly
the intended usecase [dynamic loading]), so they had this jnilib hack thing.
Hope that helps!
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
I'm not going to argue about it any more.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:48 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-2695:
-----------------------------------
Mladen,
Why should we have inconsistent mechanisms for jni library loading?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:07 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2695:
-------------------------------------
I would prefer a nice packaging and shipping method like David is proposing, if possible.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:27 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
Jason,
Not sure what you mean by inconsistent.
Reason why jboss-native is packaged the way it is, so it
can work inside multiple AS versions each having different layout
which constantly changes with each release.
So the solution is to create separate jboss-native-as7 distribution layout
and change LibraryLoader to use the mechanism from NativeLibraryResourceLoader
although NativeLibraryResourceLoader could as well use what we made back in 2008.
BTW, the way the code in NativeLibraryLoader does not support OpenBSD or NetBSD
while supporting some weirdos like MPEI/IX
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 p.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
Just noticed that getProperty("catalina.home")
returns
/foo/bar/jboss-as-7.1.0.Beta1/standalone/tmp
Is there a way we can get
/foo/bar/boss-as-7.1.0.Beta1/modules/org/jboss/as/web/main
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere updated AS7-2695:
-------------------------------------
Attachment: (was: jbossweb-native.jar.jar)
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:22 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere updated AS7-2695:
-------------------------------------
Attachment: jbossweb.jar
jbossweb.jar to replace modules/org/jboss/as/web/main/jbossweb-7.0.5.Final.jar
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere updated AS7-2695:
-------------------------------------
Attachment: jbossweb-native.jar.jar
jar file to explode in modules/org/jboss/as/web/main
It provides support for win32/64, linux intel 32/64 and macosx intel.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar, jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:08 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
David,
Where is the code that intercepts System.loadLibrary
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar, jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:14 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2695:
----------------------------------
There is no such code, Mladen. System.loadLibrary gets the caller's class loader and
invokes its library location methods. Check out the javadoc for ClassLoader for more
info.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar, jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
Jean-Frederic forwarded me your explanation for findLibrary
Thanks.
Now, how can we make that not hard coded?
It would be nice to have some configuration file which
would be used to construct different layouts.
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar, jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:23 a.m.
[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat resolved AS7-2695.
---------------------------------
Resolution: Done
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL: https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Labels: eap6_prd_req
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar, jbossweb.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4632
days inactive
4707
days old
53 comments
12 participants
participants (12)
-
Andrig Miller (Commented) (JIRA) -
Andrig Miller (Issue Comment Edited) (JIRA)
-
David Lloyd (Commented) (JIRA)
-
David Lloyd (Created) (JIRA)
-
David Lloyd (Updated) (JIRA)
-
Jason Greene (Commented) (JIRA)
-
Jean-Frederic Clere (Commented) (JIRA)
-
Jean-Frederic Clere (Updated) (JIRA)
-
Mladen Turk (Commented) (JIRA)
-
Mladen Turk (Issue Comment Edited) (JIRA)
-
Remy Maucherat (Commented) (JIRA)
-
Remy Maucherat (JIRA)