[JBoss JIRA] (WFLY-10892) Generation of application.log file -wildfly 11.0.0
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-10892?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFLY-10892.
-------------------------------------
Assignee: (was: Jason Greene)
Resolution: Rejected
> 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
> Priority: Major
>
> 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.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-10953) Spring Application fails to boot
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-10953?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10953:
------------------------------------
Component/s: Class Loading
> Spring Application fails to boot
> --------------------------------
>
> Key: WFLY-10953
> URL: https://issues.jboss.org/browse/WFLY-10953
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 13.0.0.Final, 14.0.0.Beta2
> Reporter: Giovanni Lovato
> Assignee: Jason Greene
> Priority: Major
>
> When a Spring {{@Service}} has a {{@Transactional}} method and an {{@Autowired}} constructor, the app fails to boot with this exception:
> {code}
> org.springframework.aop.framework.AopConfigException: Unable to instantiate proxy using Objenesis, and regular proxy instantiation via default constructor fails as well; nested exception is java.lang.NoSuchMethodException: com.example.demo.MessageService$$EnhancerBySpringCGLIB$$afee8fff.<init>()
> at org.springframework.aop.framework.ObjenesisCglibAopProxy.createProxyClassAndInstance(ObjenesisCglibAopProxy.java:82)
> at org.springframework.aop.framework.CglibAopProxy.getProxy(CglibAopProxy.java:205)
> ... 44 more
> Caused by: java.lang.NoSuchMethodException: com.example.demo.MessageService$$EnhancerBySpringCGLIB$$afee8fff.<init>()
> at java.lang.Class.getConstructor0(Class.java:3302)
> at java.lang.Class.getDeclaredConstructor(Class.java:2512)
> at org.springframework.aop.framework.ObjenesisCglibAopProxy.createProxyClassAndInstance(ObjenesisCglibAopProxy.java:76)
> ... 45 more
> {code}
> Removing the {{@Transactional}} method or the injected repository from the service, makes the app start.
> Worth noting: the app runs fine in WildFly 12.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11151) Wildfly 14 mixes up HTML response in JSF applications
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11151?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11151:
---------------------------------------
Assignee: Farah Juma (was: Jason Greene)
[~fjuma] FYI. It looks like the key info is in the linked mojarra issues.
> Wildfly 14 mixes up HTML response in JSF applications
> -----------------------------------------------------
>
> Key: WFLY-11151
> URL: https://issues.jboss.org/browse/WFLY-11151
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Final
> Reporter: Tamás Ábele
> Assignee: Farah Juma
> Priority: Major
>
> Introduced in wildfly 14 we receive a new JSF implementation (developed years ago), which is based on mojarra 2.3.5. In certain circumstances this JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and spoils it somewhere else you would never guess, or produces an invalid partial response. Anything can happen, and the real problem will be really hard to find. This behavior led to a more severe error than the original one in two reported cases at github.
> I opened an issue ([eclipse-ee4j/mojarra#4488|https://github.com/eclipse-ee4j/mojarra/issues/...]) about this, but the mojarra development team closed this issue without solving it. Now a lot of teams starting to move towards wildfly 14. They are likely to face similar magical errors like us. In the other case ([jboss/mojarra#21|https://github.com/jboss/mojarra/issues/21]) the developer team switched back to JSF 2.2. I’m also worried to change to wildfly 14, because of the future magical errors it will cause in our systems.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11451) Classloading issues on IBM JDK 8 when JProfiler agent is enabled
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11451?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11451:
---------------------------------------
Component/s: Logging
Assignee: James Perkins (was: Jason Greene)
> Classloading issues on IBM JDK 8 when JProfiler agent is enabled
> ----------------------------------------------------------------
>
> Key: WFLY-11451
> URL: https://issues.jboss.org/browse/WFLY-11451
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 14.0.1.Final
> Environment: IBM JDK 8:
> java version "1.8.0_191"
> Java(TM) SE Runtime Environment (build 8.0.5.25 - pxa6480sr5fp25-20181030_01(SR5 FP25))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20181029_400846 (JIT enabled, AOT enabled)
> OpenJ9 - c5c78da
> OMR - 3d5ac33
> IBM - 8c1bdc2)
> JCL - 20181022_01 based on Oracle jdk8u191-b26
> Reporter: Tomas Kyjovsky
> Assignee: James Perkins
> Priority: Major
>
> When I enable JProfiler agent for the server running on IBM JDK 8 the server doesn't start, throwing classloading exceptions.
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final
> JAVA: /home/tkyjovsk/software/java/ibm-java-80/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentpath:/home/tkyjovsk/software/tools/jprofiler9/bin/linux-x64/libjprofilerti.so=port=6766 -Xshareclasses:none
> =========================================================================
> JProfiler> Protocol version 55
> JProfiler> Using JVMTI
> JProfiler> Thread status info workaround enabled.
> JProfiler> Restricted JVMTI version 1.1 detected.
> JProfiler> 64-bit library
> JProfiler> Listening on port: 6766.
> JProfiler> Instrumenting native methods.
> JProfiler> Native library initialized
> JProfiler> VM initialized
> JProfiler> Waiting for a connection from the JProfiler GUI ...
> JProfiler> Using dynamic instrumentation
> JProfiler> Time measurement: elapsed time
> JProfiler> CPU profiling enabled
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Nov 30, 2018 1:48:31 PM org.jboss.msc.service.ServiceContainerImpl <clinit>
> INFO: JBoss MSC version 1.4.3.Final
> Nov 30, 2018 1:48:31 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.2.Final
> Nov 30, 2018 1:48:31 PM org.jboss.as.server.BootstrapImpl internalBootstrap
> WARN: WFLYSRV0071: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended
> Nov 30, 2018 1:48:31 PM org.jboss.as.server.ApplicationServerService start
> INFO: WFLYSRV0049: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) starting
> Nov 30, 2018 1:48:33 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.6.0.Final
> Nov 30, 2018 1:48:34 PM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:495)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:470)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:432)
> at org.jboss.as.server.ServerService.boot(ServerService.java:427)
> at org.jboss.as.server.ServerService.boot(ServerService.java:386)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372)
> at java.lang.Thread.run(Thread.java:812)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask.report(FutureTask.java:133)
> at java.util.concurrent.FutureTask.get(FutureTask.java:203)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107)
> ... 11 more
> Caused by: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:194)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:104)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:812)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Nov 30, 2018 1:48:34 PM org.jboss.as.server.ServerService$4 logExit
> FATAL: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {noformat}
> I tried to work around this by adding "{{org.jboss.logmanager}}" to {{JBOSS_MODULES_SYSTEM_PKGS}} and adding "{{-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:...}}" in {{JAVA_OPTS}} but that just results in another class-loading error:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final
> JAVA: /home/tkyjovsk/software/java/ibm-java-80/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.awt.headless=true -agentpath:/home/tkyjovsk/software/tools/jprofiler9/bin/linux-x64/libjprofilerti.so=port=6766 -Xshareclasses:none -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.4.Final.jar
> =========================================================================
> JProfiler> Protocol version 55
> JProfiler> Using JVMTI
> JProfiler> Thread status info workaround enabled.
> JProfiler> Restricted JVMTI version 1.1 detected.
> JProfiler> 64-bit library
> JProfiler> Listening on port: 6766.
> JProfiler> Instrumenting native methods.
> JProfiler> Native library initialized
> JProfiler> VM initialized
> JProfiler> Waiting for a connection from the JProfiler GUI ...
> JProfiler> Using dynamic instrumentation
> JProfiler> Time measurement: elapsed time
> JProfiler> CPU profiling enabled
> java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
> at org.jboss.logmanager.ExtLogRecord.<init>(ExtLogRecord.java:87)
> at org.jboss.logmanager.Logger.log(Logger.java:796)
> at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:53)
> at org.jboss.logging.Logger.logf(Logger.java:2398)
> at org.jboss.msc.service.ServiceLogger_$logger.greeting(ServiceLogger_$logger.java:40)
> at org.jboss.msc.service.ServiceContainerImpl.<clinit>(ServiceContainerImpl.java:91)
> at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:250)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.register(BootstrapImpl.java:229)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.access$100(BootstrapImpl.java:219)
> at org.jboss.as.server.BootstrapImpl.<init>(BootstrapImpl.java:70)
> at org.jboss.as.server.Bootstrap$Factory.newInstance(Bootstrap.java:278)
> at org.jboss.as.server.Main.main(Main.java:106)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months