Liferay Counter Service database connection timeout

Hello,
We are using OEID 2.4 version , the issue is that database connection between studio and the liferay db (SQL Server) was dropped when the SQL Server database is restarted or bounced . After then, users cannot login to Endeca studio application. To resolve the issue we are manually bouncing the Studio to re-establish the connection. Is there any workaround to fix this issue.
Please could you give your suggestions as early as possible, we are looking for the solution urgently. Any help is highly appreciated.
Thanks,
Laxmana

Please open a support request and quote bug number 18518702.

Similar Messages

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.

Database connection timeout

We have successfully developed reports in CR XI and have been testing these reports on our website. All the tests had been going great until we realized that if the server was down we received a timeout error and then a connection information box asking for the connection information i.e. Server, User Id, Password, Database etc.. We obviously do not want our customers to see this information.
My question is, what can we do to prevent them from seeing this information when the connection to the database server is not online? Our first thoughts where to do something in the report to simulate a request for something with no data. That doesnt seem to work. Any ideas would be helpful.
We are using a OLE DB (ADO) connection.

Hi Tom
Set the "Connect Timeout" property a larger value, or just set it to 0, which means no limit for timeout. This property is available while creating report and also in the Set Data Source Location you can edit the Connect timeout.
Hope this helps!
Thanks

Database connectivity timeout

Hello,
   I'm using the database connectivity toolkit to connect to a MySQL database. If the database isn't there or there is a mistake in an SQL query after I have connected my program takes 15s (the default) to realise. I've tried wiring different values to the connection timeout node but this doesn't seem to make any difference whatsoever. I've hacked the first problem by pinging the machine with the DB on before trying to connect as suggested in another post, but this doesn't help if I screw up my INSERT syntax... any ideas what could be wrong?
       Cheers,
              Tim

Hi Tim,
You should be able to use the command timeout (s) parameter of the DB Tools Set Properties VI of the Database Connectivity Toolkit to set the maximum time to wait for a command to execute, in seconds.
Regards,
Imtiaz Chowdhury
Head of Digital Technologies
Brand786

Database connection timeouts and datasource errors

Connections in the pool randomly die overnight. Stack traces show that for some reason, the evermind driver is being used even though the MySql connection pool is specified.
Also, the evermind connection pool is saying connections aren't being closed, and the stack trace shows they're being allocated by entity beans that are definitely not left hanging around.
Sometimes we get non-serializable errors when trying to retrieve the datasource (this is only after the other errors start). Some connections returned from the pool are still good, so the application limps along.
EJBs and DAOs both use jdbc/SQLServerDSCore.
Has anyone seen this problem?
<data-sources>
     <data-source
          class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
          name="SQLServerDSCore"
          location="jdbc/SQLServerDSCore"
          xa-location="jdbc/xa/SQLServerXACore"
          ejb-location="jdbc/SQLServerDSCore"
          connection-driver="com.mysql.jdbc.Driver"
          min-connections="5"
          username="xxx"
          password="xxx"
          staleness-timeout="3600"
          alive-poll-query="SELECT 1 FROM medispan"
          url="jdbc:mysql://1.2.3.4:3306/dbo?autoReconnect=true&autoReconnectForPools=true&cachePrepStmts=true&is-connection-validation-required=true"
          inactivity-timeout="30"
     >
          <property name="autoReconnect" value="true"/>
          <property name="autoReconnectForPools" value="true"/>
          <property name="is-connection-validation-required" value="true"/>
          <property name="cachePrepStmts" value="true"/>
     </data-source>
</data-sources>

Rick,
OC4J 9.0.4.0.0 - BTW, do you know of any patches?As far as I know, there are no patches for the 9.0.4
production version of OC4J stand-alone.
I'm using container managed persistence,It was not clear to me, from your previous post, that you
are using CMP entity beans.
I found staleness-timeout and alive-poll-query
somewhere on a website when trying to track this
down. Here's four sources:Those sources refer to OrionServer -- and an older version, too, it seems.
Like all other Oracle products that start out as somebody
else's -- including, for example, JBuilder (that became "JDeveloper"), Apache Web Server (that became "Oracle HTTP Server") and TopLink -- their development paths diverge, until, eventually, there is absolutely no similarity between them at all. Hence, the latest versions of OC4J and "OrionServer" are so different, that you cannot be sure that something that works for "OrionServer" will work for OC4J.
I recall reading something, somewhere, sometime about configuring OC4J to use different databases (other than Oracle), but I really don't remember any details (since it was not relevant to me, because we only use Oracle database). In any case, it is possible to use a non-Oracle database with OC4J.
Good Luck,
Avi.

Connection Timeout Expired in Windows Event Logs

I just recently installed SharePoint 2013 SP1 on a Windows Server 2008 R2 SP1 server and have been receiving this error message in the Windows Event logs:
Cannot connect to SQL Server. <database server name> not found. Additional error information from SQL Server is included below.
Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create
multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=12; handshake=6; [Login] initialization=0; authentication=0; [Post-Login] complete=14000;
I have never seen this error message before in my life on any prior installation of SharePoint that I have ever done. It is only occurring on this one particular installation of SharePoint. The environment is corporate built, so I have no idea
as to how to troubleshoot or determine the root cause of this error message.
I looked at the value of the database-connection-timeout in stsadm and it gets back a value of 15, however, I am unable to alter the database connection timeout using stsadm since I either get an "Object reference not sent to an instance of an object"
error message or "This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database. To connect this server to the server farm, use the SharePoint
Products Configuration Wizard, located on the Start menu in Microsoft SharePoint 2010 Products."
Please advise.

What is specification of your SQL server? i think its more CPU, RAM, I/O issue with SQL server.
under which account you are running the stsadm command?
check this one
http://stackoverflow.com/questions/21230927/sql-azure-the-timeout-period-elapsed-during-the-post-login-phase
may be you fall in this bug
http://connect.microsoft.com/VisualStudio/feedback/details/821803/connection-timeout-expired-the-timeout-period-elapsed-during-the-post-login-phase
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Shared Services database content not found in the specified database - EPM

I installed three VM machines (Workstation) for the following on Windows 2003 OS:
VM1 : Oragle DB 11g, Shared Services. Workspace
VM2 : Financial Management, EPMA, Calc Manager
VM3 : Microsoft Active Directory
I have configured Database and Shared services successfully and all machines talk to one another.
Also, I created the appropriate table spaces for the Hyperion products with the right access on the database. And, I am able to connect from the client (VM 2 to the Database VM 1)using SQLplus.
When I tried to configure Financial Management, using the EPM System Configurator and put in the following values:
Database Type: Oracle
Server: VMDatabase (Name of VM1)
Port: 1521
SID ORCL
Username: HFM
password: *********
It returned the error message: "*Shared Services database content not found in the specified database*"
Can someone please help on what I need to check, Please!?
Thanks for your time.
K

Hi,
Information from Oracle Support:
Shared Services database content not found in specified database
Cause
There is a flag in the shared services repository that indicates the shared services database is to be used as a registry. If that flag is not set, the configtool will not re-configure the database as a shared services repository.
Solution
Note: Make sure the Shared Services repository is backed up before doing any Shared Services Registry changes.
The registry flag isRegistryDB must exist and be set to true on the Shared Services Database Connection.
epmsys_registry.bat VIEW DATABASE_CONN
Find the shared services database registry entry. The entry in bold will be missing. The italicized item is the 'unique_id' referenced later (different in each installation).
COMPONENT - 3
NAME - Database:ORCL:HSS
ID - +11d1def534ea1be07ad8eb3012d2e3d310a7ff4+
TYPE - DATABASE_CONN
HOST - Database
HYPERION HOME - /home/hypadmin/Oracle/Middleware/EPMSystem11R1
PROPERTIES -
isRegistryDB = true
dbUserName = HSS
dbJDBCDriverProperty = oracle.jdbc.OracleDriver
dbJdbcUrl = jdbc:oracle:thin:@Database:1521:ORCL
registryDatasource = EPMSystemRegistry
registryDatasourceJNDI = jdbc/EPMSystemRegistry
dbName = ORCL
version = 9.5.0.0
dbPort = 1521
instance_home = /home/hypadmin/Oracle/Middleware/user_projects/epmsystem1
dbPassword = GABaMyyplja+wLNCmLs8ag==
Run the following update to populate the isRegistryDB flag with the unique_id being the ID field used in the DATABASE_CONN registry entry.
epmsys_registry.bat addproperty #unique_id/@isRegistryDB true
Repeat the epmsys_registry VIEW DATABASE_CONN to make sure the flag is now set.
You will be able to reconfigure the shared services repository.
You can mark it as Answer/Helpful if you feel so.
Cheers!
J

Timeout: Tuxedo kills the service but not the database connection

Hi all,
I am experiencing some performance problems on my system due an efficient SQL and a Tuxedo improper timeout handling.
A service is using a "problematic" SQL (we will tune it but it's not the main problem). After 60 seconds from the execution, Tuxido kills the services for a timeout.
At this point I would like Tuxedo to notify DB2 database as well in order to stop processing the SQL. Instead the SQL continues running on the database (also if the service is killed) and this produce a gradual slow down of the performances.
In the UBBCONFIG, we are using a service configuration like the following timeout configuration:
.RESOURCES
SCANUINIT 5
SANITYSCAN 6
BLOCKTIME 12
.SERVICES
DEFAULT: SVCTIMEOUT=45
service1 SVCTIMEOUT=60 TRANTIME=60
service2 SVCTIMEOUT=60 TRANTIME=60
Note: not all the services are listed in the .SERVICES section and we are using the default NOTIFY as well as an OPENINFO.
Can you please help me in finding a configuration to kill both the services and the database?
Thanks in advance,
Benedetto

Hi Benedetto.
First of all, Tuxedo doesn't kill services, it kills servers. Your UBBCONFIG file specifies three timeouts, BLOCKTIME, SVCTIMEOUT, and TRANTIME.
BLOCKTIME specifies how long a Tuxedo API that needs a response will wait for that response. If the response isn't received in that period of time, Tuxedo will return TPETIME to the caller. As with any failure, if the request was part of a transaction, the transaction is marked rollback only. Note, this timeout does not affect the request, whether sitting in a server's IPC queue or currently executing in a server.
SVCTIMEOUT is a much more severe timeout and determines how long Tuxedo will allow a service implementation to execute. If a service implementation doesn't reply within the SVCTIMEOUT period, Tuxedo will issue an OS level KILL request to kill the process. If the server is marked restartable, Tuxedo will then try to restart the server assuming none of the restart limits have been reached. Killing the server causes the request to be lost within the server so the caller will stay blocked until BLOCKTIME is reached at which point the above actions will take place.
TRANTIME is the amount of time Tuxedo allows a transaction to remain active and viable. When this period expires, Tuxedo will mark the transaction as timed out with the only option being rollback. As well, Tuxedo aborts any API requests that would normally cause messaging to occur, i.e., making a tpcall() within a timed out transaction will fail without any attempt to call the service.
So in your case, the issue is partially that you have the values of your timeouts in somewhat reverse order. Typically we see BLOCKTIME being the smallest value, with TRANTIME typically larger than BLOCKTIME, and SVCTIMEOUT larger even still, although there are good reasons for exceptions to this guideline. Part of the reasoning behind this is that killing a server is a significant thing and its usually best to try and let the server complete whatever its doing, if if the work has been timed out either due to BLOCKTIME or TRANTIME, since the cost of killing and restarting a server is significant.
Tuxedo will notify the database of the transaction status when the application finally issues a tpcommit() or a tpabort() request, but not until then. Although, if SVCTIMEOUT is hit, then killing the server should cause the database connection to be lot.
If you could describe the behavior you are seeing and the relevant portions of your ULOG we can try to make some sense of what is happening.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

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

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.

Http connection timeout for business services from proxy service?

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

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

Set HTTP Connection timeout to avoid Deny Of Service attack

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

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

Enabling Usage Rights for Web Service and Database connectivity

We are looking for code that allows us to enable web service and database connectivity rights into a form. We are using LiveCycle Forms 7.2 to render the XDP and merge data. Because we are merging data into the form, it has to be reader enabled through the code everytime it is presented to the user in our application.
usageRights[0] = com.adobe.document.pdf.DOCUMENT_SAVE.value;
usageRights[1] = com.adobe.document.pdf.FORM_FILL_IN.value;
usageRights[2] = com.adobe.document.pdf.FORM_EXPORT.value;
usageRights[3] = com.adobe.document.pdf.FORM_IMPORT.value;
usageRights[4] = com.adobe.document.pdf.FORM_ONLINE.value;
Anyone's help would be greatly appreciated

This topic was cross posted. See responses here:
http://forums.adobe.com/message/2111421#2111421

Liferay Counter Service database connection timeout

Similar Messages

Maybe you are looking for