[JBoss JIRA] Created: (JBMESSAGING-1162) JBM takes eons to startup with topic persisted messages within db
by Gabriele Garuglieri (JIRA)
JBM takes eons to startup with topic persisted messages within db
-----------------------------------------------------------------
Key: JBMESSAGING-1162
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1162
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core Persistence
Affects Versions: 1.4.0.SP1
Environment: Java 1.5.0_14
JBoss 4.2.2
Solaris 10, AMD Opteron biprocessor machine
Reporter: Gabriele Garuglieri
Assigned To: Tim Fox
Priority: Critical
The problem is reproduced as follows:
1-Start server
2-start a producer that inserts persisted messages (we tried 90.000 messages) in TestTopic topic with default configuration where there are some consumers subscribed but not active
3-stop producer and orderly shutdown the server
4-start server
During server startup JBM executes a select to load the persisted messages id's then executes 180 selects loading 500 messages at time.
With 90.000 messages those 180 selects takes about 10 minutes. The DBMS is Oracle 10g with dedicated instance on a separate machine with no more than 1% cpu load during test and physical db on a very fast NAS.
While JBM is executing those selects, obviously the server startup hangs until the load is finished.
--
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
18 years
[JBoss JIRA] Created: (JGRP-652) ReplicaetdHashMapTest fails
by Bela Ban (JIRA)
ReplicaetdHashMapTest fails
---------------------------
Key: JGRP-652
URL: http://jira.jboss.com/jira/browse/JGRP-652
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Fix For: 2.7
[email from Robert Newson]
The ViewDeliveryDemo was testing a new feature, it was not the code I sent to Vlad or the code we discussed for the atlanta test. The ViewDeliveryDemo works fine for me once I suppress sending messages after block() as per your change.
The test I'm struggling with is the ReplicatedMapDemo which I gave to Vlad several days before writing the ViewDeliveryDemo, sorry for any confusion, but the atlanta lab were testing before I wrote the VDD, so I'm not sure how we got muddled.
I've reattached the demo in question.
Also, I can confirm that I've written a separate test to demonstrate the losslessness of MessageDispatcher with a zero timeout. It seems to work, though on occasion a VM will block indefinitely on the cast (even though the other boxes are still receiving replies from it), probably a coding error on my part, but fyi.
For clarity, the only test the Atlanta lab should run is ReplicatedMapDemo and with these arguments (5 N 50) where N is the total number of nodes. For more stress, increase the first and last parameter (the first is number of maps, the second the number of entries). All boxes should print "PASSED" within some reasonable number of retries (the retry number indicates how long it took for all the puts everywhere to arrive, it polls). It should be started on all boxes concurrently and needs to be run a number of times. I find that it seldom reaches "PASSED" on all boxes though, curiously can reach passed on some but not others (even though map.put() is synchronous)...
I have a workaround where I multiplex my own maps over a single, non-multiplexed channel, which works but is far from ideal.
--
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
18 years
[JBoss JIRA] Created: (JBRULES-1341) Analytics fails on Inner Class Enums
by Steve Shabino (JIRA)
Analytics fails on Inner Class Enums
------------------------------------
Key: JBRULES-1341
URL: http://jira.jboss.com/jira/browse/JBRULES-1341
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0
Reporter: Steve Shabino
Drools Analytics fails when flattening a condition with an inner-class enum like this:
vs : WorkerStatus(type != WorkerStatus.Type.ON_JOB)
NPE in PackageDescrFlattener when executing method:
private void flatten(QualifiedIdentifierRestrictionDescr descr, AnalyticsComponent parent, int orderNumber)
on line:
restriction.setVariableId(variable.getId());
Running in the debugger proves that variable == null.
One can reproduce this error by running analytics on the "dispatch" example in contrib/benchmarks
--
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
18 years