Need to disable/change ports when installing CS5Tools

CodeSite Dispatcher, CodeSite Viewers, CodeSite Controller

Need to disable/change ports when installing CS5Tools

Postby jkottas » Mon Aug 29, 2016 11:50 am

I have a client who has random unrelated traffic on port 3434 which is causing exceptions and memory leaks in CS Dispatcher. Since I don't need any ports open, I'd like to turn off port monitoring or maybe change the ports to something impossible like 0 or -1. Is there perhaps a flag I can set in CodeSiteToolsSetup.txt to do this? I know that MONITOR_PORTS=NO doesn't work in CS5 anymore.
jkottas
 
Posts: 7
Joined:
Thu Dec 20, 2012 9:44 pm

Re: Need to disable/change ports when installing CS5Tools

Postby Raize Support » Tue Aug 30, 2016 2:10 am

Hi,

It is true that CS5 always monitors the ports. There currently is no setting in the CodeSiteToolsSetup.txt to allow setting the actual port numbers to monitor, but that is a good idea.

The CodeSite Controller can be used to change the port numbers, but you could also do that my editing the CSDispatcher.ini file that is stored at C:\ProgramData\Raize\CodeSite\5.0

Ray
Raize Software Support
Raize Software
http://www.raize.com
Raize Support
 
Posts: 611
Joined:
Fri Mar 25, 2011 9:04 pm

Re: Need to disable/change ports when installing CS5Tools

Postby jkottas » Tue Aug 30, 2016 1:58 pm

Ok, that makes sense. I did try modifying my client's ini file yesterday so that it was listening to port 0 instead of 3434, but it didn't resolve their problem... so maybe I'd better describe the original problem.

After running for a while, my app (all apps, really) start throwing out of memory exceptions. When this happens we can see several out of memory error dialogs spawned by CSDispatcher, and in Task Manager we can see that CSDispatcher is using 1.9 GB of memory. The CSDispatcherLog.txt file says

...
Warning 8/25/2016 13:50:38.575 Received unsupported CodeSite message format ($16030100) via TCP.
Warning 8/25/2016 13:50:38.577 Received unsupported CodeSite message format ($5C010000) via TCP.
Warning 8/25/2016 13:50:38.580 Received unsupported CodeSite message format ($58030157) via TCP.
Warning 8/25/2016 13:50:38.581 Received unsupported CodeSite message format ($BF5A1E9B) via TCP.
Warning 8/25/2016 13:50:38.584 Received unsupported CodeSite message format ($E3136C2A) via TCP.
Warning 8/25/2016 13:50:38.586 Received unsupported CodeSite message format ($F593315A) via TCP.
Warning 8/25/2016 13:50:38.587 Received unsupported CodeSite message format ($240DFEF6) via TCP.
Warning 8/25/2016 13:50:38.588 Received unsupported CodeSite message format ($78C23B05) via TCP.
Warning 8/25/2016 13:50:38.589 Received unsupported CodeSite message format ($F21159C5) via TCP.
Warning 8/25/2016 13:50:38.590 Received unsupported CodeSite message format ($D555B996) via TCP.
Warning 8/25/2016 13:50:38.592 Received unsupported CodeSite message format ($FC3D6300) via TCP.
Warning 8/25/2016 13:50:38.593 Received unsupported CodeSite message format ($18C014) via TCP.
Warning 8/25/2016 13:50:38.596 Received unsupported CodeSite message format ($C013C00A) via TCP.
Warning 8/25/2016 13:50:38.600 Received unsupported CodeSite message format ($C0090035) via TCP.
Warning 8/25/2016 13:50:38.604 Received unsupported CodeSite message format ($2F0038) via TCP.
Warning 8/25/2016 13:50:38.607 Received unsupported CodeSite message format ($32000A) via TCP.
Warning 8/25/2016 13:50:38.608 Received unsupported CodeSite message format ($130005) via TCP.
Warning 8/25/2016 13:50:38.609 Received unsupported CodeSite message format ($40100) via TCP.
Warning 8/25/2016 13:50:38.610 Received unsupported CodeSite message format ($17000A) via TCP.
Warning 8/25/2016 13:50:38.611 Received unsupported CodeSite message format ($80006) via TCP.
Warning 8/25/2016 13:50:38.614 Received unsupported CodeSite message format ($190017) via TCP.
Warning 8/25/2016 13:50:38.616 Received unsupported CodeSite message format ($18000B) via TCP.
Warning 8/25/2016 13:50:38.619 Received unsupported CodeSite message format ($20100) via TCP.
Warning 8/25/2016 13:50:38.620 Received unsupported CodeSite message format ($FF010001) via TCP.
Error 8/25/2016 13:50:48.592 Exception in TcpServerExecute: Connection Closed Gracefully.
Error 8/25/2016 13:50:48.597 Exception in TcpServerExecute: Connection Closed Gracefully.
Error 8/25/2016 13:50:48.600 Exception in TcpServerExecute: Connection Closed Gracefully.
Error 8/25/2016 13:50:48.601 Exception in TcpServerExecute: Connection Closed Gracefully.
...

So based on that I started assuming there was bad traffic on TCP 3434, but maybe that was a bad assumption. This is using 5.1.0 obviously, since the 'Gracefully' messages are still in there.

Any help would be greatly appreciated.
jkottas
 
Posts: 7
Joined:
Thu Dec 20, 2012 9:44 pm

Re: Need to disable/change ports when installing CS5Tools

Postby Raize Support » Wed Aug 31, 2016 12:36 am

After you changed the port settings in the CSDispatcher.ini file, did you restart the Dispatcher?

Please send the full CSDispatcherLog.txt file (zipped up) to support@raize.com and we'll take a look.

Ray
Raize Software Support
Raize Software
http://www.raize.com
Raize Support
 
Posts: 611
Joined:
Fri Mar 25, 2011 9:04 pm

Re: Need to disable/change ports when installing CS5Tools

Postby jkottas » Mon May 08, 2017 10:32 am

If anyone else runs into this, updating to 5.1.8 ended up being the fix.
jkottas
 
Posts: 7
Joined:
Thu Dec 20, 2012 9:44 pm


Return to Tools

Who is online

Users browsing this forum: No registered users and 1 guest

cron