October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-563) Use a property in the enforcer for the minimum version of maven required

by Arnaud Heritier (JIRA)

Use a property in the enforcer for the minimum version of maven required ------------------------------------------------------------------------ Key: JBBUILD-563 URL: https://jira.jboss.org/jira/browse/JBBUILD-563 Project: JBoss Build System Issue Type: Task Components: JBoss Parent POM Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: JBoss Parent POM - 5.0-beta-3 Allow to change it in sub projects -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-562) Add plugins in pluginsMgt

by Arnaud Heritier (JIRA)

Add plugins in pluginsMgt ------------------------- Key: JBBUILD-562 URL: https://jira.jboss.org/jira/browse/JBBUILD-562 Project: JBoss Build System Issue Type: Task Components: JBoss Parent POM Reporter: Arnaud Heritier Fix For: JBoss Parent POM - 5.0-beta-3 eclipse, intellij, buildnumber are often useful -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-561) Update plugins to latest versions

by Arnaud Heritier (JIRA)

Update plugins to latest versions --------------------------------- Key: JBBUILD-561 URL: https://jira.jboss.org/jira/browse/JBBUILD-561 Project: JBoss Build System Issue Type: Task Components: JBoss Parent POM Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: JBoss Parent POM - 5.0-beta-3 {code} [INFO] The following plugin updates are available: [INFO] maven-assembly-plugin ...................... 2.2-beta-2 -> 2.2-beta-4 [INFO] maven-clean-plugin ....................................... 2.2 -> 2.3 [INFO] maven-dependency-plugin .................................. 2.0 -> 2.1 [INFO] maven-ear-plugin ..................................... 2.3.1 -> 2.3.2 [INFO] maven-ejb-plugin ......................................... 2.1 -> 2.2 [INFO] maven-install-plugin ..................................... 2.2 -> 2.3 [INFO] maven-javadoc-plugin ..................................... 2.5 -> 2.6 [INFO] maven-plugin-plugin .................................... 2.4.3 -> 2.5 [INFO] maven-project-info-reports-plugin .................... 2.0.1 -> 2.1.2 [INFO] maven-resources-plugin ................................... 2.3 -> 2.4 [INFO] maven-site-plugin ............................... 2.0-beta-7 -> 2.0.1 [INFO] maven-war-plugin .......................... 2.1-alpha-2 -> 2.1-beta-1 [INFO] org.codehaus.mojo:cobertura-maven-plugin ................. 2.1 -> 2.3 [INFO] org.codehaus.mojo:findbugs-maven-plugin ................ 2.0.1 -> 2.1 [INFO] org.codehaus.mojo:taglist-maven-plugin ................... 2.0 -> 2.4 {code} -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-560) Use properties to configure plugin instead of explicit configuration settings

by Arnaud Heritier (JIRA)

Use properties to configure plugin instead of explicit configuration settings ----------------------------------------------------------------------------- Key: JBBUILD-560 URL: https://jira.jboss.org/jira/browse/JBBUILD-560 Project: JBoss Build System Issue Type: Task Components: JBoss Parent POM Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: JBoss Parent POM - 5.0-beta-3 When a configuration entry in a plugin can be set from a property it is better to use it because sub-project will just have to redefine its value instead of all the plugin configuration. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-559) put plugin versions in properties

by Arnaud Heritier (JIRA)

put plugin versions in properties --------------------------------- Key: JBBUILD-559 URL: https://jira.jboss.org/jira/browse/JBBUILD-559 Project: JBoss Build System Issue Type: Task Components: JBoss Parent POM Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: JBoss Parent POM - 5.0-beta-3 With that it is easy to update versions in a child pom, and it is easy to reuse the version versions between plugins and reports when it is necessary -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7310) JChannelFactory not passing ref to protocol to JMX wrapper object

by Brian Stansberry (JIRA)

JChannelFactory not passing ref to protocol to JMX wrapper object ----------------------------------------------------------------- Key: JBAS-7310 URL: https://jira.jboss.org/jira/browse/JBAS-7310 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.2.0.Beta1 The AS JChannelFactory is not passing a ref to the underlying JGroups protocol instance to the org.jgroups.jmx package wrapper object it registers in JMX. As a result, If you go into the jmx-console and look at any of the mbeans in the jboss.jgroups domain with type=protocol, all of the attribute values are "javax.management.RuntimeMBeanException" Simple, fix, just add the required call to the wrapper object's attachProtocol method. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1069) Log4jImpl: show line numbers of calling class, not of Log4jImpl

by Bela Ban (JIRA)

Log4jImpl: show line numbers of calling class, not of Log4jImpl --------------------------------------------------------------- Key: JGRP-1069 URL: https://jira.jboss.org/jira/browse/JGRP-1069 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 Attachments: Log4JLogImpl.java [David Forget] We are using log4j as default logger, I have set my appender to use %l as you proposed but all logs from JGroups always have the line number of the log implementer (Log4JLogImpl) as opposed to the class calling the logger. In the following log example (Log4JLogImpl.java:73), but we are interested to get the line number of org.jgroups.JChannel not Log4JLogImpl. <134>2009-09-29 13:44:12,376 INFO csp_in1 OTHER_0000 "JGroups version:2.8.0.CR2" <VERBOSE=71> [Thread - WrapperStart] (org.jgroups.JChannel)(Log4JLogImpl.java:73) <END> My log4j.properties --------------------- log4j.rootLogger=WARN, SYSLOG, FILE, CONSOLE #define the appender named CONSOLE log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=[%d} [%t] [%-5p] [%c] - [%l][%L][%m][%n] log4j.logger.org.jgroups=DEBUG I did a change to Log4JLogImpl to use same method as common logging and it work fine: <134>2009-10-02 09:54:04,116 INFO csp_in1 OTHER_0000 "JGroups version: 2.8.0.CR2" <VERBOSE=69> [Thread - WrapperStart] (org.jgroups.JChannel) (JChannel.java:1699) <END> -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6842) Unwanted deployment of the shared STLBs

by Miroslav Havram (JIRA)

Unwanted deployment of the shared STLBs --------------------------------------- Key: JBAS-6842 URL: https://jira.jboss.org/jira/browse/JBAS-6842 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.0.1.GA Reporter: Miroslav Havram Assignee: Ales Justin STLBs from the EAR's lib are deployed even if they are explicitly excluded from deployment. More information can be found on the related forum topic. -- 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

14 years, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-6299) Cluster Performance tuning docs

by Brian Stansberry (JIRA)

Cluster Performance tuning docs ------------------------------- Key: JBAS-6299 URL: https://jira.jboss.org/jira/browse/JBAS-6299 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Docs/Performance Tuning Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.1.0.Beta1 Document suggestions for increased performance in a cluster. Off the top of my head, I'm sure there are others, in no particular order: 1) Adjust UDP buffer kernel defaults. 2) Buddy replication for session use case. 3) Separate transport for high load channel. a) Bundling enabled for async use case; udp-async stack 4) No FC for synchronous use case; udp-sync stack. 5) Shorter cluster names. 6) Remove cache loader config from web session cache if not using passivation. 7) TCP for smaller clusters??? -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBAS-7102) Problem sending large files via farm service

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7102?page=com.atlassian.jira.plug... ] Brian Stansberry commented on JBAS-7102: ---------------------------------------- I've added a test that farms a 150MB file[1] and it passes, with the test taking < 25 secs to run (which includes time to write out the 150MB file). I'll comment in more detail on the forum thread, but here are a couple suggestions: 1) Stop the hot deployment scanner thread before doing lengthy I/O operations (e.g. copying in files) in the farm/ (or deploy/) folders. Then restart it when I/O is done. This avoids the hot deployment scanning running and seeing partially completed I/O. The scanner can be stopped by invoking the JMX stop() operation on the jboss.deployment:flavor=URL,type=DeploymentScanner MBean. This can be done via the jmx-console or via the twiddle utility in $JBOSS_HOME/bin. 2) Make sure your network is tuned to limit losses of UDP packets. Among other things, increase the OS maximum network read and write buffers; e.g. on Linux sysctl -w net.core.rmem_max=26214400 sysctl -w net.core.wmem_max=1048576 [1] https://svn.jboss.org/repos/jbossas/branches/Branch_5_x/testsuite/src/mai... > Problem sending large files via farm service > -------------------------------------------- > > Key: JBAS-7102 > URL: https://jira.jboss.org/jira/browse/JBAS-7102 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering, ProfileService > Affects Versions: JBossAS-5.1.0.GA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: JBossAS-6.0.0.Alpha1 > > > Users have reported issues sending large files over the AS 5.1 farming service; see forum thread. -- 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

14 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2009