[JBoss JIRA] (AS7-3276) NPE thrown in SecurityContextAssociationValve.
by Jeremy Whiting (Created) (JIRA)
NPE thrown in SecurityContextAssociationValve.
----------------------------------------------
Key: AS7-3276
URL: https://issues.jboss.org/browse/AS7-3276
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: On any platform running Java.
OpenJDK 6.
Reporter: Jeremy Whiting
Assignee: Remy Maucherat
With a debugger attached to AS7 I am seeing a NullPointerException thrown in a JBoss implementation of a Valve. This happens on every web request that does not have a principle in the session. The exception type has never appeared in logs because it is caught and a generic message is displayed.
This affects the performance.
Also the class uses the debugf logging method in the catch block. But does not pass in a format. A format is expected as the first parameter to the debugf method.
Included with this JIRA is a patch to change the code so that null references are detected. The second change changes the logging method call to instead use debug. Whether it should be a error message rather than a debug is a different matter and this JIRA does not tackle the question.
Regards,
Jeremy
--
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 years, 8 months
[JBoss JIRA] (AS7-2974) Web fragments and annotations are processed although web.xml is metadata-complete
by Robert Panzer (Created) (JIRA)
Web fragments and annotations are processed although web.xml is metadata-complete
---------------------------------------------------------------------------------
Key: AS7-2974
URL: https://issues.jboss.org/browse/AS7-2974
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.Beta1
Environment: JBoss 7.1.0.Beta1 (Current Snapshot), Win7 64Bit, Jdk 1.6.0_29 64Bit
Reporter: Robert Panzer
Assignee: Remy Maucherat
When deploying a web application the WarMetaDataProcessor merges information from web-fragment.xmls and annotations although the web.xml has an attribute metadata-complete="true"
The specification is pretty clear about how this scenario has to be handled and defines in chapter 8.4:
Deployment descriptor metadata-complete process annotations and web fragments
web.xml 2.5 Yes No
web.xml 2.5 no yes
web.xml 3.0 yes no
web.xml 3.0 no yes
--
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 years, 8 months
[JBoss JIRA] (AS7-2695) Package APR native libraries correctly
by David Lloyd (Created) (JIRA)
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
12 years, 8 months