February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1790) A single lagging JBM topic subscriber can cause all publishes to lag

by Jason Burton (JIRA)

A single lagging JBM topic subscriber can cause all publishes to lag -------------------------------------------------------------------- Key: JBMESSAGING-1790 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1790 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.3.GA Environment: JBoss 5.1.0_GA, JDK 1.6.0_14 and JDK 1.6.0_18, multiple versions of Windows (2008, 2003, Vista) Reporter: Jason Burton We have an application that makes heavy use of JMS topics. The attached stack traces lead me to believe that we have one client that has some sort of network problem and that JBM is trying to write messages to it. Evidently this client's socket isn't working anymore. That's no problem (and maybe could be expected), but this causes every other client publish to hang. The attached stack traces are from JBoss and taken 10 seconds apart during an occurence of this. During this time, we observed that one or more calls to JBossMessageProducer.publish() took 50 seconds to complete (normally takes 2-5 milliseconds). Best I can tell, the "WorkManager(2)-3" thread is the culprit. Over the 50 seconds, it seemed to be stuck in a socketWrite() and has object <0x143a2250> locked. There are a few other publishing threads waiting on that lock. I'm pretty sure this relates to a closed bug: https://jira.jboss.org/jira/browse/JBMESSAGING-1220 This bug report states to run a client out of memory to reproduce the problem, but at the point of the attached server stack traces. there aren't any clients that are out of memory. We have been able to reproduce this by running a client out of memory, though. That bug report stated to reduce the prefetchSize to a number of messages whose size would be under the TCP window size. Best I can tell by searching, the TCP window size defaults to 16K on Windows. It is definitely possible that the messages we send are larger than 16K, so even setting the prefetchSize to 1 would be larger that the TCP window size. Let me know if you need any more information. -- 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

13 years

4
13
0 / 0

[JBoss JIRA] Created: (JBBUILD-357) Eclipse PDE integration into Maven and unit test failure

by Mark Proctor (JIRA)

Eclipse PDE integration into Maven and unit test failure -------------------------------------------------------- Key: JBBUILD-357 URL: http://jira.jboss.com/jira/browse/JBBUILD-357 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Mark Proctor Assigned To: Paul Gier Eclipse plugin building and testing is automated by ant, executed by the Eclipse antRunner. Inside of Maven we have antRunner called in two different phases. When the test phase has unit test failures, they are not propagated up to maven, so failures are not flagged and a sucecssful build reported. Look in the drools-eclipse module of jboss rules for more details. -- 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

13 years

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-470) Release plugin doesn't pickup compile plugin configuration from parent

by Carlo de Wolf (JIRA)

Release plugin doesn't pickup compile plugin configuration from parent ---------------------------------------------------------------------- Key: JBBUILD-470 URL: http://jira.jboss.com/jira/browse/JBBUILD-470 Project: JBoss Build System Issue Type: Bug Environment: 4-beta2 Reporter: Carlo de Wolf Assigned To: Paul Gier Compile configuration defined in a parent pom does not get picked up by the release plugin during release. -- 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

13 years

2
4
0 / 0

[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree

by Andrew Lee Rubinger (JIRA)

Move JBossAS Maven Plugins into their own tree ---------------------------------------------- Key: JBASMP-12 URL: https://jira.jboss.org/jira/browse/JBASMP-12 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Currently under maven/plugins/jboss/trunk is: drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire -rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml Those prefixed with "maven-jboss-as" should be in their own tree -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-7) Break out Deployment-related Plugins into their own Project

by Andrew Lee Rubinger (JIRA)

Break out Deployment-related Plugins into their own Project ----------------------------------------------------------- Key: JBASMP-7 URL: http://jira.jboss.com/jira/browse/JBASMP-7 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-plugin Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 0.1.0 The Control Plugin currently houses Deployment Mojos; these should have their own Plugin. -- 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

13 years

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-478) Create "deploy" Mojo for maven-jboss-as-control-plugin

by Andrew Lee Rubinger (JIRA)

Create "deploy" Mojo for maven-jboss-as-control-plugin ------------------------------------------------------ Key: JBBUILD-478 URL: http://jira.jboss.com/jira/browse/JBBUILD-478 Project: JBoss Build System Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop". We need to add a "deploy" Mojo which delegates to congruent functionality from jboss-test. Existing Mojos: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-c... Root Checkout Location: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk After the "deploy" Mojo is created, configuration to use it should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM. This is the self-documenting usage project which may also prove its validity. -- 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

13 years

3
14
0 / 0

[JBoss JIRA] Created: (JBASMP-5) Rename folder structure of modules

by Andrew Lee Rubinger (JIRA)

Rename folder structure of modules ---------------------------------- Key: JBASMP-5 URL: http://jira.jboss.com/jira/browse/JBASMP-5 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Modules are currently namespaced with "maven-jboss-as-", which is unnecessary due to the groupId and folder structure. For instance: maven-jboss-as-build ...should become: build -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-8) Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable

by Andrew Lee Rubinger (JIRA)

Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable ------------------------------------------------------------------------------- Key: JBASMP-8 URL: https://jira.jboss.org/jira/browse/JBASMP-8 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 Replace all instances of non-Maven Logging code to AbstractMojo.getLog() within the Mojos themselves -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-4) Implement Deltas-only copying of configurations

by Andrew Lee Rubinger (JIRA)

Implement Deltas-only copying of configurations ----------------------------------------------- Key: JBASMP-4 URL: http://jira.jboss.com/jira/browse/JBASMP-4 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger >From Antony Stubbs: The other thing I noticed is that the JbossAsControlCreateConfigurationMojo doesn't seem to perform a delta copy as ALR has mentioned in places, but instead copies the entire directory every time and overwrites existing files. Is this a feature worth pursuing? It took quite a long time (at least 60 seconds) copying the config directory on every invoke for me - i.e. it appears worth it to me. -- 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

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBASMP-11) Rename incorrect src/main/resources/conf/bootstap-beans.xml

by Andrew Lee Rubinger (JIRA)

Rename incorrect src/main/resources/conf/bootstap-beans.xml ----------------------------------------------------------- Key: JBASMP-11 URL: https://jira.jboss.org/jira/browse/JBASMP-11 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-example Affects Versions: 0.1.0 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Go to "bootstrap" :) -- 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

13 years

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2010