[JBoss JIRA] (WFLY-5731) PollSelectorImpl's FD leak for asyncServlet
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5731?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-5731:
-----------------------------------
This should be fixed in WildFly 9,
can you test with 9, or even better with latest 10.0.CR4
> PollSelectorImpl's FD leak for asyncServlet
> -------------------------------------------
>
> Key: WFLY-5731
> URL: https://issues.jboss.org/browse/WFLY-5731
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Environment: OS:Red Hat Enterprise Linux Server release 5.5 (Tikanga)
> MW:wildfly-8.1.0.Final
> JDK:
> java version "1.7.0_25"
> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
> Reporter: 浩 陈
> Assignee: Stuart Douglas
> Priority: Critical
> Attachments: DemoServlet.java
>
>
> AsyncServlet doGet() like this:
> protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
> resp.setContentType("text/html;charset=UTF-8");
> AsyncContext ctx = req.startAsync();
> new Thread(new Executor(ctx)).start();
> }
> public class Executor implements Runnable {
> private AsyncContext ctx = null;
> public Executor(AsyncContext ctx) {
> this.ctx = ctx;
> }
> public void run() {
> try {
> char[] data = new char[1024 * 1024 * 1];
> PrintWriter out = ctx.getResponse().getWriter();
> out.write(data);
> out.flush();
> ctx.complete();
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
> do request this Servlet some times , run linux cmd :
> lsof -p [JAVAPID]|grep pipe|wc -l
> this number increases by two every one request,but never decrease! when this number up to OS's open file limit everything is not OK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5731) PollSelectorImpl's FD leak for asyncServlet
by 浩 陈 (JIRA)
浩 陈 created WFLY-5731:
-------------------------
Summary: PollSelectorImpl's FD leak for asyncServlet
Key: WFLY-5731
URL: https://issues.jboss.org/browse/WFLY-5731
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.1.0.Final
Environment: OS:Red Hat Enterprise Linux Server release 5.5 (Tikanga)
MW:wildfly-8.1.0.Final
JDK:
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Reporter: 浩 陈
Assignee: Stuart Douglas
Priority: Critical
Attachments: DemoServlet.java
AsyncServlet doGet() like this:
protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
resp.setContentType("text/html;charset=UTF-8");
AsyncContext ctx = req.startAsync();
new Thread(new Executor(ctx)).start();
}
public class Executor implements Runnable {
private AsyncContext ctx = null;
public Executor(AsyncContext ctx) {
this.ctx = ctx;
}
public void run() {
try {
char[] data = new char[1024 * 1024 * 1];
PrintWriter out = ctx.getResponse().getWriter();
out.write(data);
out.flush();
ctx.complete();
} catch (Exception e) {
e.printStackTrace();
}
}
do request this Servlet some times , run linux cmd :
lsof -p [JAVAPID]|grep pipe|wc -l
this number increases by two every one request,but never decrease! when this number up to OS's open file limit everything is not OK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (JBMETA-391) web-app_x_y.xsd is missing in metadata common schema folder
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JBMETA-391?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on JBMETA-391:
-------------------------------------
Is this related to the error:
{quote}
2015-11-24 04:13:12,404 WARN [org.jboss.metadata.parser.util.XMLResourceResolver] (MSC service thread 1-4) Cannot load publicId from resource: web-app_2_5.xsd
2015-11-24 04:13:12,406 WARN [org.jboss.metadata.parser.util.XMLResourceResolver] (MSC service thread 1-3) Cannot load publicId from resource: web-app_2_5.xsd
2015-11-24 04:13:13,106 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-3) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd: org.xml.sax.SAXParseException; systemId: http://java.sun.com/xml/ns/javaee/javaee_5.xsd; lineNumber: 83; columnNumber: 38; sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:132) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4093) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4088) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(XSDHandler.java:3746) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(XSDHandler.java:1315) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:610) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:233) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_60]
at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:167) [jboss-modules.jar:1.4.4.Final]
at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117)
at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85)
at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:104)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.2.Final.jar:2.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
2015-11-24 04:13:13,115 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-3) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
2015-11-24 04:13:13,112 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-4) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd: org.xml.sax.SAXParseException; systemId: http://java.sun.com/xml/ns/javaee/javaee_5.xsd; lineNumber: 83; columnNumber: 38; sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:132) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4093) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4088) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(XSDHandler.java:3746) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(XSDHandler.java:1315) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:610) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:233) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_60]
at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:167) [jboss-modules.jar:1.4.4.Final]
at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117)
at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85)
at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:104)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.2.Final.jar:2.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
2015-11-24 04:13:13,120 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-4) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
{quote}
wildfly-10.0.0.CR5-SNAPSHOT/docs/schema seems to contain {web-app_2_4.xsd web-app_2_5.xsd web-app_3_0.xsd web-app_3_1.xsd}, should that copy be validated instead of the http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd?
> web-app_x_y.xsd is missing in metadata common schema folder
> -----------------------------------------------------------
>
> Key: JBMETA-391
> URL: https://issues.jboss.org/browse/JBMETA-391
> Project: JBoss Metadata
> Issue Type: Task
> Components: common
> Affects Versions: 10.0.0.Beta1
> Reporter: Jim Ma
>
> What's the criteria for putting xsd files under schema folder ? I saw the web-app_x_y.xsd files are all missing in common schema folder. This leads web-app xsd is downloaded for each web deployment when system property "org.jboss.metadata.parser.validate" is set to true.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-989) Saving/Restoring drools session prevents timer-related rules from firing
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-989?page=com.atlassian.jira.plugin... ]
Mario Fusco updated DROOLS-989:
-------------------------------
Issue Type: Bug (was: Feature Request)
> Saving/Restoring drools session prevents timer-related rules from firing
> ------------------------------------------------------------------------
>
> Key: DROOLS-989
> URL: https://issues.jboss.org/browse/DROOLS-989
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: David Weir
> Assignee: Mario Fusco
> Priority: Blocker
> Attachments: DroolsTimerTest.java, DroolsTimerTest.java
>
>
> Attached test case shows a timer-base rule firing. Then the session is saved and restored per the manual. When the trigger is inserted again, the rule does not fire.
> This is killing my system whenever I have to restart and restore the current sessions.
> The workaround is to create the session again from scratch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5728) Wrong behavior of IIOP subsystem migration command when expressions are used
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-5728?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka updated WFLY-5728:
-----------------------------------
Summary: Wrong behavior of IIOP subsystem migration command when expressions are used (was: Wrong behavior of migration command when expressions are used)
> Wrong behavior of IIOP subsystem migration command when expressions are used
> ----------------------------------------------------------------------------
>
> Key: WFLY-5728
> URL: https://issues.jboss.org/browse/WFLY-5728
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Reporter: Ondřej Chaloupka
> Assignee: Tomasz Adamski
>
> If I use expressions in jacorb subsystem then migration to iiop-openjdk is not fully ok.
> I have troubles with following attributes to be migrated correctly
> - {{giop-version}}
> - {{transactions}}
> - {{export-corbaloc}}
> - {{add-component-via-interceptor}}
> For {{giop-versions}} there is strange string written to element after migration. For {{export-corbaloc}} and {{add-component-via-interceptor}} the value is changed directly to default one without considering the existence of the expression. For {{transactions}} the expression is left but the default value is not changed from {{on}} to {{full}}. This thing of some enum change values could be problem of other properties as well (maybe).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months