[JBoss JIRA] (WFCORE-249) Wrap the default logging handlers in an AsyncHandler
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-249?page=com.atlassian.jira.plugin... ]
James Perkins closed WFCORE-249.
--------------------------------
Resolution: Rejected
I don't see much benefit in this. If anyone disagrees please feel free to reopen.
> Wrap the default logging handlers in an AsyncHandler
> ----------------------------------------------------
>
> Key: WFCORE-249
> URL: https://issues.jboss.org/browse/WFCORE-249
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Logging
> Reporter: Kyle Lape
> Assignee: James Perkins
>
> This change could potentially enhance performance under heavier logging loads, but the the disadvantages probably need to be considered first.
> * Under light logging load, is performance improved much?
> * How about under medium load?
> * Under heavy load, the async queue may overflow, causing either one of two sceanrios:
> ** {{OverflowAction.DISCARD}}: The loss of messages. Probably not the right choice for default.
> ** {{OverflowAction.BLOCK}}: Threads block until queue clears. Could be argued that async is not much better than plain synchronous logging in this scenario.
> * If the aync thread crashes, are messages lost? If so, is this much worse than synchronous logging, and how often can an async thread crash?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1548) Access denied when deploying to wildfly 10
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1548?page=com.atlassian.jira.plugi... ]
James Perkins closed WFCORE-1548.
---------------------------------
Resolution: Rejected
I'm closing this as rejected because it does seem it's related to an antivirus scan.
> Access denied when deploying to wildfly 10
> ------------------------------------------
>
> Key: WFCORE-1548
> URL: https://issues.jboss.org/browse/WFCORE-1548
> Project: WildFly Core
> Issue Type: Bug
> Environment: Wildfly 10, Windows 7, java 1.8_05, maven 3.0.5, maven 3.3.9
> Reporter: Srecko Mandelj
> Assignee: James Perkins
> Priority: Minor
> Attachments: TestMavenPlugin.zip, server.log
>
>
> I have a war application containing web services. I have no problems deploying war to wildfly 8.1. After upgrade to wildfly 10, the plugin doesn't work any more. I get this error when trying to deploy:
> {code}
> [Server:server-one] 09:36:51,162 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 132) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/ActivatorFrontEnd'
> [Server:server-one] 09:36:51,220 SEVERE [javax.enterprise.resource.webcontainer.
> jsf.config] (ServerService Thread Pool -- 132) Critical error during deployment:
> : com.sun.faces.config.ConfigurationException: java.util.concurrent.ExecutionException: javax.faces.FacesException: java.io.FileNotFoundException: C:\podatki\jboss_configurations\wildfly10\domainController\servers\server-one\tmp\vfs\temp\temp1e3a1daf9121b0e4\content-34b685741ee5aeb4\content-6322725066713898564.tmp (Access is denied)
> {code}
> It looks like a concurrency issue - one process is trying to use a file that other process is using. If I deploy through web console or via CLI, I don't have this issue. It is somehow related to jsf implementation. If I remove jsf from wildfly configuration file (the module and subsystem), deploy works ok (Mojara is then not triggered and deploy is successful).
> I tried to deploy with 1.1.9.Alpha8, but I get the same error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1758) WFLYCC0034: Closing leaked controller client
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1758?page=com.atlassian.jira.plugi... ]
James Perkins closed WFCORE-1758.
---------------------------------
Resolution: Out of Date
I'm not seeing this issue any longer. If you're still seeing it on the newest versions of maven plugin please feel free to reopen.
> WFLYCC0034: Closing leaked controller client
> --------------------------------------------
>
> Key: WFCORE-1758
> URL: https://issues.jboss.org/browse/WFCORE-1758
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: James Perkins
> Attachments: server.log
>
>
> We are intermittently getting "WFLYCC0034: Closing leaked controller client" from RemotingModelControllerClient#finalize method.
> I wonder, isn't implementation of RemotingModelControllerClient#finalize() method [1] example of dangerous "safety net" implementation discussed in presentation "JVM finalize pitfalls" [2] ?
> *Reproducer:*
> 1. using ibm java 1.8
> 2. setting <startup-timeout>1</startup-timeout>
> [1] https://github.com/wildfly/wildfly-core/blob/master/controller-client/src...
> [2] https://www.youtube.com/watch?v=UrGP6pfb0H8
> [3]
> {noformat}
> 05:54:10 Aug 16, 2016 5:54:10 AM org.jboss.as.controller.client.impl.RemotingModelControllerClient finalize
> 05:54:10 WARN: WFLYCC0034: Closing leaked controller client
> 05:54:10 WFLYCC0030: Allocation stack trace:
> 05:54:10 at java.lang.Thread.getStackTrace(Thread.java:1552)
> 05:54:10 at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:74)
> 05:54:10 at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:567)
> 05:54:10 at org.wildfly.plugin.common.ManagementClient.<init>(ManagementClient.java:37)
> 05:54:10 at org.wildfly.plugin.common.AbstractServerConnection.createClient(AbstractServerConnection.java:126)
> 05:54:10 at org.wildfly.plugin.server.StartMojo.execute(StartMojo.java:269)
> 05:54:10 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 05:54:10 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 05:54:10 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 05:54:10 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 05:54:10 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 05:54:10 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 05:54:10 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 05:54:10 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 05:54:10 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 05:54:10 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 05:54:10 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 05:54:10 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 05:54:10 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 05:54:10 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 05:54:10 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 05:54:10 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 05:54:10 at java.lang.reflect.Method.invoke(Method.java:498)
> 05:54:10 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 05:54:10 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 05:54:10 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 05:54:10 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month