[jboss-jira] [JBoss JIRA] (WFLY-10892) Generation of application.log file -wildfly 11.0.0
Brian Stansberry (JIRA)
issues at jboss.org
Tue Aug 21 11:32:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622182#comment-13622182 ]
Brian Stansberry commented on WFLY-10892:
-----------------------------------------
This sounds like a question for the forums. Our standard configs don't include any handler writing an application.log. See our standard config settings for server.log which illustrates how to configure a handler to write to the log dir:
{code}
<periodic-rotating-file-handler name="FILE" autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="true"/>
</periodic-rotating-file-handler>
{code}
The 'relative-to' is the key bit.
> Generation of application.log file -wildfly 11.0.0
> ---------------------------------------------------
>
> Key: WFLY-10892
> URL: https://issues.jboss.org/browse/WFLY-10892
> Project: WildFly
> Issue Type: Bug
> Environment: wildfly 11.0.0 and it has only one instance
> Reporter: Lilly rose
> Assignee: Jason Greene
>
> When I have ran start , stop or restart commands or any operation the application.log file is generatin.
> 1)Ran commands after .war deployment
> 2) Ran commands after undeployment of .war file
> that application.log files is genarating in both cases , what needs to be done to make it generate undder our specific logs path.
> Example : If we run our start commands under some X path the application.log file generating under X path its not generating under logs path.
> Our goal is to make it fall under our logs path no matter from where we ran the command.
> Below is the content of application.log file .
> 09:19:31,760 INFO io.undertow.servlet:360 - Initializing AtmosphereFramework
> 09:19:31,780 DEBUG com.vaadin.server.communication.JSR356WebsocketInitializer:151 - Creating AtmosphereFramework for rates
> 09:19:31,796 INFO org.atmosphere.cpr.AtmosphereFramework:529 - Installed AtmosphereHandler com.vaadin.server.communication.PushAtmosphereHandler mapped to context-path: /*
> 09:19:31,797 INFO org.atmosphere.cpr.AtmosphereFramework:530 - Installed the following AtmosphereInterceptor mapped to AtmosphereHandler com.vaadin.server.communication.PushAtmosphereHandler
> 09:19:31,799 INFO org.atmosphere.util.IOUtils:399 - META-INF/services/org.atmosphere.cpr.AtmosphereFramework not found in class loader
> 09:19:31,815 INFO org.atmosphere.cpr.AtmosphereFramework:2600 - Atmosphere is using org.atmosphere.util.VoidAnnotationProcessor for processing annotation
> 09:19:31,816 DEBUG org.atmosphere.cpr.AtmosphereFramework:2636 - Scanning all classes on the classpath
> 09:19:31,824 INFO org.atmosphere.cpr.AtmosphereFramework:1601 - Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
> 09:19:31,829 INFO org.atmosphere.container.JSR356AsyncSupport:65 - JSR 356 Mapping path /{path}
> 09:19:31,831 INFO io.undertow.websockets.jsr:707 - UT026005: Adding programmatic server endpoint class org.atmosphere.container.JSR356Endpoint for path /{path}
> 09:19:31,833 INFO io.undertow.websockets.jsr:707 - UT026005: Adding programmatic server endpoint class org.atmosphere.container.JSR356Endpoint for path /{path}/{path0}
> 09:19:31,833 INFO io.undertow.websockets.jsr:707 - UT026005: Adding programmatic server endpoint class org.atmosphere.container.JSR356Endpoint for path /{path}/{path0}/{path1}
> 09:19:31,834 INFO io.undertow.websockets.jsr:707 - UT026005: Adding programmatic server endpoint class org.atmosphere.container.JSR356Endpoint for path /{path}/{path0}/{path1}/{path2}
> 09:19:31,834 INFO io.undertow.websockets.jsr:707 - UT026005: Adding programmatic server endpoint class org.atmosphere.container.JSR356Endpoint for path /{path}/{path0}/{path1}/{path2}/{path3}
> 09:19:31,834 INFO org.atmosphere.cpr.AtmosphereFramework:1102 - Installing Default AtmosphereInterceptors
> 09:19:31,835 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.CorsInterceptor : CORS Interceptor Support
> 09:19:31,835 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.CacheHeadersInterceptor : Default Response's Headers Interceptor
> 09:19:31,836 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.PaddingAtmosphereInterceptor : Browser Padding Interceptor Support
> 09:19:31,837 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.AndroidAtmosphereInterceptor : Android Interceptor Support
> 09:19:31,837 INFO org.atmosphere.cpr.AtmosphereFramework:1120 - Dropping Interceptor org.atmosphere.interceptor.HeartbeatInterceptor
> 09:19:31,838 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.SSEAtmosphereInterceptor : SSE Interceptor Support
> 09:19:31,838 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.JSONPAtmosphereInterceptor : JSONP Interceptor Support
> 09:19:31,839 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.JavaScriptProtocol : Atmosphere JavaScript Protocol
> 09:19:31,839 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor : org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor
> 09:19:31,840 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.OnDisconnectInterceptor : Browser disconnection detection
> 09:19:31,840 INFO org.atmosphere.cpr.AtmosphereFramework:1140 - org.atmosphere.interceptor.IdleResourceInterceptor : org.atmosphere.interceptor.IdleResourceInterceptor
> 09:19:31,841 INFO org.atmosphere.cpr.AtmosphereFramework:1130 - Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults to disable them.
> 09:19:31,843 INFO org.atmosphere.cpr.AtmosphereFramework:935 - Using EndpointMapper class org.atmosphere.util.DefaultEndpointMapper
> 09:19:31,843 INFO org.atmosphere.cpr.AtmosphereFramework:944 - Using BroadcasterCache: org.atmosphere.cache.UUIDBroadcasterCache
> 09:19:31,844 INFO org.atmosphere.cpr.AtmosphereFramework:949 - Default Broadcaster Class: org.atmosphere.cpr.DefaultBroadcaster
> 09:19:31,844 INFO org.atmosphere.cpr.AtmosphereFramework:950 - Broadcaster Polling Wait Time 100
> 09:19:31,844 INFO org.atmosphere.cpr.AtmosphereFramework:951 - Shared ExecutorService supported: true
> 09:19:31,845 INFO org.atmosphere.cpr.AtmosphereFramework:958 - Messaging Thread Pool Size: Unlimited
> 09:19:31,845 INFO org.atmosphere.cpr.AtmosphereFramework:968 - Async I/O Thread Pool Size: 200
> 09:19:31,845 INFO org.atmosphere.cpr.AtmosphereFramework:979 - Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
> 09:19:31,845 INFO org.atmosphere.cpr.AtmosphereFramework:980 - Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
> 09:19:31,848 INFO org.atmosphere.cpr.AtmosphereFramework:990 - Invoke AtmosphereInterceptor on WebSocket message true
> 09:19:31,849 INFO org.atmosphere.cpr.AtmosphereFramework:991 - HttpSession supported: true
> 09:19:31,849 INFO org.atmosphere.cpr.AtmosphereFramework:993 - Atmosphere is using DefaultAtmosphereObjectFactory for dependency injection and object creation
> 09:19:31,849 INFO org.atmosphere.cpr.AtmosphereFramework:994 - Atmosphere is using async support: org.atmosphere.container.JSR356AsyncSupport running under container: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) - 1.4.18.Final using javax.servlet/3.0 and jsr356/WebSocket API
> 09:19:31,850 INFO org.atmosphere.cpr.AtmosphereFramework:996 - Atmosphere Framework 2.2.9.vaadin2 started.
> 09:19:31,852 INFO org.atmosphere.cpr.AtmosphereFramework:2403 - Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority BEFORE_DEFAULT
> 09:19:31,852 DEBUG com.vaadin.server.communication.JSR356WebsocketInitializer:155 - Created AtmosphereFramework for rates
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list