October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1188) Probe.sh does not display matches summary on termination.

by Richard Achmatowicz (JIRA)

Probe.sh does not display matches summary on termination. --------------------------------------------------------- Key: JGRP-1188 URL: https://jira.jboss.org/jira/browse/JGRP-1188 Project: JGroups Issue Type: Bug Affects Versions: 2.4.7 Reporter: Richard Achmatowicz Assignee: Bela Ban Priority: Minor Fix For: 2.4.8 Matched statistics are not appearing at the end of the probe.sh output - when probe.sh, with the -match option specified, terminates, I should only see responses which contain the match string, and should see a summary line something like: Total responses=1, 1 matches, 3 non-matches This reflects how many responses were matched with the -match <match string> parameter. For example: [rachmatowicz@vmg18 bin]$ ./probe.sh -match Tomcat-Cluster -- send probe on /224.0.75.75:7500 #1 (262 bytes): 10.16.95.19:44066 (Tomcat-Cluster) local_addr=10.16.95.19:44066 group_name=Tomcat-Cluster version=2.4.7.GA, cvs="$Id: Version.java,v 1.42.2.14 2009/11/03 23:15:25 rachmatowicz Exp $" view: [10.16.95.19:44066|0] [10.16.95.19:44066] group_addr=239.11.12.13:45577 Here, the responses were correctly matched, but no summary line is produded. This summary line is not appearing, because a thread set up to close the multicast socket after timeout seconds is causing the multicast socket to generate an exception and return, before the control loop can be exited and the summary line printed. Moving the summary line into the exception handling code fixes the problem. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8479) Use ModuleLoaderSelector from ClassifyingModuleLoaderService

by Thomas Diesler (JIRA)

Use ModuleLoaderSelector from ClassifyingModuleLoaderService ------------------------------------------------------------ Key: JBAS-8479 URL: https://jira.jboss.org/browse/JBAS-8479 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.M1 Framework is overriding the module selector. Instead it needs to use the one available in the ClassifyingModuleLoaderService. Note that this service should be moved earlier in AS7 before subsystems are started. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8491) Upgrade jboss-service-binding to 1.2.0.Final

by Brian Stansberry (JIRA)

Upgrade jboss-service-binding to 1.2.0.Final -------------------------------------------- Key: JBAS-8491 URL: https://jira.jboss.org/browse/JBAS-8491 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.CR1 To pick up SVCBIND-5 and allow resolution of JBAS-8455. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-435) Add a Version class with basic information

by Jesper Pedersen (JIRA)

Add a Version class with basic information ------------------------------------------ Key: JBJCA-435 URL: https://jira.jboss.org/browse/JBJCA-435 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 Include a Version class which has the version information about the build. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-434) Include DTDs/XSDs in common artifact

by Jesper Pedersen (JIRA)

Include DTDs/XSDs in common artifact ------------------------------------ Key: JBJCA-434 URL: https://jira.jboss.org/browse/JBJCA-434 Project: IronJacamar Issue Type: Task Components: Common Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 Include the DTDs and XSDs for JCA and IronJacamar in the common-api.jar artifact -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2721) Build Guvnor standalone with maven and remove the ANT script in drools-guvnor

by Geoffrey De Smet (JIRA)

Build Guvnor standalone with maven and remove the ANT script in drools-guvnor ----------------------------------------------------------------------------- Key: JBRULES-2721 URL: https://jira.jboss.org/browse/JBRULES-2721 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 5.2.0.M1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2705) Guvnor gwt compile uses different eclipse jdt ecj version in ant script (due to gwt-dev) than in pom

by Geoffrey De Smet (JIRA)

Guvnor gwt compile uses different eclipse jdt ecj version in ant script (due to gwt-dev) than in pom ---------------------------------------------------------------------------------------------------- Key: JBRULES-2705 URL: https://jira.jboss.org/browse/JBRULES-2705 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.2.0.M1 Blocks removing the ant script and switching to 100% maven build with the maven gwt plugin -- 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, 2 months

1
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2720) Guvnor: In the about dialog the version and revision should be automatically up to date or removed. Make the version up to date and remove the revision.

by Geoffrey De Smet (JIRA)

Guvnor: In the about dialog the version and revision should be automatically up to date or removed. Make the version up to date and remove the revision. -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2720 URL: https://jira.jboss.org/browse/JBRULES-2720 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: 5.2.0.M1 There's an old ANT script, revision-number.xml, which is commented out and a version.txt file to do this, But it hasn't been used in over a year apparently: - on trunk, the version.txt says "5.0.0.SNAPSHOT 25673M" -- The version is wrong 5.0.0.SNAPSHOT should be 5.2.0.SNAPSHOT -- The revision is wrong: the current revision is at least 10000 revisions higher - on branch 5.1.X it's the same "5.0.0.SNAPSHOT 25673M" I am removing the old ANT script and version.txt, replacing it with maven filtered properties, see drools/drools-guvnor/src/main/filtered-resources/org/drools/guvnor/client/messages/BuildConstants.properties Making the version up to date with ${pom.version}. Note: when you build from eclipse you might see ${pom.version} because eclipse doesn't support maven filtering, but any maven or hudson or release build will have the correct version filled in. Not adding the revision (yet?). If anyone wants this (QA maybe?), I can do that in the BuildConstants.properties too, with the buildnumber-maven-plugin. http://mojo.codehaus.org/buildnumber-maven-plugin/index.html but that plugin is beta, might slow down the build (network access) and by default it wants to have svn on command line (which doesn't work if your svn command line is out of date with the version used by your IDE), however there's a way to use javasvn instead apparently. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-8169) Make default values of org.jboss.metadata.IorSecurityConfigMetaData configurable

by Dimitris Andreadis (JIRA)

Make default values of org.jboss.metadata.IorSecurityConfigMetaData configurable -------------------------------------------------------------------------------- Key: JBAS-8169 URL: https://jira.jboss.org/browse/JBAS-8169 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: IIOP service Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA, JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assignee: Stefan Guilhen User wants to allow the configuration of all IOR default parameters that are hard coded in org.jboss.metadata.IorSecurityConfigMetaData ([SasContext : callerPropagation] and [AsContext : authMethod, realm, required] and [TransportConfig : integrity, confidentiality, detectMisordering, detectReplay, establishTrustInTarget, establishTrustInClient]). Mostly they want to be able to configure [AsContext : realm] and [SasContext : callerPropagation] -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1121) Leverage JAXB to the full extent

by Vladimir Blagojevic (JIRA)

Leverage JAXB to the full extent -------------------------------- Key: JGRP-1121 URL: https://jira.jboss.org/jira/browse/JGRP-1121 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.9 Since we are going to base 2.9 release on JDK 6 we can use JAXB for configuration reading, XSD schema and documentation generation. -- 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, 2 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2010