[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
13 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
13 years, 7 months
[JBoss JIRA] (AS7-5501) AS7 allows use of weak ciphers for management console https
by R Stokoe (JIRA)
R Stokoe created AS7-5501:
-----------------------------
Summary: AS7 allows use of weak ciphers for management console https
Key: AS7-5501
URL: https://issues.jboss.org/browse/AS7-5501
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: R Stokoe
Assignee: Anil Saldhana
This is a security vulnerability.
Default accepted ciphers should be stronger or method should be provided to specify allowed ciphers as with the web subsystem.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-5934) RAR inside EAR: deployment issues
by Marcel Šebek (JIRA)
Marcel Šebek created AS7-5934:
---------------------------------
Summary: RAR inside EAR: deployment issues
Key: AS7-5934
URL: https://issues.jboss.org/browse/AS7-5934
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.4.Final (EAP)
Reporter: Marcel Šebek
Assignee: Jesper Pedersen
I'm having troubles with deploying inbound RARs inside EARs. For example, the test ear attached to AS7-5471 is sometimes deployed successfully and sometimes not, it seems that the probability does not depend on the fact whether it is the first deployment or redeployment. The exception is:
[org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test-ear.ear"."test-rar-2.0.0-SNAPSHOT.rar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "test-rar-2.0.0-SNAPSHOT.rar" of deployment "test-ear.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException
at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:182)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.4.Final-SNAPSHOT.jar:7.1.4.Final-SNAPSHOT]
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:351)
at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:332)
at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:139)
... 6 more
A bigger project with MDB and @ResourceAdapter annotation sometimes fails (and sometimes not) with the following exception:
[org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."adapter-snmp-ear.ear"."adapter-snmp-ejb.jar".component.InboundMDB.CREATE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."adapter-snmp-ear.ear"."adapter-snmp-ejb.jar".component.InboundMDB.CREATE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: java.lang.IllegalStateException: JBAS014331: No resource adapter registered with resource adapter name adapter-snmp-ear.ear#adapter-snmp-rar
at org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:83)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:89)
at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:91)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.start(MessageDrivenComponentCreateService.java:76)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
--
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
13 years, 7 months