Hi can any one help me how to resolve this ucf timeout issue.
thanks in advance,
please find the below issue log.
O 07:05:00ERROR com.documentum.web.common.Trace No of formhistories in the session :Q1By5wFkT1M_w26soJrPIeZ, exceeds threshold, no of formhistories in the session: 50, confiugred threshold: 50
[7/25/12 7:06:50:255 EDT] 0000002a SystemOut O 07:06:50ERROR com.documentum.web.common.Trace invokeMethod() failed while calling: onOk
ucf session wait timeout
java.lang.IllegalStateException: ucf session wait timeout
at com.documentum.web.contentxfer.ucf.UcfSessionManager.newSession(UcfSessionManager.java:391)
at com.documentum.web.contentxfer.ucf.UcfSessionManager.getSession(UcfSessionManager.java:137)
at com.documentum.web.contentxfer.ucf.UcfContentTransport.getUcfSession(UcfContentTransport.java:195)
at com.documentum.web.contentxfer.ucf.UcfContentTransport.<init>(UcfContentTransport.java:68)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1328)
at com.documentum.webcomponent.library.contenttransfer.ContentTransferServiceContainer.createTransport(ContentTransferServiceContainer.java:731)
at com.documentum.webcomponent.library.contenttransfer.ContentTransferServiceContainer.invokeService(ContentTransferServiceContainer.java:320)
at com.ford.gci.web.container.PublishContainer.invokeService(PublishContainer.java:397)
at com.documentum.webcomponent.library.contenttransfer.ContentTransferServiceContainer.invokeService(ContentTransferServiceContainer.java:307)
at com.ford.gci.web.container.PublishContainer.importUpload(PublishContainer.java:217)
at com.ford.gci.web.container.PublishContainer.onOk(PublishContainer.java:314)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java:1633)
at com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java:1487)
at com.documentum.web.form.FormProcessor.fireActionEvent(FormProcessor.java:1303)
at com.documentum.web.form.RecallOperation.execute(RecallOperation.java:101)
at com.documentum.web.form.FormProcessor.processAction(FormProcessor.java:113)
at com.documentum.web.form.FormAction.processAction(FormAction.java:107)
at com.documentum.web.env.WDKController.doStartRequest(WDKController.java:191)
at com.documentum.web.env.WDKController.processRequest(WDKController.java:92)
at com.documentum.web.env.WDKController.doFilter(WDKController.java:83)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:848)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:691)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:654)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:526)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:248)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:764)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:133)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:457)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:300)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1551)
[7/25/12 7:06:50:683 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/errorhandler.jsp]: Initialization successful.
[7/25/12 7:06:54:477 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/system/errormessage/errormessage.jsp]: Initialization successful.
[7/25/12 7:06:54:816 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalContainerStart.jsp]: Initialization successful.
[7/25/12 7:06:55:097 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalEdgesStart.jsp]: Initialization successful.
[7/25/12 7:06:55:482 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalContentGutterStart.jsp]: Initialization successful.
[7/25/12 7:06:55:773 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalContentGutterEnd.jsp]: Initialization successful.
[7/25/12 7:06:56:054 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalEdgesEnd.jsp]: Initialization successful.
[7/25/12 7:06:56:431 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalButtonbarStart.jsp]: Initialization successful.
[7/25/12 7:06:56:809 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalButtonbarEnd.jsp]: Initialization successful.
[7/25/12 7:06:57:092 EDT] 0000002a ServletWrappe I SRVE0242I: [gci_gciEAR] [/gci] [/wdk/fragments/modal/modalContainerEnd.jsp]: Initialization successful.
The UCF feature in Documentum seems to be a necessary evil. I have had more complaints from our users regarding UCF than any other Documentum component.
The most common complaint is – It is DAMN slow to launch!!
I agree with the users. Launching UCF in our organization’s environment takes around 50-70 seconds!!!
Imagine that you read around 20 documents at different times in the day and every time you want to read a document, you have to wait for 50 seconds. Can you imagine the wait while your browser displays a blank page? No wonder the users complain about this.
After running several rounds of tests, we identified the factors that cause these really slow response times.
1) UCF uses Java JRE 1.5.x. JRE needs time to initialize itself and load into memory before UCF kicks into action. On a laptop with 1GB RAM and a reasonably fast CPU, JRE takes around 20-30 seconds to launch.
2) Another key factor is the presence of Anti-virus software on the user’s laptop. Since AV will scan all the JRE related .jar files, the JRE initialization will be further slowed slowed down.
From our tests, (Only the first operation after browser restart takes this long. Next operations should finish between 10-15 seconds)
– Export operation using UCF with Anti-virus takes around 50-70 seconds
– When Anti-virus is turned off, the Export operation takes around 35-45 seconds.
Some suggestions:
– Tune your anti-virus settings to exclude JRE folders and UCF folders
– Exclude anti-virus from scanning into .zip and archive files
– TEST with various settings
Here are some of the other common problems with UCF:
– JRE gets updated automatically when a new update is available from sun.com. Sometimes this breaks the UCF. Solution could be to try deleting all the UCF related folders and files in UCF folder (usually found in C:Documents and SettingsDocumentumucf)
Customers who are planning to use Documentum should test the performance of UCF in their environment.
1) Setup a pilot environment on a test server. Access Webtop from a typical end-user PC and check the response times. Make sure you are running anti-virus and any other software that are standard to your environment. This is one way to ensure that the system performance will be acceptable to the end-users.
2) If you are planning to conduct any peformance testing and load testing, ensure that you specify that some scenarios include testing with UCF enabled.
This entry was posted on Monday, September 1st, 2008 at 2:28 pm and is filed under Admin, WDK. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
UCF Session Wait Time Out
Recently I faced this issue. This was the consequence of the some update patches done on the server. As a result the compatibility issues raised between IE and Java versions.
Due to update in patches by Java each time when these update takes place, default settings override the existing settings in IE. As a result the Java get unregistered with the browser, result, Documentum shows message during applet operation — your browser don’t support Java, UCF Wait Timeout or just a blank window with no progress bar shown and you are stuck forever.
However, there are few configuration thorugh which you can get rid of this —
1) Ensure you have latest Java version installed on your server and client
2) Ensure you have latest IE browser version installed on your client machine
2) Check your Internet Options for Java Applet
3) Verify that your Java Plugins are enabled properly
4) Check that next generation java plugin is disabled
1. Latest Java Version
Latest Java version will ensure maximum security updates and any new enhancements in java framework. All Java versions have backward compatibility to their previous versions for minimal impact. To Install Latest Java, just go to the java site. You can Google it out on internet. The java site will automatically check for the version of java you have installed on the computer or you can opt for the executable download for the another computer, in case you are not downloading it on your target machine.
2. Latest IE Browser
Browser is your window to the world. Keep your browser updated whenever possible. Most of the companies keep on updating their browser version through security patches, fixes, new functionality. Latest browser version means improved performance, faster response, safety from latest potential threat etc.
3. Enabling Java Applet for your browser
Sometimes having latest version of Java and browser is just not enough. You have to enable certain configurations in order to use them. These can be found in Tools-> Internet Options… ->Security Tab. You can set custom level for each of the internet, local intranet, trusted sites and restricted sites by enabling ActiveX to atleast prompt for your action. Further, set the advanced options in ‘Advanced’ Tab enable use of JRE under Java(Sun) heading, if it is not there, probably your JRE is ot properly installed.
4. Manage Add ons
Add-on are like extensions or additional features that extend the functionality of your browser. These are DLL files which can be enabled or disabled based on the requirement and frequency of use. Open your browser Add-ons by Clicking on Tools->Manage Add ons…
Verify that the Java related plugins are enabled if not enable them.
5. Disabling Next Gen Option
This is a new option added in JRE 1.6.0_10 onwards. Follow the steps below to disable it —
1. Go to Control Panel->Java
2. Under Advanced tab, disable the next generation java plug-in under Java Plug-In
Clear any cache of browser and delete any temporary files.
Delete this documentum folder mostly found on location: C:Documents and
SettingsUSER_IDDocumentum, or take backup.
Kill java process
Kill javaw process.
Restart browser and login webtop application.
Hopefully, the next time you open your applet window, you won’t see the incompatibility issue.
If you have similar solution, please feel free to comment it
Popular posts from this blog
Tenalirama: Man who bring kingdom to its knees with rice and chessboard !
Witty Wednesday What is interesting fact that you can come up with seemingly mundane everyday rice and game of strategy, chess. Let me tell you this in a story. The story of a man who bring whole kingdom down on its knees, single handedly with these two things. This is one of the famous story of TenaliRama. I was watching one TV serial the other day named “TenaliRama». TenaliRama was the real person who was famous for his wits and who is protagonist in this serial. «Tenali Ramakrishna who was known as Vikatakavi (clown jester poet), was a Telugu poet who hailed from the present-day Andhra Pradesh region, generally known for his wit and humor. He was one of the Ashtadiggajas or the eight poets at the court of Krishnadevaraya, the Vijayanagar emperor. (1509–1530). Tenali Ramakrishna composed works on Hinduism. Tenali Ramakrishna was also a great scholar of several languages that included Marathi, Tamil, and Kannada.»- Wikipedia As the
DFC_DOCBROKER_EXCLUDED: Primary Docbroker Blacklisted
Problem & Cause Have you ever come across the error in the log java.io.IOException: DFC_DOCBROKER_EXCLUDED. This means that somehow, your DFC is not able to communicate with your docbroker, specified in dfc.properties. Your docbroker is responsible for communication between the application deployed on the application server, and the docbase. Docbroker acts like a bridge between the two layers of architecture. But, due to some reason, this bridge is broken. There can be multiple reasons behind it. 1. Bad connection or Network failure 2. Docbroker does not start properly 3. Docbroker is not properly added in dfc.properties 4. Patch applied for DFC doesn’t get deployed properly 5. Web application doesn’t start properly 6. DNS entry not resolved for the docbroker server 7. Any other unidentified reason. How does it work? The DFC of application maintains the list of docbrokers, which it can communicate. However, if it is not able to communicate with
AdiYogi Shiva: Feel the spiritual power
The bliss of a feeling of nothingness, the void around me, when my mind was like an empty container with nothing but one thought of his, when there was no sense of individuality and yet feeling of direct connection with the one; with everyone around me and I still felt the inner silence; at this point of state, I felt the vastness, the power of his and my tininess. This kind of experience can make you humble, it certainly made me. The experience I wrote above is hard to attain and may need years of practice and meditation. However, my last year visit to Coimbatore’s one of the most spiritual place, famously known as Adi Yogi Shiva can jump start your spiritual experience. The whole surrounding, the aura in the air and the weather uniting together with Mantras (enchantments) created positive energy all around to make one feel cleansed, right through his soul. Concept Designed by Sadhguru Jaggi Vasudev, who is also the founder of Isha Foundation, Adi Yogi Shiva is a Bust St
I am currently working in a java program involving mysql. I encountered a problem with these message:
Communications link failure. The last packet successfully received
from the server was 174,165,153 milliseconds ago. The last packet sent
successfully to the server was 4 milliseconds ago.
I believe this has to do with the session variable ‘wait_timeout’. My assumption could be wrong though so I am confirming it here. Is this really because of the ‘wait_timeout’ session variable? Does this error mean that my database connection is «expired» in a sense that the session timeout already lapsed? If yes, I have another problem.. I cannot reproduce the said error..
This is what I am trying in order to replicate the error.
-
Setting the
wait_timeoutvariable to5which is originally28800( 8 hrs ).mysql> set session wait_timeout=5; -
Thinking that my next attempt to access database would apply this, I would run this code:
Class.forName("com.mysql.jdbc.Driver"); oConnection = DriverManager.getConnection(sUrl,sUser,sPass); System.out.println("Database Connection Established.n"); Thread.sleep(6000); executeSimpleQuery();The
executeSimpleQuery()function just executes a simpleSELECT * FROMstatement to check if the connection is still working. Apparently, if the wait_timeout is just 5 and I’ve made the thread sleep for 6 seconds, the connection would now be expired and the error should be produced. But, the expected result does not happen instead it performs the query.
What should i do to replicate the error?
asked Oct 25, 2011 at 10:43
You set wait_timeout=5 for current session; then opened another session (in java application) and executed the query. Try to set this variable after the opening connection, or set it globally.
For example —
SET @@global.wait_timeout = 15; -- Set global variable
SET @@local.wait_timeout = 25; -- Set session variable
SELECT @@global.wait_timeout, @@local.wait_timeout; -- Check global and session variables
answered Oct 25, 2011 at 11:43
DevartDevart
118k22 gold badges162 silver badges184 bronze badges
1
Есть проблема с недавней программой
The last packet successfully received from the server was 38251886 milliseconds ago. The last packet sent successfully to the server was 38251886 milliseconds ago. 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
Если возникает такая проблема, в соответствии со значением перевода: «Последний пакет был успешно получен до 38251886 миллисекунд. 38251886 составлял около 10 часов, что превысило конфигурацию данных данных. Также рассмотрите возможность добавления времени wait_timeout «
Но wait_timeout не может быть установлен слишком долго.
У wabt_timeout есть уровень сеанса и глобальный уровень
Сеанс — это сеанс, что означает, что этот сеанс
Global Global
Ниже мы посмотрим на разницу между сессией и глобальным:
session:
Измените wait_timeout сеанса:
set session wait_timeout=200;
Посмотреть еще раз:
Был изменен
Выйдите из MySQL и снова войдите в систему:
Посмотрите на wait_timeout сеанса снова и обнаружил, что 200 ранее модифицированные 200 снова были восстановлены до 100
*То есть мы изменили переменную сеанса, только после того, как этот сеанс будет эффективным. После выхода, войдите снова, и настройки будут восстановлены
global
Просмотреть wate_timeout
Изменить Global:
Gloal был изменен на 200, поэтому в настоящее время wait_timeout, соответствующий сеансу сеанса, изменен:
Кажется, что wait_timeout of Global, тогда wait_timeout сеанса не будет изменена
В этот момент мы выйдем из MySQL и снова вхожу в систему, будет ли изменен сеанс
Wait_timeout, соответствующий ранее измененным глобальным, не будет выходить из строя, и данные будут восстановлены для восстановления
После сеанса снова войдите в систему:
Или 100 указывает на то, что только изменение переменных wait_timeout of Global не вызывает изменения в сеансе
Затем мы продолжаем изменять переменную Global Internet_timeout: после модификации
После модификации мы снова бросили сеанс
измененный,Другими словами, мы изменили переменную Global Interactive_timeout, а затем вышли из значения переменной wait_timeout, соответствующей сеансу.
Кажется, что глобальные и сессии связаны
На самом деле, мы видим в этом месте:
Сеанс — это сеанс. Переменные, которые мы модифицируем, будут восстановлены, когда мы выйдем из сеансов MySQL
Global ， Global inveractive_timeout session interactive_timeout, wait_timeout ， interactive_timeout ，
Затем после глобальной модификации это не будет изменено, нет
Модификация глобальной переменной будет восстановлена с помощью перезапуска MySQL
Ниже мы модифицированы глобальные переменные, но я не перезапустил MySQL:
Теперь мы перезагружаем MySQL:
Я обнаружил, что установленные выше переменные были восстановлены после перезапуска MySQL
Итак, как мы можем изменить переменные Internet_timeout и wait_timeout, даже если они все еще не восстановлены после перезапуска, в настоящее время нам нужно изменить файл конфигурации my.cnf Configuration File в настоящее время
Изменить my.cnf
[mysqld]
interactive_timeout = 57600
wait_timeout = 57600
После изменения этого файла конфигурации мы обнаружим, что настройки переменных MySQL после перезапуска получаются из файла конфигурации
Это считается окончательной модификацией
Выше представлено обсуждение модификации wait_timeout и Interactive_timeout
Надеюсь помочь вам
У меня есть java-программа, когда я вхожу в систему, после ~ 600 000 миллисекунд (я на самом деле пытался несколько раз, и ее всегда ~ 600 000, вот почему я думаю, что где-то настроен тайм-аут на 600 000 милисекунд) моя программа больше не работает (ее всегда нужно подключать к базе данных). Это дает мне ошибку Communication link failure. я Вот мои настройки подключения mysql:
import java.sql.*;
import javax.swing.*;
public class mysqlconnect {
Connection conn = null;
public static Connection ConnectDb() {
try{
Class.forName("com.mysql.jdbc.Driver");
Connection conn = DriverManager.getConnection("jdbc:mysql://server_name/database_name","user_name","user_password");
return conn;
}catch (Exception e) {
JOptionPane.showMessageDialog(null, "Cant connect to db");
return null;
}
}
}
Я попытался добавить ?autoReconnect=true и tcpKeepAlive к моему коду, но не повезло. Есть ли способ перейти на phpmyadmin и изменить некоторые настройки там (увеличить время ожидания)?
Ответ 1
SET SESSION wait_timeout = 999999;//or anything you want
Из командной строки mysql, которая увеличит значение таймаута. Чтобы увидеть значение:
SHOW VARIABLES LIKE 'wait_timeout';
Ответ 2
Вы можете сделать этот запрос, чтобы показать свой тайм-аут в MySql
SHOW VARIABLES LIKE 'connect_timeout';
Затем вы можете обновить его до 60 секунд для примера
SET GLOBAL connect_timeout=60;
Если проблема заключается в запросе, вы можете использовать Statement.setQueryTimeout
Ответ 3
Вы можете установить wait_timeout NET_read_timeout и connect_timeout для устранения проблемы следующим образом.
SHOW VARIABLES LIKE 'wait_timeout';
SET SESSION wait_timeout = 999999;
SHOW variables LIKE 'NET_read_timeout';
SET SESSION net_read_timeout = 1000;
SHOW VARIABLES LIKE 'connect_timeout';
SET GLOBAL connect_timeout = 1000;
Ответ 4
Я обычно делаю это одним из следующих способов:
1) Отредактируйте файл my.ini. Этот файл обычно находится на C:ProgramDataMySQLMySQL Server 5.6my.ini
[mysqld]
interactive_timeout=2147483
wait_timeout=2147483
(максимальное значение 2147483 для Windows и 31536000 в других ОС)
После этого перезагрузите машину.
2) Включите параметр времени ожидания в URL JDBC. Здесь URL JDBC взят из моего кода
JDBC: MySQL://HOST: PORT/DATABASE_NAME autoReconnect = истина & амп; sessionVariables = sql_mode = ‘STRICT_TRANS_TABLES, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION, PAD_CHAR_TO_FULL_LENGTH’, interactive_timeout = 2147483,wait_timeout = 2147483