November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3238) Using -DgenerateModel=YES try to compile using Drools compiler test classes

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3238?page=com.atlassian.jira.plugi... ] Luca Molteni resolved DROOLS-3238. ---------------------------------- Resolution: Done > Using -DgenerateModel=YES try to compile using Drools compiler test classes > --------------------------------------------------------------------------- > > Key: DROOLS-3238 > URL: https://issues.jboss.org/browse/DROOLS-3238 > Project: Drools > Issue Type: Bug > Components: tools > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > Attachments: image-2018-11-05-11-45-49-430.png, test-generateModel-kjararchetype.zip > > > With the attachment zip file and use -DgenerateModel=YES flag. > Error will be reported as: > !image-2018-11-05-11-45-49-430.png! > It looks like generate exec model mojo is trying to compile classes and resources which belong to the test scope. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3237) Using -DgenerateModel=YES skips resources compilation check

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3237?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3237: --------------------------------- Sprint: 2018 Week 45-47 > Using -DgenerateModel=YES skips resources compilation check > ----------------------------------------------------------- > > Key: DROOLS-3237 > URL: https://issues.jboss.org/browse/DROOLS-3237 > Project: Drools > Issue Type: Bug > Components: tools > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > Usually the standard kie-maven-plugin mojo compiles any Drools resource at compile time in order to check for errors. > Using -DgenerateModel=YES instead generate the exec model, but skips resource compilation. > To replicate: > introduce a Drools resource which does NOT compile in the KJAR. Without the flag, it fail maven compilation. With the flag, maven compilation succeeds. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3238) Using -DgenerateModel=YES try to compile using Drools compiler test classes

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3238?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3238: --------------------------------- Sprint: 2018 Week 45-47 > Using -DgenerateModel=YES try to compile using Drools compiler test classes > --------------------------------------------------------------------------- > > Key: DROOLS-3238 > URL: https://issues.jboss.org/browse/DROOLS-3238 > Project: Drools > Issue Type: Bug > Components: tools > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > Attachments: image-2018-11-05-11-45-49-430.png, test-generateModel-kjararchetype.zip > > > With the attachment zip file and use -DgenerateModel=YES flag. > Error will be reported as: > !image-2018-11-05-11-45-49-430.png! > It looks like generate exec model mojo is trying to compile classes and resources which belong to the test scope. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-148?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-148: ----------------------------------- Could we simply hard-code the old value in the message associated to the new value until the next major release? For example: {code} @Message(id = 139000, value = "AMQ129000: Invalid filter: {0}", format = Message.Format.MESSAGE_FORMAT) ActiveMQInvalidFilterExpressionException invalidFilter(@Cause Throwable e, SimpleString filter); ActiveMQInvalidFilterExpressionException invalidFilter(@Cause Throwable e, SimpleString filter); {code} This would log the message with the new (correct) and old (duplicated) value: {code} 18:59:56,722 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 86) AMQ139000: AMQ129000: invalid filter: foo=bar" {code} > Artemis logging codes/IDs have changed for CORE protocol > -------------------------------------------------------- > > Key: WFWIP-148 > URL: https://issues.jboss.org/browse/WFWIP-148 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 > For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > {code} > but newly it would have code AMQ219007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.] > {code} > This is problem for any user/customer who had monitoring based on those codes as this will require to change it. > The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-525) Add "OpenShift docker registry" into insecure registry of other OpenShift

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-525?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-525: ----------------------------------- Assignee: Filip Brychta (was: Michael Foley) > Add "OpenShift docker registry" into insecure registry of other OpenShift > ------------------------------------------------------------------------- > > Key: SWSQE-525 > URL: https://issues.jboss.org/browse/SWSQE-525 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Filip Brychta > Priority: Major > > We are building Jenkins slave on "prod.os.jonqe.lab.eng.bos.redhat.com", > When I pull an image from this registry (docker-registry-default.prod.os.jonqe.lab.eng.bos.redhat.com) on other OpenShift environment, I face the insecure issue. To resolve this issue I added manually (docker-registry-default.prod.os.jonqe.lab.eng.bos.redhat.com) to the docker insecure registry of my OpenShift. > When I rebuild an OpenShift environment, I lose my changes. It will be good to add "docker-registry-default.prod.os.jonqe.lab.eng.bos.redhat.com" in the insecure registry by automation script(ansible) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11374: ------------------------------------ Hi [~jason.greene], Can you take a look on this. > Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Blocker > Attachments: master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-11127: ------------------------------ Assignee: Lin Gao (was: Jeff Mesnil) > Can not get activemq and undertow subsystem data from HTTP management api > ------------------------------------------------------------------------- > > Key: WFLY-11127 > URL: https://issues.jboss.org/browse/WFLY-11127 > Project: WildFly > Issue Type: Bug > Components: Management, Web (Undertow) > Affects Versions: 12.0.0.Final > Reporter: Toni Moreno > Assignee: Lin Gao > Priority: Critical > > As described in https://github.com/wildfly/wildfly/issues/11309 > I can not get some subsystems info data with the HTTP management API working with > > ====================================== > "product-version" => "12.0.0.Final", > "product-community-identifier" => "Product", > "product-home" => "/usr/local/wildfly-12.0.0.Final", > "standalone-or-domain-identifier" => "HOST_CONTROLLER", > "host-operating-system" => "Debian GNU/Linux 8 (jessie)}} > =============== > This the a activemq POST request with curl and its error > ---------8<------------------------------------------8<----------------------- > root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin > Enter host password for user 'admin': > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Sat, 02 Jun 2018 08:05:53 GMT > HTTP/1.1 500 Internal Server Error > Connection: keep-alive > X-Frame-Options: SAMEORIGIN > Content-Type: application/json; charset=utf-8 > Content-Length: 103 > Date: Sat, 02 Jun 2018 08:05:53 GMT > "java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR > --------->8------------------------------------------>8----------------------- > And this the query with the GUI client > [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...] > Also with undertow subsystem > ---------8<------------------------------------------8<----------------------- > root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin > Enter host password for user 'admin': > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Sat, 02 Jun 2018 08:19:54 GMT > HTTP/1.1 500 Internal Server Error > Connection: keep-alive > X-Frame-Options: SAMEORIGIN > Content-Type: application/json; charset=utf-8 > Content-Length: 302 > Date: Sat, 02 Jun 2018 08:19:54 GMT > { > "outcome" : "failed", > "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]", > "rolled-back" : true > } > --------->8------------------------------------------>8----------------------- > Here Image of the GUI management query. > [jboss_undertow_listener_gui_query|https://user-images.githubusercontent.c...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Matthew Stevens (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-3330: ----------------------------------------- Hello, I think the arrangement of the properties is good. Two of the properties, however, are currently hidden in Stunner - background color and border color. Please see JBPM-5783. I don't have a strong opinion about the properties themselves but wonder if they should be hidden in DMN for consistency's sake. [~KrisVerlaenen] [~ibek] [~kgaevski]. > DMN Properties panel - Style menu > --------------------------------- > > Key: DROOLS-3330 > URL: https://issues.jboss.org/browse/DROOLS-3330 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Optional > Labels: UX, UXTeam, drools-tools > Attachments: styles.png > > > Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. > Rationale: > * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. > * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. > * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-216) Reduce recursive lock usage on recursive close

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-216?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-216: ------------------------------------ Assignee: David Lloyd Resolution: Done > Reduce recursive lock usage on recursive close > ---------------------------------------------- > > Key: LOGMGR-216 > URL: https://issues.jboss.org/browse/LOGMGR-216 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 3.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-215) Enhance NDC to use arrayCopy

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-215?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-215: ------------------------------------ Assignee: David Lloyd Resolution: Done > Enhance NDC to use arrayCopy > ---------------------------- > > Key: LOGMGR-215 > URL: https://issues.jboss.org/browse/LOGMGR-215 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > Fix For: 3.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018