January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3529) mod_cluster stickySessionForce should default to false if running a HA profile

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3529: ----------------------------------- Summary: mod_cluster stickySessionForce should default to false if running a HA profile Key: AS7-3529 URL: https://issues.jboss.org/browse/AS7-3529 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Having stickySessionForce* mod_cluster set to true by default IMHO defeats the whole purpose of using HA, if the client is going to end up with error returned anyway. I propose if we are running AS7 the default should be false and failover should be just transparent and with ASYNC having a stale session is better than returning an error. I guess the configuration should keep in mind that mod_cluster is primarily used with HA clusters. This makes most sense with standalone Tomcat only. *Return an error when the request cannot be routed to the right node. -- 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

1
2
0 / 0

[JBoss JIRA] (AS7-2175) EJB thread pools not changeable through management API

by David Bosschaert (Created) (JIRA)

EJB thread pools not changeable through management API ------------------------------------------------------ Key: AS7-2175 URL: https://issues.jboss.org/browse/AS7-2175 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: David Bosschaert Assignee: Carlo de Wolf The EJB thread pools that can be managed through /subsystem=ejb3/thread-pool=* have the access type on their attributes set as read-only. This means that a user can only change these by removing a thread pool and then re-adding it with different values. These attributes should really be read-write IMHO. -- 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

2
1
0 / 0

[JBoss JIRA] (AS7-3454) Resolve logging & message ids overlap in ejb3

by Carlo de Wolf (JIRA)

Carlo de Wolf created AS7-3454: ---------------------------------- Summary: Resolve logging & message ids overlap in ejb3 Key: AS7-3454 URL: https://issues.jboss.org/browse/AS7-3454 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: Carlo de Wolf Assignee: jaikiran pai Fix For: 7.1.0.Final As per https://community.jboss.org/wiki/LoggingIds the range of reserved ids for ejb3 is 14100 - 14399. There are however messages falling outside of this range. -- 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

3
3
0 / 0

[JBoss JIRA] (AS7-2727) Remove Infinispan core module's dependency on Infinispan commons

by Brent Douglas (Created) (JIRA)

Remove Infinispan core module's dependency on Infinispan commons ---------------------------------------------------------------- Key: AS7-2727 URL: https://issues.jboss.org/browse/AS7-2727 Project: Application Server 7 Issue Type: Bug Environment: Ubuntu 10.10, AS7 master branch, Infinispan 5.1.0.BETA4 (bundled) Reporter: Brent Douglas $JBOSS_HOME/modules/org/infinispan/main/module.xml has a dependency on infinispan commons which is included in core. 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.BETA4.jar:5.1.0.BETA4] 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.BETA4.jar:5.1.0.BETA4] at org.infinispan.atomic.AtomicHashMapProxy.put(AtomicHashMapProxy.java:206) [infinispan-core-5.1.0.BETA4.jar:5.1.0.BETA4] 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.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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-3275) Extraneos logging of "ISPN000149: Fetch persistent state and purge on startup are both disabled"

by Radoslav Husar (Created) (JIRA)

Extraneos logging of "ISPN000149: Fetch persistent state and purge on startup are both disabled" ------------------------------------------------------------------------------------------------- Key: AS7-3275 URL: https://issues.jboss.org/browse/AS7-3275 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro Priority: Minor Fix For: 7.1.0.Final Looks like this is not intentional, there is a lot of this logging after https://github.com/jbossas/jboss-as/pull/1054 CR3 upgrade. Also at startup, but this happens with each request to a JSF for instance: :-) {noformat} 14:54:26,451 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,451 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,453 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,453 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,454 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,455 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,455 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup 14:54:26,455 WARN [org.infinispan.configuration.cache.LoaderConfigurationBuilder] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) ISPN000149: Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup {noformat} -- 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

3
2
0 / 0

[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

12 years, 8 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

12 years, 8 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

12 years, 8 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

12 years, 8 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

12 years, 8 months

8
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012