Search Results

jServer is based on Jetty. It provides logging via its own org.eclipse.jetty.util.log.Logger layer, and does not natively use any existing Java logging framework. See https://docs.huihoo.com/jetty/the-definitive-reference/configuring-logging.html

Yes. The jetty logging level affects the messages that logged from the engine itself. In most cases you don't need to touch it.
link: My first question is: in order to record in myappfile.txt whatever I receive in the handler, should I simply add a Log line like below? Log(req.FullR

jWebSocketClient v2.00 is attached. It requires Java 11+. It solves the wss connection issue. It wasn't fully tested so consider it a beta version. The instructions are a bit more complicated than usual: 1. jWebSocketClient.xml + jar go into the internal libraries folder. 2. The other two jars from
link: I wish for a jWebSocketClient library (that can have a different name, so as to keep the jWebSocketClient library that's based on Jetty3) that is base
link: BTW, thank you @OliverA for this request. I forgot that jWebSocketClient was based on Jetty 3. I guess that it didn't support newer TLS ciphers / prot
link: When trying to compile with the new version, I get: Cannot find: C:\Program Files\Anywhere Software\B4J\libraries\jserver/websocket-jetty-client-11.0.

eclipse.jetty.logging.StdErrAppender.format(StdErrAppender.java:134) at org.eclipse.jetty.logging.StdErrAppender.emit(StdErrAppender.java:93) at org.eclipse.jetty.logging.JettyLogger.emit(JettyLogger.java:647) at org.eclipse.jetty.logging.JettyLogger.warn(JettyLogger.java:558) at org

There is no out of the box way to disable logging. In later versions of Jetty there is a setting for the logging called setIgnorePaths which presumably would allow us to ignore some or all handler paths - but this is not implemented in our version of Jetty. I haven't extensively tested this but th

Hi, see example Sub. But as Erel stated, be careful turning off. It requires the JavaObject library. 'Set Jetty Logging Level 'Parameter: Level. Possible values: ALL|DEBUG|INFO|WARN|OFF 'See: http://download.eclipse.org/jetty/9.3.6..html 'Note: Be aware that logging contains important info. Defau
link: Hi, The following information always displayed no matter in debug version of release version of my b4j project: 2015-12-17 11:09:13.546:INFO::main:
link: Implementing this using Inline Java? http://stackoverflow.com/questions/2120370/jetty-how-to-disable-logging

It works with the standalone packager with these declarations: #PackagerProperty: AdditionalModuleInfoString = provides org.slf4j.spi.SLF4JServiceProvider with org.eclipse.jetty.logging.JettyLoggingServiceProvider; #PackagerProperty: AdditionalModuleInfoString = provides org.eclipse.jetty.io.ssl.AL
link: @Erel Is there any chance the ClosedChannelException could also log a one-liner instead of the whole stack trace? This exception is always logged when
link: Log: INFO org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@602e0143{HTTP/1.1, (http/1.1)}{0.0.0.0:55055} INFO org.eclipse.jetty
link: java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at anywheresoftware.b4a.BA.raiseEvent2(BA.java:109) at anywheresoft

Im using a library that included slf4j as a dependency. What Ive noticed is that when I include this library my (Jetty) Server starts logging at the debug level. According to the Jetty documentation documentation this is expected; If the class org.slf4j.Logger exists in server classpath, the Jetty
link: And of course I find the answer a minute after posting!!! This must be done before the Initialize SetSystemProperty("org.eclipse.jetty.util.log.cla

Hi all, I'm converting a B4J project based on jServer 3 where I'm using the code provided by @rwblinn long time ago (see https://www.b4x.com/android/forum/threads/how-to-disable-jetty-debug-info-please.61448/post-387786): 'Set Jetty Logging Level 'Parameter: Level. Possible values: ALL|DEBUG|INFO|W
link: Exactly, I want to control the logging level. The default INFO level mostly works, but sometimes I need more verbose logging and so I change the level
link: Thanks Erel. You're right, but it doesn't seem to work as it did before with jServer 3. Here's an example of my logs set to DEBUG level with jServer 3

Sorry for the jetty logging i forgot to search it on the forums, because i saw that there are still some logs after implementing your c3p0 solution. I`m sorry I wasted your time, since I could have searched for that part myself. Thank you .
link: Thank you. This is working great. Is there an option to disable also the server /jetty logging in console? Is not a must, but it would be nice. Star
link: https://www.b4x.com/android/forum/threads/how-to-disable-jetty-debug-info-please.61448/#post-387786 I found it here: https://www.b4x./?query=jetty+lo

Powered by ColBERT