John,
I believe based on your original email you are using Jetty 9.4.x with the
*console-capture* module installed. The easiest way to accomplish the
separation would be the following:
1. Copy the ${jetty.home}/etc/console-capture.xml file to ${jetty.base}/etc
(create the folder if it does not
John,
we need some more info to really help you out. Firstly, exactly which
version of jetty 9? There are some significant differences between 9.2.x,
9.3.x and 9.4.x in logging.
But if I had to guess, I'd say that you are running 9.4 and have the
console-capture module enabled... or 9.3 with
Hi,
On Tue, Jan 31, 2017 at 6:08 PM, David Persson wrote:
> It isn't clear to me where to enable javax.net.debug=all.
On the server that closes the connection, and on the client that
receives the connection closed.
> The server jetty9 does not have slf4jlog or javautillog
On Tue, Jan 31, 2017 at 06:08:12PM +0100, David Persson wrote:
> It isn't clear to me where to enable javax.net.debug=all.
Several ways, if you're just experiementing:
https://www.eclipse.org/jetty/documentation/9.4.x/start-jar.html
- You can add 'javax.net.debug=all' to your start.ini file.
-
It isn't clear to me where to enable javax.net.debug=all.
The server jetty9 does not have slf4jlog or javautillog defined, the level
is at debug when I open prunmgr//ES//nameofservice, the stack trace from
this server log is in the first email.
I don't even know whether
On 24/01/2017 18:08, Chris Walker wrote:
John,
Can you share how you had your logging setup in Jetty 8 in more detail?
The Jetty-specific logging implementation has remained largely
unchanged. Were you using a SLF4J implementation before?
Hi Chris,
So far I haven't been able to resolve this.
Hi,
On Tue, Jan 31, 2017 at 11:11 AM, David Persson wrote:
> Hi, thanks for your reply.
>
> The EOF call that yields a functional issue for the end user appears to be
> made from the 'server side' of this application to its neighbour application
> in the same Jetty9(and as
Hi, thanks for your reply.
The EOF call that yields a functional issue for the end user appears to be
made from the 'server side' of this application to its neighbour
application in the same Jetty9(and as such the same jre, 8), Geoserver. I
don't see it when looking at traffic between an end user
Hi Simone,
Thank you very much for your quick response. I have CC'ed other stakeholder
in this thread.
We will try the suggestions you made and update you if we requires further
help :)
Thanks!
Tharindu Munasinghe.
Undergraduate, Department of Computer Science and Engineering
University of