January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1023) Change kmodule.xsd targetNamespace to become versionless (to avoid hardcoding "6.0.0" in it)

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1023: ---------------------------------------- Summary: Change kmodule.xsd targetNamespace to become versionless (to avoid hardcoding "6.0.0" in it) Key: DROOLS-1023 URL: https://issues.jboss.org/browse/DROOLS-1023 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 6.3.0.Final Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 6.4.x Switch namespace to "http://www.drools.org/xsd/kmodule". But also make sure that the old namespace "http://jboss.org/kie/6.0.0/kmodule" still works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1022) WebSphere: unable to deploy Kie server war

by Karel Suta (JIRA)

Karel Suta created DROOLS-1022: ---------------------------------- Summary: WebSphere: unable to deploy Kie server war Key: DROOLS-1022 URL: https://issues.jboss.org/browse/DROOLS-1022 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 6.4.x Environment: WebSphere Platform 8.5.5.7 Kie server 6.4.0-SNAPSHOT Reporter: Karel Suta Assignee: Edson Tirelli Attachments: SystemOut.log When I try to deploy latest Kie server on WebSphere I get exception listed in log. This error also prevents user from logging into WebSphere console (with error: "SECJ0118E: Authentication error during authentication for user xxx") In 6.3.1-SNAPSHOT deployment works without issue. Issue may be related xercesImpl which was missing in 6.3.1 and is present in 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1993) ENCRYPTAsymmetricTest fails on IBM jdk 1.8

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/JGRP-1993?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on JGRP-1993: --------------------------------------- I don't think it is much of an issue: the IBM JDK is returning its own internal representation for the key spec, but I expect the behaviour to be identical. The test should be fixed to verify key equivalence instead of equality. > ENCRYPTAsymmetricTest fails on IBM jdk 1.8 > ------------------------------------------ > > Key: JGRP-1993 > URL: https://issues.jboss.org/browse/JGRP-1993 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.6 > Environment: IBM jdk 1.8 > Reporter: Richard Janík > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.7 > > > org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange fails on IBM jdk 1.8 (JGroups 3.6.6.Final): > {code} > Error Message > expected [javax.crypto.spec.SecretKeySpec@174de] but found [com.ibm.crypto.provider.AESSecretKey@e562eaa8] > Stacktrace > java.lang.AssertionError > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotEquals(Assert.java:496) > at org.testng.Assert.assertEquals(Assert.java:125) > at org.testng.Assert.assertEquals(Assert.java:167) > at org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange(ENCRYPTAsymmetricTest.java:404) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:639) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108) > at org.testng.TestRunner.privateRun(TestRunner.java:774) > at org.testng.TestRunner.run(TestRunner.java:624) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:359) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312) > at org.testng.SuiteRunner.run(SuiteRunner.java:261) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1140) > at org.testng.TestNG.run(TestNG.java:1048) > at org.testng.TestNG.privateMain(TestNG.java:1355) > at org.testng.TestNG.main(TestNG.java:1324) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5636) Cannot load root node after domain start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-5636?page=com.atlassian.jira.plugin.... ] Thomas Diesler reassigned WFLY-5636: ------------------------------------ Assignee: (was: Thomas Diesler) > Cannot load root node after domain start > ----------------------------------------- > > Key: WFLY-5636 > URL: https://issues.jboss.org/browse/WFLY-5636 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Thomas Diesler > > {code} > Caused by: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined > at org.jboss.as.arquillian.container.domain.ManagementClient.checkSuccessful(ManagementClient.java:446) > at org.jboss.as.arquillian.container.domain.ManagementClient.executeForResult(ManagementClient.java:439) > at org.jboss.as.arquillian.container.domain.ManagementClient.readResource(ManagementClient.java:417) > at org.jboss.as.arquillian.container.domain.ManagementClient.readRootNode(ManagementClient.java:294) > at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:387) > at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115) > at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:126) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1993) ENCRYPTAsymmetricTest fails on IBM jdk 1.8

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1993?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1993: -------------------------------- I have no idea what the problem is, but I'm no security expert. I asked [~NadirX] to take a look... > ENCRYPTAsymmetricTest fails on IBM jdk 1.8 > ------------------------------------------ > > Key: JGRP-1993 > URL: https://issues.jboss.org/browse/JGRP-1993 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.6 > Environment: IBM jdk 1.8 > Reporter: Richard Janík > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.7 > > > org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange fails on IBM jdk 1.8 (JGroups 3.6.6.Final): > {code} > Error Message > expected [javax.crypto.spec.SecretKeySpec@174de] but found [com.ibm.crypto.provider.AESSecretKey@e562eaa8] > Stacktrace > java.lang.AssertionError > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotEquals(Assert.java:496) > at org.testng.Assert.assertEquals(Assert.java:125) > at org.testng.Assert.assertEquals(Assert.java:167) > at org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange(ENCRYPTAsymmetricTest.java:404) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:639) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108) > at org.testng.TestRunner.privateRun(TestRunner.java:774) > at org.testng.TestRunner.run(TestRunner.java:624) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:359) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312) > at org.testng.SuiteRunner.run(SuiteRunner.java:261) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1140) > at org.testng.TestNG.run(TestNG.java:1048) > at org.testng.TestNG.privateMain(TestNG.java:1355) > at org.testng.TestNG.main(TestNG.java:1324) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5652) Datasource spy attribute has no effect

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-5652?page=com.atlassian.jira.plugin.... ] Lin Gao closed WFLY-5652. ------------------------- Resolution: Cannot Reproduce If anyone does not agree, please feel free to reopen. :-) > Datasource spy attribute has no effect > -------------------------------------- > > Key: WFLY-5652 > URL: https://issues.jboss.org/browse/WFLY-5652 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2 > Reporter: Rich DiCroce > Assignee: Lin Gao > > The spy attribute of a datasource does not appear to have any effect. The datasources XSD says to set spy to true and enable the org.jboss.jdbc log category, but I did that and got no debug info in my log. From a quick search of the WildFly and IronJacamar codebases, it looks like no meaningful code ever checks the value of the spy attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5652) Datasource spy attribute has no effect

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-5652?page=com.atlassian.jira.plugin.... ] Lin Gao commented on WFLY-5652: ------------------------------- I tested using log category: 'jboss.jdbc.spy', and it works well. So close it. > Datasource spy attribute has no effect > -------------------------------------- > > Key: WFLY-5652 > URL: https://issues.jboss.org/browse/WFLY-5652 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2 > Reporter: Rich DiCroce > Assignee: Lin Gao > > The spy attribute of a datasource does not appear to have any effect. The datasources XSD says to set spy to true and enable the org.jboss.jdbc log category, but I did that and got no debug info in my log. From a quick search of the WildFly and IronJacamar codebases, it looks like no meaningful code ever checks the value of the spy attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1202: ------------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1196343|https://bugzilla.redhat.com/show_bug.cgi?id=1196343] from MODIFIED to ASSIGNED > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Derek Horton > Fix For: 2.0.5.CR1 > > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1202: ------------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1196343|https://bugzilla.redhat.com/show_bug.cgi?id=1196343] from POST to MODIFIED > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Derek Horton > Fix For: 2.0.5.CR1 > > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5652) Datasource spy attribute has no effect

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-5652?page=com.atlassian.jira.plugin.... ] Lin Gao commented on WFLY-5652: ------------------------------- Would you please try whether log category: "jboss.jdbc.spy" works for you? > Datasource spy attribute has no effect > -------------------------------------- > > Key: WFLY-5652 > URL: https://issues.jboss.org/browse/WFLY-5652 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2 > Reporter: Rich DiCroce > Assignee: Lin Gao > > The spy attribute of a datasource does not appear to have any effect. The datasources XSD says to set spy to true and enable the org.jboss.jdbc log category, but I did that and got no debug info in my log. From a quick search of the WildFly and IronJacamar codebases, it looks like no meaningful code ever checks the value of the spy attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016