January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2001) Can't enter time of day portion of Date object belonging to a fact in test Scenarios

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2001?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2001: -------------------------------- Tester: Jozef Marko > Can't enter time of day portion of Date object belonging to a fact in test Scenarios > ------------------------------------------------------------------------------------- > > Key: DROOLS-2001 > URL: https://issues.jboss.org/browse/DROOLS-2001 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Running on Windows 7 with BRMS Standalone 5.1. Issue arises in both firefox and google chrome browsers. > Reporter: Jeff Forte > Assignee: Guilherme Carreiro > Fix For: 7.6.0.Final > > > I have a set of facts that hold a Date asset for comparison between each other. The comparison is supposed to be between the time of day of the object; however, when trying to enter the date and time of day into the test scenario the time of day portion always gets wiped upon running the scenario. The date stays but there is no long any time of day and I can't seem to find a way to enter the time even with the "enter date" button. I can't test while this is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2223) Conversion from XLSX decision table -> Guided Decision Table has not worked correctly.

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2223?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-2223: ----------------------------------- Assignee: Michael Anstis (was: Mario Fusco) > Conversion from XLSX decision table -> Guided Decision Table has not worked correctly. > -------------------------------------------------------------------------------------- > > Key: DROOLS-2223 > URL: https://issues.jboss.org/browse/DROOLS-2223 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, XLS Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Shabbeer Shaik > Assignee: Michael Anstis > Attachments: myrepo_Test_Dates.zip > > > Please check the below link for more details > https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w > Getting Error : > {color:red}Error :{color} > [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2223) Conversion from XLSX decision table -> Guided Decision Table has not worked correctly.

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2223?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2223: -------------------------------- Tester: Jozef Marko Description: Please check the below link for more details https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w Getting Error : {color:red}Error :{color} [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] was: Please check the below link for more details https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w > Conversion from XLSX decision table -> Guided Decision Table has not worked correctly. > -------------------------------------------------------------------------------------- > > Key: DROOLS-2223 > URL: https://issues.jboss.org/browse/DROOLS-2223 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor, XLS Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Shabbeer Shaik > Assignee: Mario Fusco > Attachments: myrepo_Test_Dates.zip > > > Please check the below link for more details > https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w > Getting Error : > {color:red}Error :{color} > [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2223) Conversion from XLSX decision table -> Guided Decision Table has not worked correctly.

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2223?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2223: -------------------------------- Component/s: (was: decision tables) > Conversion from XLSX decision table -> Guided Decision Table has not worked correctly. > -------------------------------------------------------------------------------------- > > Key: DROOLS-2223 > URL: https://issues.jboss.org/browse/DROOLS-2223 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, XLS Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Shabbeer Shaik > Assignee: Mario Fusco > Attachments: myrepo_Test_Dates.zip > > > Please check the below link for more details > https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w > Getting Error : > {color:red}Error :{color} > [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2223) Conversion from XLSX decision table -> Guided Decision Table has not worked correctly.

by Shabbeer Shaik (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2223?page=com.atlassian.jira.plugi... ] Shabbeer Shaik updated DROOLS-2223: ----------------------------------- Description: Please check the below link for more details https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w was: Please check the below link for more details https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w Getting Error : {color:red}Error :{color} [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] > Conversion from XLSX decision table -> Guided Decision Table has not worked correctly. > -------------------------------------------------------------------------------------- > > Key: DROOLS-2223 > URL: https://issues.jboss.org/browse/DROOLS-2223 > Project: Drools > Issue Type: Bug > Components: decision tables, Guided Decision Table Editor, XLS Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Shabbeer Shaik > Assignee: Mario Fusco > Attachments: myrepo_Test_Dates.zip > > > Please check the below link for more details > https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2223) Conversion from XLSX decision table -> Guided Decision Table has not worked correctly.

by Shabbeer Shaik (JIRA)

Shabbeer Shaik created DROOLS-2223: -------------------------------------- Summary: Conversion from XLSX decision table -> Guided Decision Table has not worked correctly. Key: DROOLS-2223 URL: https://issues.jboss.org/browse/DROOLS-2223 Project: Drools Issue Type: Bug Components: decision tables, Guided Decision Table Editor, XLS Decision Table Editor Affects Versions: 7.4.1.Final Reporter: Shabbeer Shaik Assignee: Mario Fusco Attachments: myrepo_Test_Dates.zip Please check the below link for more details https://groups.google.com/forum/#!topic/drools-usage/iPIwL-QC77w Getting Error : {color:red}Error :{color} [KBase: defaultKieBase]: Unable to Analyse Expression getBP_DATE() > "-12": [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-9096 at 1/9/18 8:09 AM: ---------------------------------------------------------- Fix can be merged as soon as Artemis will be upgraded as part of WFLY-9407. (backports was rejected - artemis will be upgraded soon instead) was (Author: honza889): Fix can be merged as soon as Artemis will be upgraded as part of WFLY-9407. > JMS client fails to connect with SSL on IBM JDK 8 > ------------------------------------------------- > > Key: WFLY-9096 > URL: https://issues.jboss.org/browse/WFLY-9096 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Affects Versions: 11.0.0.Alpha1 > Environment: IBM JDK 8: > {code} > $ java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled) > J9VM - R28_20170314_2309_B340265 > JIT - tr.r14.java.green_20170314_134138 > GC - R28_20170314_2309_B340265 > J9CL - 20170314_340265) > JCL - 20170318_01 based on Oracle jdk8u121-b13 > {code} > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: eap7.1-risks-mitigation > > If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with: > {code} > ERROR: AMQ214016: Failed to create netty connection > java.nio.channels.ClosedChannelException > at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) > Producer got exception and ended:javax.jms.JMSException: Failed to create session factory > javax.jms.JMSException: Failed to create session factory > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260) > at ProducerTransSession.run(ProducerTransSession.java:75) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755) > ... 3 more > {code} > If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully. > Issue is under investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-9096: ---------------------------------- Fix can be merged as soon as Artemis will be upgraded as part of WFLY-9407. > JMS client fails to connect with SSL on IBM JDK 8 > ------------------------------------------------- > > Key: WFLY-9096 > URL: https://issues.jboss.org/browse/WFLY-9096 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Affects Versions: 11.0.0.Alpha1 > Environment: IBM JDK 8: > {code} > $ java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled) > J9VM - R28_20170314_2309_B340265 > JIT - tr.r14.java.green_20170314_134138 > GC - R28_20170314_2309_B340265 > J9CL - 20170314_340265) > JCL - 20170318_01 based on Oracle jdk8u121-b13 > {code} > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: eap7.1-risks-mitigation > > If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with: > {code} > ERROR: AMQ214016: Failed to create netty connection > java.nio.channels.ClosedChannelException > at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) > Producer got exception and ended:javax.jms.JMSException: Failed to create session factory > javax.jms.JMSException: Failed to create session factory > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260) > at ProducerTransSession.run(ProducerTransSession.java:75) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787) > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755) > ... 3 more > {code} > If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully. > Issue is under investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9529) Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry

by Scott Van Wart (JIRA)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Scott Van Wart commented on WFLY-9529: -------------------------------------- [~emmartins] You were perfectly clear. I was looking for a workaround. Unfortunately packaging our deployment as a single WAR would involve a dramatic restructuring that we simply can't do. I've since created an EJB that accepts a lambda it provides with an @Injected JMSContext. We're running with this for awhile to see if the issue appears but it looks like a viable workaround for now. > Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9529 > URL: https://issues.jboss.org/browse/WFLY-9529 > Project: WildFly > Issue Type: Bug > Components: JMS, Naming > Affects Versions: 10.1.0.Final, 11.0.0.Final > Environment: Running on Windows 10, Java 64-bit 1.8.0_131 > Reporter: Scott Van Wart > Assignee: Eduardo Martins > Labels: ActiveMQ, jms, transaction > Attachments: injected-jms.zip, injected-jms2.zip, wildfly-11-injected-jms.txt > > > If I try to use an @Injected JMSContext while executing within a background task (ManagedExecutorService) or thread (ManagedThreadFactory), I get the attached stacktrace. I've experienced this a number of times with Wildfly 10.1.0, including messages sent in Infinispan's expiry task thread. > My original workaround was to submit an additional task on a separate thread to send the message, then wait for it to complete. That seemed unreliable (sometimes it would still produce NameNotFoundException). I've resorted to creating my own JMSContext by using @Resource( lookup="java:/ConnectionFactory" ) and sending messages that way. Both workarounds prevent the message sending logic from participating in any ongoing transactions. > I'm also attaching a sample EAR project. It can be built with Maven. It creates a background task that waits 3 seconds and then tries to send a JMS message in a new transaction using an injected JMS context. I use the standalone-full.xml profile to run it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9529) Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-9529: --------------------------------------- [~silvaran] maybe I was not clear enough but packing your app in a war, instead of ear, is the workaround. This (app scope cdi events) is a relative new and grey area in spec, for instance Glassfish 5 provides some JNDI access but JMS there malfunctions, plus the fix in progress is in sensitive code so I want to be sure we going the right direction. > Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9529 > URL: https://issues.jboss.org/browse/WFLY-9529 > Project: WildFly > Issue Type: Bug > Components: JMS, Naming > Affects Versions: 10.1.0.Final, 11.0.0.Final > Environment: Running on Windows 10, Java 64-bit 1.8.0_131 > Reporter: Scott Van Wart > Assignee: Eduardo Martins > Labels: ActiveMQ, jms, transaction > Attachments: injected-jms.zip, injected-jms2.zip, wildfly-11-injected-jms.txt > > > If I try to use an @Injected JMSContext while executing within a background task (ManagedExecutorService) or thread (ManagedThreadFactory), I get the attached stacktrace. I've experienced this a number of times with Wildfly 10.1.0, including messages sent in Infinispan's expiry task thread. > My original workaround was to submit an additional task on a separate thread to send the message, then wait for it to complete. That seemed unreliable (sometimes it would still produce NameNotFoundException). I've resorted to creating my own JMSContext by using @Resource( lookup="java:/ConnectionFactory" ) and sending messages that way. Both workarounds prevent the message sending logic from participating in any ongoing transactions. > I'm also attaching a sample EAR project. It can be built with Maven. It creates a background task that waits 3 seconds and then tries to send a JMS message in a new transaction using an injected JMS context. I use the standalone-full.xml profile to run it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018