November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1422) Set clustered to false by default in persistence configs

by Tim Fox (JIRA)

Set clustered to false by default in persistence configs -------------------------------------------------------- Key: JBMESSAGING-1422 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1422 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 1.4.0.SP3.CP04, 1.4.1.GA We should set clustered to false by default in our persistence-service configs. It's a classic user mistake to copy e.g. mysql-persistence-service.xml over to the AS in a non clustered config, but forget to set clustered to false -- 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

17 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1395) Testsuite hangs on windows after SelectorTest

by Phillip Thurmond (JIRA)

Testsuite hangs on windows after SelectorTest --------------------------------------------- Key: JBMESSAGING-1395 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1395 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP03 Environment: Windows 2003, MySQL DB Reporter: Phillip Thurmond Assigned To: Clebert Suconic Fix For: Stable branch Attachments: ant-launcher.dump, RMITestServer.dump The testsuite hangs after running SelectorTest remotely. This leaves two java processes: the ant launcher process, and the RMITestServer process. Thread dumps from each of these are attached. -- 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

17 years, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1402) Node failure does not trigger failover for new nodes entering the cluster.

by Jay Howell (JIRA)

Node failure does not trigger failover for new nodes entering the cluster. -------------------------------------------------------------------------- Key: JBMESSAGING-1402 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1402 Project: JBoss Messaging Issue Type: Bug Reporter: Jay Howell Assignee: Tim Fox When a node fails, users are reporting that the failure doesn't trigger a cluster failover. When a member starts back up and tries to join, it experiences a failure trying to reconnect to the downed node causing the container not to start. Users are getting.. 2008-07-18 08:42:53,211 144578 DEBUG [org.jboss.messaging.core.impl.postoffice.GroupMember] (main:) We are the first member of the group so no need to wait for state 2008-07-18 08:42:53,221 144588 INFO [STDOUT] (UpHandler (MPING):) ------------------------------------------------------- GMS: address is 69.52.50.155:7900 ------------------------------------------------------- 2008-07-18 08:42:56,251 147618 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying 2008-07-18 08:43:02,303 153670 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying 2008-07-18 08:43:10,791 162158 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying 2008-07-18 08:43:15,811 167178 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying 2008-07-18 08:43:20,832 172199 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying 2008-07-18 08:43:25,852 177219 WARN [org.jgroups.protocols.pbcast.GMS] (main:) join(69.52.50.155:7900) sent to 69.52.24.96:7900 timed out, retrying which occurs every 5 seconds and prevents the container from starting up. -- 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

17 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1417) Provide thread pools with ordered executors for session threads

by Tim Fox (JIRA)

Provide thread pools with ordered executors for session threads --------------------------------------------------------------- Key: JBMESSAGING-1417 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1417 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assignee: Tim Fox Fix For: 1.4.0.SP3.CP04 Currently, each session on both server and client side maintains its own thread. If a very large number of sessions are created this can results in a large number of threads created which may be a problem on some operating systems. We can fairly easily remedy this by using a static OrderedExecutorFactory initialised with a cached thread pool and JBMThreadFactory for both client and server session threads. This is the way it is currently done in JBM 2.0 -- 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

17 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1428) JBM stops processing message due to switch to PULL ServerInvokerCallbackHandler

by Clebert Suconic (JIRA)

JBM stops processing message due to switch to PULL ServerInvokerCallbackHandler ------------------------------------------------------------------------------- Key: JBMESSAGING-1428 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1428 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP03 Reporter: Jiri Pechanec Assignee: Tim Fox Fix For: 1.4.0.SP3.CP04 This issue links JBPAPP-1219 -- 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

17 years, 8 months

2
5
0 / 0

[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

17 years, 8 months

6
32
0 / 0

[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

17 years, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1293) Document that Sybase cuts the payload according to pagesize by deafult

by Jiri Pechanec (JIRA)

Document that Sybase cuts the payload according to pagesize by deafult ---------------------------------------------------------------------- Key: JBMESSAGING-1293 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1293 Project: JBoss Messaging Issue Type: Feature Request Components: Documentation and Training Affects Versions: 1.4.1.CR1 Reporter: Jiri Pechanec Assigned To: Tim Fox When the database is created it sets the maximum size of text and image datatypes to page size. It is by default 2 KB. The longer message payload is truncated without any information or warning. The database parameters has to be updated. http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15... http://infocenter.sybase.com/help/topic/com.sybase.help.ase_15.0.omni_ug/... -- 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

17 years, 8 months

4
9
0 / 0

[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

17 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1378) ClassLoaderJMXWrapper simplification

by Clebert Suconic (JIRA)

ClassLoaderJMXWrapper simplification ------------------------------------ Key: JBMESSAGING-1378 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1378 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: 1.4.0.SP3_CP03, 1.4.0.SP4 During the upgrade of AOP, per JBMESSAGING-1267 we discovered an issue on the ClassLoading as specified in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=133377&start=0 To avoid future problems, I have changed the usage of JMXClassLoading on the AOP, as pointed out that is the correct usage. -- 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

17 years, 8 months

2
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008