Synchronous JDBC - message timeout

Hi,
I have a scenario RFC-XI-JDBC synch. I am getting a message timeout error while trying to post large data volume. Apparently the sync message is geting expired after timeout (default 180 sec).
I found SAP note 730870 (question 14) suggests to increase the property xiadapter.inbound.timeout.default. However, SAP note 791379 says you should never change this value.
Is anyone has chaged this value in oreder to optimize performance ? Pls suggest.
Also pls let me know if you have any other suggestion.

As per the documentation
http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
You should increase the timeout from 180000(default) to 240000.
or 240 sec.
please visit
Re: MessageExpired because of large amount of data

Similar Messages

Synchronous Proxy to Synchronous JDBC scenario

Hi,
I have a scenario for a synchronous PROXY to a synchronous JDBC scenario. I have set 4 message types .
MT_PROXYOUT u2013 o/b synch with a response MT_PROXYIN
MT_JDBC - i/b synch with a response MT_JDBC_RESPONSE
I then set up an interface mapping for both the request and response message interfaces. The design looks good but I got stuck in the configuration part.
Since itu2019s a proxy sender, the sender agreement is not needed(Correct me if I am wrong). In the interface determination, there is provision for only the inbound interface which in case would be the JDBC (request/response) back to the proxy and the interface mapping is applied.
So do I need just one interface determination from the proxy as sender and jdbc as receiver and also one receiver determination again with the proxy as sender and the jdbc as receiver. I am confused here because when I try to create a receiver determination for the response back from JDBC to proxy receiver , the interface mapping comes blank. Is it taken in account by the single receiver determination in synchronous to synchronous scenarios??
Teresa

Hi Teressa,
Java Proxy to Synchronous JDBC scenario and SAP XI:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP proxies-
Client proxy:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Cheers
Sunil

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Synchronous JDBC adapter(receiver side) with stored procedure

Hi experts,
Can some database processing logic be included in receiver JDBC (synchronous) adapter...to put it simply
I have synchronous JDBC adapter in the receiver side..Using this JDBC adapter I want to get some response back from the table..
The requirement is not a simple fetch from the table..It involves some processing in the database side which I guess will be done by stored procedure..After this database processing , this output will be picked up by the JDBC adapter and will send to PI.
How can this be achived ..Any Blog..
Thanks
Ayan

Yes u can use stroed procedure and send back the response,
refer this link for stored procedure structure.
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/frameset.htm
chirag.

Synchronous Fault Message

Can anybody tell abt Synchronous Fault messaging.......
How mapping is done between them.
Thanks
Jai

Hi,
Check the Threads Treatement of Fault Messages in Synchronous Scenarios?!
Re: Synchronous & Fault
Thanks!

HTTP message timeout

Hi All,
I am unable to set the time out value for complete message time out=-1 in weblogic 10.
In weblogic 8.1 we can set the value og http message time out as -1.
Is there any such parameter for weblogic 10?
If yes can we set it to -1.
By setting complete timeout =480, I am facing timeout issues for message greater than 10MB.

Hi,
*<complete-http-message-timeout>* is the maximum number of seconds spent waiting for a complete HTTP message to be received. If you configure network channels for this server, each channel can override this HTTP message timeout.
This timeout helps guard against a denial of service attack in which a caller indicates that it will be sending a message of a certain size which it never finishes sending.
*A value of -1 indicates that this value should be obtained from network channels configured for this server.*
Minimum value: -1
Maximum value: 480 (U have set the Maximum possible value for this at your end)
Secure value: 60
Admin Console Location to Edit this value:
Home---> DomainName-->Server Summary--->AdminServer (Or any other Server)---> Protocol(tab)---->General(tab)
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are here)

Deferred Message Timeout

The Default is 4 days for a Deferred Message Timeout in GroupWise. My questions are: Is this an RFC standard? I have been asked to shorten, Have other GroupWise shops shortened the Deferred Message Timeout?
Thanks

On 4/6/2012 7:30 AM, Kirk White wrote:
> The Default is 4 days for a Deferred Message Timeout in GroupWise. My
> questions are: Is this an RFC standard? I have been asked to shorten,
> Have other GroupWise shops shortened the Deferred Message Timeout?
> Thanks
It's mostly recommendations in RFC 2821
but they recommend 4-5 days
4.5.4.1. Sending Strategy
The general model for an SMTP client is one or more processes that
periodically attempt to transmit outgoing mail. In a typical system, the
program that composes a message has some method for requesting immediate
attention for a new piece of outgoing mail, while mail that cannot be
transmitted immediately MUST be queued and periodically retried by the
sender. A mail queue entry will include not only the message itself but
also the envelope information.
The sender MUST delay retrying a particular destination after one
attempt has failed. In general, the retry interval SHOULD be at least 30
minutes; however, more sophisticated and variable strategies will be
beneficial when the SMTP client can determine the reason for non-delivery.
Retries continue until the message is transmitted or the sender gives
up; the give-up time generally needs to be at least 4-5 days. The
parameters to the retry algorithm MUST be configurable.
A client SHOULD keep a list of hosts it cannot reach and corresponding
connection timeouts, rather than just retrying queued mail items.
Experience suggests that failures are typically transient (the target
system or its connection has crashed), favoring a policy of two
connection attempts in the first hour the message is in the queue, and
then backing off to one every two or three hours.
The SMTP client can shorten the queuing delay in cooperation with the
SMTP server. For example, if mail is received from a particular address,
it is likely that mail queued for that host can now be sent. Application
of this principle may, in many cases, eliminate the requirement for an
explicit "send queues now" function such as ETRN [9].
The strategy may be further modified as a result of multiple addresses
per host (see below) to optimize delivery time vs. resource usage.
An SMTP client may have a large queue of messages for each unavailable
destination host. If all of these messages were retried in every retry
cycle, there would be excessive Internet overhead and the sending system
would be blocked for a long period. Note that an SMTP client can
generally determine that a delivery attempt has failed only after a
timeout of several minutes and even a one-minute timeout per connection
will result in a very large delay if retries are repeated for dozens, or
even hundreds, of queued messages to the same host.
At the same time, SMTP clients SHOULD use great care in caching negative
responses from servers. In an extreme case, if EHLO is issued multiple
times during the same SMTP connection, different answers may be returned
by the server. More significantly, 5yz responses to the MAIL command
MUST NOT be cached.
When a mail message is to be delivered to multiple recipients, and the
SMTP server to which a copy of the message is to be sent is the same for
multiple recipients, then only one copy of the message SHOULD be
transmitted. That is, the SMTP client SHOULD use the command sequence:
MAIL, RCPT, RCPT,... RCPT, DATA instead of the sequence: MAIL, RCPT,
DATA, ..., MAIL, RCPT, DATA. However, if there are very many addresses,
a limit on the number of RCPT commands per MAIL command MAY be imposed.
Implementation of this efficiency feature is strongly encouraged.
Similarly, to achieve timely delivery, the SMTP client MAY support
multiple concurrent outgoing mail transactions. However, some limit may
be appropriate to protect the host from devoting all its resources to mail.
===========

What constraints force usage of Synchronous JMS Messaging

Hi,
I fail to understand why would synchronous JMS messaging be used when there are multiple ways of achieveing remote synchronous calls.
I have read the threads on JMS, some people have mentioned that due to some constraints they are forced to use JMS Synchronous messaging.
What are the contraints that force Synchronous JMS Messaging?
Which commercial applications use Synchronous Messaging?
Thanks
Rashmi

In our project, the only time sync messaging seems to make any sense is if a human is waiting on the answer as opposed to a headless type of systematic transaction. This represents a very small portion of our problem space.
hope this helps
ricardo

Changing message timeouts

I'm running the 4.9 SP2 Client on a 2K box.
I cannot find a message timeout setting in the advanced settings of the
client tab. Is there a way to change the message timeouts with this client.
What I'm trying to do is get the print job notification to pop up for two
seconds and then go away without having to click the "clear" button. It
used to work on the older clients but stopped when I installed newer OS And
client.
Thanx
Kevin Funnell

In article <[email protected]>, Dave Parkes
wrote:
> As do the Win9x clients
Guess it's been too long since I used it. Thanks for the
addition/correction.
-Barry. [Novell Support Forums SysOp]

Synchronized JDBC

Hi this is slighly off topic.
I'm new to Oracle (not Java) and am calling stored procs,
using prepareCall, via JDBC (level 4) on Oracle 8.05.
My Java app will have multiple threads inserting/updating. Do I
have to synchronize my java calls (performance issue) or can
Oracle handle multiple synchronous JDBC calls. Generally I would
synchronize and will do unless someone tells me otherwise.
Thanks for any help
Ritchie
null

Oracle will handle multiple synchronous JDBC calls. The standard
row locking behavior will apply though.
Hope this helps,
-Chris
ritchie turner (guest) wrote:
: Hi this is slighly off topic.
: I'm new to Oracle (not Java) and am calling stored procs,
: using prepareCall, via JDBC (level 4) on Oracle 8.05.
: My Java app will have multiple threads inserting/updating. Do
I
: have to synchronize my java calls (performance issue) or can
: Oracle handle multiple synchronous JDBC calls. Generally I
would
: synchronize and will do unless someone tells me otherwise.
: Thanks for any help
: Ritchie
null

Synchronous JDBC Timeout

Hi Experts, I have a synchronous proxy-jdbc with SQL_QUERY (Select) as action. When the query is executed directly in the DB, it's only taking 3-4 minutes to get the results. But when it's run thru PI, we always encounter synchronous timeout exceeded error (20 minutes). Since the query is getting results on time in the DB, I'm thinking the problem could be in PI side but I'm running out of options to check. Has anyone faced this problem before? Any inputs will be greatly appreciated. Thanks!

Hi Mark,
It looks like a network problem. Can you ping the database hostname in your PI system (create ping command in SM69)? Also take a look at this note: Note 1085539 - XI JDBC/FTP connection Test and XML Validation Application
Hope this helps,
Mark

Message Timeout in Peoplesoft

In configuration PSAPPSRV timeout is set to 300 seconds. There are instances when for an inbound syncrequest the processing time in Peoplesoft might take more than 300 seconds. Since IG doesnt receive a response within 300 seconds it reposts the same message again to Peoplesoft (with a different message transaction_id). Is there a way to stop these messages from being reposted? I do not want to change the timeout specified in the configuration file. I just want to stop these messages from being re-posted
SO Used: Inbound Synchronous
Message Type: Non-Rowset (transformed)
PT version : 8.51.10

Hi,
See this doc which explains how you can override the timeout on runtime for a specific service operation
E-IB: How to Override Default Timeout for Integration Broker Synchronous Service Operations (Messages) [ID 658690.1]
Also see PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: Integration Broker > Sending and Receiving Messages > Generating and Sending Messages > Overriding Synchronous Timeout Intervals at Runtime
This PeopleBooks uses the SyncServiceTimeout property of the IBInfo Class.
PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: PeopleCode API Reference > Message Classes
Snipet from PeopleBooks:
SyncServiceTimeout
Description
This property takes a time (in seconds). This time overrides the default HTTP timeout that is used for all requests. If you set this property, you can use this to read back the time, that is, set the time before the SyncRequest is executed, then see when it is changed in an implementation of the OnSend method.
Note. This property is only for synchronous requests.
Generally, you use SyncServiceTimeout to dynamically set the timeout value for a specific transaction. The http header file is modified to take this new parameter. In addition this value is sent to the gateway to be used for the http timeout. Use this so that a long running transaction will not timeout. In addition, you don't have to wait through the default period for a specific transaction to timeout.
The following is a typical example of using this property:
&MSG.SetXmlDoc(&xmlReq);
&MSG.IBInfo.LoadConnectorPropFromNode(Node.EAI)
&MSG.IBInfo.SyncServiceTimeout = 360000;
&MSG.IBInfo.ConnectorOverride = true;
&MSG_Resp = SyncRequest(&MSG, Node.EAI);
&xmlResponseDoc = &MSG.GetXmlDoc();
Setting the XML directly is not valid. You need to use the message object to set the value. In order for this to work you must override the connector properties, which means you must set up the connector properties for this transaction, using one of the load methods (such as LoadConnectorPropFromNode, LoadConnectorPropFromTrx, and so on.)
This property is read-write.

JDBC Wait timeout in WL 7.0

Hi All,
We are using the JDBC connection pool in the application and I have
coinfigured the max connections as 100. Its been observed that, when
the 101st user request for the connection, pool throws
ResourceException immediately without waiting any time. Is it possible
to coinfigure pool in WL 7.0 with wait timeout? if possible how?
Thank you all,
Santhosh.

Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]..
Currently there is no way to make the pool waiting. But you can
easily fix the problem by increasing size of the connection
pool.So if he increases to 200, and his 201st user logs in and gets the same
problem?Aparently, if you can not set up a pool to satisfy all requests,
there is a problem with code/design. We can hardly fight
programming/design mistakes except may be giving good
advices.
The fundamental problem is that the design of his application is retaining
a pooled JDBC connection indefinitely, spanning multiple interactionsbetween
a given user and the server. If this is necessary the customer must either
have a pool with as many connections as he will have concurrent users,I meant exactly that.
or he should write his application to use direct non-pooled connectionswhich
he gets from the DBMS driver.Than application will get screwed up using direct driver calls.
As for me, it doesn' t make big difference. At least using
pool helped to identify the fact of the problem presence
quickly.
< Ideally, the customer can design the application
like EJBs or good servlets, that get a connection, use it, and return itto the pool,
all with a single user-server message/response.Sure.
Regards,
Slava Imeshev

Synchronous JDBC scenario

Hi All,
The scenario is
SAP Portal will send data to XI using web service(SOAP Adapter) and then XI will post data in Database using JDBC adapter.
When above scenario executes it is automatically creating response (Synchronous) once it post data in Database (New message in SXI_MONITOR). I have checked message interface both inbound and outbound are asynchronous. When I ran the same scenario using file adapter instead of SAP portal it is not creating new message.
Please guide how to avoid creating new message in case of SAP Portal .

Hi,
The jdbc response is generated in synchronous cases.
Make sure the webservice call that you are making is asynchronous.
In case of file adapter the call you made was asynchronous, hence no response was generated.
Check this blog for configuration for Capturing response message.
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
- Deepak

Synchronous JDBC - message timeout

Similar Messages

Maybe you are looking for