Browser connection(request) time out with the Tomcat server after 1 hour

Hi,
I made a servlet request from IE to tomcat server but exactly after 1 hr the browser is showing page can' be fount error even though the request is being executed in Tomcat. Before the server sends the response to browser it is showing page can't found. I tried with the tag <session-timeout> in web.xml and
connectiontimout in server.xml.Also i tried by adding registry variable 'KeepAliveTimeout' to internetsettings using regedi, but there is no use.Can sombody help me out of this problem.
thanks inadvance

Hi,
well - openDoc can also be used on IIS or Java AS. Where do you use openDoc ?
Check the parameters from the bost above mine. You should also check SAP Note - 1413774
https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3134313337373426
and SAP Note - 1198539
https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3131393835333926
Regards
-Seb.

Similar Messages

  • JMX Connectivity has been discontinued with the managed server

    Dear all,
    I am getting following msg in my weblogic 11g manage server and admin server.
    Namage Server Log
    ####<Nov 22, 2010 2:15:39 PM IST> <Warning> <Log Management> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415539687> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    Admin Server Log
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <JMX> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-149507> <JMX Connectivity has been discontinued with the managed server NewTradeServer.>
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-002634> <The server "NewTradeServer" disconnected from this server.>
    ####<Nov 22, 2010 2:51:32 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417692374> <BEA-002635> <The server "NewTradeServer" connected to this server.>
    During this time my admin server in running, i can able to loggin to admin server console,
    Problem which i am faceing is that, i am not able to see the server status of that particular
    manage server, i am not able to see the any sub tabs statistic in Monitoring TAB of manage server, and after 1/2 and hours the manage server stop responding, then i restart the manage server and after that every thing work fine..
    any one have the solution for this error????///
    Regds
    Amar Shaw

    Kindly fing the log for the server problem time.
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.177.97.179:21,557 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.206.128.110:1,069 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 203.123.173.169:50,920 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.180.84.228:50,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,297 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.166.48.41:21,631 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.22.34.38:39,481 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 113.193.25.104:52,294 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.122:18,934 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.241.80.244:24,575 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 196.15.16.20:38,791 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 202.65.136.252:4,055 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,777 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 110.227.109.138:64,362 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.223.187:1,046 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 114.30.77.228:50,110 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.164.238.6:1,935 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 192.20.251.68:41,430 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 195.189.142.85:51,932 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:3,974 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 82.178.3.115:11,545 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.21.153.192:7,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.177.2.33:50,437 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.201.90.244:5,725 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 220.227.95.145:17,067 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.248.137.70:33,786 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:6,260 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.55.98:6,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.162.145.253:1,603 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,443 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,298 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 121.243.135.163:2,342 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,451 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 204.194.141.28:15,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.215.198.169:2,108 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:40,204 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,044 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.241.82.55:50,090 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.134.134:1,079 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.162.69.77:4,185 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:60,708 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 121.245.188.43:1,262 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 125.17.188.19:45,490 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.165.58.249:49,239 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.17.215.126:4,085 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 124.125.27.11:2,992 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:7,639 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.246.47.199:2,426 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.169.70.18:14,392 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:42,408 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.197.237.98:51,852 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.163.89.69:64,984 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 192.20.246.168:13,547 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:37,198 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:39,842 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,450 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.90.72.203:3,972 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:58,671 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,043 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.163.163.25:1,957 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 115.240.50.203:1,059 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.197.42.2:34,187 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.124.135.246:21,650 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 93.186.23.240:11,235 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.133:4,215 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.161.99.67:20,466 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <WebLogicServer> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576578> <BEA-000000> <WebLogic Server "NewTradeServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Notice> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576703> <BEA-170019> <The server log file D:\BEA11G\user_projects\domains\IndiabullsWLS\servers\NewTradeServer\logs\NewTrade_%yyyy%_%MM%_%dd%_%hh%_%mm%.log is opened. All server side log events will be written to this file.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576718> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Diagnostics> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576812> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "http" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "https" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:80
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576968> <BEA-002609> <Channel Service initialized.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576999> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000436> <Allocating 4 reader threads.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000446> <Native IO Enabled.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <IIOP> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577281> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578718> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578796> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_KNcrxQIcWPsGUMqWWNL3mWV+Tkc=>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579203> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579390> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Securit

  • My Macbook disconnect with the vpn server after 1-2minutes inactivity

    My Macbook disconnect with the vpn server after 1-2minutes inactivity. Why ? I would like maybe 5 minutes later some date download from this vpn server .

    I hope this will help ..
    setting the following on the VPN custom connection:
    a) "lifetime time 24 hours;" or more
    b) dpd_delay 0;
    c) proposal_check claim;

  • Cannot connect to Time Machine with the Mail app open

    This is the first time that I have tried to use TM since upgrading to Lion. I have a MBP with a Time Capsule with my TM backups on it. I want to retrieve some emails that got deleted. Prior to Lion if I had Mail open then TM would know that that is the app I needed to restore some files to. But with Lion I can't figure out how to get a few emails out of TM. TC is wirelessly connected to my MBP. Thanks for any help, Judy

    Connect the external drive and try using Finder to locate those files.  'Users'' is a high level folder you will want to drill down into for pictures and stuff. 
    Least, my system works this way.

  • Request time out with opendocument

    Hello,
    our system is BO XI 3.1 SP2 on Windows 2008 x64 with MS sql server 2005 SP3 x64.
    We're running a huge report from .net opendocument and we get the following error:
    An error has occurred:Request timed out.
    What can I do?
    thank you

    Hi,
    well - openDoc can also be used on IIS or Java AS. Where do you use openDoc ?
    Check the parameters from the bost above mine. You should also check SAP Note - 1413774
    https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3134313337373426
    and SAP Note - 1198539
    https://websmp130.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3131393835333926
    Regards
    -Seb.

  • Time-out on the Answers server to be increased

    The Current situation is User is running a query, it takes sometime to to fetch the results and after sometime the request errors out saying that Query time out.
    Though the session remains active.
    Is there any paramter in instanceconfig to increase the time the user would be able to run the query.

    User,
    Refer this
    http://oracleintelligence.blogspot.com/2008/08/obiee-time-to-expire-for-idle.html
    thanks,
    Saichand.v

  • No conection with the mail server after update to 10.4.7

    I'm already loosing my head!!
    I've updated to 10.4.7 and after appeared a dialog box message. link of the message in portuguese (http://rapidshare.de/files/26407351/mail.tiff.html)
    In english it means: Mail have beed updated. Do you want allow that the new version access the same items of keys (as password) that the old version?
    -This change is permanent and efects all the items of keys used by mail.
    *Aply *don't aply
    So after this my mail loosed the connection with any server, I can't connect any account with the mail, but using Thunderbird it work okay.
    Somebody help me!!
    Thanks in advance.

    Don't panic, or you'll end up making things worse (if you haven't already).
    The Mac OS X 10.4.7 Update has introduced connection issues as a result of (according to the documentation) "Mail now supports connecting to mail servers through a SOCKS proxy". If that's the problem, you must go to System Preferences > Network and disable the SOCKS Proxy in the network configuration used to connect to the Internet, if it's enabled.

  • Remote Desktop Connection Times Out With "Can't Connect" From One Specific Computer Only

    This is an odd one... I manage several servers from this computer. This particular server, 2012 Essentials, won't allow for remote desktop connections to either the server or attached workstations. I can get into the server's remote web page but when I
    attempt a remote desktop connection, it hangs on "Initiating remote connection..." and then times out with the error response that remote desktop can't connect. But... if I attempt the same connections from any other computer, I am able to get in
    and utilize remote desktop. Does this mean that there is a certificate issue with the computer unable to connect and if so, how does one remedy this? Or is it some other issue? I've attempted everything within my technical ability to no avail. Any suggestions
    are greatly appreciated.

    Hi,
    Before going further, would you please let me know the RDC version that used in the problematic computer? Was it the same with other computers?
    Please temporarily disable firewall and then check if this issue can be solved. Based on your current description, it’s hard to say the root reason of this issue.
    So, I suggest that you should check relevant log files and get some clues. It will help us to narrow down and solve your issue.
    Hope this helps.
    Best regards,
    Justin Gu

  • I want to use hibernate with the tomcat

    I want to use hibernate with the tomcat server can it be possible and if yes then what is the stepwise way.
    Infact I know the java JSF but want to command on Hibernate plz help me.
    I'll be thankful to you.

    To be honest, I wouldn't even know where to start. Do you know what Hibernate does and how it works? Do you know how Tomcat works? All you'd need to do to combine those two would be to let Tomcat provide the DB connections for Hibernate, I suppose. Neither of those products are a topic of this board though.

  • Tried to reinstall OSX Mountain Lion 10.8.4 and every time i start with the installation i get a requested time out message, had to shut down my MacBook Pro retina. Now when i start up it automatically start internet recovery

    tried to reinstall OSX Mountain Lion 10.8.4 and every time i start with the installation i get a requested time out message, had to shut down my MacBook Pro retina. Now when i start up it automatically start internet recovery for two ouers. After the internet recovery the same problem with reinstalling OSX message

    Gave up on the GUI.  This script derived from http://blog.netnerds.net/2012/07/os-x-how-to-setup-nat-on-lion-and-mountain-lion / seems to work for me:
    gwdev=en0 # This is my WiFi connection (has Internet connection)
    targetdev=en1 # This is the USB to Ethernet adapter (to give Internet connection)
    /sbin/ifconfig $targetdev down
    /sbin/ifconfig bridge0 create
    /sbin/ifconfig bridge0 up
    /sbin/ifconfig bridge0 addm $gwdev
    /sbin/ifconfig bridge0 $HOST_ADDR
    /sbin/route add default -interface bridge0 -ifscope bridge0 -cloning
    /usr/sbin/sysctl -w net.inet.ip.forwarding=1
    /sbin/ipfw add 100 divert natd ip from any to any via $gwdev
    /usr/sbin/natd -interface $gwdev -use_sockets -same_ports -unregistered_only -dynamic -clamp_mss -enable_natportmap -natportmap_interface $targetdev

  • When I click on Web mail I get "The connection has time out

    When I click on "Web Mail" from Glossbrenner United Methodist Church web page, it won't log on to my email page. I keep getting - The connection has time out
    The server at 74.220.207.173 is taking too long to respond.
    The site could be temporarily unavailable or too busy....
    If you are unable to load any pages, check you computers' network connection.
    If your computer or network is protected by a firewall.....

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    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.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Ifou don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the Console window, select
              DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar.
    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
    If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
    Please don’t post other kinds of diagnostic report.
    I know the report is long, maybe several hundred lines. Please post all of it anyway.

  • 504 PROXY TIME OUT. The connection time out

    Hi
    one of our users is facing  504 proxy time out. The connection time out 
    using our ITS link.  what would be the possible solutions to reduce this kind of error.  
    Regards 
    MA.Sreenivasan

    Hello,
    If only a particular user is facing this problem, check with the user on what she/he is doing.
    if everyone is facing, have a look at ITS timeout parameters.
    ~rfcTimeOut
    ~userTimeout
    Regards,
    Siddhesh

  • I have attempted to update my software over 10 times but I get a network connection error. Anyone with the same problem? Got it on the wireless and wired network.

    I have attempted to update my software over 10 times but I get a network connection error. Anyone with the same problem? Got it on the wireless and wired network.

    Disable all Firewalls & Anti-Virus software...try again.

  • The connection has timed out with certain sites on all browsers

    When I type in google.ca or bing.com in my address bar, it says " The connection has timed out. The server at bing.com is taking too long to respond." i have done may virus scans and that has not worked. This happens in all brosers and i am using windows XP. I am mainly using FireFox 3.6. My friends can access the sites and seem like i am the only one with the problem.
    == URL of affected sites ==
    http://bing.com
    == User Agent ==
    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefo8769 79680741803 (.NET CLR 3.5.30729)

    Only on some sites.
    Really weird thing is, Internet Explorer works FINE!!!

  • Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

    Fresh installation of Exchange Server 2013 on Windows Server 2012.
    Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
    your folders with your Outlook data file (.ost)" is displayed.
    If I turn off cached Exchange mode, setting the email account to not
    cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
    time.
    I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
    Microsoft Exchange RPC Client Access service is running.
    No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
    Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

    So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
    Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
    First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
    Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
    This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
    work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
    In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
    up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
    like OutlookAnywhere - which I might add had their place under that scenario.
    In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
    previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
    EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
    So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
    but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
    users.
    Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
    Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
    certificate.
    See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
    So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
    Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
    always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
    This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
    there is a 3rd - I forgot, but you get the idea).
    Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
    the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
    Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
    NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
    Open Outlook - BOOM! It works... Was it as good for you as it was for me?
    You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
    and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
    So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
    Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
    So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
    SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
    Frustrating beyond reason - that should be Exchange's new slogan...
    Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
    PS
    ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

Maybe you are looking for