Re: Web Connection Timeout

I have a Nokia C6-01 and I have a problem when I connect to WLAN at my office. It establishes connection, but when I start browsing it hangs and I get an error message "Web: Connection time-out".
When I try connecting the same in some other phone, it works perfect. It connects to WLAN and the firewall setting appears and when the username and password is provided, it works just fine.
Could someone help me out to sort out this issue

You better check with your company IT department on permissions.
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

Similar Messages

Connection timeout error in web report(portal)

Hi Experts,
Points to note about the 500 connection timeout error
1. Error persists only in portal. query/ report works fine in RSRT and Bex Analyser.
2.As per previous discussions tried implementing SAP notes to change ICM parameter for max of 10 minutes.
However, it is said by Basis team that they can change parameter only if all the report gives the same error.
Since all the report works fine they are nt ready to change the parameter.
4. Error: Time exceeds 600seconds
5.This issue arised only after upgrading the system to 7.3. post - upgrade. this report was working fine before.
6. Even in the portal, report works fine when we use ABAP web link.
Please share your suggestions.

In the trace file there is a error message for this report "Could not find a command, masscommand or group command with alias <new task>. It is defined in group . <TaskCollectionGroup>. pls any one help me. This is for 7.31 NW portal

Web Services Connection Timeout

Hello All,
I have a web services client that runs in Tomcat. When making a web service call, I am getting the following exception:
HTTP transport error: java.net.ConnectException: A remote host did not respond within the timeout period.
at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:87)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:71)
Initially, I thought this was a tomcat problem and just to prove that it was, I added code to make a HTTPS connection to the server that is running the web service. I am able to connect and download the WSDL through the client code running on Tomcat. So this seems to be a web services client problem rather than a tomcat problem. I am using the following:
JDK = 1.3.1
OS = IBM AIX 5.2
Tomcat = 4.1.27
Web Services = 1.1
JAX RPC = 1.0.3
Any help is appreciated.
Regards,
Jeba

I am able to make HTTPS connection from the Tomcat. If is the connection time out, would that affect the straight HTTPS call also. Also this seems to work on a Windows box. The connection timeout is being received on AIX only and I am able to make HTTPS connection from within tomcat. The web service call using HTTPS is getting the connection time out error message.

Web Service Connection Timeout - Whats the default value?

Does anyone know the default value of connection timeout property in Web Service activity?
One of my web service takes longer time for processing. So just wanted to know this value for debugging.
Thanks,
Nith

Hi Dexter,
In your case, we can try to increasing the size of the connection pool to resolve the issue. By default, the Max Pool Size is 100. You can refer to the similar issue below:
http://social.msdn.microsoft.com/Forums/en-US/c57c0432-c27b-45ab-81ca-b2df76c911ef/timeout-expired-the-timeout-period-elapsed-prior-to-obtaining-a-connection-from-the-pool?forum=adodotnetdataproviders
Since the issue is related with ADO.NET. I suggestion you post the question in the following forum:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=adodotnetdataproviders
It is appropriate and more experts will assist you.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Web Service connection timeout

How to configure the web service connection timeout properties (eg. weblogic.wsee.transport.connection.timeout) in configuration files rather setting them at client's stub code?
Help is appreciated.

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

Connection timeout in web service calls

Hi,
We have a clustered weblogic 10gR3 environment where two nodes are for ILOG rule engine, two nodes for Oracle BPM engine and four nodes for Oracle BPM workspace. All the webserices calls are SOAP over HTTP. All the webservices to rule engine and DBAdapter are hosted on Oracle Service Bus. Some of the webservice calls when invoked throw a connection timeout exception. Can any one help on how to debug this or the possible causes for this scenario? The same webservice call when invoked or retried after a few minutes is working fine. Below is the stack trace:
Stacktrace: java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
     at org.apache.axis.client.Call.invoke(Call.java:2748)
     at org.apache.axis.client.Call.invoke(Call.java:2424)
     at org.apache.axis.client.Call.invoke(Call.java:2347)
     at org.apache.axis.client.Call.invoke(Call.java:1804)
     at fuego.soaptype.SoapCall.invoke(SoapCall.java:234)
     at fuego.soaptype.SoapObject.invoke(SoapObject.java:309)
     at fuego.lang.Invokeable.invokeImpl(Invokeable.java:234)
     at fuego.lang.Invokeable.invokeDynamic(Invokeable.java:188)
     at xobject.EDP.EDP.EDPObject.helpBusinessRules(EDPObject.xcdl:59)
     at oracle.EDPPROCESS.Default_6_6.Instance.CIL_checkRTDIInformation(Instance.xcdl:12)
     at oracle.EDPPROCESS.Default_6_6.Instance.CIL_checkRTDIInformation(Instance.xcdl)
     at sun.reflect.GeneratedMethodAccessor7653.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1083)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1278)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:126)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:84)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:261)
     at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:223)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:209)
     at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:120)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
     at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
     at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

EJP, thanks for confirming that the generated code is incorrect and that the finally block should be used.
Jschell, thanks for the suggestions and the trust in my technical skills... though writing my own generator seems a bit of too great enterprise for me haha!
The generator is not open source so I cannot modify it and using another one is not an option as it is the "standard" in the company.
In the end I decided for writing a post processor (in the form of a JDeveloper extension) to fix the code after it is generated. I will also probably be filing a bug for it with Oracle.
Cheers,
Luis

Network Connection Timeout when "Chkng for available downloads" from iTunes

I have been struggling with this problem for weeks and have spent a significant amount of time trying to diagnose and fix without success.
When I select “Check for Available Downloads” through iTunes, I receive a “Network Connection Timeout” message and iTunes fails to download any information. It does ask me to validate my access with a password before it fails.
This problem initially occurred after I purchased the iTunes Plus updates for my music library. It backlogged about 70 updates that are now sitting in the queue to be downloaded to my local iTunes library. However, since I made that purchase, I have not successfully been able to do any downloads from the iTunes store. I suspect that the volume of items in the queue is related to the problem (as a trigger or the cause).
I have also tried to buy a single song. Although the purchase is successful (it charges my card and adds the song to the download queue), it doesn’t successfully download the song. I cannot, at this time, even get to a point where I can display a list of the queue for download. It always fails when trying to access that available download queue.
Podcast downloads still work fine through iTunes. I have never had problems with the store before and have done very large downloads (e.g. audio books) in the past. I have had no changes to my configuration leading up to this problem.
I am running a relatively new computer with a clean install of Windows 7, plenty of memory and very fast processors. I’ve got high capacity DSL. The connection is wired from the router into my network card (not wireless).
I have tried a number of things as noted below and the problem still occurs:
1. Confirmed access to internet, and ability to download from other web sites without timeout
2. Confirmed my ability to access the iTunes store, change my personal information, browse songs
3. Confirmed ability to download podcasts
4. Deactivated my windows firewall, antivirus and Net nanny content protection.
5. Deactivated the router firewall, and placed my PC in the DMZ of the router (which means that it should be wide open to the external network).
6. Swapped out the DSL modem for a different DSL modem and completely removed the router from the configuration.
7. Checked my drivers on the network card and made sure they are up to date.
8. Ran Windows 7 network diagnostics – no problems detected
9. Ran iTunes network diagnostics – no problems detected
10. Uninstalled all software related to iTunes and reinstalled most current versions (iTunes, Quicktime, Bonjur, etc.)
Thoughts?

have the same problem...still waiting
http://waugh.cchem.berkeley.edu/licence/faq/13/map.html
http://waugh.cchem.berkeley.edu/licence/faq/14/map.html
http://waugh.cchem.berkeley.edu/licence/faq/15/map.html
http://waugh.cchem.berkeley.edu/licence/faq/16/map.html
http://waugh.cchem.berkeley.edu/licence/faq/17/map.html
http://waugh.cchem.berkeley.edu/licence/faq/18/map.html
http://waugh.cchem.berkeley.edu/licence/faq/13/index.html
http://waugh.cchem.berkeley.edu/licence/faq/14/index.html
http://waugh.cchem.berkeley.edu/licence/faq/15/index.html
http://waugh.cchem.berkeley.edu/licence/faq/16/index.html
http://waugh.cchem.berkeley.edu/licence/faq/17/index.html
http://waugh.cchem.berkeley.edu/licence/faq/18/index.html

Webservice Connection Timeout Error in Sun Java System Application server

I have a java code to connect to Ebay Shopping Webservice that uses the client stub generated through Axis. The code works fine when I run it from the main method of a stand alone Java application. Which means there is no issue with the Proxy settings or any other network setting that could block the webservice from my system. However when I use the same code inside a JSF based Web Application, a connection timeout error comes up. The Web application is deployed on the Sun Java System Application server. The stacktrace of the exception is
java.net.ConnectException: Connection timed out: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527)
     at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
     at java.net.Socket.connect(Socket.java:520)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:125)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.ebay.api.soap.ShoppingBindingStub.findProducts(ShoppingBindingStub.java:1217)
     at com.shopping.ebay.EbayServiceUtility.performEBaySearch(EbayServiceUtility.java:66)
     at searchProduct.SearchProductBean.search(SearchProductBean.java:98)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:151)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96)
     at javax.faces.component.UICommand.broadcast(UICommand.java:383)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:450)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:759)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
The JDK version on my machine is 1.5.0_14. Can somebody point me as where I should be looking for errors?

You need to delete all the files under the 'generated' directory to force the server to recompile them after the JDK upgrade. Also check in domain.xml and make sure the JVM parameter is pointing to the JDK that you have installed. It is also worthwhile to check asenv.conf to see which JDK that file is pointing to as well.

Tomcat 4.1:connection timeout error

Hi. I got a HTML form that allows a user to enter freehand SQL statements and send them to an DB2 database via a SQL Java servlet. After the query executes, it returns an Excel file containing the resultset of my query. Unfortunately, I got a query that when executed, my browser returns "The page could not be found..." due to connection timeout. With another query with different set of criteria, it runs fine-so my Tomcat is running fine. I've executed the same exact query in Excel via JDBC-ODBC bridge Java application and it ran fine and also executed the same query in QMF for Windows, and it ran fine also. So this lends me to believe I need to configure my Tomcat somehow, I presume the connection timeout limit.
Is there a way to remove or increase the connection timeout limit?
Thanks in advance.

Arrrggg!!! That didn't work. Here's the error message:
"The page cannot be displayed There is a problem with the page you are trying to reach and it cannot be displayed.
Please try the following:
Click the Refresh <javascript:location.reload()> button, or try again later.
Open the home page, and then look for links to the information you want.
If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the home page.
10060 - Connection timeout
Internet Security and Acceleration Server
Technical Information (for support personnel)
Background:
The gateway could not receive a timely response from the Web site you are trying to access. This might indicate that the network is congested, or that the Web site is experiencing technical difficulties.
ISA Server: MMPINF17
Via:
Time: 1/27/2003 1:04:11 PM GMT"
Does this mean my company's firewall administrator has set a connection timeout limit? Or is it still my Tomcat's configuration?

500 CONNECTION TIMEOUT ERROR

Hi Experts,
When try to test the url for c project I am getting this error.
Is there any way to change the connection time out.
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Tue Apr 29 14:19:08 2008
Module: icxxthr.c
Line: 2698
Server: m576_IDS_00
Error Tag: {-}
Detail: Connection to partner timed out after 60s
please guide me step step procedure I am functional consultant .
I found that it will be change in T CODE :RZ10
BUT IN THAT what parameter I NEED TO CHANGE PLEASE GUIDE ME
full points will be reward for help help full answer.
thanks
sunil jawalkar

Hi Sunil,
If you are using this particular cProjects URL for the first time, you should generate the screens using SGEN transaction. Select Web Dynpro for ABAP and give the cProjects application.
Having done SGEN, the page wouldnt take long to open up.
To increase the connection timeout, pl contact your basis guy.
Regards,
Reema.
Edited by: Reema Shahbazkar on Apr 29, 2008 6:05 PM

Set connection timeout in LightSwitch HTML

Hi.
I am creating Lightswitch HTML application and implementing export functionality using ServerApplicationContext.
I am trying to export a lot of data and i when i call for DB objects I get connection error. I have tried to set ;Connection Timeout=300 in connection string in web.config but it seams like not functioning, and still failing after 30sec.
Can you please guide me where can I set a connection timeout in order to change it's default value from 30 sec to something bigger?

Igor,
I think what you are looking for is "CommandTimeout" and not connection timeout. The connection timeout is how long the SQL Client will wait while establishing a connection. A command timeout is how long the SQL Client will wait for a command to complete.
So if you are executing a long running command, you will run into command timeout issues.
In order to set the command timeout for your SQL data source, add a "key" to your web.config's <appSettings> node of the following form:
<appSettings>
<add key="DataSourceName_CommandTimeout" value="60" />
</appSettings>
Replace DataSourceName with the name of your data source. So if you are using the ApplicationData data source, the key would be named "ApplicationData_CommandTimeout". Look in your Solution Explorer under "Data Sources" for the name of your
data source.
The value is the number in seconds for the timeout.
Eric
http://blogs.msdn.com/b/eric_erhardt/

How to handle a Connection Timeout

Hi Everybody,
My situation is as follows: I have a web application, some sort of content management system. I'm using MySQL to store information. The application is obtaining Connection objects via a Connection Pool. I'm runngin Sun Java Application Server 8 Update 1 and MySQL 4.1.9 on a Windows 2003 Server machine.
After 8 hours of inactivity, the system it's raising an exception. Searching the log, I've found the cause, an SQL Exception with a "recv failed" error. Google said that MySQL shuts the idle connections after 8 hours, and also found a code to correctly handling that disconnection. The thing is that the Application Server is handling the connection pool to physically connect with the database, I'm not dealing with connection setup. I've tried setting autoReconnect and autoReconnectForPools properties (in the management console) without success.
Anyone has any idea to correct this?
Thanks in advance for your time.
Best regards
Antonio Varela.

You could execute a query from time to time, but you can't control which connection is being used. For example, you could be accessing the same connection all the time, and in the end only one functioning connection would remain in the pool.
As said in another thread,
The problem (in detail) is how the MySQL JDBC driver operates. The physical connection to the database can fail, but the Connection.isClosed() method will still return false.
So, there seems to be some problem with the MySQL driver.
But even in this case, the "connection validation" options should work on the application server, which they just don't. I am inclined to blame this problem on the connection pool implementation.
The only "solution" I found so far was to set larger connection timeouts on the MySQL server:
interactive_timeout = 2764800
wait_timeout = 2764800

Database connectivity timeout problem

I am using struts framework for my web application and in between just for a test I have used spring framework database connectivity too in few files. I have deployed my application on tomcat 5.5 server on linux machine. Application is running fine, but sometimes this application shutdown by itself and I have to restart tomcat again (like 3-4 times a month). I wan to run this application continuously. I am getting this error in my log files
1 Error: DAO.SpringInformDAO[ERROR](SpringInformDAO.java:loadTypelessNameIDListProduct:246)org.springframework.dao.DataAccessResourceFailureException: StatementCallback;
2.Caused by: com.mysql.jdbc.CommunicationsException: The last packet successfully received from the server was40524 seconds ago.The last packet sent successfully to the server was 40524 seconds ago, which is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
3. Caused by: java.net.SocketException: Broken pipe
Does someone has any idea how to solve this problem?? It would be great help
Thanks

mantoo wrote:
Thanks for reply. Ok let me explain again, may I was using wrong words. Actually, my web application stops automatically after few hours, I don't know know what is the reason, whether it is tomcat or sql sever. What I concluded from various Google search that it might be because of sql server waiting time and connection ideal time difference does not match. By default SQL server's wait_time is 8 hours, so after that this errors occurs. For dealing this I put following attributes in my resource tag in context.xml.
(testWhileIdle="true" timeBetweenEvictionRunsMillis="10000" minEvictableIdleTimeMillis = "60000" )
After doing this I am not getting those errors which I have written in my previous post, but now it is showing this :
ERROR: transport error 202: handshake failed - received >GET http://www< - excepted >JDWP-Handshake< ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal errorListening for transport dt_socket at address: 8000So the real problem is that tomcat is exiting. It isn't crashing, just exiting.
Database problems would not cause that. Excluding the possibility that the driver is calling System.exit() - in which case you would be using a non-standard driver.
Other reasons for application exit.
1. Your code, or some library that you use is calling System.exit().
2. Your JNI code or some library that uses JNI code has a library in C/C++ that is calling the OS application exit in that code.
3. Tomcat probably has some API that allows you to stop it - some place the java code is calling it
4. Some other process outside of tomcat is terminating the application.
Greping can potentially eliminate some of the possibilities above.
As for 4 you can analyze the shutdown time to determine if it shuts down at the same time or after the same amount of time.

OAS 10.1 3.1 0 OC4J JDBC Connection/Timeout settings

I am fairly new to OAS, and am trying to resolve a intermitent issue,
I have an OAS 10.1.3.1.0 with a deployed EAR file I was provided by a supplier containing mainly PL/SQL based logic, which configured the OAS to ask a middle tier for a an external to pass data to it via Stored Procedure and then usiing the deployed package connect to an external Oracle DB and insert the data.
Oas is running on a Windows 2003 platform that has no problems or connectivity problems, how ever intermittenlt the OAS stops uploading data to the external Oracle DB. Some custom external logging details this as a communication at the time it occurs, how ever there are no comms issues. A quick restart of the OAS windows service resolves the issue.
Apart from upgrading OAS to patch set 5, the only other thing I considered could be causing the issue is how OAS is handling the session timeout or connection pool.
I can see the following settings for the JDBC connection I am using, I wondered if anyone could advise anything that could be changed? I am not sure the implications on setting the validate connection to True and also not sure why maximum number of connections is set to -1?
Connections
Initial size of Connection Cache
Minimum Number of Connections
Maximum Number of Connections
Connection Retry Interval (seconds)
Maximum Connection Attempts
Maximum Number of Statements Cached
Lower Threshold Limit On Pool (%)
Defaults to 20% of max connections.
Validate Connection FalseTrue
Timeouts
Inactivity Timeout (seconds)
Time that an unused connection is inactive before it is removed from the pool.
Wait For Used Connection Timeout (seconds)
Maximum time to wait for a used connection to be released.
Max Active Time for a Used Connection (seconds)
Maximum time a used connection may be active.
Abandoned Connection Timeout (seconds)
Enforce Timeout Limits Interval (seconds)
Any help would be appreciated

Hi,
Along with Priya's suggestions, please refer the link below for the details on the parameters.
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/datasrc.htm#CHDCFCHB
Hope this will help understand all the parameters.
Also refer,
What Should Be My Maximum Connection Pool Size? [ID 1061155.1]
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
Regards,
Mithun

Handle WSDL data connection timeout during PDF generation

I have created in LiveCycle Designer XDP template. In template i defined WSDL Data connection. For data loading i call xfa.connectionSet.WsDataConnection.execute(0).
For PDF generation i created LiveCylce process and use generatePDFOutput component.
If WebService works output service generates document with all data - OK.
If i turn off webservice and run process ouputservice generates PDF document with empty fields. Is where any possibility to raise execption to calling process if WSDL connection timeouts or gives SOAP fault error in response?
I want catch web service errors in process and do not generate PDF if some webservice used in PDF template is not accesible during generation.

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

Re: Web Connection Timeout

Similar Messages

Maybe you are looking for