[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
[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
[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