[JBoss JIRA] (DROOLS-2941) [DMN Designer] - save external dmn model
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2941?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2941:
--------------------------------
Description:
Save of an external dmn model in workbench throws an error in a server log.
- Before save: [^LACE Scoring.dmn]
- After save: [^lace-scoring.dmn]
was:Save of an external dmn model in workbench throws an error in a server log.
> [DMN Designer] - save external dmn model
> ----------------------------------------
>
> Key: DROOLS-2941
> URL: https://issues.jboss.org/browse/DROOLS-2941
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: LACE Scoring.dmn, error.log, lace-scoring.dmn
>
>
> Save of an external dmn model in workbench throws an error in a server log.
> - Before save: [^LACE Scoring.dmn]
> - After save: [^lace-scoring.dmn]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-10812) JDK11 Some security tests fail on closed channel exception
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10812?page=com.atlassian.jira.plugin... ]
Jan Kalina commented on WFLY-10812:
-----------------------------------
Tips for debugging for anybody who will solve similar issues:
To force SSL version on client side put following into system-properties in pom.xml:
{code}
<jdk.tls.server.protocols>TLSv1.2</jdk.tls.server.protocols>
<jdk.tls.client.protocols>TLSv1.2</jdk.tls.client.protocols>
{code}
To get SSL debug output from the wildfly started from test put arguments into arquillian.xml:
{code}
<property name="jbossArguments">${jboss.args} -Djavax.net.debug=all</property>
{code}
> JDK11 Some security tests fail on closed channel exception
> ----------------------------------------------------------
>
> Key: WFLY-10812
> URL: https://issues.jboss.org/browse/WFLY-10812
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Richard Opalka
> Assignee: Jan Kalina
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> With latest JDK11 (build 11-ea+25) the following tests fail due to closed channel exception: modified:
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapExtLikeAdvancedLdapLMTestCase.java
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapExtLoginModuleTestCase.java
> * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/security/loginmodules/LdapLoginModuleTestCase.java
> * testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ssl/UndertowTwoWaySslNeedClientAuthTestCase.java
> * testsuite/integration/iiop/src/test/java/org/jboss/as/test/iiopssl/basic/IIOPSslInvocationTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/security/OutboundLdapConnectionClientCertTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/security/OutboundLdapConnectionTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/CertificateRolesLoginModuleTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/DatabaseCertLoginModuleTestCase.java
> * testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/HTTPSWebConnectorTestCase.java
> * testsuite/integration/ws/src/test/java/org/jboss/as/test/integration/ws/wsse/trust/WSTrustTestCase.java
> Is there a known SSL issue in JDK11? Could somebody from our security team investigate this issue?
> When these tests will start passing WF test suite will be passing 100% of tests on JDK11.
> Potential investigator from our security team may want to include this PR:
> https://github.com/wildfly/wildfly/pull/11499
> to fix known JDK11 issues.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-10950) JDK11 basic LdapLoginModuleTestCase failure
by Jan Kalina (JIRA)
Jan Kalina created WFLY-10950:
---------------------------------
Summary: JDK11 basic LdapLoginModuleTestCase failure
Key: WFLY-10950
URL: https://issues.jboss.org/browse/WFLY-10950
Project: WildFly
Issue Type: Sub-task
Components: Test Suite
Reporter: Jan Kalina
{code}
cd testsuite/integration/basic
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=LdapLoginModuleTestCase#testLdaps -Djavax.net.debug=all
{code}
{code}
javax.net.ssl|ERROR|1D|NioProcessor-5|2018-08-30 12:28:39.055 CEST|TransportContext.java:317|Fatal (CERTIFICATE_UNKNOWN): Received fatal alert: certificate_unknown (
"throwable" : {
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:128)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:312)
at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:270)
at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:181)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164)
at java.base/sun.security.ssl.SSLEngineImpl.decode(SSLEngineImpl.java:666)
at java.base/sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:621)
at java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:438)
at java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:417)
at java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
at org.apache.mina.filter.ssl.SslHandler.unwrap(SslHandler.java:754)
at org.apache.mina.filter.ssl.SslHandler.unwrapHandshake(SslHandler.java:689)
at org.apache.mina.filter.ssl.SslHandler.handshake(SslHandler.java:575)
at org.apache.mina.filter.ssl.SslHandler.messageReceived(SslHandler.java:360)
at org.apache.mina.filter.ssl.SslFilter.messageReceived(SslFilter.java:500)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:542)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300(DefaultIoFilterChain.java:48)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:947)
at org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:109)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:542)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:535)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:703)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:659)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:648)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(AbstractPollingIoProcessor.java:68)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1120)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-2535) Standalone Authoring - Project Explorer should show up
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2535?page=com.atlassian.jira.plugi... ]
Toni Rikkola commented on DROOLS-2535:
--------------------------------------
[~tomasdavidorg] Since LibraryPerspective covers what the Project Explorer used to do. Changing projects, finding assets and so on. I think it then covers all the needs that the AuthoringStandalone used to do.
And for just opening a specific asset. You can now do that with the AuthoringPerspective. Since it is still included in kie-drools-wb.war I should probably remove it. I can rename and reopen this ticket for the task.
> Standalone Authoring - Project Explorer should show up
> ------------------------------------------------------
>
> Key: DROOLS-2535
> URL: https://issues.jboss.org/browse/DROOLS-2535
> Project: Drools
> Issue Type: Bug
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
>
> When using the Workbench standalone the Project Explorer does not show up for kie-wb.war. It does work for kie-drools-wb.war
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months