December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-242) the deployment content is deleted if first undeploy and then deploy the same application using CLI batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-242?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-242: ------------------------------------------------ Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1163173|https://bugzilla.redhat.com/show_bug.cgi?id=1163173] from ASSIGNED to POST > the deployment content is deleted if first undeploy and then deploy the same application using CLI batch > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-242 > URL: https://issues.jboss.org/browse/WFCORE-242 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Jay Kumar SenSharma > Assignee: Emmanuel Hugonnet > Priority: Minor > > - If deploy and undeploy CLI commands executed in a batch mode then it causes missing deployment inside the "data/content" directory which leads to the following error: > {code} > [Host Controller] 10:33:42,387 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "example.war")]) - failure description: "WFLYDC0058: No deployment content with hash d85f1e3106bc8a49838a0dccae9e80819c25e02c is available in the deployment content repository for deployment 'example.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 10:33:42,390 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-423) No way to grep/more or find a line in the CLI

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-423?page=com.atlassian.jira.plugin... ] Ståle Pedersen commented on WFCORE-423: --------------------------------------- this is supported in the latest version of æsh, just need to get jboss-cli to use it. > No way to grep/more or find a line in the CLI > --------------------------------------------- > > Key: WFCORE-423 > URL: https://issues.jboss.org/browse/WFCORE-423 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jim Tyrrell > Assignee: Alexey Loubyansky > Labels: eap6-ux > > In the CLI I should be able to page through the pages of information that are presenting using | more or equivalent. By the same token I should be able to grep to find the one line that I am looking for, when I know what it is I am looking for. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-414) Issue in Interactive mode on cygwin not working.

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-414?page=com.atlassian.jira.plugin... ] Ståle Pedersen commented on WFCORE-414: --------------------------------------- i did look into this a while ago and from what i could see there is now way for java to know that it is running under cygwin. eg, the system.os property etc is windows, same with other properties. ive tried different approaches to detect if it runs under cygwin, but never found a way for it to work reliably. - if anyone got any tips i would be very happy to hear about them. in the script thats used to start jboss-cli, if you somehow can check there if its running under cygwin you could set some runtime properties for æsh so that it should work. ive tested that locally and it did work. > Issue in Interactive mode on cygwin not working. > ------------------------------------------------ > > Key: WFCORE-414 > URL: https://issues.jboss.org/browse/WFCORE-414 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Windows 7, windows2k8, Cygwin 1.7.15 > Reporter: Peter Cadman > Assignee: Alexey Loubyansky > Priority: Minor > > After connecting to standalone server on localhost, Cgywin doesn't response to input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3910) To be added AJP connector connectionTimeout parameter

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-3910?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-3910: --------------------------------- Assignee: Stuart Douglas (was: Thomas Diesler) > To be added AJP connector connectionTimeout parameter > ----------------------------------------------------- > > Key: WFLY-3910 > URL: https://issues.jboss.org/browse/WFLY-3910 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Angel Ivanov > Assignee: Stuart Douglas > > Hi, > We need configuration parameter for Undertow to manage especially AJP connector connection timeout, because created threads staid alive forever. > In tomcat such kind of connector parameter was connectionTimeout. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3910) To be added AJP connector connectionTimeout parameter

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-3910?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-3910: --------------------------------- Component/s: Web (Undertow) (was: ConfigAdmin) > To be added AJP connector connectionTimeout parameter > ----------------------------------------------------- > > Key: WFLY-3910 > URL: https://issues.jboss.org/browse/WFLY-3910 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Angel Ivanov > Assignee: Thomas Diesler > > Hi, > We need configuration parameter for Undertow to manage especially AJP connector connection timeout, because created threads staid alive forever. > In tomcat such kind of connector parameter was connectionTimeout. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4142) ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml

by Gabriele Garuglieri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4142?page=com.atlassian.jira.plugin.... ] Gabriele Garuglieri commented on WFLY-4142: ------------------------------------------- I asked the developer who showed me the problem to strip away the proprietary parts and assemble something to reproduce it. In the meanwhile could you kindly point me to the source for the referred test? Thanks, Gabriele > ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml > --------------------------------------------------------------------------------- > > Key: WFLY-4142 > URL: https://issues.jboss.org/browse/WFLY-4142 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 8.2.0.Final, 9.0.0.Alpha1 > Reporter: Gabriele Garuglieri > Assignee: Stuart Douglas > > The default processor runs later, and overwrites the value provided by this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-444) JAVA_OPTS environment variable not used for domain mode on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-444: ------------------------------------------------ Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1170051|https://bugzilla.redhat.com/show_bug.cgi?id=1170051] from NEW to POST > JAVA_OPTS environment variable not used for domain mode on Windows > ------------------------------------------------------------------ > > Key: WFCORE-444 > URL: https://issues.jboss.org/browse/WFCORE-444 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Josef Cacek > Assignee: Josef Cacek > > When I use JAVA_OPTS as an environment variable (i.e. configured before starting the AS) it's not propagated when used in domain mode on windows (domain.bat). > For standalone mode (standalone.bat) it works. > For Linux/Unix it works in both cases (standalone.sh, domain.sh). > Steps to reproduce: > {code} > SET "JAVA_OPTS=...MyOwnJavaOptsConfig..." > domain.bat > {code} > Actual result: > The configured JAVA_OPTS are not used. > Expected result: > Provided JAVA_OPTS are used for the process controller and host controller processes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3316: ----------------------------------------------- Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1094380|https://bugzilla.redhat.com/show_bug.cgi?id=1094380] from NEW to ASSIGNED > Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3316 > URL: https://issues.jboss.org/browse/WFLY-3316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Labels: ejb, naming, remote-clients, remote-ejb-connection > Attachments: reproducer.zip > > > If a client run multi threads and each Thread use it's own InitialContext the behaviour is unexpected. > The behaviour is as followed: > if each invocation create it's own IC and lookup the EJB there is sometimes a EJBCLIENT000025 because one of the one thread has closed the IC until another thread try to invoke an EJB. > If the IC is reused the failure might happen only if the first Thread has finished the invocations and close the IC during other Threads are still running. > It looks that the underlying remote connection will be closed if the first IC is closed without respect that there are different IC's created and still in use. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3316) Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/WFLY-3316?page=com.atlassian.jira.plugin.... ] Enrique González Martínez reassigned WFLY-3316: ----------------------------------------------- Assignee: Enrique González Martínez (was: Jason Greene) > Multi threaded ejb invocations via remote-naming produce EJBCLIENT000025 if the Context is closed > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3316 > URL: https://issues.jboss.org/browse/WFLY-3316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Enrique González Martínez > Labels: ejb, naming, remote-clients, remote-ejb-connection > Attachments: reproducer.zip > > > If a client run multi threads and each Thread use it's own InitialContext the behaviour is unexpected. > The behaviour is as followed: > if each invocation create it's own IC and lookup the EJB there is sometimes a EJBCLIENT000025 because one of the one thread has closed the IC until another thread try to invoke an EJB. > If the IC is reused the failure might happen only if the first Thread has finished the invocations and close the IC during other Threads are still running. > It looks that the underlying remote connection will be closed if the first IC is closed without respect that there are different IC's created and still in use. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-444) JAVA_OPTS environment variable not used for domain mode on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-444: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1170051 > JAVA_OPTS environment variable not used for domain mode on Windows > ------------------------------------------------------------------ > > Key: WFCORE-444 > URL: https://issues.jboss.org/browse/WFCORE-444 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Josef Cacek > Assignee: Josef Cacek > > When I use JAVA_OPTS as an environment variable (i.e. configured before starting the AS) it's not propagated when used in domain mode on windows (domain.bat). > For standalone mode (standalone.bat) it works. > For Linux/Unix it works in both cases (standalone.sh, domain.sh). > Steps to reproduce: > {code} > SET "JAVA_OPTS=...MyOwnJavaOptsConfig..." > domain.bat > {code} > Actual result: > The configured JAVA_OPTS are not used. > Expected result: > Provided JAVA_OPTS are used for the process controller and host controller processes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 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 2014