April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8635) Monitoring SessionTimeout of Specific SFSB

by Yogesh Vedpathak (JIRA)

Yogesh Vedpathak created WFLY-8635: -------------------------------------- Summary: Monitoring SessionTimeout of Specific SFSB Key: WFLY-8635 URL: https://issues.jboss.org/browse/WFLY-8635 Project: WildFly Issue Type: Feature Request Components: EJB, Web (Undertow) Affects Versions: 10.0.0.CR1 Environment: JBoss EAP 7. WildFly 10 Reporter: Yogesh Vedpathak Assignee: Stuart Douglas Priority: Optional Requirement is to monitor the SessionTimeout set for a Stateful Session Bean. Jboss gives a default timeout for session beans which can be monitored through CLI. SessionTimeout set for a specific bean, will either be in the bean code with annotaion or in the config files. This can not be monitored through JBoss. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1477) DMN Extension Elements

by Alexandros Koufoudakis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1477?page=com.atlassian.jira.plugi... ] Alexandros Koufoudakis updated DROOLS-1477: ------------------------------------------- Description: To use extension elements inside inputData elements in order to provide “external” information: GEO location, time and location tracking of a decision making (when and were specific decision was taken). This is the primary scope of the use. In case extension element represents a complex type customer prefers to get back an instance of the complex type, assuming the complex type is defined as a class by the development team on the customer side. However, the customer also understands that it can be more complex and considers the possibility to get the complex type as an XML snippet. The parsing and turning the XML snippet into the complex type, defined by the customer. The possibility of getting the list of extension elements is expected from other DMN elements, which extend from DMNElement, according to the DMN specification and meta model diagram by OMG. In other words, the usage of extension elements is not limited to be a part of input data elements only. The client is not expecting “authoring” of the extension elements. Since extension elements are a part of DMN specification, this is an attempt to make it possible for drools to register custom extension elements in a generic way. was:Currently, the extension elements are disregarded. As I'm working in one of the projects, which uses Drools 7 beta release and relies on extension elements, I would like to add this feature and to try to implement it. > DMN Extension Elements > ---------------------- > > Key: DROOLS-1477 > URL: https://issues.jboss.org/browse/DROOLS-1477 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > > To use extension elements inside inputData elements in order to provide “external” information: GEO location, time and location tracking of a decision making (when and were specific decision was taken). This is the primary scope of the use. > In case extension element represents a complex type customer prefers to get back an instance of the complex type, assuming the complex type is defined as a class by the development team on the customer side. However, the customer also understands that it can be more complex and considers the possibility to get the complex type as an XML snippet. The parsing and turning the XML snippet into the complex type, defined by the customer. > The possibility of getting the list of extension elements is expected from other DMN elements, which extend from DMNElement, according to the DMN specification and meta model diagram by OMG. In other words, the usage of extension elements is not limited to be a part of input data elements only. > The client is not expecting “authoring” of the extension elements. > Since extension elements are a part of DMN specification, this is an attempt to make it possible for drools to register custom extension elements in a generic way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-93) CFME Tests: More Domain mode Server Tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-93?page=com.atlassian.jira.plu... ] Hayk Hovsepyan reassigned HAWKULARQE-93: ---------------------------------------- Assignee: Hayk Hovsepyan (was: Michael Foley) > CFME Tests: More Domain mode Server Tests > ----------------------------------------- > > Key: HAWKULARQE-93 > URL: https://issues.jboss.org/browse/HAWKULARQE-93 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Review Existing Polarion testcases. > Review existing automation testcases. > Add new tests for: > Domain mode Servers. > Domain mode Server Groups. > Domain mode Servers in Bulk. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-93) CFME Tests: More Domain mode Server Tests

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-93: ---------------------------------------- Summary: CFME Tests: More Domain mode Server Tests Key: HAWKULARQE-93 URL: https://issues.jboss.org/browse/HAWKULARQE-93 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Review Existing Polarion testcases. Review existing automation testcases. Add new tests for: Domain mode Servers. Domain mode Server Groups. Domain mode Servers in Bulk. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-92) CFME Tests: Mark automated testcases in Polarion

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-92?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-92. -------------------------------------- Resolution: Done Done. > CFME Tests: Mark automated testcases in Polarion > ------------------------------------------------ > > Key: HAWKULARQE-92 > URL: https://issues.jboss.org/browse/HAWKULARQE-92 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Those testcases in Polarion which are automated in CFME Tests, should be marked as "automated". > Testcases are in this manual run https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > The reason is to remove the automated ones from next ER2 run. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1529) Return in new item returns to the home screen instead of creating the item

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1529?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1529: ---------------------------------------- [~tirelli] [~karreiro] TBH I can't say I've seen any commits that would influence this. I suspect the "focus" remains on the "Home" menu item; and pressing enter (in Windows/Edge at least) is causing the element with the focus to activate. > Return in new item returns to the home screen instead of creating the item > -------------------------------------------------------------------------- > > Key: DROOLS-1529 > URL: https://issues.jboss.org/browse/DROOLS-1529 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.CR1 > Environment: wildfly 10.0 - Windows 10 - Microsoft Edge > Reporter: Martijn Burger > Assignee: Guilherme Carreiro > Priority: Minor > > When I create a new item in the KIE Workbench, for instance a DRL file, after entering the item name when a hit enter, I expect that the item will be created. Instead the system returns me to the home screen without creating the item. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1529) Return in new item returns to the home screen instead of creating the item

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1529?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1529: --------------------------------------- [~karreiro] [~manstis] , was this fixed already? > Return in new item returns to the home screen instead of creating the item > -------------------------------------------------------------------------- > > Key: DROOLS-1529 > URL: https://issues.jboss.org/browse/DROOLS-1529 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.CR1 > Environment: wildfly 10.0 - Windows 10 - Microsoft Edge > Reporter: Martijn Burger > Assignee: Guilherme Carreiro > Priority: Minor > > When I create a new item in the KIE Workbench, for instance a DRL file, after entering the item name when a hit enter, I expect that the item will be created. Instead the system returns me to the home screen without creating the item. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1529) Return in new item returns to the home screen instead of creating the item

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1529?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1529: ------------------------------------- Assignee: Guilherme Carreiro (was: Edson Tirelli) > Return in new item returns to the home screen instead of creating the item > -------------------------------------------------------------------------- > > Key: DROOLS-1529 > URL: https://issues.jboss.org/browse/DROOLS-1529 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.CR1 > Environment: wildfly 10.0 - Windows 10 - Microsoft Edge > Reporter: Martijn Burger > Assignee: Guilherme Carreiro > Priority: Minor > > When I create a new item in the KIE Workbench, for instance a DRL file, after entering the item name when a hit enter, I expect that the item will be created. Instead the system returns me to the home screen without creating the item. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-8217: -------------------------------------- [~silvaran] Thanks for the update! I've reproduced it on EAP 7.1.0.DR16 so I cloned it to JBEAP-10503. Added automatic test based on your reproducer. Unfortunately I'm not CDI master so not sure if there is a problem in the way how CDI bean is injected to MDB. It's @ApplicationScoped bean which has injected JMSContext. This JMSContext should be @TransactionScoped. So it's MDB with @ApplicationScoped bean which has @TransactionScoped bean. I'm not sure if this is correct usage. Probably JMSContext should be Injected to MDB and passed to @ApplicationScoped bean which sends message as parameter but not sure about this. > ActiveMQ leaks connections if a JMS message is sent from an MDB > --------------------------------------------------------------- > > Key: WFLY-8217 > URL: https://issues.jboss.org/browse/WFLY-8217 > Project: WildFly > Issue Type: Bug > Components: JMS, Transactions > Affects Versions: 10.1.0.Final > Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Reporter: Scott Van Wart > Assignee: Jeff Mesnil > Priority: Minor > Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log > > > If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). > 1) Build the EAR > 2) Run wildfly with the standalone-full.xml configuration: > {{standalone.bat --server-config=standalone-full.xml}} > 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: > {{jboss-cli.bat -c}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} > 4) Deploy the EAR. > 5) Access http://localhost:8080/leak-web/rest/test?message=Hi > The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs > (see attached log.txt) > I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8634) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-8634: ------------------------------------ Summary: ActiveMQ leaks connections if a JMS message is sent from an MDB Key: WFLY-8634 URL: https://issues.jboss.org/browse/WFLY-8634 Project: WildFly Issue Type: Bug Components: JMS, Transactions Affects Versions: 10.1.0.Final Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Minor Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). 1) Build the EAR 2) Run wildfly with the standalone-full.xml configuration: {{standalone.bat --server-config=standalone-full.xml}} 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: {{jboss-cli.bat -c}} {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} 4) Deploy the EAR. 5) Access http://localhost:8080/leak-web/rest/test?message=Hi The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs (see attached log.txt) I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017