[JBoss JIRA] (AS7-4637) Get core resources and operations out of the controller module
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4637:
-------------------------------------
Summary: Get core resources and operations out of the controller module
Key: AS7-4637
URL: https://issues.jboss.org/browse/AS7-4637
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server.
Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff.
--
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
11 years, 7 months
[JBoss JIRA] (AS7-5418) Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5418:
-------------------------------------
Summary: Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"
Key: AS7-5418
URL: https://issues.jboss.org/browse/AS7-5418
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource handler will catch the UOE and leave the attribute undefined, but the description says it's not nillable.
Specifically, PlatformMBeanDescriptions.getThreadingResource()'s THREAD_CPU_TIME_ENABLED attribute, although there may well be others.
This leads to this unit test failure on jvms where the UOE is thrown:
failure message="thread-cpu-time-enabled is undefined"
type="junit.framework.AssertionFailedError">junit.fra mework.AssertionFailedError: thread-cpu-time-enabled is undefined
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.validateResource(PlatformMBeanResourceUn
itTestCase.java:595)
at org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.basicResourceTest(PlatformMBeanResourceUnitTestCase.java:563)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.testThreadingMXBean(PlatformMBeanResourceUnitTestCase.java:340)
--
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
11 years, 7 months
[JBoss JIRA] (AS7-5879) Eliminate imports of jboss-as-controller classes from arquillian modules
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5879:
-------------------------------------
Summary: Eliminate imports of jboss-as-controller classes from arquillian modules
Key: AS7-5879
URL: https://issues.jboss.org/browse/AS7-5879
Project: Application Server 7
Issue Type: Task
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.CR1
The arquillian modules have some imports of classes in the jboss-as-controller module in client-side classes. I've seen them in the ManagementClient classes; there may be others. Basically imports of string constants and some static utility methods.
The controller module is a server side module and its classes should not leak out to client-side code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (AS7-2390) Warnings ARJUNA16037, ARJUNA16038 in log file
by Robert Petermeier (Created) (JIRA)
Warnings ARJUNA16037, ARJUNA16038 in log file
---------------------------------------------
Key: AS7-2390
URL: https://issues.jboss.org/browse/AS7-2390
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.0.1.Final
Environment: Windows 7, Windows Server 2008
Reporter: Robert Petermeier
Assignee: Jonathan Halliday
Priority: Minor
We keep seeing the following warning messages in our log files every 2m, 10s:
12:05:29,290 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac146de0:3231b1f3:4ea67b21:4acc, node_name=1, branch_uid=0:ffffac146de0:3231b1f3:4ea67b21:4ad5, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@79453076 >
On another system these are intermixed with
14:41:27,440 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86a7, node_name=1, branch_uid=0:ffffac1448a6:-7e9454f8:4e86f7c3:86ab, eis_name=unknown eis name >
We are using JBoss 7 in standalone mode, with three datasources. One of them is an XA datasource (a H2 database with class org.h2.jdbcx.JdbcDataSource on one system, oracle.jdbc.xa.client.OracleXADataSource on another). JDBC drivers for Oracle and H2 are deployed as jars in standalone/deployments along with our app.
--
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
11 years, 7 months
[JBoss JIRA] (JBRULES-3692) memory leak occurs with problem fact change
by Radovan Synek (JIRA)
Radovan Synek created JBRULES-3692:
--------------------------------------
Summary: memory leak occurs with problem fact change
Key: JBRULES-3692
URL: https://issues.jboss.org/browse/JBRULES-3692
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.5.0.Final
Reporter: Radovan Synek
Assignee: Geoffrey De Smet
When using Planner with DroolsScoreDirector, after each problem fact change, number of planning entity instances increases.
Steps to reproduce:
1. open cloud balance example with GUI, choose the largest input
2. start solving the problem
3. delete some of the listed computers - to make the fact change (for me, 5 computers in a 5 seconds are enough)
4. take a heapdump (I used jmap -dump:live,file=... to enforce GC first)
5. open visualvm or similar tool and look for the planning entity class
6. repeat 3. - 5. several times, you should see increasing number of planning entity instances
Also, there is a rule base holding sessions under the Planner API - and number of sessions also increases in time (these sessions reference to planning entity instances).
Steps to reproduce:
1. open the last heapdump in similar tool and look for ReteooRuleBase.
2. the rule base holds ObjectHashSet with stateful sessions in its entries
3. you should see a different number of these session in every heapdump taken in previous recipe
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months