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)

Similar Messages

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

  • BEA-101083 Connection failure.java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@16907c  at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger

    While trying to publish mesaage by MQ 5.3 .I got the following error
              Please help.
              <Error> <HTTP> <BEA-101083> <Connection failure.
              java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff
              3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
              at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:775)
              at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
              at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

    Can you help me ? I have the same problem.

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

  • A complete message could not be read on socket

    hello to everybody...
    I have a client swing application witch call in RMI a stateless ejb deployed on a WeblogicServer 8.1 sp5.
    The problem is that when we have a slow net I receive on the client the following Exception.The server don't receive the calling ( otherwise the complete message time out on the server is of 480 seconds ).So I think that I ahve to set a client timeout,but witch?and how?and where?...perhaps the heartbeat timeout?
    Going around in the internet forums I have seen that a lot of people have the same people...so if someone could be so kind to help us....I would be very grateful...
    thanks for help and sorry for bad english
    weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@b01d43', in the configured timeout period of '60' secs
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
         at irma.ejb.serviceSessionManager.ServiceSessionManager_b1engw_EOImpl_812_WLStub.getService(Unknown Source)
         at irma.serviceLocator.ResourceLocator.remoteService(ResourceLocator.java:72)

    giorgio giustiniani <> writes:
    You need to increase the value of CompleteMessageTimeout
    andy
    hello to everybody...
    I have a client swing application witch call in RMI a stateless ejb deployed on a WeblogicServer 8.1 sp5.
    The problem is that when we have a slow net I receive on the client the following Exception.The server don't receive the calling ( otherwise the complete message time out on the server is of 480 seconds ).So I think that I ahve to set a client timeout,but witch?and how?and where?...perhaps the heartbeat timeout?
    Going around in the internet forums I have seen that a lot of people have the same people...so if someone could be so kind to help us....I would be very grateful...
    thanks for help and sorry for bad english
    weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@b01d43', in the configured timeout period of '60' secs
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
         at irma.ejb.serviceSessionManager.ServiceSessionManager_b1engw_EOImpl_812_WLStub.getService(Unknown Source)
         at irma.serviceLocator.ResourceLocator.remoteService(ResourceLocator.java:72)

  • Java.io.IOException: A complete message could not be read on socket

    Hell All , Am gettign this issue very frequently .. From my googling i see that this can be because weblgic server was not able to do an IO operation because of time out or may be because of Net work issue ..
              I would like to know how this can be fixed
              java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@a7f309 - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs

    Hi All,
    Has anyone got any further information on this problem? I have several instances of the message
    ###<Dec 13, 2005 2:29:40 PM GMT> <Error> <socket> <finland> <serviceview> <ExecuteThread: '12' for queue: 'default'> <kernel identity> <> <000424> <I
    OException on socket: weblogic.socket.MuxableSocketDiscriminator@4a4b21 - number of bytes read: '0', buffer: 'null', fd: 23
    java.net.SocketException: Connection refused: Connection refused>
    java.net.SocketException: Connection refused: Connection refused
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(Unknown Source)
    at weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:898)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:782)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:708)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    In my wl-domain.log. I have no idea how to solve this? I am running WebLogic 7 SP4 on HP-UX 11.11 with JDK 1.3.1.09.
    I note that the release notes for WL7 SP 6 release notes mention MuxableSocketDiscriminator. See link http://e-docs.bea.com/wls/docs70/notes/resolved2.html Is this the problem? Anyone else come accross this and solve it?
    Best Regards,
    Kevin.
    Any help much appreciated. Best Regards, Kevin.

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

  • Deployment operation was not completed within timeout

    I use Eclipse 3.3 and WLS 10. If i deploy my EAR to the server after 5min i get the following error in plugin "com.bea.workshop.wls.core":
    "Deployment operation was not completed within timeout. State Type : running; Command Type : distribute; Action Type : execute; Completed : false; Failed : false; Message : null; Exception : null"
    The timeout ist just in the eclipse-plugin , the deplyoment on the server runs to end but the application ist not activated.
    Anyone has solved this problem?
    Thanks
    Diego

    The timeout happens every time when i deploy the ear the first time to the server and the stubs are generated and compiled.
    it is funny that last info before timeout-error 'publishing finished' comes while wls is in full action compiling the myprojEjbEntity-module.
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
    !MESSAGE Module not added:[myprojEar-TEST]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
    !MESSAGE Module not added:[myprojEar-TEST,myproj]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.091
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbAllgemein]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbEntity]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbBackoffice]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbCes]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbDisposition]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbFormulare]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbLogistik]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbPerformancetest]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbStammdaten]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.106
    !MESSAGE Module not added:[myprojEar-TEST,myprojEjbRm]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:17.200
    !MESSAGE Getting available modules on Weblogic server.
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.140
    !MESSAGE Deployment manager created @13032027
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.218
    !MESSAGE Releasing deployment manager @13032027
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.218
    !MESSAGE Total deleted modules: 0
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.281
    !MESSAGE Publishing beginning.
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:18.328
    !MESSAGE Module Status:
    -myprojEar-TEST (add) (deploy)
    --myproj (add)
    ---myprojEjbAllgemein (add)
    ----myprojEjbEntity (add)
    -----myprojEjbBackoffice (add)
    ------myprojEjbCes (add)
    -------myprojEjbDisposition (add)
    --------myprojEjbFormulare (add)
    ---------myprojEjbLogistik (add)
    ----------myprojEjbPerformancetest (add)
    -----------myprojEjbStammdaten (add)
    ------------myprojEjbRm (add)
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.282
    !MESSAGE Deployment manager created @10400586
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.314
    !MESSAGE ***dm.getAvailableModules (initModuleNameCache)
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.345
    !MESSAGE Deploying library module wls-commonslogging-bridge#[email protected]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:19.345
    !MESSAGE ***dm.distribute (deployLibrary) wls-commonslogging-bridge#[email protected]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.128
    !MESSAGE Waiting on ProgressObject:@4026405
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.738
    !MESSAGE ProgressObject completed :@4026405
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.738
    !MESSAGE ***dm.start (deployLibrary) wls-commonslogging-bridge#[email protected]
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.770
    !MESSAGE Waiting on ProgressObject:@14021095
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
    !MESSAGE ProgressObject completed :@14021095
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
    !MESSAGE Library module wls-commonslogging-bridge#[email protected] was deployed sucessfully.
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.895
    !MESSAGE ***dm.distribute (deploy) myprojEar-TEST
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:36:20.989
    !MESSAGE Waiting on ProgressObject:@26461882
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.003
    !MESSAGE ProgressObject completed :@26461882
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.035
    !MESSAGE ***dm.getAvailableModules (initModuleNameCache)
    !ENTRY com.bea.workshop.wls.core 2 3000 2007-08-14 07:41:21.097
    !MESSAGE Module myprojEar-TEST was not found on the server. Unable to perform undeploy.
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.113
    !MESSAGE Releasing deployment manager @10400586
    !ENTRY com.bea.workshop.wls.core 1 2000 2007-08-14 07:41:21.160
    !MESSAGE Publishing finished.
    !ENTRY com.bea.workshop.wls.core 4 0 2007-08-14 07:41:21.238
    !MESSAGE Module named 'myprojEar-TEST' failed to deploy.
    !SUBENTRY 1 com.bea.workshop.wls.core 4 4000 2007-08-14 07:41:21.238
    !MESSAGE Deployment operation was not completed within timeout. State Type : running; Command Type : distribute; Action Type : execute; Completed : false; Failed : false; Message : null; Exception : null

  • Log4j not logging messages out to weblogic console for custom automatplugin

    Hi,
    We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
    <category name="com.mtsa.osm.plugin">
    <priority value="debug"/>
    </category>
    Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
    //Declaration
    private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
    mthod1(){
    log.info("xyz");
    In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
    <xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
    The logger that allows printing of these lines is "com.mslv.oms.automation".
    <category name="com.mslv.oms.automation">
    <priority value="info"/>
    </category>
    These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
    <16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
    Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
    I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
    $$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    $$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
    log4j: debug attribute= "false".
    Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
    Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
    I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
    Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
    Thanks
    Edited by: user3693508 on Mar 18, 2012 11:38 AM

    Hi,
    We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
    <category name="com.mtsa.osm.plugin">
    <priority value="debug"/>
    </category>
    Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
    //Declaration
    private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
    mthod1(){
    log.info("xyz");
    In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
    <xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
    The logger that allows printing of these lines is "com.mslv.oms.automation".
    <category name="com.mslv.oms.automation">
    <priority value="info"/>
    </category>
    These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
    <16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
    Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
    I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
    $$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    $$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
    log4j: debug attribute= "false".
    Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
    Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
    I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
    Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
    Thanks
    Edited by: user3693508 on Mar 18, 2012 11:38 AM

  • HelpMac mail sends emails prematurely  while I'm still composing..sometimes it sends 4-5 email versions in various states of completion. I've got clients asking what happened, because they only get a partial email..its becoming a serious problem. Help!

    Help. Mac mail sends myemails prematurely  while I'm still composing..sometimes it sends 4-5 email versions in various states of completion. I've got clients asking what happened, because they only get a partial email..its becoming a serious problem. Help!

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ If you’re running OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Click the Clear Display icon in the toolbar. Try the action again. Post any messages that appear in the Console window – the text, please, not a screenshot.
    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

  • Can weblogic client takes empty arrays being returned.

    Hi All:
    I am using weblogic 9.2 to generate the web service client code.
    Here is my build.xml file to build the java client code:
    >
    <project name="webservices-TEST" default="client">
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    <target name="client" >
    <clientgen
         wsdl=" http://test:7035/TEST-engine/services/accumulator.wsdl"
         destDir="clientclasses"
         packageName="com.TEST.TEST2.caps.wsclient"
         >
    </clientgen>
    </target>
    </project>
    Here is my client code to test the web service.
    >
    public class testWebServicesClient
         public static void main(String[] test)
              try {
              Long recipientId = 11597997730620L;
              AccumulatorWS impl = new AccumulatorWS_Impl("http://test:7035/TEST-engine/services/accumulator.wsdl");
              IAccumulatorWS iAccWS1 = impl.getIAccumulatorWS();
              AccumulatorResponse response = iAccWS1.getCurrentAccumulators(recipientId, "", "", "", "en", "");
              System.err.println("The status is: " + response.getStatus());
              catch (Exception e) {
              e.printStackTrace();
    I get the following error:
    java.rmi.RemoteException: Illegal Capacity: -1; nested exception is:
         java.lang.IllegalArgumentException: Illegal Capacity: -1
         at com.test.wsclient.IAccumulatorWS_Stub.getCurrentAccumulators(IAccumulatorWS_Stub.java:46)
         at test.testWebServicesClient.main(testWebServicesClient.java:27)
    Caused by: java.lang.IllegalArgumentException: Illegal Capacity: -1
         at java.util.ArrayList.<init>(ArrayList.java:111)
         at com.bea.staxb.runtime.internal.util.collections.ArrayListBasedObjectAccumulator.createNewStore(ArrayListBasedObjectAccumulator.java:42)
         at com.bea.staxb.runtime.internal.util.collections.ObjectAccumulator.<init>(ObjectAccumulator.java:39)
         at com.bea.staxb.runtime.internal.util.collections.ArrayListBasedObjectAccumulator.<init>(ArrayListBasedObjectAccumulator.java:31)
         at com.bea.staxb.runtime.internal.util.collections.AccumulatorFactory.createAccumulator(AccumulatorFactory.java:37)
         at com.bea.staxb.runtime.internal.util.collections.AccumulatorFactory.createAccumulator(AccumulatorFactory.java:74)
         at com.bea.staxb.runtime.internal.SoapArrayRuntimeBindingType.createIntermediary(SoapArrayRuntimeBindingType.java:255)
         at com.bea.staxb.runtime.internal.RuntimeBindingProperty.createIntermediary(RuntimeBindingProperty.java:117)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalElementProperty(SoapUnmarshalResult.java:364)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:241)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
         at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
         at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.umarshalComplexElementWithId(SoapUnmarshalResult.java:395)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalElementProperty(SoapUnmarshalResult.java:366)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.basicExtractAndFill(SoapUnmarshalResult.java:241)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.extractAndFillElementProp(SoapUnmarshalResult.java:174)
         at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
         at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshal(AttributeUnmarshaller.java:38)
         at com.bea.staxb.runtime.internal.SoapUnmarshalResult.unmarshalBindingType(SoapUnmarshalResult.java:110)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
         at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
         at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
         at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
         at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
         at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
         at weblogic.wsee.codec.soap11.SoapDecoder.decodeReturn(SoapDecoder.java:316)
         at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:165)
         at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
         at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeOutput(CodecHandler.java:117)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:94)
         at weblogic.wsee.ws.dispatch.client.CodecHandler.handleResponse(CodecHandler.java:71)
         at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:242)
         at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:226)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:161)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:116)
         at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)
         at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:335)
         at com.test.IAccumulatorWS_Stub.getCurrentAccumulators(IAccumulatorWS_Stub.java:37)
         ... 1 more
    If I changed from
    Long recipientId = 11597997730620L;
    to
    Long recipientId = 14998712L;
    I get the error message The status is: 4.
    The group that generates the web service state that the weblogic client code is choking
    on empty arrays being returned. They say they have to return empty arrays
    instead of nulls where no data is returned.
    Is there something wrong with the weblogic tools
    or am I using it incorrectly?
    Yours,
    Frustrated.

    you'd have to check your generated code.
    If it can't handle empty arrays that would bring my trust in Bea's code down another notch (and from what I've experienced indirectly of their WS stack I wasn't all that thrilled).

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

  • 451 4.7.0 Timeout waiting for client input

    My organization is running Small Business Server 2008 with Exchange.  After installing Exchange users reported not reciveing emails from Comcast and a few other domains.  Looking at the logs, domains including gmail and comcast are unable to deliver email to our Exchange mailboxes.  They receive an error message like the following.
    Technical details of temporary failure:
    Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 451 451 4.7.0 Timeout waiting for client input (state 18).
    Other domains send just fine. Any ideas what is causing the 451 4.7.0 connection timeout error message?  The following is an example SMTPReceive log.
    2009-06-08T23:15:11.964Z,,+,,
    2009-06-08T23:15:11.964Z,,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2009-06-08T23:15:11.964Z,,"220 remote.domain.com Microsoft ESMTP MAIL Service ready at Mon, 8 Jun 2009 16:15:11 -0700",
    2009-06-08T23:15:12.027Z,,<,EHLO smtp3.mail.com,
    2009-06-08T23:15:12.027Z,,250-remote.domain.com Hello [123.12.123.123],
    2009-06-08T23:15:12.027Z,,250-SIZE 10485760,
    2009-06-08T23:15:12.027Z,,250-PIPELINING,
    2009-06-08T23:15:12.027Z,,>,250-DSN,
    2009-06-08T23:15:12.027Z,,>,250-ENHANCEDSTATUSCODES,
    2009-06-08T23:15:12.027Z,,>,250-STARTTLS,
    2009-06-08T23:15:12.027Z,,>,250-AUTH,
    2009-06-08T23:15:12.027Z,,>,250-8BITMIME,
    2009-06-08T23:15:12.027Z,,>,250-BINARYMIME,
    2009-06-08T23:15:12.027Z,,>,250 CHUNKING,
    2009-06-08T23:15:12.105Z,,<,STARTTLS,
    2009-06-08T23:15:12.105Z,,>,220 2.0.0 SMTP server ready,
    2009-06-08T23:15:12.105Z,,*,,Sending certificate
    2009-06-08T23:15:12.105Z,,*,CN=remote.domain.com,Certificate subject
    2009-06-08T23:15:12.105Z,,*,CN=ecf-DOMAINSERVER-CA,Certificate issuer name
    2009-06-08T23:15:12.105Z,,*,,Certificate serial number
    2009-06-08T23:15:12.105Z,DOMAIN\Windows SBS Internet Receive DOMAIN,,20,,*,,Certificate thumbprint
    2009-06-08T23:15:12.105Z,DOMAIN\Windows SBS Internet Receive DOMAIN,,21,,,*,remote.domain.com;domain.com;DOMAIN.local,Certificate alternate names
    2009-06-08T23:15:12.355Z,,EHLO smtp3.mail.com,
    2009-06-08T23:15:12.355Z,,250-remote.domain.com Hello [123.12.123.123],
    2009-06-08T23:15:12.355Z,,250-SIZE 10485760,
    2009-06-08T23:15:12.355Z,,250-PIPELINING,
    2009-06-08T23:15:12.355Z,,250-DSN,
    2009-06-08T23:15:12.355Z,,250-ENHANCEDSTATUSCODES,
    2009-06-08T23:15:12.355Z,,250-AUTH,
    2009-06-08T23:15:12.355Z,,250-8BITMIME,
    2009-06-08T23:15:12.355Z,,>,250-BINARYMIME,
    2009-06-08T23:15:12.355Z,,>,250 CHUNKING,
    2009-06-08T23:15:12.433Z,,<,MAIL From:<[email protected]> SIZE=52018,
    2009-06-08T23:15:12.433Z,DOMAIN\Windows SBS Internet Receive DOMAIN,,,,,,,receiving message
    2009-06-08T23:15:12.433Z,,250 2.1.0 Sender OK,
    2009-06-08T23:15:12.496Z,,RCPT To:<[email protected]>,
    2009-06-08T23:15:12.496Z,,250 2.1.5 Recipient OK,
    2009-06-08T23:15:12.496Z,,DATA,
    2009-06-08T23:15:12.496Z,,354 Start mail input; end with <CRLF>.<CRLF>,
    2009-06-08T23:15:20.277Z,,451 4.7.0 Timeout waiting for client input,
    2009-06-08T23:15:20.277Z,,,Local
    2009-06-08T23:16:03.276Z,,451 4.7.0 Timeout waiting for client input,
    2009-06-08T23:16:03.276Z,,,Local

    I had a similar issue with fortigate firewall. I could not able to resolve this issue with fortigate. Fortunately I had a Cisco PIX firewall in my stock. Eventhough it is not a best practise I have replaced the fortigate firewall with Cisco PIX mail flow
    started perfectly without any issues.
    If any fortigate experts are seeing this forum please suggest what has to be done for solving this issue.
    I have escalated this case to fortigate and they resolved the issue by executing the following commands on the fortigate firewall.
    set tcp-mss-sender1452
    set tcp-mss-receiver1452
    Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA

  • _setProperty weblogic.wsee.transport.read.timeout  in weblogic 8.1

    I need to set the timeout in the client deployed in weblogic 8.1 when making a call to a webservice.
    I have tried the following code:
    ((ManagePrepaidCardRegistrationPort_Stub) managePrepaidCardRegistrationPort)._setProperty("weblogic.wsee.transport.read.timeout","10");
    and get the following error:
    java.lang.UnsupportedOperationException: unknow property:weblogic.wsee.transport.read.timeout
         at weblogic.webservice.core.rpc.StubImpl._setProperty(StubImpl.java:146)
    How do I do set the timeout property in the client deployed on weblogic 8.1 sp4 when making a call to a webservice?
    I would appreciate any pointers?
    Cheers
    Charlie

    Hi,
    WLS 10.3 documentation
    =======================
    http://download.oracle.com/docs/cd/E13222_01/wls/docs103/webserv_ref/anttasks.html
    <taskdef name="clientgen"
    classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    once you generate client stubs you can use below options
    The below options are for timeout only for JAX-RPC Webservice clients generated from clientgen:
    import javax.xml.rpc.Stub;
    ((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
    ((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
    how are you running your client what are jar files are there in the classpath when running the client
    http://docs.oracle.com/cd/E13222_01/wls/docs103/webserv/client.html#standalone_invoke
    Regards,
    Sunil P

  • My iPhone 6plus will no longer connect to my Dodge UConnect system. Phone calls get a beep "phone call completed" message. Music will play though. Just can't make calls. Tried turning off iCloud and repairing but nothing works. It did work a few days

    My iPhone 6plus will no longer connect to my Dodge UConnect system. Phone calls get a beep "phone call completed" message. Music will play though. Just can't make calls. Tried turning off iCloud and repairing but nothing works. It did work a few days

    Hi Jpcbew,
    The article linked below provides a lot of great information and troubleshooting tips that can help you resolve the issue with your iPhone 6 Plus connecting to you car stereo system. 
    Get help using your iPhone, iPad, or iPod touch with your car stereo - Apple Support
    So long,
    -Jason

Maybe you are looking for

  • Limit Front Panel Bounds programmably

    Hi,    My front panel contains a picture control that fills the panel. I allow the user to resize the window and also apply zoom factors to it. At times, I have to limit the panel size to prevent the panel from being larger than the drawing area of t

  • How to add new "text" field in GL item fast entry?

    Hi Gurus, Is that possible to add "text" column or field in GL item fast entry. For example, if i go to Txn F-04, i enter all the details then i go to: "Goto>GL item fast entry (shift+F8). Now you will see layout (GL item fast entry). So back to my q

  • 802.1x eap-tls machine + user authentication (wired)

    Hi everybody, right now we try to authenticate the machines and users which are plugged to our switches over 802.1X eap-tls. Works just fine with windows. You plug a windows laptop to a switchport and machine authenticates over eap-tls with computer

  • How to migrate a weblogic project files into oracle 9i JDeveloper?

    Hi, I have a simple customer registration website (on top of 8.1.7 DB using oracle jdbc thin driver) as follow: It is all under c:\weblogic\myserver\public_html\jsp\ (Which is the document root) 12 html files under c:\weblogic\myserver\public_html\js

  • PDR/Repl.Workbench, Handle 2 Message Types for Materials

    Hi there, here in an existing landscape material data gets distributed to a couple of systems with the PDR tool. A custom message type ZMATMAS2 is being used and in UPSC01 the object type MAT is mapped to that ZMATMAS2. Now, I need to connect a new s