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)

Similar Messages

  • 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.

  • ABAP Program to send HTTP message

    Hi All,
    I tried executing the program in "[ABAP-Based HTTP Client for Messages to SAP XI|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ae388f45-0901-0010-0f99-a76d785e3ccc]" Article to send HTTP messages to XI system.
    Entered all required parameters and entered XMl Payload with the option "Insert Payload as Text"
    The scenario in XI has Integration Process and the first step is a Sync-Async step.
    The message execution fails in that step with status "Pipeline Timeout"
    I can see only half of the xml payload in sxmb_moni.
    There are no short dumps and the Integration Process is working fine when I send messages using HTTP client.
    Let me know if there are any checks for tracing the problem.
    Thanks,
    Uma

    Hi,
    I have gone thru this blog but I want send SMS to US Mobile no.I checked other webservice but it supports only few cellular networks in US.
    any other alternate for this...
    anyway thanks for your reply
    Regards,
    Nivas

  • 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

  • Http connection timeout for business services from proxy service?

    I've only done limited experiments in ALSB (2.1) at this point, but a question occurred to me, and I can't find this mentioned in the docs anywhere.
    When a proxy service configures a connection to a downstream business service through HTTP, is it possible to configure an http connection timeout value? This will cause the connection attempt to fail if it takes too long to determine whether the connection attempt succeeded or failed.
    I've heard that this is one advantage that Axis has over JAXRPC/SAAJ, as a connection timeout value can be specified.

    Hello Billy
    Thanks for the reply. I thought there may be some implementation of begin_request in another environment that had the option to specify a connect timeout. But as you have explained, it doesn't work like that. As always, I learn something every day!
    So realistically if I want to stop the calling process hanging in the event of the server not being available, I need use the message based approach...send a message containing the request to another process via a message queue and attach to the reply queue and wait for a message comming back with a timeout. Does that sound like a reasonable approach?
    Thanks
    David

  • HTTP Connection timeout setting

    Hi,
    I'm using ebXML protocol for B2B 10.1.2.3+MLR 5.
    I talk to multiple trading partners and when one of the TP is down, we see that there is a pileup of messages in the backend queues.
    This is because, there is constant message inflow into the JMS queues by the back-end application and each message is taking a long time to timeout (nearly 20 seconds). So what effectively happens is that a message was supposed to reach the TP in 1 sec will take 20 sec before it labels as a HTTP connection timeout error .
    Can we set the HTTP Connection timeout setting in B2B? (I saw a setting in B2BGurus for EDI though)
    If not, please can you suggest if it can be set in the Application Server level?
    Please help!
    Thanks in advance,
    Warm Regards,
    Suhas.

    All,
    At the application server level, there is a timeout setting in httpd.conf. The default value has been set to 300 seconds.
    Regards,
    Suhas.

  • HTTP_RESP_STATUS_CODE_NOT_OK - HTTP message to XI system

    Hi,
    We receive this error when trying to post HTTP message to XI system.
    Have edited the username, password in SICF, xi->engine but it did not solve the problem.
    Can you please let us know if there is anything else we can do.
    Regards,
    Amar

    hi,
    when making a call to xi you need to provide credentials before the interface is executed .
    for example
      reqString = reqString + document.MessageParameters.Server.value+":";
      reqString = reqString + document.MessageParameters.Port.value + "/sap/xi/adapter_plain?";
      reqString = reqString + "namespace=" + senderNamespace;
      reqString = reqString + "&interface=" + document.MessageParameters.SenderInterface.value;
      reqString = reqString + "&service=" + document.MessageParameters.SenderService.value;
      reqString = reqString + "&party=" + document.MessageParameters.SenderParty.value;
      reqString = reqString + "&agency=" + document.MessageParameters.SenderAgency.value;
      reqString = reqString + "&scheme=" + document.MessageParameters.SenderScheme.value;
      reqString = reqString + "&QOS=" + document.MessageParameters.Qos.value;
      reqString = reqString + "&sap-user=<b>useid</b>&sap-password=<b>pwd</b>";
      reqString = reqString + "&sap-client=" + document.MessageParameters.Client.value + "&sap-language=D";
    cheers,
    naveen

  • "Failed to Send the HTTP Message..." - HTTPSupport problem

    Hello,
    We're having a few difficulties when the HTTPServer in UDS5.0.3 running on Solaris 8. Basically, we have a pair of MS .NET servers using some XML Webservices that we reside on the UDS server.
    The symptoms of the problem are that a lot of "Failed to send the HTTP message..." messages are being seen in the log for the partition that contains instances of the HTTPServer. The reason given is a UsageException on the ExternalConnection - stating that the "Object is not open for I/O so it cannot be read or written" (ExternalConnection::Write at 1). This only occurs when a HTTP Response is to be sent back to the .NET server.
    Unfortunately, this exception appears to be occurring somewhere within the code held in the HTTPSupport library, so we can't easily trace the error. Worse still, we don't actually know what's causing the error.
    Does the error indicate a problem with comms between our UDS HTTPServer and the .NET servers? We've also noticed a large number of socket connections being left in a state of CLOSE_WAIT when this error occurs (which eventually block the port altogether resulting in the HTTPServer instances becoming unresponsive).
    As far as I can tell, the Solaris TCP/IP settings are all at the OS default.
    Many thanks for any assistance,
    Jason Bridgen.

    Hi Gordon,
    The problem was solved, the customer changed his ip adress on the server and it's OK now!
    Thank you !!
    Hilla.

  • How can I capture the complete http-message sent from client to WAS?

    Hello,
    When debugging a BSP application several utility classes/objects are available. Only I can't find the original authentication information forwarded by the client (userid). Therefor I would like to have available the whole http-message (full header and body) so I can distil the information myself.
    Is there a method available which gives me the full, original http-message sent by the client?
    NOTE: I use http-watch in my browser but this is not available on the reversed proxy.
    kind regards,
    Roelof Jan

    Thanks Durairaj,
    I have converted ws_xtring to a string which results in the readable stream below:
    GET /tomonline(bD1lbiZjPTAxMA==)/bp_login.htm HTTP/1.0##host: kappa.trespa.com:8
    015##accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vn
    d.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-sho
    ckwave-flash, /##accept-language: en-us##cache-control: no-cache##connection:
    Keep-Alive##cookie: sap-usercontext=sap-client=010;##pragma: no-cache##referer:
    https://trespa.infonet-asp.com/__extraweb__authen##user-agent: Mozilla/4.0 (comp
    atible; MSIE 6.0; Windows NT 5.0)##authorization:
    But now we get to my real problem. I'm missing authentication information in the httpmessage, forwarded by a reversed proxyserver which is visible in the serverlog (SMICM>Goto>HTTP Log>Server Name>Display Entries):
    ...snapshot of logtail, related to http string above
    212.189.47.211 - tomadmin [20/Apr/2006:11:50:12 +0200] "GET /tomonline(bD1lbiZjPTAxMA==)/bp_login.htm HTTP/1.0" 500 3700
    >212.189.47.211 = the ipadres of the reversed proxy (=client for the BSP application)
    >tomadmin       = the userid which is forwarded basic authentication userid by reversed proxy
    I'm purely interested in this userid <b>tomadmin</b> which I want to use in my application.
    Where did my <b>tomadmin</b> go???
    I configured the service ztomonline as anonymous login. Maybe this mechanism strips of the userid.
    regards Roelof Jan
    Message was edited by: Roelof Jan Bouwknegt

  • How to handle HTTP Message Format

    Hi All,
    i have the interface like XML File(Supplier)--XI--HTTP Message Post(SRM Server)
    How to handle this case and how to handle the HTTP Message formats, what Adapters and all i need to use here
    Regards
    Vamsi

    check susma's reply
    File to HTTP
    File to HTTP
    /people/kausik.medavarapu/blog/2005/12/29/csv-file-lookup-with-http-request-and-response-in-xi

  • Set HTTP Connection timeout to avoid Deny Of Service attack

    Hi,
    Is there a way to set a HTTP Connection timeout in Sun Java Application Server Platform Edition ?
    I need this because many clients are holding an HTTP Connection too long on my Application Server causing a Deny Of Service because of file descriptor leak.
    Regards,
    Laurent.

    All,
    At the application server level, there is a timeout setting in httpd.conf. The default value has been set to 300 seconds.
    Regards,
    Suhas.

  • 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.
    ===========

  • 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]

  • 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.

  • Complete message timeout in weblogic client

    Hi,
    We have a weblogic client application connecting to weblogic server 8.1 SP6. The client is getting the below error while executing a rmi call. I have tried setting the CompleteMessagetimeout in weblogic console as well as the client program (-Dweblogic.CompleteMessageTimeout=480). But still the below exception occurs. Any one can help to identify how to set a higher value for CompleteMessageTimeout in client side ? I noticed a number of threads in the forums, but unable to find a concrete answer.
    ERROR stdErr 22/Jan/2010/09:45:28 - Caused by: java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@125d61e', in the configured timeout period of '60' secs
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:796)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Hi,
    Please try applying the following two properties in the Service Stub... (This change you need to make on Client Program after getting the "port" reference....rest of the code will be same)
    ((Stub)port)._setProperty("weblogic.wsee.transport.read.timeout ","480");
    ((Stub)port)._setProperty("weblogic.wsee.transport.connection.timeout ","480");
    Actually 60-Seconds is the Default " T3 Connection Timeout " period which u are getting in the Logs...i am finding a way to tune that...amy be some JAVA_OPTIONS..(ideally it is not recommended to change t3 Timeout).
    Are you trying to Upload Large amount of file to the WebService?
    Example:
    HelloWorldService service = new HelloWorldService_Impl();
    HelloWorldPortType port = service.getHelloWorldPortTypeSoapPort();
    int time=Integer.parseInt(args[1]);
    System.out.println("\n\n\t Timeout is set for "+time+"-Seconds");
    ((Stub)port)._setProperty("weblogic.wsee.transport.read.timeout", time);
    ((Stub)port)._setProperty("weblogic.wsee.transport.connection.timeout",30);
    port.sayHello("Jay");
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

Maybe you are looking for