[JBoss JIRA] Created: (JBAS-8787) Native libraries not found when using IBM JDK
by Mike Millson (JIRA)
Native libraries not found when using IBM JDK
---------------------------------------------
Key: JBAS-8787
URL: https://issues.jboss.org/browse/JBAS-8787
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: 6.0.0.Final
Reporter: Mike Millson
Assignee: Remy Maucherat
The native components are not found on x86_64 using the IBM JDK because the startup script is looking in "lib" instead of "lib64".
You get this error:
2011-01-04 16:39:37,205 INFO [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/mmillson/jboss/eap-5.1.0/jboss-as/native/lib
run.sh and run.bat set the native directory based on whether the reported version includes the string "64-bit":
IS_64_BIT_JVM=`"$JAVA" $JAVA_OPTS -version 2>&1 | $GREP -i 64-bit`
if [ "x$IS_64_BIT_JVM" != "x" ]; then
JBOSS_NATIVE_DIR="$JBOSS_NATIVE_DIR/lib64"
else
JBOSS_NATIVE_DIR="$JBOSS_NATIVE_DIR/lib"
fi
But with the IBM JDK "java -version" does not report that string:
Java(TM) SE Runtime Environment (build pxa6460sr8fp1-20100624_01(SR8 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8ifx-20100609_59383 (JIT enabled, AOT enabled)
J9VM - 20100609_059383
JIT - r9_20100401_15339ifx2
GC - 20100308_AA)
JCL - 20100624_01
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (AS7-754) Rename php licence files to html
by Radoslav Husar (JIRA)
Rename php licence files to html
--------------------------------
Key: AS7-754
URL: https://issues.jboss.org/browse/AS7-754
Project: Application Server 7
Issue Type: Enhancement
Components: Build System
Affects Versions: 7.0.0.Beta3
Reporter: Radoslav Husar
Assignee: Jason Greene
Priority: Trivial
These 3 should be renamed to to .html.
{code}
[rhusar@rhusar licenses]$ ll *.php
-rw-r--r-- 1 rhusar jbossaci 33728 Apr 19 23:59 GNU Lesser General Public License 2.1 - lgpl-2.1.php
-rw-r--r-- 1 rhusar jbossaci 20417 Apr 19 23:58 MIT License - mit-license.php
-rw-r--r-- 1 rhusar jbossaci 14340 Apr 19 23:59 The BSD License - bsd-license.php
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-8423) Ensure that connectors that handle end user request start late in the server start process
by Brian Stansberry (JIRA)
Ensure that connectors that handle end user request start late in the server start process
------------------------------------------------------------------------------------------
Key: JBAS-8423
URL: https://jira.jboss.org/browse/JBAS-8423
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.0.0.M1
Ensure all connectors that handle user requests have appropriate behavior with respect to not starting until the overall server start is in a state where the connector can handle the expected requests.
Part of this is understanding how the clients work; i.e. for some connectors clients may never send a request that the server can't correctly handle. For others, e.g. web connectors fronted by mod_jk or most hardware load balancers, once the connector is started, it may start receiving requests for apps that are not deployed.
This is somewhat related to graceful shutdown, where the connector should stop handling requests at the appropriate point in a shutdown process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-8208) Expressing configuration property metadata in domain schema
by Brian Stansberry (JIRA)
Expressing configuration property metadata in domain schema
-----------------------------------------------------------
Key: JBAS-8208
URL: https://jira.jboss.org/browse/JBAS-8208
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.0.0.M1
Clients of the domain management API are going to need to see metadata about the various items they are configuring. Besides simple type stuff, information on things like whether changes require restart, etc, need to be available.
This task is to determine where this information comes from and how it can be made available to the layer that provides it to the client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments
by David Lloyd (JIRA)
Detect, filter, and act upon system APIs found in deployments
-------------------------------------------------------------
Key: JBAS-8983
URL: https://issues.jboss.org/browse/JBAS-8983
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: 7.0.0.CR1
Implement a fixed set of package paths which are automatically filtered out of deployments. In addition, certain paths should be interpreted as an implicit dependency request.
For example if "org/slf4j" is found in a deployment, it should be filtered, and an implicit import dependency upon the org.slf4j module (which provides the org.slf4j package) should be added to the deployment.
Use sub-tasks for each API to filter or detect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months