January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3527) Upgrade JBoss Transactions to 4.16.2.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created AS7-3527: ---------------------------------- Summary: Upgrade JBoss Transactions to 4.16.2.Final Key: AS7-3527 URL: https://issues.jboss.org/browse/AS7-3527 Project: Application Server 7 Issue Type: Task Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Trivial Critical JTS recovery issue discovered -- 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

[JBoss JIRA] Created: (AS7-1804) Fix the Web Services description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix the Web Services description providers for the improved validation in jboss-as-subsystem-test -------------------------------------------------------------------------------------------------- Key: AS7-1804 URL: https://issues.jboss.org/browse/AS7-1804 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Alessio Soldano Fix For: 7.1.0.Alpha1 I added a test called WebServicesSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows: @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } @Override protected boolean isValidateOperations() { //TODO fix providers https://issues.jboss.org/browse/AS7-1789 return false; } Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes The above is standard text as I'm going through and creating tests. The test has been @Ignored due to a further failure once validation 'passes' (i.e. the validation is not run due to the flags set) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
7
0 / 0

[JBoss JIRA] (AS7-3490) Rewrite WS subsystem schema

by Richard Opalka (JIRA)

Richard Opalka created AS7-3490: ----------------------------------- Summary: Rewrite WS subsystem schema Key: AS7-3490 URL: https://issues.jboss.org/browse/AS7-3490 Project: Application Server 7 Issue Type: Task Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.1.0.Final There are many issues with current WS subsystem schema plus there are many configuration elements that are not supported at all :( The solution is to simplify and rewrite current schema to list and allow configure only supported features. -- 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
5
0 / 0

[JBoss JIRA] (AS7-2908) App client should have java: namespace available from all threads

by Stuart Douglas (Created) (JIRA)

App client should have java: namespace available from all threads ----------------------------------------------------------------- Key: AS7-2908 URL: https://issues.jboss.org/browse/AS7-2908 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.0.Beta1 Reporter: Stuart Douglas Assignee: John Bailey -- 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-2977) Add sun.io package to the sun.jdk module

by Robert Reimann (Created) (JIRA)

Add sun.io package to the sun.jdk module ---------------------------------------- Key: AS7-2977 URL: https://issues.jboss.org/browse/AS7-2977 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.Beta1 Reporter: Robert Reimann Please add the sun.io package to the sun.jdk module to support IBM DB2 JDBC drivers. Current DB2 JDBC drivers require access to the sun.io package as described in http://www.ibm.com/developerworks/forums/message.jspa?messageID=14230275 Otherwise it is likely to get the following exception: {com.ibm.db2.jcc.a.SqlException: [jcc][t4][10199][10462][4.0.100] Required character converter is not available. ERRORCODE=-4220, SQLSTATE=null at com.ibm.db2.jcc.a.yc.a(yc.java:55) at com.ibm.db2.jcc.a.yc.a(yc.java:119) at com.ibm.db2.jcc.a.dc.a(dc.java:1788) at com.ibm.db2.jcc.a.dc.n(dc.java:496) at com.ibm.db2.jcc.a.dc.F(dc.java:1262) at com.ibm.db2.jcc.a.mk.d(mk.java:938) at com.ibm.db2.jcc.a.mk.getString(mk.java:916) at com.ibm.db2.jcc.a.mk.getString(mk.java:1368) at org.jboss.jca.adapters.jdbc.WrappedResultSet.getString(WrappedResultSet.java:1359)} After adding the following path to the sun.jdk module descriptor ($JBOSS_HOME/modules/sun/jdk/main/module.xml), the required character converter classes are found and the application behaves as expected: {<path name="sun/io"/>} -- 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
3
0 / 0

[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

14 years, 2 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

14 years, 2 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

14 years, 2 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

14 years, 2 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

14 years, 2 months

3
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