[JBoss JIRA] Created: (JBMESSAGING-1359) JBM is not able to work with MSSQL
by Martin Vecera (JIRA)
JBM is not able to work with MSSQL
----------------------------------
Key: JBMESSAGING-1359
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1359
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core Persistence
Affects Versions: 1.4.0.SP3.CP02
Environment: SOA-P 4.2 CP02, RHEL5, MSSQL
Reporter: Martin Vecera
Assigned To: Tim Fox
Priority: Critical
Reproducible: 100%
Description: There is something that prevents MSSQL to clean deleted rows from JBM_MSG table and the disk space occupied by that table grows permanently.
I had HelloWorld ESB service listening on JMS queue. I was constantly sending messages to that queue. JBM_MSG table contains around 1000 in average - this is balanced between sender and receiver. Consumer consumes old messages, new messages are still arriving.
Every message has 5kB.
The DB grows in size during this procedure until it takes the whole disk space and make the DB unusable for JBM.
Evidence - attached files:
dbstat.csv - status report for all the tables in DB - see RowCount, DataSpace for JBM_MSG
jbm_msg.csv - content of JBM_MSG table when status report was generated
soaesb1_dbstat.sql - SQL script for generating status report
Caution: MSSQL is required in SOA-P PRD. If this cannot be solved, the requirement should be removed.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1277) Object isolation verification
by Clebert Suconic (JIRA)
Object isolation verification
-----------------------------
Key: JBMESSAGING-1277
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1277
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.1.CR1, 1.4.0.SP3.CP02
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Minor
Fix For: Stable branch
I believe there is a bug on ObjectMessage as reported by an user.
On the patch attached there is a testcase validating the Object isolation.
IMO an ObjectMessage shouldn't cache serialized objects, and it should aways return a new de-serialized object. It is user's responsibility to proper manage calls to getobject in order to not cause performance issues and excessive serialization on this case.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1429) ConcurrentModificationException is thrown from JBM MessagingQueue.java
by Tyronne Wickramarathne (JIRA)
ConcurrentModificationException is thrown from JBM MessagingQueue.java
----------------------------------------------------------------------
Key: JBMESSAGING-1429
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1429
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP02
Environment: Sybase ASE 15.02, JDBC Driver jTDS 1.2.1, JBoss-EAP-4.3_CP1, JDK -1.5.0_10
Reporter: Tyronne Wickramarathne
Assignee: Tim Fox
2008-10-08 17:57:44,955 [WorkerThread#18[10.0.15.102:49566]] ERROR org.jboss.messaging.util.ExceptionUtil - ConsumerEndpoint[g7-swt4i2mf-1-8mfqh2mf-h5u36p-x2f0a] close [i7-rwu4i2mf-1-8mfqh2mf-h5u36p-x2f0a]
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841)
at java.util.HashMap$KeyIterator.next(HashMap.java:877)
I couldn't reproduce this problem locally. However, I have noted the code segment which leads to this problem. This exception is thrown when unregisterSucker() or registerSucker() is called by the time the HashSet containing suckers are iterated. Replacing the HashSet with ConcurrentHashMap is the easiest fix it seems though the other approach is to use synchronized(lock) in the informSuckers().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months