Service Transport TCP is busy (5485)

Posted by tharanga_herath on 20-Jan-2015 05:10

Hi Guys,

We are getting following error  "Service Transport TCP is busy (5485)" from the progress client application.

But Error is not appear always.  Clients are connecting trough Terminal Server sessions

Database server is in Windows 2003  64bit

Progress version is 9.1E with SP 4 which is applied for both appserver and database server 

nine databases available in the database server

We have properly set up the database ports and  min max ports for each database. all the databases configure through progress explorer as admin server aware databases.

When we got the error, still the same session we can telenet broker ports

 But for the app it need to make several tries to connect to the application again.

We have stop scanning the db files and progress files through the virus scan and also we have exclude the ports from virus scan.

But still  we are receiving this error and not sure where to start cause we don't get any errors in the database log ..

Is anybody have similar experience?     

Progress User Groups - Forum
Posted by tharanga_herath on 06-Mar-2015 04:12

Hi Libro,

Sorry for the late response

Thanks for the help. issue is happening due to the internal ports create by the socket program. you fix  help to fix the issue.

But we change the socket program and implement it in an  different method so then we dont need to increase the port ranges ect.  

Many thanks

All Replies

Posted by Libor Laubacher on 20-Jan-2015 05:45

I am going to assume (based on the error) that you are using AppServer.
One of the possible reasons for this is “conflict” between AppServer minport/maxport and ports/services defined in etc/services on the AppServer machine.
 
You want the appserver minport/maxport range not to have any “conflict” with etc/services, eg define minport/maxport for the appserver in range not used/defined in etc/services
 
[collapse]
From: tharanga_herath [mailto:bounce-tharanga_herath@community.progress.com]
Sent: Tuesday, January 20, 2015 12:11 PM
To: PUG-Forum@community.progress.com
Subject: [Progress User Groups - Forum] Service Transport TCP is busy (5485)
 
Thread created by tharanga_herath

Hi Guys,

We are getting following error  "Service Transport TCP is busy (5485)" from the progress client application.

But Error is not appear always.  Clients are connecting trough Terminal Server sessions

Database server is in Windows 2003  64bit

nine databases available in the database server

We have properly set up the database ports and  min max ports for each database. all the databases configure through progress explorer as admin server aware databases.

When we got the error, still the same session we can telenet broker ports

 But for the app it need to make several tries to connect to the application again.

We have stop scanning the db files and progress files through the virus scan and also we have exclude the ports from virus scan.

But still  we are receiving this error and not sure where to start cause we don't get any errors in the database log ..

Is anybody have similar experience?     

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by tharanga_herath on 20-Jan-2015 07:06

Thanks

. But we are not going through appserver.

This is client server application where clients are

connect through client networking

min max port i referring hear is in database server port

range

ra

Posted by Libor Laubacher on 20-Jan-2015 07:18

The database has indeed minport/maxport parameters/range.
The same what I said about that and etc/services apply there too.
 
[collapse]
From: tharanga_herath [mailto:bounce-tharanga_herath@community.progress.com]
Sent: Tuesday, January 20, 2015 2:08 PM
To: PUG-Forum@community.progress.com
Subject: RE: [Progress User Groups - Forum] Service Transport TCP is busy (5485)
 
Reply by tharanga_herath

Thanks

. But we are not going through appserver.

This is client server application where clients are

connect through client networking

min max port i referring hear is in database server port

range

ra

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by tharanga_herath on 20-Jan-2015 07:29

Yes. Agreed. I have test that. This happens even all

the database servers are started in db. No error in db.

don't know where to start. I have already log a case on sp

support portal till issue is their

Posted by Libor Laubacher on 20-Jan-2015 07:35

Ø  I have test that

 
You have tested what ?
 

Ø  don't know where to start

 
Checking the db minport/maxport is outside the ports defined in etc/services ?
 
[collapse]
From: tharanga_herath [mailto:bounce-tharanga_herath@community.progress.com]
Sent: Tuesday, January 20, 2015 2:30 PM
To: PUG-Forum@community.progress.com
Subject: RE: [Progress User Groups - Forum] Service Transport TCP is busy (5485)
 
Reply by tharanga_herath

Yes. Agreed. I have test that. This happens even all

the database servers are started in db. No error in db.

don't know where to start. I have already log a case on sp

support portal till issue is their

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by tharanga_herath on 20-Jan-2015 08:02

Hi,

I have tested port are blocking in the database min max port range.

I have set -Mi value to one and make database connections and started all the servers. once I done that I ask users to connect through the terminal server. Still We are getting TCP port blocking issue.

Same time  in  same session I have telenet the database broker port and It is possible to telenet.

Hope I answer to your question.

Posted by tharanga_herath on 20-Jan-2015 08:03

Is this a issue related to Terminal server ?.

Posted by Libor Laubacher on 20-Jan-2015 09:19

Ø  Hope I answer to your question.

I am afraid I don’t know as I don’t know what does “I have tested port are blocking in the database min max port range.” mean.

I asked you if you can check whether the minport/maxport range for your databases does not ‘collide’ with ports defined in etc/services.

Ø  Is this a issue related to Terminal server ?

Can you connect to the database from somewhere else at the very same time ?

Posted by tharanga_herath on 20-Jan-2015 17:42

Hi  Libro,

I am afraid I don’t know as I don’t know what does “I have tested port are blocking in the database min max port range.” mean. -

Yes port are not conflicting with services.

If all the database servers are started It means all the ports are open  for that database --- Is this wrong ???

Cause if you go to the promon you can see the server process ID and the port. so I don't see any Port conflicting come on that stage maximum servers are started for all databases when customers are connecting to database

Ø  Is this a issue related to Terminal server ?

Can you connect to the database from somewhere else at the very same time ?

Yes It is possible to make the connection.

Not all the Terminal server users are getting this error. even a user get this error same session I can connect to the

database from data dictionary. also same session  after some time user can connect again without error.

Posted by Libor Laubacher on 21-Jan-2015 04:06

Can you apply suggestions from those 2 articles onto the Windows terminal server machine to see if that helps ?
 
 
[collapse]
From: tharanga_herath [mailto:bounce-tharanga_herath@community.progress.com]
Sent: Wednesday, January 21, 2015 12:43 AM
To: PUG-Forum@community.progress.com
Subject: RE: [Progress User Groups - Forum] Service Transport TCP is busy (5485)
 
Reply by tharanga_herath

Hi  Libro,

I am afraid I don’t know as I don’t know what does “I have tested port are blocking in the database min max port range.” mean. -

Yes port are not conflicting with services.

[/collapse]

Posted by tharanga_herath on 06-Mar-2015 04:12

Hi Libro,

Sorry for the late response

Thanks for the help. issue is happening due to the internal ports create by the socket program. you fix  help to fix the issue.

But we change the socket program and implement it in an  different method so then we dont need to increase the port ranges ect.  

Many thanks

This thread is closed