November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type (/) - Parameters recognized in imported 1.1. model (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Parameters recognized in imported 1.2. model (/) - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type (/) - Parameters recognized in imported 1.1. model - Parameters recognized in imported 1.2. model - Undo/Redo (/) - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below > - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Function parameter is simple data type (/) > - Parameters recognized in imported 1.1. model (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Parameters recognized in imported 1.2. model (/) > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type (/) - Parameters recognized in imported 1.1. model - Parameters recognized in imported 1.2. model - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Parameters recognized in imported 1.1. model - Parameters recognized in imported 1.2. model - Undo/Redo (/) - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below > - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Function parameter is simple data type (/) > - Parameters recognized in imported 1.1. model > - Parameters recognized in imported 1.2. model > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2869) Use a dock component in the right panel to match the UX proposal

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2869?page=com.atlassian.jira.plugi... ] Toni Rikkola reopened DROOLS-2869: ---------------------------------- > Use a dock component in the right panel to match the UX proposal > ---------------------------------------------------------------- > > Key: DROOLS-2869 > URL: https://issues.jboss.org/browse/DROOLS-2869 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Priority: Major > > Update right panel interation to match UX proposal -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Parameters recognized in imported 1.1. model - Parameters recognized in imported 1.2. model - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below > - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Function parameter is simple data type > - Parameters recognized in imported 1.1. model > - Parameters recognized in imported 1.2. model > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - -Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123]- similar produced during verification of the below > - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Function parameter is simple data type > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/2227#issuecomment-...] > - Function parameter is simple data type > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type - Function parameter is simple data type - Undo/Redo (/) - Chrome, Edge, Firefox (/) was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type - Function parameter is simple data type - Undo/Redo - Chrome, Edge, Firefox (/) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type > - Function parameter is simple data type > - Undo/Redo (/) > - Chrome, Edge, Firefox (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3193: -------------------------------------- [~tirelli], I don't think this is the case. Based on discussions with [~gabriolo] and [~danielezonca], my understanding is that having multiple anonymous instances of the same type does not really make sense (even to the user; how would you distinguish between them?). Please ask Gabriele and Daniele for further information. [~uxdlc], to me, introducing aliases ("nicknames") is the most straightforward and simple option to do. > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png > > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11134) SecurityAuditingTestCase fails intermittently

by Radovan Stancel (Jira)

[ https://issues.jboss.org/browse/WFLY-11134?page=com.atlassian.jira.plugin... ] Radovan Stancel commented on WFLY-11134: ---------------------------------------- [~vobratil]This issue is specific only to RHEL? I am running it on Win 10 with following configuration: $ mvn --version Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) Maven home: E:\devel\tools\apache-maven-3.5.3 Java version: 11.0.1, vendor: Oracle Corporation Java home: E:\devel\tools\jdk-11.0.1 and the test is passing: [INFO] Running org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 67.544 s - in org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase > SecurityAuditingTestCase fails intermittently > --------------------------------------------- > > Key: WFLY-11134 > URL: https://issues.jboss.org/browse/WFLY-11134 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Environment: RHEL6 (x86_64), dynamic, large > OpenJDK 1.8 and OpenJDK 1.11 > Apache Maven 3.5.0 > and > Apache Maven 3.5.0 (Red Hat 3.5.0-6) > Maven home: /usr/share/maven > Java version: 1.8.0_181, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181.b15-0.fc27.x86_64/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.18.10-100.fc27.x86_64", arch: "amd64", family: "unix" > --- > openjdk version "1.8.0_181" > OpenJDK Runtime Environment (build 1.8.0_181-b15) > OpenJDK 64-Bit Server VM (build 25.181-b15, mixed mode) > Reporter: Vilém Obrátil > Priority: Major > > org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template seems to occasionally fail with the following message: > Login record has not been written into audit log! (time expired). Checked regex=(TRACE.+org.jboss.security.audit.+Success.+user1|SecurityAuthenticationSuccessfulEvent.*"name":"user1") > This seems to be happening most often on RHEL 6 x64 machines. > *Stack Trace:* > java.lang.AssertionError: Login record has not been written into audit log! (time expired). Checked regex=(TRACE.+org.jboss.security.audit.+Success.+user1|SecurityAuthenticationSuccessfulEvent.*"name":"user1") > at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.checkAuditLog(SecurityAuditingTestCase.java:234) > at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template(SecurityAuditingTestCase.java:188) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260) > at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:324) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:317) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-209) NoSuchAlgorithmException in SocketHandlerTests on IBM JDK

by Nikoleta Žiaková (Jira)

Nikoleta Žiaková created LOGMGR-209: --------------------------------------- Summary: NoSuchAlgorithmException in SocketHandlerTests on IBM JDK Key: LOGMGR-209 URL: https://issues.jboss.org/browse/LOGMGR-209 Project: JBoss Log Manager Issue Type: Bug Affects Versions: 2.1.5.Final Reporter: Nikoleta Žiaková Following tests fail on IBM JDK: {code} org.jboss.logmanager.handlers.SocketHandlerTests#testProtocolChange org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConnection org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConfig {code} Error: {code} java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) {code} Stack Trace: {code} Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) at java.security.Provider$Service.newInstance(Provider.java:1628) at sun.security.jca.GetInstance.getInstance(GetInstance.java:248) at sun.security.jca.GetInstance.getInstance(GetInstance.java:176) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:6) at javax.net.ssl.SSLContext.getDefault(SSLContext.java:8) at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:32) ... 29 more Caused by: java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format at com.ibm.jsse2.ah.a(ah.java:72) at com.ibm.jsse2.aj.g(aj.java:5) at com.ibm.jsse2.aj.<init>(aj.java:13) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) at java.lang.reflect.Constructor.newInstance(Constructor.java:437) at java.security.Provider$Service.newInstance(Provider.java:1606) ... 34 more {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 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 November 2018