[JBoss JIRA] (DROOLS-3038) [DMN Designer] Added type can not be resolved
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3038:
---------------------------------------
Story Points: 5
> [DMN Designer] Added type can not be resolved
> ---------------------------------------------
>
> Key: DROOLS-3038
> URL: https://issues.jboss.org/browse/DROOLS-3038
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Blocker
> Labels: drools-tools
> Attachments: DROOLS-3038.dmn, Screenshot from 2018-09-26 12-57-20.png, Screenshot from 2018-09-26 12-58-02.png, Screenshot from 2018-09-26 12-58-12.png
>
>
> {{12:53:34,884 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 3) Unable to resolve type reference 'tNum' on node 'Decision-1'}} is error shown to user after reopening DMN model with used new defined item definition.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11229) Quickstarts JBDS WSDLAnalyzer warning
by Sande Gilda (Jira)
[ https://issues.jboss.org/browse/WFLY-11229?page=com.atlassian.jira.plugin... ]
Sande Gilda moved JBEAP-15710 to WFLY-11229:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11229 (was: JBEAP-15710)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: Quickstarts)
> Quickstarts JBDS WSDLAnalyzer warning
> -------------------------------------
>
> Key: WFLY-11229
> URL: https://issues.jboss.org/browse/WFLY-11229
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS
> Reporter: Sande Gilda
> Assignee: Eduardo Martins
> Priority: Major
>
> The following quickstarts:
> * jaxws-addressing
> * jaxws-retail
> * wsat-simple
> have the following warning after an import to Red Hat Developer Studio:
> {noformat}
> WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
> AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
> RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem
> ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
> {noformat}
> This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10504) -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFLY-10504?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-10504:
---------------------------------
cc: Marek Kopecky, James Perkins, Kabir Khan
I've withdrawn as jira owner. I don't have timely access to a windows machine.
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> -----------------------------------------------------------------------
>
> Key: WFLY-10504
> URL: https://issues.jboss.org/browse/WFLY-10504
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Priority: Critical
>
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> Steps to reproduce:
> # start powershell
> # .\domain.bat "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is present in PC or HC
> # exit domain.bat
> # .\domain.ps1 "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is *not* present in PC or HC
> Secmgr can't be enabled also by $env:SECMGR = "true"
> This issue is not about java-opts, but it is related with WFCORE-3830
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10504) -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFLY-10504?page=com.atlassian.jira.plugin... ]
R Searls reassigned WFLY-10504:
-------------------------------
Assignee: (was: R Searls)
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> -----------------------------------------------------------------------
>
> Key: WFLY-10504
> URL: https://issues.jboss.org/browse/WFLY-10504
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Priority: Critical
>
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> Steps to reproduce:
> # start powershell
> # .\domain.bat "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is present in PC or HC
> # exit domain.bat
> # .\domain.ps1 "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is *not* present in PC or HC
> Secmgr can't be enabled also by $env:SECMGR = "true"
> This issue is not about java-opts, but it is related with WFCORE-3830
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10944) Add Timer script for MariaDB
by Filippe Spolti (Jira)
[ https://issues.jboss.org/browse/WFLY-10944?page=com.atlassian.jira.plugin... ]
Filippe Spolti commented on WFLY-10944:
---------------------------------------
Hi [~bstansberry2], do you think it can be ported to eap 7.2?
> Add Timer script for MariaDB
> ----------------------------
>
> Key: WFLY-10944
> URL: https://issues.jboss.org/browse/WFLY-10944
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Ruben Romero Montes
> Assignee: Ruben Romero Montes
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> The timer-sql properties file is missing a script for MariaDB. It is indeed the same as for MySQL but it is more convenient to have its own entry.
> It will help when configuring a MariaDB datasource.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-3151:
---------------------------------------
[~uxdlc] [~bdellasc]
Please consider during the definition of the new palette of colours also the "error state"
https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070
> [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-3151
> URL: https://issues.jboss.org/browse/DROOLS-3151
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools
> Attachments: GDT.png, dtable-column-colours.png
>
>
> [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
> {quote}
> this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
> {quote}
> See the attached screenshot.
> Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (AG-100) Bypass validate-on-borrow
by Philippe Marschall (Jira)
Philippe Marschall created AG-100:
-------------------------------------
Summary: Bypass validate-on-borrow
Key: AG-100
URL: https://issues.jboss.org/browse/AG-100
Project: Agroal
Issue Type: Feature Request
Reporter: Philippe Marschall
Assignee: Luis Barreiro
We recently evaluated JDBC connections pools for Java SE and were impressed by the connection validation algorithm implemented by [HikariCP|https://github.com/brettwooldridge/HikariCP]. We would like to see something similar implemented by Agroal.
HikariCP implements validate-on-borrow using {{java.sql.Connection.isValid(int)}} (Java 1.6/JDBC 4.0). However if the connection has been successfully used in the past 500ms then this check is bypassed. To quote the author
{quote}Generally speaking, in an active application or process, this avoids nearly all validation, while providing confidence that the connections returned by the pool are actually alive.{quote}
Discussion is here https://groups.google.com/forum/#!searchin/hikari-cp/batch%7Csort:date/hi...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10469) Dropped message did not match the computed checksum
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-10469?page=com.atlassian.jira.plugin... ]
Radoslav Husar closed WFLY-10469.
---------------------------------
Fix Version/s: 14.0.0.Final
Resolution: Done
Resolving – this has been fixed somewhere before WF 14 went final.
> Dropped message did not match the computed checksum
> ---------------------------------------------------
>
> Key: WFLY-10469
> URL: https://issues.jboss.org/browse/WFLY-10469
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Romain Pelisse
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 14.0.0.Final
>
>
> We saw this error during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) (21 occurences).
> The error started to occur on *server*
> {code}
> 04:42:59,767 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-20,ee,perf21) perf21: exception occurred decrypting message
> [JBossINF] 04:42:59,768 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: dropped message from perf20 as the message's checksum (3775292975120264796) did not match the computed checksum (2347657351)
> [JBossINF] 04:42:59,768 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-10,ee,perf21) perf21: unrecognized cipher; discarding message from perf20
> {code}
> together with decrypting WARN messages 2 seconds after new cluster view was received:
> {code}
> 04:42:57,878 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-6,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf19|4] (3) [perf19, perf21, perf20]
> {code}
> Link to server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov...
> Client did not log any error at that time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months