October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11118) inter-app can't be deployed

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFLY-11118: ------------------------------------------- Summary: inter-app can't be deployed Key: WFLY-11118 URL: https://issues.jboss.org/browse/WFLY-11118 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Jean-Francois Denise Assignee: Eduardo Martins When deploying we have un-resolved dependency. 16:45:57,040 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 3.0.5 (Final) 16:45:57,454 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] } 16:45:57,457 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11062) Missing "Multi-Release: true" in MANIFEST for multirelease jar infinispan-commons-9.3.3.Final-redhat-00001.jar

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-11062?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-11062: ------------------------------------------ When and how will be this fixed for WildFly ? Remember this is tracker for WF, not ISPN. I think this should be kept open. > Missing "Multi-Release: true" in MANIFEST for multirelease jar infinispan-commons-9.3.3.Final-redhat-00001.jar > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11062 > URL: https://issues.jboss.org/browse/WFLY-11062 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final > Reporter: tommaso borgato > Priority: Major > > Project {{org.infinispan:infinispan-commons:9.3.3.Final}} contains classes specific for JDK-10. > In the {{pom.xml}} file there is a {{jdk10-compile}} profile for the multi-release compilation. > The MANIFEST in jar {{infinispan-commons-9.3.3.Final-redhat-00001.jar}} shipped with {{jboss-eap-7.2.0.CD14.CR1.zip}} does not contain line {{Multi-Release: true}}. > Note this may be related to JBEAP-15502. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11117) Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy

by Jan Kašík (Jira)

Jan Kašík created WFLY-11117: -------------------------------- Summary: Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy Key: WFLY-11117 URL: https://issues.jboss.org/browse/WFLY-11117 Project: WildFly Issue Type: Bug Components: mod_cluster Reporter: Jan Kašík Assignee: Radoslav Husar Running legacy operation ends up with an error: {code} [standalone@localhost:9990 /] /subsystem=modcluster/:disable { "outcome" => "failed", "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.", "rolled-back" => true } {code} mod_cluster configuration: {code} [standalone@localhost:9990 /] /subsystem=modcluster/:read-resource { "outcome" => "success", "result" => { "mod-cluster-config" => {"configuration" => undefined}, "proxy" => {"default" => undefined} } } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3070) Ensure DMN JUnit tests in modules are parametrized for running also for compilation with exec model

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3070?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3070: ---------------------------------- Sprint: 2018 Week 39-41 > Ensure DMN JUnit tests in modules are parametrized for running also for compilation with exec model > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-3070 > URL: https://issues.jboss.org/browse/DROOLS-3070 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.12.0.Final > Reporter: Matteo Mortari > Assignee: Tibor Zimányi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2278) JDBC_PING: log SQL statements

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2278?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2278: --------------------------------- Description: All PreparedStatements are logged at TRACE level (was: All PreparedStatements are loggedt at TRACE level) > JDBC_PING: log SQL statements > ----------------------------- > > Key: JGRP-2278 > URL: https://issues.jboss.org/browse/JGRP-2278 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.13 > > > All PreparedStatements are logged at TRACE level -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2709) Revise and align visual presentation of tables (DMN, scenario, DT)

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-2709?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-2709: --------------------------------------- [~uxdlc] Yes I said that because style updates for DMN/Dtable and Scenario are not strictly related so we can update one by one. If we update _behavioural_ requirements directly to the parent componet uberfire-wires-code-grids will be probably inherited by all of them at the same time (probably because if one of them has it own behaviour, it will be not changed) For instance currently DMN looks better than Scenario > Revise and align visual presentation of tables (DMN, scenario, DT) > ------------------------------------------------------------------- > > Key: DROOLS-2709 > URL: https://issues.jboss.org/browse/DROOLS-2709 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor, Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > > As a practitioner I need a clear and consistent presentation of table styles, so that I can learn the visual cues once for all tables in the application suite. > When possible, iteratively update visual styles for tables using the following proposed options: https://redhat.invisionapp.com/share/RXLG7XB2TCW -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by Ziad Saade (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] Ziad Saade updated WFLY-11116: ------------------------------ Security: (was: Red Hat Internal) > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final > Reporter: Ziad Saade > Assignee: Stuart Douglas > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11115) bumpTimeout method usage in InMemorySessionManager

by Adam Krajcik (Jira)

[ https://issues.jboss.org/browse/WFLY-11115?page=com.atlassian.jira.plugin... ] Adam Krajcik updated WFLY-11115: -------------------------------- Component/s: Web (Undertow) > bumpTimeout method usage in InMemorySessionManager > -------------------------------------------------- > > Key: WFLY-11115 > URL: https://issues.jboss.org/browse/WFLY-11115 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Adam Krajcik > Assignee: Stuart Douglas > Priority: Major > > Possible bug as mentioned in https://developer.jboss.org/thread/278634. As mentioned in the thread, use of bumpTimeout may cause a session that may never expire. > From [~jstourac]: > {quote} > The list of methods where 'bumpTimeout' is actually used in [InMemorySessionManager|https://github.com/undertow-io/undertow/blob/maste...] to following: createSession(), setMaxInactiveInterval(), getAttribute(), getAttributeNames(), setAttribute(), removeAttribute(). From this list usage in following methods is suspicious: getAttribute(), getAttributeNames(), setAttribute(), removeAttribute(). > All occurrences were added by [this commit|https://github.com/undertow-io/undertow/commit/be768b6cb98c13f02df...] with initial session timeout implementation. > The truth is the [Servlet 4.0, section 7.5|https://javaee.github.io/servlet-spec/downloads/servlet-4.0/servlet-4_0_FINAL.pdf] specification (Servlet 3.1 is almost identical) specifies that timeout depends on user activity only: > "This means that the only mechanism that can be used to indicate when a client is no longer active is a time out period." > {quote} > Response from [~stuartdouglas] from mail: > {quote} > We could probably change that to just update the timeout in requestDone(). > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11115) bumpTimeout method usage in InMemorySessionManager

by Adam Krajcik (Jira)

[ https://issues.jboss.org/browse/WFLY-11115?page=com.atlassian.jira.plugin... ] Adam Krajcik moved UNDERTOW-1420 to WFLY-11115: ----------------------------------------------- Project: WildFly (was: Undertow) Key: WFLY-11115 (was: UNDERTOW-1420) > bumpTimeout method usage in InMemorySessionManager > -------------------------------------------------- > > Key: WFLY-11115 > URL: https://issues.jboss.org/browse/WFLY-11115 > Project: WildFly > Issue Type: Bug > Reporter: Adam Krajcik > Assignee: Stuart Douglas > Priority: Major > > Possible bug as mentioned in https://developer.jboss.org/thread/278634. As mentioned in the thread, use of bumpTimeout may cause a session that may never expire. > From [~jstourac]: > {quote} > The list of methods where 'bumpTimeout' is actually used in [InMemorySessionManager|https://github.com/undertow-io/undertow/blob/maste...] to following: createSession(), setMaxInactiveInterval(), getAttribute(), getAttributeNames(), setAttribute(), removeAttribute(). From this list usage in following methods is suspicious: getAttribute(), getAttributeNames(), setAttribute(), removeAttribute(). > All occurrences were added by [this commit|https://github.com/undertow-io/undertow/commit/be768b6cb98c13f02df...] with initial session timeout implementation. > The truth is the [Servlet 4.0, section 7.5|https://javaee.github.io/servlet-spec/downloads/servlet-4.0/servlet-4_0_FINAL.pdf] specification (Servlet 3.1 is almost identical) specifies that timeout depends on user activity only: > "This means that the only mechanism that can be used to indicate when a client is no longer active is a time out period." > {quote} > Response from [~stuartdouglas] from mail: > {quote} > We could probably change that to just update the timeout in requestDone(). > {quote} -- 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 Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-11114?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-11114: --------------------------------- Steps to Reproduce: (was: I don't have an idea how to create sensible reproduction steps at the moment, because reproduction of the problem even with our application is quite slow.) > 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 > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018