September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7122) Add configuration to disable systematic file watch in ServletResourceManager

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7122: ------------------------------------ Summary: Add configuration to disable systematic file watch in ServletResourceManager Key: WFLY-7122 URL: https://issues.jboss.org/browse/WFLY-7122 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Affects Versions: 10.0.0.Final Environment: Oracle JDK 8u74 on CentOs Reporter: Mathieu Lachance Assignee: Stuart Douglas Our application is deployed multiple time in production as an exploded war. Eventually we are running into "User limit of inotify watches reached": {code} ERROR [io.undertow] (MSC service thread 1-6) UT005024: Could not register resource change listener for caching resource manager, automatic invalidation of cached resource will not work: java.lang.RuntimeException: java.io.IOException: User limit of inotify watches reached at org.xnio.nio.WatchServiceFileSystemWatcher.watchPath(WatchServiceFileSystemWatcher.java:179) at io.undertow.server.handlers.resource.FileResourceManager.registerResourceChangeListener(FileResourceManager.java:161) [undertow-core-1.1.0.Final.jar:1.1.0.Final] at org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:80) at io.undertow.server.handlers.resource.CachingResourceManager.<init>(CachingResourceManager.java:64) [undertow-core-1.1.0.Final.jar:1.1.0.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:525) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:256) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] Caused by: java.io.IOException: User limit of inotify watches reached at sun.nio.fs.LinuxWatchService$Poller.implRegister(LinuxWatchService.java:264) [rt.jar:1.8.0_45] at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260) [rt.jar:1.8.0_45] at sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:329) [rt.jar:1.8.0_45] ... 1 more {code} >From what I'm seeing in: https://github.com/wildfly/wildfly/blob/master/undertow/src/main/java/org... https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io... https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io... there's no way to disable the file resource watch at the sole exception of using non-exploded war deployment. We will eventually switch to a non-exploded war but I think having a configuration (either within the standalone.xml or via system property) to completly turn off that feature would be a nice addition / improvement. In the meanwhile, as a workaround we have increased the inotify watch on the OS and will most likely patch either undertow and/or wildfly-undertow to not add any watch at all. Thanks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1374) Make it build & work on JDK9

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1374?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-1374: -------------------------------------- > Make it build & work on JDK9 > ---------------------------- > > Key: WFCORE-1374 > URL: https://issues.jboss.org/browse/WFCORE-1374 > Project: WildFly Core > Issue Type: Task > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Parent task to track all JDK9 related work in wildfly core. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-1802: -------------------------------------- Summary: Integrate OpenSSL Provider registration with Elytron Key: WFCORE-1802 URL: https://issues.jboss.org/browse/WFCORE-1802 Project: WildFly Core Issue Type: Task Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1295) (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment

by Hiroko Miura (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1295?page=com.atlassian.jira.plugi... ] Hiroko Miura updated DROOLS-1295: --------------------------------- Description: This is cloned from DROOLS-1286 in order to back-port to Community 6.5.x branch. Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object. In the attached screen shot, when clicking pencil icon, nothing appear. This is confirmed by both FireFox anc Chrome. At that time, the following error is shown in browser's console. [Chrome] 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null [FireFox] 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null was: Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object. In the attached screen shot, when clicking pencil icon, nothing appear. This is confirmed by both FireFox anc Chrome. At that time, the following error is shown in browser's console. [Chrome] 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null [FireFox] 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null Fix Version/s: (was: 7.0.0.Beta2) Affects Version/s: 6.5.0.CR2 > (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1295 > URL: https://issues.jboss.org/browse/DROOLS-1295 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.4.0.Final, 6.5.0.CR2 > Reporter: Hiroko Miura > Assignee: Michael Anstis > Labels: support > > This is cloned from DROOLS-1286 in order to back-port to Community 6.5.x branch. > Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object. > In the attached screen shot, when clicking pencil icon, nothing appear. > This is confirmed by both FireFox anc Chrome. > At that time, the following error is shown in browser's console. > [Chrome] > 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null > > [FireFox] > 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1295) (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment

by Hiroko Miura (JIRA)

Hiroko Miura created DROOLS-1295: ------------------------------------ Summary: (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment Key: DROOLS-1295 URL: https://issues.jboss.org/browse/DROOLS-1295 Project: Drools Issue Type: Bug Components: decision tables Affects Versions: 6.4.0.Final Reporter: Hiroko Miura Assignee: Michael Anstis Fix For: 7.0.0.Beta2 Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object. In the attached screen shot, when clicking pencil icon, nothing appear. This is confirmed by both FireFox anc Chrome. At that time, the following error is shown in browser's console. [Chrome] 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null [FireFox] 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1766) Undertow 1.4.3.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1766?page=com.atlassian.jira.plugi... ] Stuart Douglas updated WFCORE-1766: ----------------------------------- Summary: Undertow 1.4.3.Final (was: Undertow 1.4.1.Final) > Undertow 1.4.3.Final > -------------------- > > Key: WFCORE-1766 > URL: https://issues.jboss.org/browse/WFCORE-1766 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7120) NPE in SessionManagerStatsHandler

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7120?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7120: -------------------------------------- Assignee: Mathieu Lachance (was: Brian Stansberry) > NPE in SessionManagerStatsHandler > --------------------------------- > > Key: WFLY-7120 > URL: https://issues.jboss.org/browse/WFLY-7120 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Brian Stansberry > Assignee: Mathieu Lachance > > [~matlach] reports an NPE when SessionManagerStatsHandler tries to use the ServiceController for a no-longer present deployment. See https://github.com/wildfly/wildfly/pull/9189 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7120) NPE in SessionManagerStatsHandler

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7120: -------------------------------------- Summary: NPE in SessionManagerStatsHandler Key: WFLY-7120 URL: https://issues.jboss.org/browse/WFLY-7120 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry [~matlach] reports an NPE when SessionManagerStatsHandler tries to use the ServiceController for a no-longer present deployment. See https://github.com/wildfly/wildfly/pull/9189 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7121) NPE in SessionManagerStatsHandler

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7121: -------------------------------------- Summary: NPE in SessionManagerStatsHandler Key: WFLY-7121 URL: https://issues.jboss.org/browse/WFLY-7121 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry [~matlach] reports an NPE when SessionManagerStatsHandler tries to use the ServiceController for a no-longer present deployment. See https://github.com/wildfly/wildfly/pull/9189 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1719: ------------------------------------- Fix Version/s: 2.2.1.Final > Wildfly 10.1.0.CR1 does not start as a windows service > ------------------------------------------------------ > > Key: WFCORE-1719 > URL: https://issues.jboss.org/browse/WFCORE-1719 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.Final > Environment: Windows 8/Windows Server 2012 > Oracle Java 8 > Reporter: Anton Yudin > Assignee: Tomaz Cerar > Fix For: 3.0.0.Alpha6, 2.2.1.Final > > > Wildfly fails to start as a windows service. > Installation works fine: > {code} > .\service.bat install > Using the X86-64bit version of prunsrv > "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown" > Service Wildfly installed > {code} > Windows reports this error: > {quote} > Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1. > {quote} > {code} > Event log report: > The Wildfly service terminated with the following service-specific error: > Incorrect function. > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> > <System> > <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/> > <EventID Qualifiers="49152">7024</EventID> > <Version>0</Version> > <Level>2</Level> > <Task>0</Task> > <Opcode>0</Opcode> > <Keywords>0x8080000000000000</Keywords> > <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/> > <EventRecordID>196500</EventRecordID> > <Correlation/> > <Execution ProcessID="668" ThreadID="10184"/> > <Channel>System</Channel> > <Computer>ITPC7.intra.rfgh.net</Computer> > <Security/> > </System> > - > <EventData> > <Data Name="param1">Wildfly</Data> > <Data Name="param2">%%1</Data> > <Binary>570069006C00640066006C0079000000</Binary> > </EventData> > </Event> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 September 2016