January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2740) Infinispan BETA5 modules setup classloading issue

by Brent Douglas (Created) (JIRA)

Infinispan BETA5 modules setup classloading issue ------------------------------------------------- Key: AS7-2740 URL: https://issues.jboss.org/browse/AS7-2740 Project: Application Server 7 Issue Type: Bug Environment: jboss-as-7.1.0.Alpha2-SNAPSHOT, Infinispan 5.1.0.BETA5 Reporter: Brent Douglas Infinispan requires protected access across the core and api jars requiring a common class loader for all jars. The current module setup for as7 will have both loaded by different classloaders. Until ISPN-1547 is fixed they should be loaded as a single module. Caused by: java.lang.IllegalAccessError: tried to access field org.infinispan.CacheSupport.defaultLifespan from class org.infinispan.DecoratedCache at org.infinispan.DecoratedCache.put(DecoratedCache.java:297) [infinispan-core-5.1.0.BETA5.jar:5.1.0.BETA5] at org.infinispan.tree.CacheAdapter.put(CacheAdapter.java:257) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.atomic.AtomicHashMapProxy.getDeltaMapForWrite(AtomicHashMapProxy.java:150) [infinispan-core-5.1.0.BETA5.jar:5.1.0.BETA5] at org.infinispan.atomic.AtomicHashMapProxy.put(AtomicHashMapProxy.java:206) [infinispan-core-5.1.0.BETA5.jar:5.1.0.BETA5] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:70) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeStructureSupport.createNodeInCache(TreeStructureSupport.java:68) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeCacheImpl.put(TreeCacheImpl.java:430) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] at org.infinispan.tree.TreeCacheImpl.put(TreeCacheImpl.java:72) [infinispan-tree-5.1.0.BETA4.jar:7.1.0.Alpha2-SNAPSHOT] -- 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

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-2192) /subsystem=ejb3/service=async and /subsystem=ejb3/service=remote attributes not read-write

by David Bosschaert (Created) (JIRA)

/subsystem=ejb3/service=async and /subsystem=ejb3/service=remote attributes not read-write ------------------------------------------------------------------------------------------ Key: AS7-2192 URL: https://issues.jboss.org/browse/AS7-2192 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Beta1 Reporter: David Bosschaert Assignee: Carlo de Wolf Access type is currently read-only, see the resource description. In order to allow the user to change these trough the console they need to be read-write. Same for service=remote. {code}[standalone@localhost:9999 service=async] :read-resource-description { "outcome" => "success", "result" => { "description" => "The EJB3 Asynchronous Invocation Service", "attributes" => {"thread-pool-name" => { "type" => STRING, "description" => "The name of the thread pool which handles asynchronous invocations", "expressions-allowed" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-only", "storage" => "configuration" }}, "operations" => undefined, "children" => {} } }{code} -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (JBWEB-225) Include Tomcat SetCharacterEncodingFilter

by Cody Lerum (JIRA)

Cody Lerum created JBWEB-225: -------------------------------- Summary: Include Tomcat SetCharacterEncodingFilter Key: JBWEB-225 URL: https://issues.jboss.org/browse/JBWEB-225 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Cody Lerum Assignee: Remy Maucherat Tomcat has added a new filter https://github.com/apache/tomcat70/blob/trunk/java/org/apache/catalina/fi... which allows the user to easily set the charset to be used when decoding a request if none is specificed (ie UTF-8 instead of ISO-8859-1) Could this be included in JBoss web like the existing included filters such as http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_0_9_FINAL/java/or... so that the end user can just define this in their web.xml -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-3174) Ability to configure a Host Controller to ignore domain model changes

by Brian Stansberry (Created) (JIRA)

Ability to configure a Host Controller to ignore domain model changes --------------------------------------------------------------------- Key: AS7-3174 URL: https://issues.jboss.org/browse/AS7-3174 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.0.Final To ensure that, for example, and EAP 6.0 slave HC can run inside domain managed by an EAP 6.1 master HC, we need a mechanism to allow the slave HC to safely "ignore" commands from the master. This will allow, for example, new-in-EAP6.1 extensions and subsystems to be added to the domain config. The servers managed by the 6.0 HC could not be part of server-groups that use those new extensions/subystems, but other servers managed by other HC's could. My thought on this is to add a child element to <domain-controller>, paired with <remote> (i.e. it would not be available if <local/> is used.) Something like: <excludes> <profiles> <profile name="newstuff"/> <profile name="addedstuff"/> </profiles> </excludes> The <profiles> wrapper may not be necessary. Beside profile the following could be excluded: extension system-property path interface socket-binding-group server-group deployment rollout-plan If the user tried to add a server that used one of the excluded server-groups, it would fail with an appropriate error message. If the new server's server-group used one of the excluded profile, socket-binding-group or deployment elements it would fail, it would fail with an appropriate error message. If a non-excluded profile used an excluded extension, that would fail due to the absence of the extension. (For bonus points, in a later release would could detect why the extension was missing and give a better error message.) If some non-excluded resource relied on an excluded system property, interface or path, that would fail at runtime, as there's no reliable why to detect that situation. However, path, interface and system-property are really on the above list just to be thorough; I don't anticipate a reason why a later release would include elements in those configs that an earlier release could not handle. When we add back in the <include> element to profile and socket-binding-group we'll need to account for this as well (i.e. a non-excluded child can't include an excluded parent.) Note also that the basic rule is operation handlers should ignore parameters they do not understand, rather than failing. So the addition of some new attribute in 6.1 should not cause the add handler for a resource on a 7.1 HC/server to fail. An entirely new resource address would trigger failure though; hence the new for this JIRA. -- 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

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9039) Transaction/JTS integration for AS7

by David Lloyd (JIRA)

Transaction/JTS integration for AS7 ----------------------------------- Key: JBAS-9039 URL: https://issues.jboss.org/browse/JBAS-9039 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: Jonathan Halliday Fix For: 7.0.0.CR1 Issue to track JTS integration status. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
9
0 / 0

[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

14 years, 2 months

5
10
0 / 0

[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

14 years, 2 months

5
7
0 / 0

[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

14 years, 2 months

12
53
0 / 0

[JBoss JIRA] Created: (JBJCA-563) Test uploading file for CreateChildReport

by Lin Gao (JIRA)

Test uploading file for CreateChildReport ----------------------------------------- Key: JBJCA-563 URL: https://issues.jboss.org/browse/JBJCA-563 Project: IronJacamar Issue Type: Task Components: Management Reporter: Lin Gao Assignee: Lin Gao Priority: Minor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-3479) Apply logging rules to XTS subsytem integration

by Paul Robinson (JIRA)

Paul Robinson created AS7-3479: ---------------------------------- Summary: Apply logging rules to XTS subsytem integration Key: AS7-3479 URL: https://issues.jboss.org/browse/AS7-3479 Project: Application Server 7 Issue Type: Task Components: Transactions Affects Versions: 7.1.0.CR1b Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 7.1.0.Final Apply the following rules: https://community.jboss.org/wiki/LoggingInCoreJBossApplicationServer7 to: https://github.com/jbossas/jboss-as/tree/master/xts -- 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

14 years, 2 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012