[JBoss JIRA] Created: (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM
by Galder Zamarreno (JIRA)
EJB timer service should use a thread pool to avoid OOM
-------------------------------------------------------
Key: EJBTHREE-1330
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1330
Project: EJB 3.0
Issue Type: Bug
Components: pool
Affects Versions: AS 4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
The default EJB timer service used by the EJB3 layer is based on
org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates
to the standard org.jboss.ejb.txtimer.EJBTimerService.
For EJB3 beans using the EJB timer service the thread local pool should not be used.
Since the current EJB timer service creates a new thread for each timer being created, the
thread local pool will create a matching instance of the bean for that thread. Thus the number
of active instances in total can effectively grow unchecked and thus an OOM will occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-3583) CLI: data-source add command argument jndi-name not mandatory
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3583:
-------------------------------------
Summary: CLI: data-source add command argument jndi-name not mandatory
Key: AS7-3583
URL: https://issues.jboss.org/browse/AS7-3583
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
The data-source add command argument "jndi-name" is not mandatory. The CLI allows exection of data-source add command without specifying jndi name. Enabling such data-source fails.
[standalone@localhost:9999 /] data-source add --name=TestDS2 --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
[standalone@localhost:9999 /] data-source enable --name=TestDS2
JBAS010436: Failed to create DataSource instance for [{
"operation" => "enable",
"address" => [
("subsystem" => "datasources"),
("data-source" => "TestDS2")
],
"persistent" => undefined
}]
reason: IJ010068: Missing required attribute jndi-name in org.jboss.as.connector.subsystems.datasources.ModifiableDataSource
--
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, 10 months
[JBoss JIRA] (JBRULES-3355) Problems when writing rhs in Rule API
by Edson Tirelli (JIRA)
Edson Tirelli created JBRULES-3355:
--------------------------------------
Summary: Problems when writing rhs in Rule API
Key: JBRULES-3355
URL: https://issues.jboss.org/browse/JBRULES-3355
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.4.0.Beta1, 5.3.1.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.3.2.Final, 5.4.0.Beta2
Description of problem:
There are several problems when writing rhs of a rule in Rule API:
- if you omit rhs() you 'nullend' on the end of the rule which results in
compile error
- if you put comment in rhs() like rhs("//consequences") you get
'//consequencesend' which result in compile error as well
I think there should be line delimiter behind rhs and that if rhs is omitted it
should result in empty string rather than "null".
KnowledgeDescr descr = DescrFactory.newPackage().name("org.sample")
.newRule().name("results in consequencesend")
.rhs("//consequences")
.end()
.newRule().name("results in nullend")
.lhs()
.pattern("String").end()
.end()
.end()
.getDescr();
--
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, 10 months