[JBoss JIRA] Created: (JBRULES-2998) MVEL performance regression
by Lukáš Petrovický (JIRA)
MVEL performance regression
---------------------------
Key: JBRULES-2998
URL: https://issues.jboss.org/browse/JBRULES-2998
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M2
Reporter: Lukáš Petrovický
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.0.CR1
I'm filing this JIRA to track the performance regression talked over recently at the rules-dev mailing list. Blocker priority per Ḿark's off-list suggestion. Quote follows:
On 26/04/2011 15:53, Wolfgang Laun wrote:
> A simple rule containing an eval with a % b == 0 exhibits a considerable slowdown when comparing execution times between a Drools core built in February and the one there is now.
>
> The slow-down factor is 15.
There is a performance issue with MVEL. We moved to indexed (array based) mvel factories, which is suppose to give faster performance. However the MVEL author has not finished that work completely and so far they give a performance regression :( I'm pestering him daily on this.
Mark
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (AS7-699) create a new service to activate RA with method activate(ra.xml, ironjacamar.xml, classloader)
by Stefano Maestri (JIRA)
create a new service to activate RA with method activate(ra.xml, ironjacamar.xml, classloader)
----------------------------------------------------------------------------------------------
Key: AS7-699
URL: https://issues.jboss.org/browse/AS7-699
Project: Application Server 7
Issue Type: Feature Request
Components: JCA
Reporter: Stefano Maestri
Assignee: Stefano Maestri
Fix For: 7.0.0.Beta4
the method will get the necessary metadata representation and the classloader and will activate a ra. The necessary java code for ra is not deployed but it's cosidered already loaded by the given classloader.
Consider also a variant taking ra.xml and ij.xml as string containing the xml and proved parse too. Anyway the priority is on metadata variant
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-1857) Request on reconnection behavior
by Roger Hui (JIRA)
Request on reconnection behavior
--------------------------------
Key: JBMESSAGING-1857
URL: https://issues.jboss.org/browse/JBMESSAGING-1857
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Roger Hui
When a fail-over occurs (local or remote disaster recovery) the JMS clients connections must automatically re-connect to the active JMS server. Under no circumstances will the JMS clients need to re-create JMS objects (Connections, Sessions, Producers, and Consumers). Though exceptions can be thrown on edge conditions, the expectation is that operations on the JMS Producer and Consumer objects will blocked while the re-connection is complete. Once the connection enters "reconnect mode", it should block until the configured reconnect-retry-attempts are exhausted. The Exception listener should only invoked if re-connect has failed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBAS-9312) JBossAsManagedContainer prematurely thinks the AS is started
by Brian Stansberry (JIRA)
JBossAsManagedContainer prematurely thinks the AS is started
------------------------------------------------------------
Key: JBAS-9312
URL: https://issues.jboss.org/browse/JBAS-9312
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: 7.0.0.Beta2
Reporter: Brian Stansberry
Assignee: Shelly McGowan
It starts and then loops until it can connect to the JMX server. That's premature.
It should wait until it can connect to the management socket and query the management layer for server state. The server will need to add an operation to expose the state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months