April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-722) SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-722?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-722: -------------------------------------------------- FIlip Bogyai <fbogyai(a)redhat.com> changed the Status of [bug 1085497|https://bugzilla.redhat.com/show_bug.cgi?id=1085497] from ON_QA to VERIFIED > SPNEGO-fallback-to-FORM authentication does not work with httpd+JBossEAP6 if SPNEGO not available > ------------------------------------------------------------------------------------------------- > > Key: SECURITY-722 > URL: https://issues.jboss.org/browse/SECURITY-722 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_1 > Environment: RHEL6, JBoss EAP 6 > Reporter: flame liu > Assignee: Derek Horton > Fix For: Negotiation_2_2_8, Negotiation_2_3_0_CR2 > > > I configured SPNEGO in EAP6. It works well both with EAP only and EAP6 + Apache httpd(mod_proxy). Users just run kinit and will be able to be successfully authenticated. > After that, I added the fallback-to-form files/configurations both in the web app and standalone-full.xml. The fallback-to-form works only if httpd stops. If httpd starts, 401 error will always be thrown out. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-3226) Add test cases to verify LDAP caching on security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3226?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3226: ---------------------------------------- Hi [~friler] unfortunately I don't, hence me being cheeky and putting the issue out for volunteers ;-) Maybe try asking on the forums or for something like this even the dev list to see if there us anyone with some experience to help - I know various other engineers have worked with ApacheDS. > Add test cases to verify LDAP caching on security realms. > --------------------------------------------------------- > > Key: WFLY-3226 > URL: https://issues.jboss.org/browse/WFLY-3226 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Test Suite > Reporter: Darran Lofthouse > Fix For: Awaiting Volunteers > > > The existing test cases are based on a statically defined set of LDIFs, testing of caching could consider a couple of options: - > 1 - Interceptors within ApacheDS to verify if calls hit the directory. > 2 - Updates to the directory that would affect the outcome of tests if there is a cache hit, tests can then be repeated with and without clearing the cache. > Note: It would be beneficial for this to use different users and groups and maybe even different partitions so that test ordering does not affect the outcome if changes are made to the directory. -- 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

1
0
0 / 0

[JBoss JIRA] (DROOLS-456) ResourceConfigurationImpl class not found when using drools-karaf-feature

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/DROOLS-456?page=com.atlassian.jira.plugin... ] Gary Brown closed DROOLS-456. ----------------------------- Resolution: Out of Date Looks like the issue has been fixed in 6.1.0.Beta2. > ResourceConfigurationImpl class not found when using drools-karaf-feature > ------------------------------------------------------------------------- > > Key: DROOLS-456 > URL: https://issues.jboss.org/browse/DROOLS-456 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta1 > Reporter: Gary Brown > Assignee: Mario Fusco > Attachments: fuse-drools-issue.log > > > While porting RTGov to Karaf, I have been using Drools 2.0.0.CR5 successfully. > However when I updated the version to 2.0.1.Final, and subsequently to 2.1.0.Beta1, I now get a class not found issue: > {noformat} > 11:26:49,440 | ERROR | l Console Thread | ResourceTypeImpl | 290 - org.kie.internalapi - 6.1.0.20140307-1723 | Error loading resource configuration from properties > java.lang.ClassNotFoundException: org.drools.core.builder.conf.impl.ResourceConfigurationImpl not found by org.kie.internalapi [290] > at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)[org.apache.felix.framework-4.0.3.redhat-610355.jar:] > at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)[org.apache.felix.framework-4.0.3.redhat-610355.jar:] > at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07] > at java.lang.Class.forName0(Native Method)[:1.7.0_07] > at java.lang.Class.forName(Class.java:186)[:1.7.0_07] > at org.kie.internal.io.ResourceTypeImpl.fromProperties(ResourceTypeImpl.java:41)[290:org.kie.internalapi:6.1.0.20140307-1723] > {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

1
0
0 / 0

[JBoss JIRA] (WFLY-2623) Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2623?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2623: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1036739|https://bugzilla.redhat.com/show_bug.cgi?id=1036739] from ON_QA to VERIFIED > Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-2623 > URL: https://issues.jboss.org/browse/WFLY-2623 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Beta1 > Reporter: Amos Feng > Assignee: Hayk Hovsepyan > Labels: transaction > Fix For: 8.0.0.Final > > > https://bugzilla.redhat.com/show_bug.cgi?id=1036739 > process-id mechanism can not be changed from process-id-uuid to process-id-socket-binding. > The following ERROR occurred at JBoss start-up: > {noformat} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 44) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "JBAS014746: process-id-uuid may not be null" > {noformat} > The root reason is it does not check the PROCESS_ID_UUID if defined when booting the coreEnvironment service in TransactionSubsytemAdd. -- 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

1
0
0 / 0

[JBoss JIRA] (JBVFS-195) Reading MANIFEST with NULL char will fail

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBVFS-195?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated JBVFS-195: --------------------------------------- Forum Reference: https://community.jboss.org/message/869626#869626 > Reading MANIFEST with NULL char will fail > ----------------------------------------- > > Key: JBVFS-195 > URL: https://issues.jboss.org/browse/JBVFS-195 > Project: JBoss VFS > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > The paddinginputstream will create an issue if there is a NULL char in the MANIFEST as it will append \n after the NULL which breaks the attributes parsing. > https://community.jboss.org/message/869738 -- 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

1
0
0 / 0

[JBoss JIRA] (JBVFS-195) Reading MANIFEST with NULL char will fail

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created JBVFS-195: --------------------------------------- Summary: Reading MANIFEST with NULL char will fail Key: JBVFS-195 URL: https://issues.jboss.org/browse/JBVFS-195 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet The paddinginputstream will create an issue if there is a NULL char in the MANIFEST as it will append \n after the NULL which breaks the attributes parsing. https://community.jboss.org/message/869738 -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-3280) Thread locking problem when app server is going to shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3280?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3280: ------------------------------------------ Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1090147) > Thread locking problem when app server is going to shutdown > ------------------------------------------------------------ > > Key: WFLY-3280 > URL: https://issues.jboss.org/browse/WFLY-3280 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.CR1 > Reporter: Ondřej Chaloupka > Assignee: David Lloyd > Attachments: server.dump, server.log > > > I face problem that remoting thread and MSC service thread is deadlocked when server is going to shutdown. > This happens in half of the cases when I run my integration arquillian tests again EAP 6.3.0 engineering releases. > I deploy one testing application packaged as jar file and then jdbc driver is deployed by copying to deployments folder. > I'm attaching server log file and thread dump at the time when threads are stuck. > I was trying to find out where the lock occurs and from the stack trace it happens on two places. One is lock on remoting queue and other is lock on DeploymentRepository object. > I did a quick fix which seems to work for me that I removed 'synchronized' keyword from the methods which remove listeners in DeploymentRepository. > It means from: > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > and > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > I'm really not sure whether this is 'a correct' fix but I just put my observation here to have some starting point. > This could not be trouble in remoting directly, maybe it's rather problem of MSC component. If so, please, change the jira type. Thank you. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-3280) Thread locking problem when app server is going to shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3280?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3280: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1090147 > Thread locking problem when app server is going to shutdown > ------------------------------------------------------------ > > Key: WFLY-3280 > URL: https://issues.jboss.org/browse/WFLY-3280 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.CR1 > Reporter: Ondřej Chaloupka > Assignee: David Lloyd > Attachments: server.dump, server.log > > > I face problem that remoting thread and MSC service thread is deadlocked when server is going to shutdown. > This happens in half of the cases when I run my integration arquillian tests again EAP 6.3.0 engineering releases. > I deploy one testing application packaged as jar file and then jdbc driver is deployed by copying to deployments folder. > I'm attaching server log file and thread dump at the time when threads are stuck. > I was trying to find out where the lock occurs and from the stack trace it happens on two places. One is lock on remoting queue and other is lock on DeploymentRepository object. > I did a quick fix which seems to work for me that I removed 'synchronized' keyword from the methods which remove listeners in DeploymentRepository. > It means from: > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > and > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > I'm really not sure whether this is 'a correct' fix but I just put my observation here to have some starting point. > This could not be trouble in remoting directly, maybe it's rather problem of MSC component. If so, please, change the jira type. Thank you. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-3280) Thread locking problem when app server is going to shutdown

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3280?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on WFLY-3280: ---------------------------------------- I moved the bug under wildfly as I found that it's more appropriate. > Thread locking problem when app server is going to shutdown > ------------------------------------------------------------ > > Key: WFLY-3280 > URL: https://issues.jboss.org/browse/WFLY-3280 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.CR1 > Reporter: Ondřej Chaloupka > Assignee: David Lloyd > Attachments: server.dump, server.log > > > I face problem that remoting thread and MSC service thread is deadlocked when server is going to shutdown. > This happens in half of the cases when I run my integration arquillian tests again EAP 6.3.0 engineering releases. > I deploy one testing application packaged as jar file and then jdbc driver is deployed by copying to deployments folder. > I'm attaching server log file and thread dump at the time when threads are stuck. > I was trying to find out where the lock occurs and from the stack trace it happens on two places. One is lock on remoting queue and other is lock on DeploymentRepository object. > I did a quick fix which seems to work for me that I removed 'synchronized' keyword from the methods which remove listeners in DeploymentRepository. > It means from: > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > and > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > I'm really not sure whether this is 'a correct' fix but I just put my observation here to have some starting point. > This could not be trouble in remoting directly, maybe it's rather problem of MSC component. If so, please, change the jira type. Thank you. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-3280) Thread locking problem when app server is going to shutdown

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3280?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka moved REM3-188 to WFLY-3280: --------------------------------------------- Project: WildFly (was: Remoting 3) Key: WFLY-3280 (was: REM3-188) Affects Version/s: 8.1.0.CR1 (was: 3.3.1.Final) Security: Public > Thread locking problem when app server is going to shutdown > ------------------------------------------------------------ > > Key: WFLY-3280 > URL: https://issues.jboss.org/browse/WFLY-3280 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.CR1 > Reporter: Ondřej Chaloupka > Assignee: David Lloyd > Attachments: server.dump, server.log > > > I face problem that remoting thread and MSC service thread is deadlocked when server is going to shutdown. > This happens in half of the cases when I run my integration arquillian tests again EAP 6.3.0 engineering releases. > I deploy one testing application packaged as jar file and then jdbc driver is deployed by copying to deployments folder. > I'm attaching server log file and thread dump at the time when threads are stuck. > I was trying to find out where the lock occurs and from the stack trace it happens on two places. One is lock on remoting queue and other is lock on DeploymentRepository object. > I did a quick fix which seems to work for me that I removed 'synchronized' keyword from the methods which remove listeners in DeploymentRepository. > It means from: > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > and > https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jbos... > I'm really not sure whether this is 'a correct' fix but I just put my observation here to have some starting point. > This could not be trouble in remoting directly, maybe it's rather problem of MSC component. If so, please, change the jira type. Thank you. -- 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

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 April 2014