September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3915) Dynamic configuration of outbound SSL connections

by James Livingston (JIRA)

James Livingston created WFLY-3915: -------------------------------------- Summary: Dynamic configuration of outbound SSL connections Key: WFLY-3915 URL: https://issues.jboss.org/browse/WFLY-3915 Project: WildFly Issue Type: Feature Request Reporter: James Livingston Assignee: Jason Greene WebSphere has a feature called "Dynamic outbound SSL configuration" (http://www-01.ibm.com/support/knowledgecenter/SSCKBL_8.5.5/com.ibm.websph...), which allows the configuration of SSL parameters for connections which are not opened directly by the container. That can be useful for configuring the SSL usage of components such as resource adapters, JDBC drivers, and application-packaged web service libraries. For example the truststore/keystore could be configured different for all requests to the database host, so that the global javax.net.ssl settings to not need to be modified if the driver does not itself provide a way to configure it. I believe that it is implemented by using javax.net.ssl.SSLContext.setDefault() to replace the standard socket factory. The socket factory could then look at the passed hostname/port, and potentially the calling application to configure the SSL socket appropriately before returning it to the caller. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-132) BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-132?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-132: ------------------------------------------------ Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1147067|https://bugzilla.redhat.com/show_bug.cgi?id=1147067] from NEW to POST > BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-132 > URL: https://issues.jboss.org/browse/WFCORE-132 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > BoundedQueueThreadPoolWriteAttributeHandler doesn't deal with undefined values for core-threads correctly. It assumes the attribute will be defined, and that's not required. > The attribute doesn't have a fixed default value. Instead, the behavior in add is to set the runtime value to match max-threads of core-threads is undefined. BoundedQueueThreadPoolWriteAttributeHandler should do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-132) BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-132?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-132: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147067 > BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-132 > URL: https://issues.jboss.org/browse/WFCORE-132 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > BoundedQueueThreadPoolWriteAttributeHandler doesn't deal with undefined values for core-threads correctly. It assumes the attribute will be defined, and that's not required. > The attribute doesn't have a fixed default value. Instead, the behavior in add is to set the runtime value to match max-threads of core-threads is undefined. BoundedQueueThreadPoolWriteAttributeHandler should do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-132) BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-132: --------------------------------------- Summary: BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly Key: WFCORE-132 URL: https://issues.jboss.org/browse/WFCORE-132 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha8 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Alpha9 BoundedQueueThreadPoolWriteAttributeHandler doesn't deal with undefined values for core-threads correctly. It assumes the attribute will be defined, and that's not required. The attribute doesn't have a fixed default value. Instead, the behavior in add is to set the runtime value to match max-threads of core-threads is undefined. BoundedQueueThreadPoolWriteAttributeHandler should do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-197) VFSUtils#getVirtualURL requires permissions

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-197?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved JBVFS-197. ------------------------------- Fix Version/s: 3.5.0.Alpha1 Resolution: Done > VFSUtils#getVirtualURL requires permissions > ------------------------------------------- > > Key: JBVFS-197 > URL: https://issues.jboss.org/browse/JBVFS-197 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.6.Final > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 3.2.7.Final, 3.5.0.Alpha1 > > > The {{org.jboss.vfs.VFSUtils#getVirtualURL(VirtualFile)}} method requires the permission {{java.net.NetPermission" specifyStreamHandler"}}. Therefore the URL construction should be in a privileged block. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-86) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-86?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-86: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1113242|https://bugzilla.redhat.com/show_bug.cgi?id=1113242] from MODIFIED to ON_QA > RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts > -------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-86 > URL: https://issues.jboss.org/browse/REMJMX-86 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.0.Final > Reporter: Mustafa Musaji > Assignee: Brad Maxwell > Fix For: 1.1.3.Final, 2.0.1.CR1 > > > In [1] we have the following snippet of code which has a hardcoded value of 5 seconds. > {code:title=RemotingConnector.java} > // Now open the channel > final IoFuture<Channel> futureChannel = connection.openChannel(serviceName, OptionMap.EMPTY); > IoFuture.Status result = futureChannel.await(5, TimeUnit.SECONDS); > if (result == IoFuture.Status.DONE) { > channel = futureChannel.get(); > } else if (result == IoFuture.Status.FAILED) { > throw new IOException(futureChannel.getException()); > } else { > throw new RuntimeException("Operation failed with status " + result); > } > {code} > This should be a system property or the default value should be raised. > [1] https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jbo... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-88) Release Remoting JMX 1.1.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-88?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-88: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1113249|https://bugzilla.redhat.com/show_bug.cgi?id=1113249] from MODIFIED to ON_QA > Release Remoting JMX 1.1.3.Final > -------------------------------- > > Key: REMJMX-88 > URL: https://issues.jboss.org/browse/REMJMX-88 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3888) Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3888?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3888: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1145896|https://bugzilla.redhat.com/show_bug.cgi?id=1145896] from MODIFIED to ON_QA > Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly > --------------------------------------------------------------------------------------------- > > Key: WFLY-3888 > URL: https://issues.jboss.org/browse/WFLY-3888 > Project: WildFly > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > > All ERROR and WARN messages should show the full timer information, specially the customer timer-information. > This will make it more easy to identify the exact timer in case of an EJB object has multiple timer instances active. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-46) Fix intermittent failures in DeploymentOverlayCLITestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-46?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-46: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1144222|https://bugzilla.redhat.com/show_bug.cgi?id=1144222] from MODIFIED to ON_QA > Fix intermittent failures in DeploymentOverlayCLITestCase > --------------------------------------------------------- > > Key: WFCORE-46 > URL: https://issues.jboss.org/browse/WFCORE-46 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-125) Security realm cache definitions not possible for LDAP prinicipal to group group loading.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-125?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-125: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1146117|https://bugzilla.redhat.com/show_bug.cgi?id=1146117] from MODIFIED to ON_QA > Security realm cache definitions not possible for LDAP prinicipal to group group loading. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-125 > URL: https://issues.jboss.org/browse/WFCORE-125 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 1.0.0.Alpha8 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > > It's not possible to configure LDAP cache in security realms under "authorization=ldap/group-search=principal-to-group" > Possible reason: > The LdapCacheResourceDefinition is not registered under the org.jboss.as.domain.management.security.PrincipalToGroupResourceDefinition > When I try to add the cache configuration manually to standalone.xml, server doesn't start and reports: > 15:23:44,619 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014629: No resource definition is registered for address [ > ("core-service" => "management"), > ("security-realm" => "JBossTest"), > ("authorization" => "ldap"), > ("group-search" => "principal-to-group"), > ("cache" => "by-search-time") > ] > 15:23:44,621 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 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 September 2014