I am running on Wildfly 23.0.1.Final (openjdk 11) under Centos 8.
I am not using opentrace in my application at all and i also did not add any jaeger dependency.
Whenever i look in the logs, i often get an excpetion(Level: Warn) the looks like the following:
> 021-04-28 15:08:29,875 WARN [io. .internal.reporters.RemoteReporter]
> (jaeger.RemoteReporter-QueueProcessor) FlushCommand execution failed!
> Repeated errors of this command will not be logged.:
> io.jaegertracing.internal.exceptions.SenderException: Failed to flush
> spans. at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:115)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$FlushCommand.execute(RemoteReporter.java:160)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$QueueProcessor.run(RemoteReporter.java:182)
> at java.base/java.lang.Thread.run(Thread.java:834) Caused by:
> io.jaegertracing.internal.exceptions.SenderException: Could not send 1
> spans at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:85)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:113)
> ... 3 more Caused by:
> org.apache.thrift.transport.TTransportException: Cannot flush closed
> transport at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:148)
> at
> org.apache.thrift#0.13.0//org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:73) at
> org.apache.thrift#0.13.0//org.apache.thrift.TServiceClient.sendBaseOneway(TServiceClient.java:66)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.agent.thrift.Agent$Client.send_emitBatch(Agent.java:70)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.agent.thrift.Agent$Client.emitBatch(Agent.java:63)
> at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:83)
> ... 4 more Caused by: java.net.PortUnreachableException: ICMP Port
> Unreachable at java.base/java.net.PlainDatagramSocketImpl.send(Native
> Method) at
> java.base/java.net.DatagramSocket.send(DatagramSocket.java:695) at
> io.jaegertracing.jaeger#1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:146)
> ... 9 more
These messages fill the logfiles and i do not know how to disable the unwanted opentrace feature.
I was not able to find something on google concerning this strange exception.
Does anybody has some idea?
best regards
shane
If you don't use it, you can do something like the following in the CLI:
/subsystem=microprofile-opentracing-smallrye/jaeger-tracer=jaeger:write-attribute(name=sampler-param, value=0)
Another solution is to remove the opentracing subsystem, install jaeger or wait for a release of WildFly with a fix for https://issues.redhat.com/browse/WFLY-14625
You can disable this by remove
<subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:3.0" default-tracer="jaeger">
<jaeger-tracer name="jaeger">
<sampler-configuration sampler-type="const" sampler-param="1.0"/>
</jaeger-tracer>
</subsystem>
in standalone.xml
In parallel to wildfly, execute the jaeger application - a log tracer, with a suitable port configuration. You may find a docker image to run.
In HAL Management Console -> Configuration -> Subsystem -> Logging -> Configuration -> View -> Categories
In Category for 'io.jaegertracing.Configuration' disable parameter 'Use Parent Handlers'.
Or just remove 'io.jaegertracing.Configuration'
Related
I get the following error trying to use vscode-remote using ssh.
I think this is related to escape codes.. but I don't know how to resolve it.
> Starting agent...
> Waiting for server log...
> [?1034h
>
> *
> * Reminder: You may only use this software with Visual Studio family products,
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
>
> [?1034h
> 77cf6633-c4e9-44d4-93ab-d002229c03ef==36237==
> [?1034h
> [?1034h
"install" terminal command done
Received install output: [?1034h[?1034h
Failed to parse remote port from server output: [?1034h[?1034
The log file left on the server .vscode-remote directory indicates the server started fine:
IP Address: x.x.x.x
Extension host agent listening on xxxxx
Any help appreciated.
I am trying to build a IONIC project but I am facing this exception and I am not able to debug the solution for this.I tried a lot of suggestions but there was no solution.I'm waiting for your help
1-ionic start test4 tabs
2-cd test4
3-ionic platform add android
4-ionic build android
ERROR
C:\Users\onurr\test4>ionic build android
Running command: "C:\Program Files\nodejs\node.exe"
C:\Users\onurr\test4\hooks\after_prepare\010_add_platform_class.js
C:\Users\onurr\test4
add to body class: platform-android
ANDROID_HOME=C:\Users\onurr\AppData\Local\Android\sdk
JAVA_HOME=C:\Program Files (x86)\Java\jdk1.8.0_112
Subproject Path: CordovaLib
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
FAILURE: Build failed with an exception.
* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Error: cmd: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
I'm assuming you're using Windows looking at your stack trace.
Pay attention to this message in your stack trace:
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
This normally happens when you have 32-bit JVM. If your OS is 64-bit, replace 32-bit JVM with 64-bit JVM. It has higher heap constraint and will solve the problem. This is the recommended solution.
Read this oracle documentation for more info.
If your OS is 32-bit, try setting up your OS as following and reissue ionic build android command (might need to restart Command Prompt):
Go to Start → Control Panel → System → Advanced System Settings → Advanced (tab) → Environment Variables → System Variables → New:
Variable name: _JAVA_OPTIONS
Variable value: -Xmx512M
This time when I boot from USB (either "regular" boot or UEFI boot) the installer get's stuck a while at
[ok] Reached target Basic System.
After a couple of minutes it shows:
> dracut-initqueue[642]: Warning: could not boot. [ok] Started sShow
> Plymouth Boot Screen. [ok] Reached target Paths. [ok] Reached target
> Basic System. dracut-initqueue[642]: Warning: Could not boot.
> dracut-initqueue[642]: Warning: /dev/root does not exist Starting
> Dracut Emergency Shell
>
> Warning: /dev/root does not exist
>
> Generating "/run/iniramfs/rdsosreport.txt"
>
> Entering emergency mode. Exit the shell to continue.
Now what? I don't understand why I'm experiencing so much trouble, nor why the installer is so little helpful.
I'm really starting to wonder if CentOS is the way to go?
I tried to do remote debugging on a remote glassfish server for some time, using eclipse.
I want to do it on my local server which is in my own computer. I followed the same
instructions that one follows for setting up remote debugging. In eclipse, I set debug
configurations with info - host = localhost, port = 6767 and server in debug mode.
6767 is the port which I use to connect to the admin of my glassfish server.
This approach worked in the actual remote debugging. But it fails in local debugging.
I get the error - Failed to connect to remote VM. Connection timed out.
org.eclipse.jdi.TimeoutException
How do I fix this error ?
The log from the folder workspace dir > .metadata > .log is given below:
!ENTRY org.eclipse.jdt.launching
!MESSAGE Failed to connect to remote VM. Connection timed out.
!STACK 0
org.eclipse.jdi.TimeoutException
at org.eclipse.jdi.internal.connect.SocketTransportService.attach(SocketTransportService.java:162)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.attach(SocketTransportImpl.java:45)
at org.eclipse.jdi.internal.connect.SocketAttachingConnectorImpl.attach(SocketAttachingConnectorImpl.java:134)
at org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttachConnector.java:141)
at org.eclipse.jdt.internal.launching.JavaRemoteApplicationLaunchConfigurationDelegate.launch(JavaRemoteApplicationLaunchConfigurationDelegate.java:84)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I tried one solution which did not work -
open glassfish admin console in a browser > Configuration > server-config > JVM settings > Debug: Enable the checkbox
You do not debug a local application using the remote debugging method. Simply right click your project > debug as > debug on server > choose tomcat or glassfish etc.
Then, run your app from the web browser and see the debugging.
I'm working my way through the Scala blog engine tutorial (yabe) for Play! Framework, and I encountered a template execution error that refers to GenericSignatureFormatError : null when accessing comments. Specifically, the error page says:
Template execution error
Execution error occured in template /app/views/tags/display.html.
Exception raised was GenericSignatureFormatError : null.
In /app/views/tags/display.html (around line 14)
(14) | ${_arg?.comments.size() ?: 'no'}
This exception has been logged with id 666i6ifgg
The stack trace from the console is below. I can reproduce the problem within samples-and-tests/ from the github master (43b195), as follows:
% git clone https://github.com/playframework/play-scala.git
% cd play-scala/samples-and-tests/yabe
% play dependencies
~ play! 1.2, http://www.playframework.org
~ Resolving dependencies using /home/league/tmp/play-scala/samples-and-tests/yabe/conf/dependencies.yml,
~ play->scala 0.9 (from playLocalModules)
~ Installing resolved dependencies,
~ modules/scala-0.9 -> /usr/local/stow/play-1.2/share/play-1.2/modules/scala-0.9
~ lib/joda-time-1.6.jar
~ Done!
% play run
~ play! 1.2, http://www.playframework.org
~ Warning: conflict on command scala:console
~ Ctrl+C to stop
Listening for transport dt_socket at address: 8000
10:32:01,076 INFO ~ Starting /home/league/tmp/play-scala/samples-and-tests/yabe
10:32:01,079 WARN ~ Declaring modules in application.conf is deprecated. Use dependencies.yml instead (module.scala)
10:32:01,080 INFO ~ Module scala is available (/home/league/tmp/play-scala/samples-and-tests/yabe/../..)
10:32:01,080 INFO ~ Module scala is available (/usr/local/stow/play-1.2/share/play-1.2/modules/scala-0.9)
10:32:02,515 WARN ~ You're running Play! in DEV mode
10:32:02,591 INFO ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...
Then, loading http://localhost:9000/ produces the error stated above, with this console output:
#666i6ifgg
Internal Server Error (500) for request GET /
Template execution error (In /app/views/tags/display.html around line 14)
Execution error occured in template /app/views/tags/display.html. Exception raised was GenericSignatureFormatError : null.
play.exceptions.TemplateExecutionException
at play.templates.BaseTemplate.throwException(BaseTemplate.java:84)
at play.templates.GroovyTemplate.internalRender(GroovyTemplate.java:236)
at play.templates.GroovyTemplate$ExecutableTemplate.invokeTag(GroovyTemplate.java:346)
at /app/views/Application/index.html.(line:6)
at play.templates.GroovyTemplate.internalRender(GroovyTemplate.java:213)
at play.templates.Template.render(Template.java:26)
at play.mvc.results.RenderTemplate.<init>(RenderTemplate.java:24)
at play.mvc.Controller.renderTemplate(Controller.java:657)
at play.mvc.ControllerDelegate.renderTemplateForScala(ControllerDelegate.java:46)
at play.mvc.results.Template.<init>(Template.scala:12)
at play.mvc.ScalaController.Template(ScalaController.scala:77)
at controllers.Application$.index(app/controllers.scala:27)
at play.mvc.ActionInvoker.invokeWithContinuation(ActionInvoker.java:540)
at play.mvc.ActionInvoker.invoke(ActionInvoker.java:498)
at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:492)
at play.mvc.ActionInvoker.invokeControllerMethod(ActionInvoker.java:469)
at play.mvc.ActionInvoker.invoke(ActionInvoker.java:157)
at Invocation.HTTP Request(Play!)
Caused by: java.lang.reflect.GenericSignatureFormatError
at java.beans.FeatureDescriptor.getParameterTypes(FeatureDescriptor.java:385)
at java.beans.MethodDescriptor.setMethod(MethodDescriptor.java:116)
at java.beans.MethodDescriptor.<init>(MethodDescriptor.java:74)
at java.beans.MethodDescriptor.<init>(MethodDescriptor.java:58)
at java.beans.Introspector.getTargetMethodInfo(Introspector.java:1196)
at java.beans.Introspector.getBeanInfo(Introspector.java:423)
at java.beans.Introspector.getBeanInfo(Introspector.java:189)
at java.beans.Introspector.getBeanInfo(Introspector.java:250)
at java.beans.Introspector.<init>(Introspector.java:404)
at java.beans.Introspector.getBeanInfo(Introspector.java:189)
at java.security.AccessController.doPrivileged(Native Method)
at /app/views/tags/display.html.(line:14)
at play.templates.GroovyTemplate.internalRender(GroovyTemplate.java:213)
... 16 more
I was able to work around this problem by switching to the Sun JDK. I didn't realize that my Ubuntu was set to use OpenJDK instead. The installation guide claims that either one should work. Perhaps that is untrue, or perhaps I got unlucky with a particular bug related to this version of OpenJDK.
For anyone else having this problem, update-java-alternatives -l shows the available JDKs; I see:
java-6-openjdk 1061 /usr/lib/jvm/java-6-openjdk
java-6-sun 63 /usr/lib/jvm/java-6-sun
These come from the Ubuntu packages
sun-java6-bin 6.24-1build0.10.10.1
openjdk-6-jre-headless 6b20-1.9.7-0ubuntu1
Use this to select:
update-java-alternatives -s java-6-sun
Try changing this:
${_arg?.comments.size() ?: 'no'}
to
${(_arg?.comments.size() > 0) ? '': 'no'}
This should work.