February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11387) IllegalStateException when calling MetricsContextService.stop during shutdown sequence

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11387?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-11387. ------------------------------------- Fix Version/s: 16.0.0.Beta1 (was: 15.0.0.Final) Resolution: Done I'm resolving this for 16 Beta1 as the related WFCORE-4245 fix was in that release. I've read comments indicating that this is no longer seen with recent builds of WildFly master. > IllegalStateException when calling MetricsContextService.stop during shutdown sequence > -------------------------------------------------------------------------------------- > > Key: WFLY-11387 > URL: https://issues.jboss.org/browse/WFLY-11387 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 15.0.0.Beta1, 15.0.1.Final > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 16.0.0.Beta1 > > > IllegalStateException when calling MetricsContextService.stop during shutdown sequence > This doesn't happen regularly, it happened to me like once from 5 shutdowns. I saw the warning 3 times today. > "not happening always" is because of parallelism in shutdown/boot of WF/EAP > I did slight misconfiguration on purpose, but not sure if it's related or not > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > Stacktrace is this: > {code} > 09:53:23,883 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.extension.metrics.context: java.lang.IllegalStateException > at org.jboss.as.domain-http-interface@7.0.0.Beta1//org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234) > at org.jboss.as.server@7.0.0.Beta1//org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144) > at org.wildfly.extension.microprofile.metrics-smallrye@15.0.0.CR1-SNAPSHOT//org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:131) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-606) Move Complex Mesh to Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-606?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-606: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Matt Mahoney) > Move Complex Mesh to Kiali Test Mesh Operator > --------------------------------------------- > > Key: SWSQE-606 > URL: https://issues.jboss.org/browse/SWSQE-606 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Complex Mesh is an important mesh. It must be moved to KIali Test mesh operator because of the explanation on parent task. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11749) Upgrade Hibernate ORM from 5.3.7 to 5.3.8

by Gail Badner (Jira)

Gail Badner created WFLY-11749: ---------------------------------- Summary: Upgrade Hibernate ORM from 5.3.7 to 5.3.8 Key: WFLY-11749 URL: https://issues.jboss.org/browse/WFLY-11749 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Gail Badner Fix For: 16.0.0.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10540) jboss-ejb-client.xml is unable to specify global cluster config

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10540?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10540: ------------------------------------ Issue Type: Feature Request (was: Enhancement) AFAICT this is a feature so I'm changing the issue type to Feature Request. > jboss-ejb-client.xml is unable to specify global cluster config > --------------------------------------------------------------- > > Key: WFLY-10540 > URL: https://issues.jboss.org/browse/WFLY-10540 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Paul Ferraro > Priority: Critical > > When configuring an Wildfly instance with EJB Client applications to make remote EJB calls to another Wildfly instance with clustering enabled using a server to server connection configuration, the client Wildfly will specify remote-outbound-connection in the remoting subsystem. The client Wildfly instance will create and maintain these 2 connections in this example below. > Client applications deployed on the client Wildfly instance will then package a jboss-ejb-client.xml in the application which specifies the remote server aliases that it wants to have access to. > For the application to use clustered ejb, it then specifies the cluster information in the jboss-ejb-client.xml, where it has to specify connection information like username, connection options as opposed to just an alias as in the case of remoting-ejb-receiver. > The cluster info should be configured in the JBoss profile xml so that client apps jboss-ejb-client.xml can just reference aliases like the non clustered connections to avoid applications creating their own connections to the same cluster nodes. > {code} > <subsystem xmlns="urn:jboss:domain:remoting:3.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> > <outbound-connections> > <remote-outbound-connection name="remote-ejb-connection-1" outbound-socket-binding-ref="remote-ejb-1" username="ejbuser" security-realm="ApplicationRealm" protocol="http-remoting"> > <properties> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > <property name="SASL_DISALLOWED_MECHANISMS" value="JBOSS-LOCAL-USER"/> > <property name="SSL_ENABLED" value="false"/> > </properties> > </remote-outbound-connection> > <remote-outbound-connection name="remote-ejb-connection-2" outbound-socket-binding-ref="remote-ejb-2" username="ejbuser" security-realm="ApplicationRealm" protocol="http-remoting"> > <properties> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > <property name="SASL_DISALLOWED_MECHANISMS" value="JBOSS-LOCAL-USER"/> > <property name="SSL_ENABLED" value="false"/> > </properties> > </remote-outbound-connection> > </outbound-connections> > </subsystem> > {code} > {code} > <jboss-ejb-client xmlns:xsi="urn:jboss:ejb-client:1.2" > xsi:noNamespaceSchemaLocation="jboss-ejb-client_1_2.xsd"> > <client-context> > <ejb-receivers exclude-local-receiver="true"> > <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-1" /> > <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-2" /> > </ejb-receivers> > <clusters> > <cluster name="ejb" security-realm="ApplicationRealm" > username="ejb-cluster-username"> > <connection-creation-options> > <property name="org.xnio.Options.SSL_ENABLED" value="false" /> > <property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" > value="false" /> > </connection-creation-options> > </cluster> > </clusters> > </client-context> > </jboss-ejb-client> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11689) Update the "Getting Started Guide" doc for WF 16

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11689?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11689: --------------------------------------- Assignee: Brian Stansberry > Update the "Getting Started Guide" doc for WF 16 > ------------------------------------------------ > > Key: WFLY-11689 > URL: https://issues.jboss.org/browse/WFLY-11689 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 16.0.0.CR1 > > > The "Getting Started Guide"[1] is release specific. This task is to update it for 16 before we release. > My expectation here is that this is mostly just changing a few places that say "15" to "16". > The "Requirements" section should not recommend using the latest update available; it should recommend the latest *LTS* available. > [1] http://docs.wildfly.org/15/Getting_Started_Guide.html -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-610) Move run kiali-e2e jobs to DSL

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-610?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-610: ------------------------------- Parent Issue: SWSQE-603 (was: SWSQE-608) > Move run kiali-e2e jobs to DSL > ------------------------------ > > Key: SWSQE-610 > URL: https://issues.jboss.org/browse/SWSQE-610 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-609) Move Kiali on Openshift to DSL

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-609?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-609: ------------------------------- Parent Issue: SWSQE-603 (was: SWSQE-608) > Move Kiali on Openshift to DSL > ------------------------------- > > Key: SWSQE-609 > URL: https://issues.jboss.org/browse/SWSQE-609 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-613) Document Manual Events

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-613: ---------------------------------- Summary: Document Manual Events Key: SWSQE-613 URL: https://issues.jboss.org/browse/SWSQE-613 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Michael Foley Document what can not be automated Document why it can not be automated -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-611) Document the Pipeline

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-611?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-611. ------------------------------------------- Resolution: Done > Document the Pipeline > --------------------- > > Key: SWSQE-611 > URL: https://issues.jboss.org/browse/SWSQE-611 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Maistra Downstream Pipeline Needs to be documented on Service Mesh Presentation (https://docs.google.com/presentation/d/1NNk0E6QExG9AUhPDpixV9aGlymoOIqNb6...) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11495) WildFly 14-15 Create Query

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11495?page=com.atlassian.jira.plugin... ] Scott Marlow resolved WFLY-11495. --------------------------------- Resolution: Incomplete Description Feedback requested regarding trying the [http://docs.wildfly.org/15/Developer_Guide.html#hibernate-transformer] to see if that helps. Please reopen after you have tried using the application deployment transformer. > WildFly 14-15 Create Query > -------------------------- > > Key: WFLY-11495 > URL: https://issues.jboss.org/browse/WFLY-11495 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.1.Final, 15.0.0.Final > Reporter: Majid Mostafavi > Assignee: Scott Marlow > Priority: Major > > Hi > When I use this syntax for create lazy data loader > CriteriaBuilder builder = entityManager.getCriteriaBuilder(); > CriteriaQuery<{color:#DE350B}X{color}> criteria = builder.createQuery({color:#DE350B}X{color}.class); > Root<{color:#DE350B}XDTO{color}> xRoot = criteria.from(XDTO.class); > . > . > . > . > criteria.where(predicate); > Query queryResult=entityManager.createQuery(criteria); > queryResult.setFirstResult(first); > if (pageSize > 0){ > queryResult.setMaxResults(pageSize); > } > wildfly create query by this syntax > select > * > from ( {color:#14892c}select dto item1, select dto item2 from Xroot {color} ) > where > rownum <= -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019