March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-245) Add tests for suffix option on size-rotating-file-handler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-245?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-245. -------------------------------- Resolution: Out of Date I believe this is out of date. If not please feel free to reopen. > Add tests for suffix option on size-rotating-file-handler > --------------------------------------------------------- > > Key: WFCORE-245 > URL: https://issues.jboss.org/browse/WFCORE-245 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Petr Kremensky > Assignee: James Perkins > > Add tests for WFCORE-113 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (WFCORE-454) Rewrite the logging.properties file if the jboss.server.log.dir property is changed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-454?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-454. -------------------------------- Resolution: Done This won't be relevant when WFCORE-157 is solved. > Rewrite the logging.properties file if the jboss.server.log.dir property is changed > ----------------------------------------------------------------------------------- > > Key: WFCORE-454 > URL: https://issues.jboss.org/browse/WFCORE-454 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The {{PathManager}} has a way to handle callbacks when the value of a path property is changed. The logging subsystem should add a callback to change the paths (possibly not at runtime??) and rewrite the logging.properties file with the new fully qualified path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-479) The testFormats() tests in the HandlerOperationsTestCase needs to ensure colors are being used

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-479?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-479. -------------------------------- Resolution: Rejected > The testFormats() tests in the HandlerOperationsTestCase needs to ensure colors are being used > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-479 > URL: https://issues.jboss.org/browse/WFCORE-479 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > In environments like Windows colored log output is not turned on by default. The test needs to take this into account and not assume that colored output will be printed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-682) Review usage of hard-coded string constants with the application server name

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-682?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-682. -------------------------------- Resolution: Rejected > Review usage of hard-coded string constants with the application server name > ---------------------------------------------------------------------------- > > Key: WFCORE-682 > URL: https://issues.jboss.org/browse/WFCORE-682 > Project: WildFly Core > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > This is meant to be a parent for all smaller issues that might creep up with hard-coded string constants for the application server name. For example if a message in a message bundle has {{WidFly Core 1.0.0..xxx started in...}} we need to ensure the server name is a variable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (SECURITY-965) Release JBoss Negotiation 2.3.13.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-965?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-965. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.3.13.Final > -------------------------------------- > > Key: SECURITY-965 > URL: https://issues.jboss.org/browse/SECURITY-965 > Project: PicketBox > Issue Type: Release > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_13_Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8395) Upgrade jboss-negotiation to 3.0.4

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8395?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved JBEAP-9648 to WFLY-8395: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8395 (was: JBEAP-9648) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade jboss-negotiation to 3.0.4 > ---------------------------------- > > Key: WFLY-8395 > URL: https://issues.jboss.org/browse/WFLY-8395 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: legacy > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1013) PicketBox compatibility mode for PBE utility

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/ELY-1013?page=com.atlassian.jira.plugin.s... ] Peter Skopek updated ELY-1013: ------------------------------ Summary: PicketBox compatibility mode for PBE utility (was: PBE utility needs PicketBox compatible mode) > PicketBox compatibility mode for PBE utility > -------------------------------------------- > > Key: ELY-1013 > URL: https://issues.jboss.org/browse/ELY-1013 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Utils > Affects Versions: 1.1.0.Beta32 > Reporter: Peter Skopek > Assignee: Peter Skopek > > To fix issue https://issues.jboss.org/browse/WFCORE-2421 we need to have PicketBox compatibility mode in PBE utility class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017