January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1158) add "remove vault entry" option to vault tool

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/WFLY-1158?page=com.atlassian.jira.plugin.... ] Peter Skopek commented on WFLY-1158: ------------------------------------ I have branch ready for PR, just have to wait until new version of PicketBox (4.0.21.Beta1) will be released. https://github.com/pskopek/wildfly/tree/vault-tool-remove-password > add "remove vault entry" option to vault tool > ---------------------------------------------- > > Key: WFLY-1158 > URL: https://issues.jboss.org/browse/WFLY-1158 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Gernot P > Assignee: Peter Skopek > Attachments: patch.diff > > > You cannot remove an entry form vault with the vault tool. You can choose only amog following options "0: Store a password 1: Check whether password exists 2: Exit" > Pleas add "remove password" option to vault tool (vault.sh) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1777) TP: add more stats

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1777?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1777. ---------------------------- Resolution: Done Added stats for * num single msgs sent / received * num batches sent / received * avg batch sizes received > TP: add more stats > ------------------ > > Key: JGRP-1777 > URL: https://issues.jboss.org/browse/JGRP-1777 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > * Number of single messages sent and received (oob, regular ?) > * Number of bundles sent / batches received (oob, regular?) > * Avg batch size -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-788) PicketBoxSecurityVault is not writing data to store after removing from map in memory

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-788?page=com.atlassian.jira.plug... ] Peter Skopek resolved SECURITY-788. ----------------------------------- Resolution: Done > PicketBoxSecurityVault is not writing data to store after removing from map in memory > ------------------------------------------------------------------------------------- > > Key: SECURITY-788 > URL: https://issues.jboss.org/browse/SECURITY-788 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_20.Final > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: PicketBox_4_0_21.Beta1 > > > PicketBoxSecurityVault is not writing data to store after removing from map in memory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-788) PicketBoxSecurityVault is not writing data to store after removing from map in memory

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-788?page=com.atlassian.jira.plug... ] Peter Skopek updated SECURITY-788: ---------------------------------- Description: PicketBoxSecurityVault is not writing data to store after removing from map in memory. > PicketBoxSecurityVault is not writing data to store after removing from map in memory > ------------------------------------------------------------------------------------- > > Key: SECURITY-788 > URL: https://issues.jboss.org/browse/SECURITY-788 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_20.Final > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: PicketBox_4_0_21.Beta1 > > > PicketBoxSecurityVault is not writing data to store after removing from map in memory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-788) PicketBoxSecurityVault is not writing data to store after removing from map in memory

by Peter Skopek (JIRA)

Peter Skopek created SECURITY-788: ------------------------------------- Summary: PicketBoxSecurityVault is not writing data to store after removing from map in memory Key: SECURITY-788 URL: https://issues.jboss.org/browse/SECURITY-788 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_4_0_20.Final Reporter: Peter Skopek Assignee: Peter Skopek Fix For: PicketBox_4_0_21.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2591) CLI can not connect to the server started with port-offset

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-2591?page=com.atlassian.jira.plugin.... ] Michal Babacek updated WFLY-2591: --------------------------------- Affects Version/s: 8.0.0.Final > CLI can not connect to the server started with port-offset > ---------------------------------------------------------- > > Key: WFLY-2591 > URL: https://issues.jboss.org/browse/WFLY-2591 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1, 8.0.0.Final > Environment: used actual WildFly Beta from github: > commit 96160520ce245d6a85cbb77cad92a021564aa376 > Date: Wed Nov 20 17:05:00 2013 +0100 > Reporter: Wolf-Dieter Fink > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > If a standalone server is started with a binding port-offset it is not possible to connect to the native management interface. > To reproduce start a WildFly Beta server (Alpha3 has the same problem) > bin/standalone.sh -Djboss.socket.binding.port-offset=100 > and a cli client: > bin/jboss-cli.sh -c --controller=localhost:10099 > It makes no difference whether the port is changed by port-offset or configuration. > All other ports (i.e. 10090 8180) can be used correct for http-management or ejb invocation. > The server log an ERROR message: > ERROR [org.jboss.remoting.remote.connection] (Remoting "home:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: XNIO000804: Received an invalid message length of 1195725856 > The jboss-cli.sh client show: > org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:240) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:218) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:292) > at org.jboss.modules.Main.main(Main.java:455) > Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:10099 > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:960) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:772) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:238) > ... 8 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:938) > ... 11 more > Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) > at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:166) > at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:127) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 13 more > Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:283) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:266) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99) > ... 23 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2753) Workaround for auditlog syslog appName not being configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2753?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2753: ----------------------------------------------- Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1053382|https://bugzilla.redhat.com/show_bug.cgi?id=1053382] from ON_QA to VERIFIED > Workaround for auditlog syslog appName not being configurable > ------------------------------------------------------------- > > Key: WFLY-2753 > URL: https://issues.jboss.org/browse/WFLY-2753 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kyle Lape > Assignee: Kyle Lape > Fix For: 8.0.0.Final > > > Use {{-Dorg.jboss.TEMP.audit.log.appName=customApp}} where the value is the {{app-name}} as mentioned in section 6.2.5 of RFC-5424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2595) Logging DUP leaking class loaders

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2595?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2595: ----------------------------------------------- Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1049074|https://bugzilla.redhat.com/show_bug.cgi?id=1049074] from ON_QA to VERIFIED > Logging DUP leaking class loaders > --------------------------------- > > Key: WFLY-2595 > URL: https://issues.jboss.org/browse/WFLY-2595 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 8.0.0.CR1 > > > When a new {{LogContext}} is created for per-deployment logging the class loader is registered as the key. On undeploy the {{LogContext}} should be removed, but the wrong {{LogContext}}t is retrieved due to the caller class loader being used rather than the TCCL. > The use of the caller class loader is for filtering out system dependencies from the deployment so the correct {{LogContext}} is retrieved from the selector. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2804) Add -u and -p shortcuts to jboss-cli

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2804?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky updated WFLY-2804: ------------------------------------ Component/s: CLI > Add -u and -p shortcuts to jboss-cli > ------------------------------------ > > Key: WFLY-2804 > URL: https://issues.jboss.org/browse/WFLY-2804 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Arun Gupta > Assignee: carmelo aprile > Priority: Minor > Fix For: 8.0.0.Final > > > jboss-cli only provides --user and --password as the options. It would be convenient to add -u and -p as shortcut options as this will bring consistency with add-user script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2804) Add -u and -p shortcuts to jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2804?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2804: ----------------------------------- Assignee: carmelo aprile > Add -u and -p shortcuts to jboss-cli > ------------------------------------ > > Key: WFLY-2804 > URL: https://issues.jboss.org/browse/WFLY-2804 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Arun Gupta > Assignee: carmelo aprile > Priority: Minor > > jboss-cli only provides --user and --password as the options. It would be convenient to add -u and -p as shortcut options as this will bring consistency with add-user script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
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 January 2014