December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9762) JMS message is not received when using a non-transactional JMSConnectionFactoryDefinition

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-9762?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9762: -------------------------------- Fix Version/s: 15.0.0.Final > JMS message is not received when using a non-transactional JMSConnectionFactoryDefinition > ----------------------------------------------------------------------------------------- > > Key: WFLY-9762 > URL: https://issues.jboss.org/browse/WFLY-9762 > Project: WildFly > Issue Type: Bug > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > When using a JMSConnectionFactoryDefinition annotation, and specifying a non transactional connection factory, message is not being sent (or at least received by MDB). Example: > {code:java} > @JMSConnectionFactoryDefinitions( > value = { > @JMSConnectionFactoryDefinition( > name = "java:app/jms/nonXAconnectionFactorySample", > transactional = false, > properties = { > "connectors=in-vm",} > ) > } > ) > {code} > When using an MDB message isn't received. Removing "transactional" attribute makes it work again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11335) Fix Undertow Deployment Metrics

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11335?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11335: --------------------------------- Fix Version/s: 15.0.0.Final > Fix Undertow Deployment Metrics > ------------------------------- > > Key: WFLY-11335 > URL: https://issues.jboss.org/browse/WFLY-11335 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Undertow deployment metrics are relevant only when /subsystem=undertow's statistics-enabled is true. > When that it not the case (and metrics can not be computed) the metrics' read handler should not return a meaningless value (e.g. 0) as it already specifies an undefined metric value in the metrics' attribute definition. > That change and WFCORE-4190 will prevent exposing Undertow metrics when they do not report actual metric from Undertow underlying runtime. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11351) Add resource address and attribute name to metric tags

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11351?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11351: --------------------------------- Fix Version/s: 15.0.0.Final > Add resource address and attribute name to metric tags > ------------------------------------------------------ > > Key: WFLY-11351 > URL: https://issues.jboss.org/browse/WFLY-11351 > Project: WildFly > Issue Type: Enhancement > Components: MP Metrics > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > WildFly metrics are exposed as Microprofile Metrics with unique names composed of the resource address and the attribute name. > This can lead to very long unhelpful names. For example, the request-count metric on the /deployment=example.war/subsystem=undertow/servlet=org.example.MyServlet resource is named is registered as `deployment/example.war/subsystem/undertow/servlet/org.example.MyServlet/request-count`. > When the metric is exported to Prometheus format, it becomes `deployment_example_war_subsystem_undertow_servlet_org_example_my_servlet_request_count` which is a mouthful. > In order to simply query and aggregation of metrics, the resource address and the attribute name will be stored in the metric tags. > E.g. for the metric above, its tags will be: > * subsystem="undertow" > * deployment="example.war" > * servlet="org.example.MyServlet" > * attribute="request-count" > This makes it much simple for example to aggregate all metrics from a given deployment by looking at metrics with the tag deployment="example.war". > Note hower that the tags does not preserve the order of the resource address' elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11338) Upgrade Artemis to 2.6.3.jbossorg-0013

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11338?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11338: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade Artemis to 2.6.3.jbossorg-0013 > -------------------------------------- > > Key: WFLY-11338 > URL: https://issues.jboss.org/browse/WFLY-11338 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Upgrade Artemis to 2.6.3.jbossorg-0013 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11114) Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11114?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11114: --------------------------------- Fix Version/s: 15.0.0.Final > Create test for both WFLY-10531 and WFLY-9501 - closing JMS contexts > -------------------------------------------------------------------- > > Key: WFLY-11114 > URL: https://issues.jboss.org/browse/WFLY-11114 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > There are two issues https://issues.jboss.org/browse/WFLY-9501 and https://issues.jboss.org/browse/WFLY-10531. > Both covers problem with automatic closing of injected JMS contexts. > It would be nice to have a test covering both issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10971) Update mixed domain tests to use EAP 7.2.0 once it is released

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10971?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10971: --------------------------------- Fix Version/s: 15.0.0.Final > Update mixed domain tests to use EAP 7.2.0 once it is released > -------------------------------------------------------------- > > Key: WFLY-10971 > URL: https://issues.jboss.org/browse/WFLY-10971 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11320) Upgrade Infinispan to 9.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11320?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11320: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade Infinispan to 9.4.1.Final > --------------------------------- > > Key: WFLY-11320 > URL: https://issues.jboss.org/browse/WFLY-11320 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 14.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Release notes: > https://issues.jboss.org/projects/ISPN/versions/12339377 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11299) Add EAP 7.2.0 transformers tests for mod_cluster subsystem

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11299?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11299: --------------------------------- Fix Version/s: 15.0.0.Final > Add EAP 7.2.0 transformers tests for mod_cluster subsystem > ---------------------------------------------------------- > > Key: WFLY-11299 > URL: https://issues.jboss.org/browse/WFLY-11299 > Project: WildFly > Issue Type: Task > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Since work in underway, we need to have these tests in place. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11208) Infinispan IllegalStateException (Cannot create a transactional context without a valid Transaction instance) when session invalidated after redirect

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11208?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11208: --------------------------------- Fix Version/s: 15.0.0.Final > Infinispan IllegalStateException (Cannot create a transactional context without a valid Transaction instance) when session invalidated after redirect > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11208 > URL: https://issues.jboss.org/browse/WFLY-11208 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 15.0.0.Beta1 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > When accessing jsp file which contains redirect followed by session invalidation: > {code} > <% > response.sendRedirect("/foobar"); > request.getSession().invalidate(); > %> > {code} > there is an IllegalStateException thrown in server.log: > {code} > 09:43:41,501 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /undertow1374/: org.apache.jasper.JasperException: java.lang.IllegalArgumentException: Cannot create a transactional context without a valid Transaction instance. > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:473) > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:403) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:347) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.jsp.JspFileHandler.handleRequest(JspFileHandler.java:32) > at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException: Cannot create a transactional context without a valid Transaction instance. > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:64) > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:58) > at org.infinispan.cache.impl.CacheImpl.lock(CacheImpl.java:1013) > at org.infinispan.cache.impl.DecoratedCache.lock(DecoratedCache.java:188) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.lock(AbstractDelegatingAdvancedCache.java:285) > at org.infinispan.cache.impl.EncoderCache.lock(EncoderCache.java:318) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.lock(AbstractDelegatingAdvancedCache.java:285) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove(InfinispanSessionMetaDataFactory.java:120) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove(InfinispanSessionMetaDataFactory.java:110) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.remove(InfinispanSessionMetaDataFactory.java:39) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.remove(InfinispanSessionFactory.java:87) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.remove(InfinispanSessionFactory.java:37) > at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:61) > at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:388) > at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:208) > at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:198) > at org.apache.jsp.index_jsp._jspService(index_jsp.java:120) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11358) Update some quickstarts expected warnings in Readme

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11358?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11358: --------------------------------- Fix Version/s: 15.0.0.Final > Update some quickstarts expected warnings in Readme > --------------------------------------------------- > > Key: WFLY-11358 > URL: https://issues.jboss.org/browse/WFLY-11358 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Sande Gilda > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > For the following quickstarts: > {noformat} > spring-greeter, spring-kitchensink-basic, spring-kitchensink-springmvctest > {noformat} > I suggest adding/updating readme 'Server Log: Expected Warnings and Errors' section by adding the following warning > {noformat} > WARN [org.jboss.as.ee] (MSC service thread 1-2) WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause) > {noformat} > to have this warning described as expected to not confuse final users. > All information about mentioned warning can be found [here|https://issues.jboss.org/browse/JBEAP-15213?focusedCommentId=1361810...] and [here|https://issues.jboss.org/browse/WFLY-924?focusedCommentId=12785983&p...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 December 2018