[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Daniel José dos Santos (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos edited comment on DROOLS-2819 at 9/13/18 5:51 PM:
-------------------------------------------------------------------------
The cause of both issues [2820] and this is the same and is fixed by the PR to [2820]. [~manstis]
was (Author: dadossan):
The cause of both issues is the same.
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Daniel José dos Santos (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos commented on DROOLS-2819:
------------------------------------------------
The cause of both issues is the same.
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Daniel José dos Santos (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos reassigned DROOLS-2819:
----------------------------------------------
Assignee: Daniel José dos Santos (was: Michael Anstis)
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1648) FIPS NoSuchAlgorithmException: JKS KeyStore not available when trustmanager SunX509
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1648?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1648:
----------------------------------
[~mchoma] Currently trying to reproduce the error, however this is my first time working on a FIPS related issue, could you please post the steps needed to reproduce the error? Could you also please post what values you used for the variables in cli-test-wildfly-config.xml?
> FIPS NoSuchAlgorithmException: JKS KeyStore not available when trustmanager SunX509
> -----------------------------------------------------------------------------------
>
> Key: ELY-1648
> URL: https://issues.jboss.org/browse/ELY-1648
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.5.Final
> Reporter: Martin Choma
> Assignee: Justin Cook
> Attachments: java.security
>
>
> With SunX509 truststore algorithm I can succesfully connect with CLI.
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:client:1.1">
> <key-stores>
> <key-store name="truststore" type="PKCS11">
> <key-store-clear-password password="${password}" />
> </key-store>
> </key-stores>
> <ssl-contexts>
> <ssl-context name="client-cli-context">
> <trust-manager algorithm="SunX509" />
> <trust-store key-store-name="truststore" />
> <cipher-suite selector="${cipher.suite.filter}" />
> <protocol names="${protocol}" />
> </ssl-context>
> </ssl-contexts>
> <ssl-context-rules>
> <rule use-ssl-context="client-cli-context" />
> </ssl-context-rules>
> </authentication-client>
> </configuration>
> {code}
> But there is a exception in log
> {code}
> 13:58:27,652 INFO [com.redhat.eap.qe.cli.CustomCLIExecutor] (main) java.security.KeyStoreException: JKS not found
> at java.security.KeyStore.getInstance(KeyStore.java:851)
> at sun.security.util.AnchorCertificates$1.run(AnchorCertificates.java:59)
> at sun.security.util.AnchorCertificates$1.run(AnchorCertificates.java:52)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.util.AnchorCertificates.<clinit>(AnchorCertificates.java:52)
> at sun.security.provider.certpath.AlgorithmChecker.checkFingerprint(AlgorithmChecker.java:214)
> at sun.security.provider.certpath.AlgorithmChecker.<init>(AlgorithmChecker.java:164)
> at sun.security.provider.certpath.AlgorithmChecker.<init>(AlgorithmChecker.java:118)
> at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:157)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:281)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1601)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:992)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:989)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1467)
> at org.xnio.ssl.JsseSslConduitEngine.handleHandshake(JsseSslConduitEngine.java:543)
> at org.xnio.ssl.JsseSslConduitEngine.wrap(JsseSslConduitEngine.java:314)
> at org.xnio.ssl.JsseSslConduitEngine.wrap(JsseSslConduitEngine.java:204)
> at org.xnio.ssl.JsseSslStreamSinkConduit.write(JsseSslStreamSinkConduit.java:98)
> at org.xnio.ssl.JsseSslStreamSinkConduit.write(JsseSslStreamSinkConduit.java:72)
> at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:94)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> Caused by: java.security.NoSuchAlgorithmException: JKS KeyStore not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
> at java.security.Security.getImpl(Security.java:695)
> at java.security.KeyStore.getInstance(KeyStore.java:848)
> ... 31 more
> {code}
> When I change SunX509 to PKIX exception does not occure anymore.
> Seems exception is thrown by code https://github.com/JetBrains/jdk8u_jdk/blob/master/src/share/classes/sun/...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10976) Artemis warnings during startup
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10976?page=com.atlassian.jira.plugin... ]
Brian Stansberry edited comment on WFLY-10976 at 9/13/18 3:27 PM:
------------------------------------------------------------------
Both standalone-full-ha.xml and standalone-full.xml on current master produce this in the server log:
{code}
13:43:15,457 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
13:43:15,458 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
{code}
was (Author: brian.stansberry):
Both standalone-full-ha.xml and standalone-full.xml on current master produce this in the server log:
{code}
13:43:15,457 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-162813:43:15,458 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
{code}
> Artemis warnings during startup
> -------------------------------
>
> Key: WFLY-10976
> URL: https://issues.jboss.org/browse/WFLY-10976
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Brian Stansberry
>
> Artemis logs these warnings during startup when using the stock standalone-full.xml configuration:
> {code}
> 12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
> 12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
> {code}
> It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10976) Artemis warnings during startup
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10976?page=com.atlassian.jira.plugin... ]
Brian Stansberry edited comment on WFLY-10976 at 9/13/18 3:26 PM:
------------------------------------------------------------------
Both standalone-full-ha.xml and standalone-full.xml on current master produce this in the server log:
{code}
13:43:15,457 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-162813:43:15,458 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
{code}
was (Author: brian.stansberry):
Both standalone-full-ha.xml and standalone-full.xml on current master produce this in the server log:
{code}
13:43:15,457 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
{code}
> Artemis warnings during startup
> -------------------------------
>
> Key: WFLY-10976
> URL: https://issues.jboss.org/browse/WFLY-10976
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Brian Stansberry
>
> Artemis logs these warnings during startup when using the stock standalone-full.xml configuration:
> {code}
> 12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
> 12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
> {code}
> It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11017) Artemis warnings during startup
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-11017:
---------------------------------------
Summary: Artemis warnings during startup
Key: WFLY-11017
URL: https://issues.jboss.org/browse/WFLY-11017
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Reporter: Rich DiCroce
Assignee: Brian Stansberry
Artemis logs these warnings during startup when using the stock standalone-full.xml configuration:
{code}
12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
{code}
It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10976) Artemis warnings during startup
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10976?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10976:
-----------------------------------------
[~jmesnil] [~ehugonnet] FYI. I'm poking at this for a bit this afternoon as it seems to be blocking acceptance testing of CD 14:
https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-accept...
If I haven't sent up a PR or something by your Friday, please feel free to take it over.
[~jamezp] [~kabirkhan] FYI.
> Artemis warnings during startup
> -------------------------------
>
> Key: WFLY-10976
> URL: https://issues.jboss.org/browse/WFLY-10976
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Brian Stansberry
>
> Artemis logs these warnings during startup when using the stock standalone-full.xml configuration:
> {code}
> 12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
> 12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
> {code}
> It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10976) Artemis warnings during startup
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10976?page=com.atlassian.jira.plugin... ]
Brian Stansberry reopened WFLY-10976:
-------------------------------------
Assignee: Brian Stansberry (was: Bartosz Baranowski)
Both standalone-full-ha.xml and standalone-full.xml on current master produce this in the server log:
{code}
13:43:15,457 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
{code}
> Artemis warnings during startup
> -------------------------------
>
> Key: WFLY-10976
> URL: https://issues.jboss.org/browse/WFLY-10976
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Brian Stansberry
>
> Artemis logs these warnings during startup when using the stock standalone-full.xml configuration:
> {code}
> 12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628
> 12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead
> {code}
> It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11016) Ensure the org.apache.geronimo.specs are explicitly excluded
by James Perkins (JIRA)
James Perkins created WFLY-11016:
------------------------------------
Summary: Ensure the org.apache.geronimo.specs are explicitly excluded
Key: WFLY-11016
URL: https://issues.jboss.org/browse/WFLY-11016
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: James Perkins
Assignee: James Perkins
Some dependencies are bringing in dependencies on {{org.apache.geronimo.specs:*}} specs. These should be excluded in favor of using the specs defined by WildFly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months