October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-929) CLI is terminated unexpectedly after type "qui" on HPUX

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-929?page=com.atlassian.jira.plugin... ] Dominik Pospisil commented on WFCORE-929: ----------------------------------------- My findings so far: * Actually It's typing the 'u' character making the JVM to terminate * The "Aesh InputStream Reader" seems to be causing the termination * it happends somewhere on line AeshInputStream.readFromStream:126, it does not make it to line 127. Seems to be somewhere in JDK code. > CLI is terminated unexpectedly after type "qui" on HPUX > ------------------------------------------------------- > > Key: WFCORE-929 > URL: https://issues.jboss.org/browse/WFCORE-929 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Alexey Loubyansky > Priority: Minor > > *Description of problem:* > CLI is terminated unexpectedly after type "qui" on HPUX > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./standalone.sh > # ./jboss-cli.sh -c > # qui > #* type "qui" in console to CLI, do not press "enter" > *Actual results:* > CLI is terminated > *Expected results:* > CLI is not terminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1029) ManagedSocketFactory doesn't work for client sockets

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1029?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1029: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1268186 Bugzilla Update: Perform > ManagedSocketFactory doesn't work for client sockets > ---------------------------------------------------- > > Key: WFCORE-1029 > URL: https://issues.jboss.org/browse/WFCORE-1029 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 2.0.0.CR5 > Reporter: Dennis Reed > > SocketBindingManagerImpl does not work with client sockets. > It adds sockets to a map based on local address. Client sockets that have not been bound yet do not have a local address. > This breaks the JGroups subsystem's ManagedSocketFactory, which uses SocketBindingManagerImpl for both server and client sockets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5449: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1268185 Bugzilla Update: Perform > Custom socket factory for JGroups subsystem not set correctly > ------------------------------------------------------------- > > Key: WFLY-5449 > URL: https://issues.jboss.org/browse/WFLY-5449 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Dennis Reed > Assignee: Paul Ferraro > > Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. > This is not the correct API to use, and it gets overwritten when the JGroups channel starts. > A custom socket factory should be set on the JChannel. > The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1029) ManagedSocketFactory doesn't work for client sockets

by Dennis Reed (JIRA)

Dennis Reed created WFCORE-1029: ----------------------------------- Summary: ManagedSocketFactory doesn't work for client sockets Key: WFCORE-1029 URL: https://issues.jboss.org/browse/WFCORE-1029 Project: WildFly Core Issue Type: Bug Affects Versions: 2.0.0.CR5 Reporter: Dennis Reed SocketBindingManagerImpl does not work with client sockets. It adds sockets to a map based on local address. Client sockets that have not been bound yet do not have a local address. This breaks the JGroups subsystem's ManagedSocketFactory, which uses SocketBindingManagerImpl for both server and client sockets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

by Dennis Reed (JIRA)

Dennis Reed created WFLY-5449: --------------------------------- Summary: Custom socket factory for JGroups subsystem not set correctly Key: WFLY-5449 URL: https://issues.jboss.org/browse/WFLY-5449 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR2 Reporter: Dennis Reed Assignee: Paul Ferraro Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport. This is not the correct API to use, and it gets overwritten when the JGroups channel starts. A custom socket factory should be set on the JChannel. The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1026) Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1026?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1026: ---------------------------------- Summary: Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final (was: Upgrade jboss-logmanager from 2.0.0.Final to 2.0.1.Final) > Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final > -------------------------------------------------------- > > Key: WFCORE-1026 > URL: https://issues.jboss.org/browse/WFCORE-1026 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.0.CR6 > > > Bug found in the syslog handler where an extra 0 was being appended to October in the date formatter. https://issues.jboss.org/browse/LOGMGR-122. The 2.0.1.Final release only contains that fix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1026) Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1026?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1026: ---------------------------------- Description: Bug found in the syslog handler where an extra 0 was being appended to October in the date formatter. https://issues.jboss.org/browse/LOGMGR-122. (was: Bug found in the syslog handler where an extra 0 was being appended to October in the date formatter. https://issues.jboss.org/browse/LOGMGR-122. The 2.0.1.Final release only contains that fix.) > Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final > -------------------------------------------------------- > > Key: WFCORE-1026 > URL: https://issues.jboss.org/browse/WFCORE-1026 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.0.CR6 > > > Bug found in the syslog handler where an extra 0 was being appended to October in the date formatter. https://issues.jboss.org/browse/LOGMGR-122. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-808) Password not passed into DatabaseServerLoginModule

by Lorenz Froihofer (JIRA)

[ https://issues.jboss.org/browse/SECURITY-808?page=com.atlassian.jira.plug... ] Lorenz Froihofer commented on SECURITY-808: ------------------------------------------- Tracked down the issue a little bit further (picketbox-4.9.2.Final in Wildfly 9.0.1.Final): JBossCallbackHandler.getPassword() falls back to try the dynamic invocation of a method named "toCharArray": {code:java} Method m = credential.getClass().getMethod("toCharArray", types); Object[] args = {}; password = (char[]) m.invoke(credential, args); {code} This fails with a NoSuchMethodException for a RemotingConnectionCredential object as this class does not offer such a method. The exception handling just tries to create a credential by using the "toString" method on the credential object (the RemotingConnectionCredential) - leading to a String such as org.jboss.as.security.remoting.RemotingConnectionCredential@22341334 instead of the real password. As far as the code looks like, the RemotingConnectionCredential should allow for a callback to get the password, but looking at it or the wrapped Connection class, one can only get the username through org.jboss.remoting3.Connection.getUserInfo(), but no password. This seems to be a more general issue not only related to the DatabaseServerLoginModule but to custom login modules as well: https://developer.jboss.org/message/866429 > Password not passed into DatabaseServerLoginModule > -------------------------------------------------- > > Key: SECURITY-808 > URL: https://issues.jboss.org/browse/SECURITY-808 > Project: PicketBox > Issue Type: Bug > Environment: WildFly8 on Windows 7 64-bit > Reporter: Stefan Eder > Assignee: Stefan Guilhen > Priority: Critical > > Trying to migrate an application to WildFly (from AS6.1) the migration went pretty smooth except for using the security domain. > The application uses a the ClientLoginModule on the client side and the DatabaseserverLoginModule on the server side. > > Though the DatabaseServerLoginModule is called the validation of the password fails. I debugged it and the reason seems to be that in {{org.jboss.security.auth.callback.JBossCallbackHandler.getPassword()}} a {{org.jboss.as.security.remoting.RemotingConnectionCredential@22341334}} is not handled and hence instead of a password the String {{org.jboss.as.security.remoting.RemotingConnectionCredential@22341334}} is passed through to the DatabaseLoginModule. > See also [DatabaseServerLoginModule broken?|https://community.jboss.org/message/863295] and the related posts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-935) tomcat7 unable to deploy Execution server

by Siarhei Yarkavy (JIRA)

[ https://issues.jboss.org/browse/DROOLS-935?page=com.atlassian.jira.plugin... ] Siarhei Yarkavy updated DROOLS-935: ----------------------------------- Environment: Windows 7 64bit sp1 java 7u60 64bit tomcat 7.0.54 > tomcat7 unable to deploy Execution server > ----------------------------------------- > > Key: DROOLS-935 > URL: https://issues.jboss.org/browse/DROOLS-935 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.Final > Environment: Windows 7 64bit sp1 > java 7u60 64bit > tomcat 7.0.54 > Reporter: Siarhei Yarkavy > Assignee: Edson Tirelli > Attachments: catalina.2015-10-01.zip > > > Unable to properly deploy Execution server into tomcat7 container. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-935) tomcat7 unable to deploy Execution server

by Siarhei Yarkavy (JIRA)

Siarhei Yarkavy created DROOLS-935: -------------------------------------- Summary: tomcat7 unable to deploy Execution server Key: DROOLS-935 URL: https://issues.jboss.org/browse/DROOLS-935 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 6.3.0.Final Reporter: Siarhei Yarkavy Assignee: Edson Tirelli Attachments: catalina.2015-10-01.zip Unable to properly deploy Execution server into tomcat7 container. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2015