[JBoss JIRA] (WFBUILD-16) Support subsystem templates within a feature-pack
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFBUILD-16?page=com.atlassian.jira.plugin... ]
Stuart Douglas commented on WFBUILD-16:
---------------------------------------
1.1.2.Final is release with this change. You can now include a subsystem in a subsystem-templates directory in the feature pack.
> Support subsystem templates within a feature-pack
> -------------------------------------------------
>
> Key: WFBUILD-16
> URL: https://issues.jboss.org/browse/WFBUILD-16
> Project: WildFly Build Tools
> Issue Type: Feature Request
> Affects Versions: 1.1.0.CR2
> Reporter: Pedro Igor
> Assignee: Stuart Douglas
> Fix For: 1.1.2.Final
>
>
> Users should be able to customize subsystems when extending a feature-pack without being forced to have a subsystem artifact where the config file would be located.
> Accordingly with [~swd847], something like "so you could just have it in a subsystem-templates in the feature pack src" would be enough.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFBUILD-16) Support subsystem templates within a feature-pack
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFBUILD-16?page=com.atlassian.jira.plugin... ]
Stuart Douglas resolved WFBUILD-16.
-----------------------------------
Fix Version/s: 1.1.2.Final
Resolution: Done
> Support subsystem templates within a feature-pack
> -------------------------------------------------
>
> Key: WFBUILD-16
> URL: https://issues.jboss.org/browse/WFBUILD-16
> Project: WildFly Build Tools
> Issue Type: Feature Request
> Affects Versions: 1.1.0.CR2
> Reporter: Pedro Igor
> Assignee: Stuart Douglas
> Fix For: 1.1.2.Final
>
>
> Users should be able to customize subsystems when extending a feature-pack without being forced to have a subsystem artifact where the config file would be located.
> Accordingly with [~swd847], something like "so you could just have it in a subsystem-templates in the feature pack src" would be enough.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFLY-5731) PollSelectorImpl's FD leak for asyncServlet
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5731?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5731.
----------------------------------
Fix Version/s: 10.0.0.CR5
Resolution: Done
The update to XNIO 3.3.3.Final should have fixed this.
Note that you can still run out if you create and destroy a lot of threads in a very short period of time, as the Garbage collector may not be able to keep up. In general you will get way better performance with a thread pool anyway.
> 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
> Fix For: 10.0.0.CR5
>
> 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)
8 years, 11 months
[JBoss JIRA] (WFCORE-1192) Deprecate permgen attributes in the management model
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1192:
----------------------------------------
Summary: Deprecate permgen attributes in the management model
Key: WFCORE-1192
URL: https://issues.jboss.org/browse/WFCORE-1192
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.0.5.Final
The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used.
Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFCORE-1154) Deprecate permgen attributes in host and server config level jvm settings
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1154?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1154:
-------------------------------------
Issue Type: Bug (was: Task)
> Deprecate permgen attributes in host and server config level jvm settings
> -------------------------------------------------------------------------
>
> Key: WFCORE-1154
> URL: https://issues.jboss.org/browse/WFCORE-1154
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 3.0.0.Alpha1
>
>
> The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used, and add deprecation text in the xsd.
> I considered only deprecating these attributes if they appear in the host=* tree, and not doing the ones for domain-wide resources, since those could be used for legacy slaves running JDK < 8. But I think the distinction isn't worth the effort. First, these things are deprecated in all cases in the sense that they may go away in some future release. And second, all that happens is an INFO message is logged, and the chances that message may help some JDK 8 user offsets the chance that a JDK < 8 user would be annoyed by some spurious INFO logging.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1191?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1191:
-------------------------------------
Description:
The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used.
Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
was:Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
> Deprecate permgen attributes in the management model
> ----------------------------------------------------
>
> Key: WFCORE-1191
> URL: https://issues.jboss.org/browse/WFCORE-1191
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.0.5.Final
>
>
> The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used.
> Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1191?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1191:
-------------------------------------
Parent: (was: WFCORE-1154)
Issue Type: Bug (was: Sub-task)
> Deprecate permgen attributes in the management model
> ----------------------------------------------------
>
> Key: WFCORE-1191
> URL: https://issues.jboss.org/browse/WFCORE-1191
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.0.5.Final
>
>
> The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used.
> Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1191:
----------------------------------------
Summary: Deprecate permgen attributes in the management model
Key: WFCORE-1191
URL: https://issues.jboss.org/browse/WFCORE-1191
Project: WildFly Core
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.0.5.Final
Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months