LogViewPlus Support » LogViewPlus Support » Help & Support » "Real" TCP Listener

"Real" TCP Listener

nanocell — Wed, 26 Jun 2024 21:20:45 GMT

I have an application on another computer in the network that uses Log4cxx. There I have defined an appender that tries to connect to my computer on port 4561 and then sends log entries (syslog or custom log format). This works if I use a general TCP listener e.g. YAT (Yet Another Terminal).

Documentation says to the TCP Listener: LogViewPlus processes TCP logs by connecting to a remote server.... So the "TCP Listener" is actually not a listener it's more a client connecting to the server?

It looks like this person want exactly what I want but failed: https://www.logviewplus.com/forum/2095/Trouble-using-the-real-time-TCP-logging-feature
I think he misunderstood that too.

Or I'm wrong? If not, is it possible to add this function in a future update? I really like the software!

RE: "Real" TCP Listener

LogViewPlus Support — Wed, 26 Jun 2024 21:20:45 GMT

We've now released LogViewPlus v3.1.12 as a BETA release. This release removes the old TCP Listener in favour of two new types of data source: TCP Client and TCP Server.

Thanks for bringing this issue to our attention. If you are able to do any testing, I would appreciate any feedback.

Hope that helps,

Toby

RE: "Real" TCP Listener

nanocell — Fri, 21 Jun 2024 06:28:35 GMT

Great. I will be happy to test

RE: "Real" TCP Listener

LogViewPlus Support — Thu, 20 Jun 2024 12:03:08 GMT

Apologies for the delay in getting back to you.

This feature has been implemented, but it is tied up with some other work. Hopefully, we will have a BETA release out early next week.

RE: "Real" TCP Listener

nanocell — Thu, 20 Jun 2024 10:47:00 GMT

Is there a rough time frame until the function is available?

RE: "Real" TCP Listener

nanocell — Mon, 13 May 2024 13:02:49 GMT

thanks for the super quick clarification.
That would be great! :)

RE: "Real" TCP Listener

LogViewPlus Support — Mon, 13 May 2024 12:50:44 GMT

Thanks for bringing this to our attention!

I can confirm that the TCP Listener is actually using a TCP client internally. I can see where this is causing confusion and I think you are absolutely right that:
1. The name is confusing.
2. We need to support both sides of the connection (client and server).

I will take a look at this as a priority for the next release. I will post back here as soon as a BETA release is ready.

Thanks again,

Toby