on 03-12-2009 4:56 AM
Dear All,
We have a issue in our PRD environment:
we see that many Synchronous messages in PRD get TIMED OUT:
we are planning to Increase the Message TimeOut parameter Value in PI system.
I just want to know,
what can be possible Downfall and effects of Increasing the value of the Time Out Parameter.?
what will be the possible Impact on the Performance of the System?
and what value can be set for the Message Timeout Parameter?
Please Advice,
Thanks and Regards,
Senthilprakash.
we are planning to Increase the Message TimeOut parameter Value in PI system.
Do you mean the syncMessageDeliveryTimeoutMsec parameter in Visual Admin? If yes, then the value provided must be in milliseconds. Which scenario are you actually configuring (what is the receiver system)?
The only disadvantage would be that in case of slow response from receiver, the process thread will remain in use for the increased time interval till the timeout occurs. This will affect the performace negatively if you face slow response or lots of error cases at receiver.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Prateek,
Yes this is for sync Message Delivery parameter in Visual Admin. for JDBC Sync Interfaces.
What else will be the impact of this increment apart from locking of Threads for long time if delay from receiver system.
Like performance of other Async scenarios?
What will be the recommended timeOut value which can be put. as we cant do Trial and Error approach in PRD. and also this issue is not faced in Test Environment.
Please Advice,
Thanks and Regards,
Senthilprakash.
Dear Krishnamoorthy,
Sorry for the delay. Actually we are facing this problem in Synchronus JDBC-JDBC (SQL 2000 Database) scenario for a specific country.
does this timeout occure due to network slow in the country side.?
is there any parameter that can be sent in the database level?
if we increase the value to how much should we increase it to?
Please Advice,
Thanks and Regards,
Senthilprakash.
Hi
There is no specific best elapse time set for time out , it all depends of u r Receiver system response time.
So better check u r response time of u r JDBC , If u r facing this problem sending bulk data in turn causing time out --> better send first n records which always gets processed with out timed out say 100 records.This would have a control on u r interface not leting you to timed out error.
Any more queries revert back
Thanks
Srini
Thanks Venkatesh but we cant control the flow of messages (records and Priorities them) as this is happening in PRD environment and we cant ask the clients to send the data in the order we specify to them.
Will it cause any positive impact if we increase Maximum Concurrency value for JDBC Adapters with high load?
will it do any good?
Please Advice,
Thanks and Regards,
Senthilprakash.
Hi
Am not asking your client to control flow of records , we can control on Sender JDBC adapter level
by selecting first n rows with status "F" for example , important we should know the how much time it takes to process and get response , using stored procedure in receiver adapter update back those records to status "T" with set of unique combinations.
Concurreny increase wonot impact , it's a functionality helps to handle parallel processing.
rgds
srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.