[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2214:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from POST to MODIFIED
> Allow additional environment properties to be set for outbound LDAP connections used by security realms.
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2214
> URL: https://issues.jboss.org/browse/WFLY-2214
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
> result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
> String url = config.require(URL).asString();
> result.put(Context.PROVIDER_URL,url);
> + result.put("com.sun.jndi.ldap.connect.timeout", "500");
> return result;
> }
--
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
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1810:
---------------------------
Fix Version/s: 3.5
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
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
[JBoss JIRA] (WFLY-3151) Failure to start jboss-cli.sh due to space in the startup path
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3151?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3151:
------------------------------
Summary: Failure to start jboss-cli.sh due to space in the startup path (was: Possible regression standalone.sh due to a space in the startup path)
> Failure to start jboss-cli.sh due to space in the startup path
> --------------------------------------------------------------
>
> Key: WFLY-3151
> URL: https://issues.jboss.org/browse/WFLY-3151
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Arun Gupta
> Assignee: James Perkins
>
> Sent email to wildfly-dev:
> -- cut here --
> Java EE 7 CI job on WildFly trunk is failing:
> https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
> Here is the error message:
> Started 45 of 56 services (22 services are lazy, passive or on-demand)
> [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
> '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
> Error: Could not find or load main class EE
> Process leaked file descriptors. See
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
> for more information
> Build step 'Execute shell' marked build as failure
> -- cut here --
> David reponded:
> -- cut here --
> Looks like a possible regression in standalone.sh due to there being a
> space in the startup path.
> As a workaround you could change your workspace name from "Java EE 7
> Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
> similar (with no spaces).
> -- cut here --
--
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
[JBoss JIRA] (WFLY-3151) Failure to start jboss-cli.sh due to space in the startup path
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3151?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3151:
------------------------------
Description:
The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list.
Original report:
Sent email to wildfly-dev:
{noformat}
Java EE 7 CI job on WildFly trunk is failing:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
Here is the error message:
Started 45 of 56 services (22 services are lazy, passive or on-demand)
[0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
'--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
Error: Could not find or load main class EE
Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information
Build step 'Execute shell' marked build as failure
{noformat}
David responded:
{noformat}
Looks like a possible regression in standalone.sh due to there being a
space in the startup path.
As a workaround you could change your workspace name from "Java EE 7
Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
similar (with no spaces).
{noformat}
was:
Sent email to wildfly-dev:
-- cut here --
Java EE 7 CI job on WildFly trunk is failing:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
Here is the error message:
Started 45 of 56 services (22 services are lazy, passive or on-demand)
[0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
'--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
Error: Could not find or load main class EE
Process leaked file descriptors. See
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
for more information
Build step 'Execute shell' marked build as failure
-- cut here --
David reponded:
-- cut here --
Looks like a possible regression in standalone.sh due to there being a
space in the startup path.
As a workaround you could change your workspace name from "Java EE 7
Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
similar (with no spaces).
-- cut here --
> Failure to start jboss-cli.sh due to space in the startup path
> --------------------------------------------------------------
>
> Key: WFLY-3151
> URL: https://issues.jboss.org/browse/WFLY-3151
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Arun Gupta
> Assignee: James Perkins
>
> The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list.
> Original report:
> Sent email to wildfly-dev:
> {noformat}
> Java EE 7 CI job on WildFly trunk is failing:
> https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
> Here is the error message:
> Started 45 of 56 services (22 services are lazy, passive or on-demand)
> [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect
> '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)'
> Error: Could not find or load main class EE
> Process leaked file descriptors. See
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
> for more information
> Build step 'Execute shell' marked build as failure
> {noformat}
> David responded:
> {noformat}
> Looks like a possible regression in standalone.sh due to there being a
> space in the startup path.
> As a workaround you could change your workspace name from "Java EE 7
> Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or
> similar (with no spaces).
> {noformat}
--
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