July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1841) JBM_MSG_REF primary key update performance issue (possible timeout/failure)

by Gerald Turner (JIRA)

JBM_MSG_REF primary key update performance issue (possible timeout/failure) --------------------------------------------------------------------------- Key: JBMESSAGING-1841 URL: https://issues.jboss.org/browse/JBMESSAGING-1841 Project: JBoss Messaging Issue Type: Enhancement Components: JMS Clustering, Messaging Core Persistence Affects Versions: 1.4.3.GA Environment: JBoss 5.1.0.GA in "all" configuration, PostOffice has FailoverOnNodeLeave = true, using MySQL Cluster 7.1.9a backend (ndb-persistence-service.xml) Reporter: Gerald Turner The JBM_MSG_REF table has primary key MESSAGE_ID+CHANNEL_ID. On cluster node failover a statement is run that changes CHANNEL_ID, thus modifies the primary key - an expensive operation. UPDATE JBM_MSG_REF SET CHANNEL_ID = ? WHERE CHANNEL_ID = ? I'm using a pair of hefty servers for NDB storage node backends (16 CPUs, 8GB RAM dedicated to NDB process, no other processess). I've witnessed this update statement taking around 90 seconds with 70,000 messages in queue, and 180 seconds with 140,000 messages in queue. Our MySQL DataSource connections had parameter socketTimeout 30000, causing the failover process to rollback and retry several times until giving up, crashing the PostOffice. This timeout parameter can easily be changed or removed (block forever?), but failover still takes a very long time. I altered the JBM_MSG_REF table so that MESSAGE_ID is the only part of the primary key. This makes the failover CHANNEL_ID update statement run instantly. I can't imagine a case where the JBM_MSG_REF would have duplicate MESSAGE_ID rows. If this is reasonable, could the next release of jboss-messaging 1.4.x drop CHANNEL_ID from the primary key of the CREATE TABLE JBM_MSG_REF statement? Otherwise please let me know if this table alteration is unsafe. In particular, I changed one line of ndb-persistence-service.xml SqlProperties parameter, from: CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (MESSAGE_ID BIGINT, CHANNEL_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY(MESSAGE_ID, CHANNEL_ID)) ENGINE = NDBCLUSTER to: CREATE_MESSAGE_REFERENCE=CREATE TABLE JBM_MSG_REF (MESSAGE_ID BIGINT, CHANNEL_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY(MESSAGE_ID)) ENGINE = NDBCLUSTER -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-676) Maven plugin that can be configured as a cleanup for build failures

by Anil Saldhana (JIRA)

Maven plugin that can be configured as a cleanup for build failures ------------------------------------------------------------------- Key: JBBUILD-676 URL: https://issues.jboss.org/browse/JBBUILD-676 Project: JBoss Build System Issue Type: Feature Request Reporter: Anil Saldhana Assignee: John Casey Whenever a maven build fails, there can be some resources that are open that can wreak havoc in a multi-build shared environments (like hudson). It will be cool, if we can configure a maven clean up plugin. Even the maven ant plugin running in a cleanup mode can do the trick -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-50) Documentation

by Dan Allen (JIRA)

Documentation ------------- Key: JBLOGGING-50 URL: https://jira.jboss.org/browse/JBLOGGING-50 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dan Allen Assignee: David Lloyd We desperately need some documentation for this project. Obviously documentation is a component in itself. I consider this issue resolved when there is at least some information about the project available and how to use it. That could be a web site, a reference guide a wiki page...anything. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-49) Relocate @Messages and @MessageBundle to i18n package

by Dan Allen (JIRA)

Relocate @Messages and @MessageBundle to i18n package ----------------------------------------------------- Key: JBLOGGING-49 URL: https://jira.jboss.org/browse/JBLOGGING-49 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd The message bundle facility in JBoss Logging is generally useful. In fact, we are planning on using it as a foundation for comprehensive i18n support in Seam 3. However, developers are going to be very standoff-ish if they have to import the @Messages and @MessageBundle annotations from a logging package (org.jboss.logging). I suggest moving them to the org.jboss.i18n package, though keeping it part of the JBoss Logging project since that will remain a foundation library and to stick to 1 JAR. Actual: org.jboss.logging.Messages org.jboss.logging.MessageBundle Proposed: org.jboss.i18n.Messages org.jboss.i18n.MessageBundle Relocate any other types as necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1430) Creation of server-groups with invalid parameters succeeds

by Heiko Rupp (JIRA)

Creation of server-groups with invalid parameters succeeds ---------------------------------------------------------- Key: AS7-1430 URL: https://issues.jboss.org/browse/AS7-1430 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=infinispan] /server-group=bla:add(profile="asdfjasdklfjasklfj",socket-binding-group=asfasdfjaslfhjk) { "outcome" => "success", "result" => { "domain-results" => {"step-1" => undefined}, "server-operations" => undefined } } Clearly the profile and socket-binding-group are invalid - the operation still succeeds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-47) Support EAP 5.1 in JBoss Logging 3

by Pete Muir (JIRA)

Support EAP 5.1 in JBoss Logging 3 ---------------------------------- Key: JBLOGGING-47 URL: https://jira.jboss.org/browse/JBLOGGING-47 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Pete Muir Assignee: David Lloyd If you try to use JBoss Logging 3 in EAP 5.1 you get Caused by: java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object; at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47) at org.jboss.logging.Logger.getLogger(Logger.java:2164) at org.jboss.logging.Logger.getLogger(Logger.java:2189) As the LogManager is too old. We should add a provider for older versions of LogManager -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1072) Cannot use an encrypted database password

by Juergen Zimmermann (JIRA)

Cannot use an encrypted database password ----------------------------------------- Key: AS7-1072 URL: https://issues.jboss.org/browse/AS7-1072 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.0.0.Beta3 Reporter: Juergen Zimmermann I'm using Jenkins build 1241. When I declare datasources in standalone.xml with <user-name> and <password>, there is no problem. However, when I declare a security domain (java:/swe1DS is the datasource's jndi name): <security-domain name="verschluesseltesDbPassword" cache-type="default"> <authentication> <login-module code="SecureIdentity" flag="required"> <module-option name="username" value="swe2"/> <module-option name="password" value="..."/> <module-option name="managedConnectionFactoryName" value="jboss.jca:name=swe2DS,service=LocalTxCM"/> </login-module> </authentication> </security-domain> and changed the <security> section inside the datasource definition to <security-domain>verschluesseltesDbPassword</security-domain> then I get this stacktrace, when JBoss 7 is launched: 17:11:33,816 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-1) Exception during createSubject()Unauthenticated caller:null: java.lang.SecurityException: Unauthenticated caller:null at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83) at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:979) at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:959) at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26] at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:958) at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:507) at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:246) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:241) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:105) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-9150) JRuby war deployment error on JBoss AS

by Abin Shahab (JIRA)

JRuby war deployment error on JBoss AS -------------------------------------- Key: JBAS-9150 URL: https://issues.jboss.org/browse/JBAS-9150 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Abin Shahab -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-9164) Upgrade to latest available version of RESTEasy

by Jozef Hartinger (JIRA)

Upgrade to latest available version of RESTEasy ----------------------------------------------- Key: JBAS-9164 URL: https://issues.jboss.org/browse/JBAS-9164 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Jozef Hartinger Fix For: 6.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1377) RA logs under "datasources"

by Heiko Braun (JIRA)

RA logs under "datasources" --------------------------- Key: AS7-1377 URL: https://issues.jboss.org/browse/AS7-1377 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Jesper Pedersen Fix For: 7.1.0.CR1 See ResourceAdaptersExtension.java > private static final Logger log = Logger.getLogger("org.jboss.as.datasources"); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
2
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 July 2011