Hi,
Here its is:
# lsof -p 130244 | grep "protocol: TCPv6"| wc -l
19948
# netstat -p -a -6 --tcp | grep 130244
tcp6 0 0 [::]:pcsync-https [::]:* LISTEN
130244/java
tcp6 0 0 [::]:https [::]:* LISTEN
130244/java
ss has all the same options as netstat
On Fri, May 21, 2021 at 3:51 AM André Warnier (tomcat/perl)
wrote:
> Soyrry to top-post, but it's getting cluttered down there..
>
> The next thing that you may want to do :
>
> > netstat -p -a -6 --tcp
>
> That is an alternative list of sockets, which
Soyrry to top-post, but it's getting cluttered down there..
The next thing that you may want to do :
> netstat -p -a -6 --tcp
That is an alternative list of sockets, which also shows the "tcp state" of the
sockets.
To get only the ones of the tomcat JVM PID, filter with grep based of the
On 21/05/2021 05:51, Mathiazhagan, Saravanakumar TPC wrote:
Hi Mark,
Thanks for the quick response.
I suspect some sort of configuration issue. A guess would be that JBoss
EAOP isn't configured to append the jvmRoute (to use the Tomcat
configuration setting name) to the session ID.
I
Hi Christopher
Enclosed is the stacktrace of the tomcat (localhost)
On the DC side we see those messages:
Then we see the same error events like we saw before already with the normal
log level
Internal event: The LDAP server returned an error.
Additional Data
Error value:
0057:
