[JBoss JIRA] (WFLY-6678) StackoverflowError ejbclientinvocationcontext
by Jimmy Pannier (JIRA)
[ https://issues.jboss.org/browse/WFLY-6678?page=com.atlassian.jira.plugin.... ]
Jimmy Pannier commented on WFLY-6678:
-------------------------------------
Oh. it's the default formatter.
in the admin web console > the logging subsystem (http://127.0.0.1:9990/console/App.html#logging) > i don't see any parameters to disable this truncation.
the formatter is %d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n
here is the substyem in my standalone.xml
<subsystem xmlns="urn:jboss:domain:logging:3.0">
<use-deployment-logging-config value="false"/>
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<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>
<syslog-handler name="SYSLOG">
<level name="INFO"/>
<hostname value="127.0.0.1"/>
<port value="615"/>
<app-name value="my-app-name"/>
<formatter>
<syslog-format syslog-type="RFC3164"/>
</formatter>
</syslog-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="com.inovelan.cloud.user.api.server.AbstractAuthenticationFilter">
<level name="ALL"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<logger category="org.elasticsearch">
<level name="OFF"/>
</logger>
<logger category="com.inovelan" use-parent-handlers="true">
<level name="ALL"/>
</logger>
<logger category="com.inovelan.cloud.impl.storage.service.dataset.DataSetStorageCompletion" use-parent-handlers="true">
<level name="OFF"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
<handler name="SYSLOG"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
</formatter>
</subsystem>
> StackoverflowError ejbclientinvocationcontext
> ---------------------------------------------
>
> Key: WFLY-6678
> URL: https://issues.jboss.org/browse/WFLY-6678
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Environment: wildfly 9.0.1, jdk 1.8
> Reporter: Jimmy Pannier
> Attachments: server.log
>
>
> Sometimes after few days i get an exception
> Here is a stacktrace.
> 2016-06-07 07:38:10,441 ERROR [org.jboss.as.ejb3.invocation] (default task-76) WFLYEJB0034: EJB Invocation failed on component StorageServiceImpl for method public abstract java.util.List com.inovelan.cloud.api.storage.service.dataset.IStorageEjbService.loadData(com.inovelan.cloud.api.storage.model.dto.dataset.LoadDataConfig): javax.ejb.EJBTransactionRolledbackException: WFLYEJB0457: Unexpected Error
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:153)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
> .....
> Caused by: java.lang.StackOverflowError
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (LOGMGR-138) Better handle of stack trace truncation
by David Lloyd (JIRA)
David Lloyd created LOGMGR-138:
----------------------------------
Summary: Better handle of stack trace truncation
Key: LOGMGR-138
URL: https://issues.jboss.org/browse/LOGMGR-138
Project: JBoss Log Manager
Issue Type: Feature Request
Reporter: David Lloyd
Priority: Minor
When a maximum depth is configured in a stack trace format step, it simply truncates at that length.
It would be nice to see at least one of the following:
* Append a message saying "(1234 additional frames truncated)" at the bottom of the stack trace
* (Provide the option to) truncate from the middle rather than the end - so that if you limit the stack to 100 elements, and you're rendering a 4129 frame stack, it prints the first 50, then "(4029 additional frames truncated)", then the last 50
* If stack frame repeat suppression is enabled, it shouldn't count against the total
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-4892) wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4892?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-4892.
-----------------------------
Resolution: Out of Date
> wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-4892
> URL: https://issues.jboss.org/browse/WFLY-4892
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.Final
> Environment: RAM: 4GB
> OS: Fedora 3.14.8-200.fc20.i686+PAE #1 SMP Mon Jun 16 22:20:16 UTC 2014 i686 i686 i386 GNU/Linux
> JAVA VERSION: 1.8.0_45
> Reporter: vako beridze
> Attachments: hs_err_pid2211.log
>
>
> wildfly-9.0.0.Final stops working on linux machine.
> I have no idea why.
> *Server Log:*
> [CodeBlob (0xa752af48)]
> Framesize: 0
> BufferBlob (0xa752af48) used for StubRoutines (2)
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # Internal Error (sharedRuntime.cpp:834), pid=2211, tid=482995008
> # fatal error: exception happened outside interpreter, nmethods and vtable stubs at pc 0xa752c8d4
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
> # Java VM: Java HotSpot(TM) Server VM (25.45-b02 mixed mode linux-x86 )
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /opt/wildfly-9.0.0.Final/bin/hs_err_pid2211.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> #
> ./standalone.sh: line 346: 2211 Aborted "/opt/java/jdk1.8.0_45/bin/java" -D"[Standalone]" -server -server -Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/opt/wildfly-9.0.0.Final/standalone/log/server.log" "-Dlogging.configuration=file:/opt/wildfly-9.0.0.Final/standalone/configuration/logging.properties" -jar "/opt/wildfly-9.0.0.Final/jboss-modules.jar" -mp "/opt/wildfly-9.0.0.Final/modules" org.jboss.as.standalone -Djboss.home.dir="/opt/wildfly-9.0.0.Final" -Djboss.server.base.dir="/opt/wildfly-9.0.0.Final/standalone"
> *standalone.conf:*
> #
> # Specify options to pass to the Java VM.
> #
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-4892) wildfly-9.0.0.Final stops automatically on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4892?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4892:
-----------------------------------
Looks like jvm crash inside crypto engine, when processing SSL request.
{noformat}
Current thread (0x096cf000): JavaThread "default I/O-3" [_thread_in_Java, id=2293, stack(0x1cc4e000,0x1cc9f000)]
Stack: [0x1cc4e000,0x1cc9f000], sp=0x1cc9c9a0, free space=314k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x8c1ecf] VMError::report_and_die()+0x16f
V [libjvm.so+0x3862dc] report_fatal(char const*, int, char const*)+0x4c
V [libjvm.so+0x7d6ff8] SharedRuntime::continuation_for_implicit_exception(JavaThread*, unsigned char*, SharedRuntime::ImplicitExceptionKind)+0x348
V [libjvm.so+0x74d5a8] JVM_handle_linux_signal+0x648
V [libjvm.so+0x743301] signalHandler(int, siginfo*, void*)+0x31
C [+0x40c] __kernel_rt_sigreturn+0x0
J 11854 C2 com.sun.crypto.provider.GCTR.update([BII[BI)I (158 bytes) @ 0xa7851c7e [0xa7851ac0+0x1be]
{noformat}
you can either try updating JVM to latest version and/or upgrade to latest version of WildFly.
> wildfly-9.0.0.Final stops automatically on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-4892
> URL: https://issues.jboss.org/browse/WFLY-4892
> Project: WildFly
> Issue Type: Bug
> Components: Build System, EE, EJB
> Affects Versions: 9.0.0.Final
> Environment: RAM: 4GB
> OS: Fedora 3.14.8-200.fc20.i686+PAE #1 SMP Mon Jun 16 22:20:16 UTC 2014 i686 i686 i386 GNU/Linux
> JAVA VERSION: 1.8.0_45
> Reporter: vako beridze
> Attachments: hs_err_pid2211.log
>
>
> wildfly-9.0.0.Final stops working on linux machine.
> I have no idea why.
> *Server Log:*
> [CodeBlob (0xa752af48)]
> Framesize: 0
> BufferBlob (0xa752af48) used for StubRoutines (2)
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # Internal Error (sharedRuntime.cpp:834), pid=2211, tid=482995008
> # fatal error: exception happened outside interpreter, nmethods and vtable stubs at pc 0xa752c8d4
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
> # Java VM: Java HotSpot(TM) Server VM (25.45-b02 mixed mode linux-x86 )
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /opt/wildfly-9.0.0.Final/bin/hs_err_pid2211.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> #
> ./standalone.sh: line 346: 2211 Aborted "/opt/java/jdk1.8.0_45/bin/java" -D"[Standalone]" -server -server -Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/opt/wildfly-9.0.0.Final/standalone/log/server.log" "-Dlogging.configuration=file:/opt/wildfly-9.0.0.Final/standalone/configuration/logging.properties" -jar "/opt/wildfly-9.0.0.Final/jboss-modules.jar" -mp "/opt/wildfly-9.0.0.Final/modules" org.jboss.as.standalone -Djboss.home.dir="/opt/wildfly-9.0.0.Final" -Djboss.server.base.dir="/opt/wildfly-9.0.0.Final/standalone"
> *standalone.conf:*
> #
> # Specify options to pass to the Java VM.
> #
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-4892) wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4892?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-4892:
------------------------------
Summary: wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45" (was: wildfly-9.0.0.Final stops automatically on linux fedora 3.14.8-200.fc20. java version "1.8.0_45")
> wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-4892
> URL: https://issues.jboss.org/browse/WFLY-4892
> Project: WildFly
> Issue Type: Bug
> Components: Build System, EE, EJB
> Affects Versions: 9.0.0.Final
> Environment: RAM: 4GB
> OS: Fedora 3.14.8-200.fc20.i686+PAE #1 SMP Mon Jun 16 22:20:16 UTC 2014 i686 i686 i386 GNU/Linux
> JAVA VERSION: 1.8.0_45
> Reporter: vako beridze
> Attachments: hs_err_pid2211.log
>
>
> wildfly-9.0.0.Final stops working on linux machine.
> I have no idea why.
> *Server Log:*
> [CodeBlob (0xa752af48)]
> Framesize: 0
> BufferBlob (0xa752af48) used for StubRoutines (2)
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # Internal Error (sharedRuntime.cpp:834), pid=2211, tid=482995008
> # fatal error: exception happened outside interpreter, nmethods and vtable stubs at pc 0xa752c8d4
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
> # Java VM: Java HotSpot(TM) Server VM (25.45-b02 mixed mode linux-x86 )
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /opt/wildfly-9.0.0.Final/bin/hs_err_pid2211.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> #
> ./standalone.sh: line 346: 2211 Aborted "/opt/java/jdk1.8.0_45/bin/java" -D"[Standalone]" -server -server -Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/opt/wildfly-9.0.0.Final/standalone/log/server.log" "-Dlogging.configuration=file:/opt/wildfly-9.0.0.Final/standalone/configuration/logging.properties" -jar "/opt/wildfly-9.0.0.Final/jboss-modules.jar" -mp "/opt/wildfly-9.0.0.Final/modules" org.jboss.as.standalone -Djboss.home.dir="/opt/wildfly-9.0.0.Final" -Djboss.server.base.dir="/opt/wildfly-9.0.0.Final/standalone"
> *standalone.conf:*
> #
> # Specify options to pass to the Java VM.
> #
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-4892) wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4892?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-4892:
------------------------------
Component/s: Web (Undertow)
(was: Build System)
(was: EE)
(was: EJB)
> wildfly-9.0.0.Final jvm crash on linux fedora 3.14.8-200.fc20. java version "1.8.0_45"
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-4892
> URL: https://issues.jboss.org/browse/WFLY-4892
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.Final
> Environment: RAM: 4GB
> OS: Fedora 3.14.8-200.fc20.i686+PAE #1 SMP Mon Jun 16 22:20:16 UTC 2014 i686 i686 i386 GNU/Linux
> JAVA VERSION: 1.8.0_45
> Reporter: vako beridze
> Attachments: hs_err_pid2211.log
>
>
> wildfly-9.0.0.Final stops working on linux machine.
> I have no idea why.
> *Server Log:*
> [CodeBlob (0xa752af48)]
> Framesize: 0
> BufferBlob (0xa752af48) used for StubRoutines (2)
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # Internal Error (sharedRuntime.cpp:834), pid=2211, tid=482995008
> # fatal error: exception happened outside interpreter, nmethods and vtable stubs at pc 0xa752c8d4
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
> # Java VM: Java HotSpot(TM) Server VM (25.45-b02 mixed mode linux-x86 )
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /opt/wildfly-9.0.0.Final/bin/hs_err_pid2211.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> #
> ./standalone.sh: line 346: 2211 Aborted "/opt/java/jdk1.8.0_45/bin/java" -D"[Standalone]" -server -server -Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/opt/wildfly-9.0.0.Final/standalone/log/server.log" "-Dlogging.configuration=file:/opt/wildfly-9.0.0.Final/standalone/configuration/logging.properties" -jar "/opt/wildfly-9.0.0.Final/jboss-modules.jar" -mp "/opt/wildfly-9.0.0.Final/modules" org.jboss.as.standalone -Djboss.home.dir="/opt/wildfly-9.0.0.Final" -Djboss.server.base.dir="/opt/wildfly-9.0.0.Final/standalone"
> *standalone.conf:*
> #
> # Specify options to pass to the Java VM.
> #
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms512m -Xmx2048m -XX:MaxPermSize=2048m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6678) StackoverflowError ejbclientinvocationcontext
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-6678?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-6678:
-----------------------------------
Ah, looks like your log formatter was configured to truncate the stack trace after a certain size. In this case that's probably good for your logs but not so good for troubleshooting. :-)
> StackoverflowError ejbclientinvocationcontext
> ---------------------------------------------
>
> Key: WFLY-6678
> URL: https://issues.jboss.org/browse/WFLY-6678
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Environment: wildfly 9.0.1, jdk 1.8
> Reporter: Jimmy Pannier
> Attachments: server.log
>
>
> Sometimes after few days i get an exception
> Here is a stacktrace.
> 2016-06-07 07:38:10,441 ERROR [org.jboss.as.ejb3.invocation] (default task-76) WFLYEJB0034: EJB Invocation failed on component StorageServiceImpl for method public abstract java.util.List com.inovelan.cloud.api.storage.service.dataset.IStorageEjbService.loadData(com.inovelan.cloud.api.storage.model.dto.dataset.LoadDataConfig): javax.ejb.EJBTransactionRolledbackException: WFLYEJB0457: Unexpected Error
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:153)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
> .....
> Caused by: java.lang.StackOverflowError
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (LOGMGR-137) Stack trace enhancement: repeated frames
by David Lloyd (JIRA)
David Lloyd created LOGMGR-137:
----------------------------------
Summary: Stack trace enhancement: repeated frames
Key: LOGMGR-137
URL: https://issues.jboss.org/browse/LOGMGR-137
Project: JBoss Log Manager
Issue Type: Feature Request
Reporter: David Lloyd
Priority: Minor
During stack trace rendering, it would be nice (especially for stack overflows) if repeats could be abbreviated, especially when the exception formatter is limited to a certain number of frames. Take the example from WFLY-6678:
{code}
...etc...
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
...etc...
{code}
It would be nice to have something like this appear instead:
{code}
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
(2 frames repeated 49821 more times)
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
{code}
The wording is up for discussion but the idea is that we can save a lot of log space by compacting identical frames. Because of the complexity in searching repeated frames, we probably should have constraints, like one or more of the following ideas:
* Only compact frames if there is a net savings in the number of lines printed
* Only compact frames if there is a minimum of 4 repeats (one for the top, one for the bottom, and at least two for the middle)
* Only look back a maximum of _n_ frames
* Only look back _n_ frames where _n_ depends on the total stack size (the idea being that the bigger the stack, the more worthwhile the investment in trying to shrink it) - the factor might have to be something weird like a square root to make sense though
* (insert other ideas here)
Determining a repeat in an efficient manner is tricky, because you have to search back up to _n_ frames, meaning you have to check first if 1 frame is a repeat, then 2 frames, then 3 frames, etc. Furthermore there might be lesser and greater coincident repeats which have to be dealt with sensibly. Good luck! :-)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months