January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-25) Upstream work on APM

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-25: ---------------------------------------- Summary: Upstream work on APM Key: HAWKULARQE-25 URL: https://issues.jboss.org/browse/HAWKULARQE-25 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: mfoley user Top level task for Upstream work. All work goes as sub-tasks here. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-24) HOSA --- Hawkular Agent for Openshift

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-24: ---------------------------------------- Summary: HOSA --- Hawkular Agent for Openshift Key: HAWKULARQE-24 URL: https://issues.jboss.org/browse/HAWKULARQE-24 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: mfoley user Top level task for HOSA. All the work required goes here as sub-tasks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-16) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-16?page=com.atlassian.jira.plu... ] Hayk Hovsepyan reassigned HAWKULARQE-16: ---------------------------------------- Assignee: Hayk Hovsepyan (was: mfoley user) > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-16 > URL: https://issues.jboss.org/browse/HAWKULARQE-16 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: hawkular-qe-manual > > Middleware Provider running inside and outside of Openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-17) Automation Testcase

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-17?page=com.atlassian.jira.plu... ] Hayk Hovsepyan reassigned HAWKULARQE-17: ---------------------------------------- Assignee: Hayk Hovsepyan (was: mfoley user) > Automation Testcase > ------------------- > > Key: HAWKULARQE-17 > URL: https://issues.jboss.org/browse/HAWKULARQE-17 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: hawkular-qe-automation > > * Automate openshift eap7 docker container starting in preparation scripts > * In CFME CI > * Add openshift into CFME > * Verify discovery of EAP7, run smoke set of tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1423) KJAR changes are not reflected in KIE Container

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1423?page=com.atlassian.jira.plugi... ] Edson Tirelli closed DROOLS-1423. --------------------------------- Resolution: Rejected Closing the ticket as it seems a mistake on the use of the engine. Re-open the ticket with additional information if you think otherwise. > KJAR changes are not reflected in KIE Container > ----------------------------------------------- > > Key: DROOLS-1423 > URL: https://issues.jboss.org/browse/DROOLS-1423 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.5.0.Final > Reporter: LakshmiNarayanan Kesavan > Assignee: Edson Tirelli > > Step 1: Create a KJAR in Maven Repo with the DRL file and deploy the same in tomcat > Step 2: Create the container > Step 3: Execute the rule. The rule got successfully executed > Step 4: Dispose the container. We get the below message > 31-Jan-2017 14:50:13.001 INFO [http-nio-8000-exec-12] org.kie.server.services.jbpm.JbpmKieServerExtension.disposeContainer No container with id test_drl_nn_01_1 found > 31-Jan-2017 14:50:13.002 INFO [http-nio-8000-exec-12] org.kie.server.services.impl.KieServerImpl.disposeContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully stopped > Step 5: Try executing the rule. No container available hence the rule didnt get executed. > Step 6: Modify the rule logic and create the new KJAR > Step 7: Create container and we get the below message. > 31-Jan-2017 15:01:44.333 WARNING [http-nio-8000-exec-10] org.kie.server.services.jbpm.ui.JBPMUIKieServerExtension.createContainer Unable to create image reference for container test_drl_nn_01_1 due to null > 31-Jan-2017 15:01:44.334 INFO [http-nio-8000-exec-10] org.kie.server.services.impl.KieServerImpl.createContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully started > Step 8: execute the rule. > We observe the latest changes made to the rule logic is not reflecting in the container and only the old(OLD KJAR WITH OLD RULE LOGIC) contanier got created. > This happens very sporadically and not always -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1423) KJAR changes are not reflected in KIE Container

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1423?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1423: --------------------------------------- >From the log snippet you pasted, it seems that you are creating the kjar with the same version all the time? First container: com.ge.hc.services.rs:test_drl_nn_01:1 Second container: com.ge.hc.services.rs:test_drl_nn_01:1 If you do that, maven will not look inside the jar to detect differences. You must either increment the version number (recommended) or use a -SNAPSHOT suffix if you want maven to detect changes. > KJAR changes are not reflected in KIE Container > ----------------------------------------------- > > Key: DROOLS-1423 > URL: https://issues.jboss.org/browse/DROOLS-1423 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.5.0.Final > Reporter: LakshmiNarayanan Kesavan > Assignee: Edson Tirelli > > Step 1: Create a KJAR in Maven Repo with the DRL file and deploy the same in tomcat > Step 2: Create the container > Step 3: Execute the rule. The rule got successfully executed > Step 4: Dispose the container. We get the below message > 31-Jan-2017 14:50:13.001 INFO [http-nio-8000-exec-12] org.kie.server.services.jbpm.JbpmKieServerExtension.disposeContainer No container with id test_drl_nn_01_1 found > 31-Jan-2017 14:50:13.002 INFO [http-nio-8000-exec-12] org.kie.server.services.impl.KieServerImpl.disposeContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully stopped > Step 5: Try executing the rule. No container available hence the rule didnt get executed. > Step 6: Modify the rule logic and create the new KJAR > Step 7: Create container and we get the below message. > 31-Jan-2017 15:01:44.333 WARNING [http-nio-8000-exec-10] org.kie.server.services.jbpm.ui.JBPMUIKieServerExtension.createContainer Unable to create image reference for container test_drl_nn_01_1 due to null > 31-Jan-2017 15:01:44.334 INFO [http-nio-8000-exec-10] org.kie.server.services.impl.KieServerImpl.createContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully started > Step 8: execute the rule. > We observe the latest changes made to the rule logic is not reflecting in the container and only the old(OLD KJAR WITH OLD RULE LOGIC) contanier got created. > This happens very sporadically and not always -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7946) Elytron ldap-realm does not handle loops in referrals

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7946?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7946: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Elytron ldap-realm does not handle loops in referrals > ----------------------------------------------------- > > Key: WFLY-7946 > URL: https://issues.jboss.org/browse/WFLY-7946 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Attachments: print-roles.war > > > According to LDAP specification [1]: "Clients that follow referrals MUST ensure that they do not loop between servers. They MUST NOT repeatedly contact the same server for the same request with the same parameters.". > When application server is configured to use ldap-realm with dir-context which uses referral-mode=follow or throw and LDAP servers contain loop then it leads to infinite cycle. It can results to java.lang.OutOfMemoryError on EAP server. > [1] http://tools.ietf.org/html/rfc4511#section-4.1.10 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2250) CLI can exit although Aesh console has not been cleaned

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2250: -------------------------------------------- Summary: CLI can exit although Aesh console has not been cleaned Key: WFCORE-2250 URL: https://issues.jboss.org/browse/WFCORE-2250 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise 2 Threads. Thread1 is polling Aesh console status for its running state, as soon as the state is switched to !running, the CLI exists. Ctrl-C is sent to CLI, Aesh command Thread initiates a shutdown, the CLI calls console.stop(). Aesh change running state to be false THEN does some cleanup. If thread1 is scheduled, then CLI exists although cleanup has not yet been operated. leaving an insane TTY. The fix is to switch to Aesh 0.66.15 in which this bug has been fixed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1423) KJAR changes are not reflected in KIE Container

by LakshmiNarayanan Kesavan (JIRA)

LakshmiNarayanan Kesavan created DROOLS-1423: ------------------------------------------------ Summary: KJAR changes are not reflected in KIE Container Key: DROOLS-1423 URL: https://issues.jboss.org/browse/DROOLS-1423 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 6.5.0.Final Reporter: LakshmiNarayanan Kesavan Assignee: Edson Tirelli Step 1: Create a KJAR in Maven Repo with the DRL file and deploy the same in tomcat Step 2: Create the container Step 3: Execute the rule. The rule got successfully executed Step 4: Dispose the container. We get the below message 31-Jan-2017 14:50:13.001 INFO [http-nio-8000-exec-12] org.kie.server.services.jbpm.JbpmKieServerExtension.disposeContainer No container with id test_drl_nn_01_1 found 31-Jan-2017 14:50:13.002 INFO [http-nio-8000-exec-12] org.kie.server.services.impl.KieServerImpl.disposeContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully stopped Step 5: Try executing the rule. No container available hence the rule didnt get executed. Step 6: Modify the rule logic and create the new KJAR Step 7: Create container and we get the below message. 31-Jan-2017 15:01:44.333 WARNING [http-nio-8000-exec-10] org.kie.server.services.jbpm.ui.JBPMUIKieServerExtension.createContainer Unable to create image reference for container test_drl_nn_01_1 due to null 31-Jan-2017 15:01:44.334 INFO [http-nio-8000-exec-10] org.kie.server.services.impl.KieServerImpl.createContainer Container test_drl_nn_01_1 (for release id com.ge.hc.services.rs:test_drl_nn_01:1) successfully started Step 8: execute the rule. We observe the latest changes made to the rule logic is not reflecting in the container and only the old(OLD KJAR WITH OLD RULE LOGIC) contanier got created. This happens very sporadically and not always -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2249) ObjectTypeValidator only validates fields the user provides

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2249: ---------------------------------------- Summary: ObjectTypeValidator only validates fields the user provides Key: WFCORE-2249 URL: https://issues.jboss.org/browse/WFCORE-2249 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Alpha23 This in ObjectTypeValidator is wrong: {code} @Override public void validateParameter(final String parameterName, final ModelNode value) throws OperationFailedException { super.validateParameter(parameterName, value); if (value.isDefined()) { for (String key : value.keys()) { if (allowedValues.containsKey(key)) { allowedValues.get(key).getValidator().validateParameter(key, value.get(key)); } else { throw ROOT_LOGGER.invalidKeyForObjectType(key, parameterName); } } } } {code} 1) It only iterates over the keys in 'value' so if value is missing any required fields that isn't detected. 2) It's not really appropriate to reject keys that are not part of the definition. The management code is meant to be forgiving in such cases. For now I think I'll just focus on #1. It's debatable whether being forgiving is really ideal in general, and since this particular bit of unforgivingness has been around since at least 2012 I think I'll leave it alone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2017