[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ]
Clebert Suconic closed JBMESSAGING-343.
---------------------------------------
Resolution: Done
> Stress test with a large number of clients accessing the server in parallel
> ---------------------------------------------------------------------------
>
> Key: JBMESSAGING-343
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.4.0.CR1
>
>
> Push the limit of concurent clients to limit
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ]
Clebert Suconic reopened JBMESSAGING-343:
-----------------------------------------
> Stress test with a large number of clients accessing the server in parallel
> ---------------------------------------------------------------------------
>
> Key: JBMESSAGING-343
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.4.0.CR1
>
>
> Push the limit of concurent clients to limit
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ]
Clebert Suconic closed JBMESSAGING-343.
---------------------------------------
Resolution: Done
> Stress test with a large number of clients accessing the server in parallel
> ---------------------------------------------------------------------------
>
> Key: JBMESSAGING-343
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.4.0.CR1
>
>
> Push the limit of concurent clients to limit
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-343:
---------------------------------------------
Added SeveralClientsStressTest...
The test has 200 Consumers and 200 Producers... a Worker (Producer or Consumer) is closed/recreated on every minute..
The test keeps doing that for 5 minutes...
This same test is also used for SoakTests
> Stress test with a large number of clients accessing the server in parallel
> ---------------------------------------------------------------------------
>
> Key: JBMESSAGING-343
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.4.0.CR1
>
>
> Push the limit of concurent clients to limit
--
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
set/get GlobalResolver
----------------------
Key: JBRULES-994
URL: http://jira.jboss.com/jira/browse/JBRULES-994
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Reteoo
Reporter: Mark Proctor
Assigned To: Mark Proctor
Fix For: 4.0.0.MR4
We added setGlobalResolver, getGlobalResolver is also needed. Also the working memory should no longer handle any form of chaining, should just check the provided, or default, resolver.
--
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
jboss-ds-1.5.dtd is not up-to-date
----------------------------------
Key: JBAS-4528
URL: http://jira.jboss.com/jira/browse/JBAS-4528
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1
The jboss-ds-1.5.dtd is not up-to-date, e.g.
no-tx-connection-factory should support a prefill element.
All the most recent features need checking to make sure they've all been updated correctly.
--
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
ProxyMapCreator does not handle default annotation values
---------------------------------------------------------
Key: JBMICROCONT-126
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-126
Project: JBoss MicroContainer
Issue Type: Task
Components: General
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Assigned To: Kabir Khan
There is a fixme in ProxyMapCreator that says
"//TODO: Need to handle default values for annotations in jdk 1.5"
--
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
Fixme in test org.jboss.test.classinfo.support.AnnotatedSubClass
----------------------------------------------------------------
Key: JBMICROCONT-124
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-124
Project: JBoss MicroContainer
Issue Type: Task
Components: General
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Assigned To: Kabir Khan
Priority: Minor
There is a FIXME in the above class.
Kabir can you update this task to describe the problem.
--
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
Rules - in ESB Content Based Router - reports error reading rules file with CR/NL line endings
----------------------------------------------------------------------------------------------
Key: JBRULES-920
URL: http://jira.jboss.com/jira/browse/JBRULES-920
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.MR2
Environment: JBoss ESB - from svn 20070612
drools-compiler-4.0.0.11754MR2.jar
drools-core-4.0.0.11754MR2.jar
drools-decisiontables-4.0.0.11754MR2.jar
drools-jsr94-4.0.0.11754MR2.jar
Reporter: Len DiMaggio
Assigned To: Mark Proctor
Priority: Minor
Attachments: MyESBRules-XPath.drl.CRNL
It's a non-fatal error:
ERROR [STDERR] line 7:0 no viable alternative at character '\r'
The problem was first reported here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110672
--
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