Terminal.app Annoyance: Login timed out after 300 seconds

I have a default terminal "window group" of 4 Terminal windows. When I start Terminal.app it should provide 4 working terminal tabs, but frequently it happens that one or two sessions (tabs) fail to start and show the following message:
Login timed out after 300 seconds
[Process completed]

Post Unix and Terminal queries to the Unix forum under OS X Technologies.

Similar Messages

WEBLOGIC 5.1SP9 : ListenThread Connection rejected: 'Login timed out after 5000 msec.

I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe

hi.
I'm not clear on this - what do you mean you are running a J2EE application from
an editor?
Also the error is coming from a servlet. Is one of your servlets calling a
getParameter() method after reading from the ServletInputStream()? If it is it
should be corrected.
Regards,
Michael
Christophe Chastang wrote:
I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe--
Michael Young
Developer Relations Engineer
BEA Support

The transaction is no longer active - Transaction timed out after 30 second

We have an intermittent error here, and I'm a rookie. The error results in a 500 being sent to the customer every 10th-20th POST and only occurs under heavy load. The heavy loading is over the for the day, but it'll be back.
My first suspicion was the app code doing transaction work and having database performance problems. But the app is non-transactional and the database is fine. The server farm nodes (4) are all experiencing the problems at equal rates, and the other apps on the farm are fine, so it appears to be app-specific rather than rooted in server state or database state.
I looked at the stack a little more closely and it appears to be some kind of internal persistence issue, but a completely foreign one to me. We have no Persistent Stores configured, so I don't know where to even start on this puppy.
EJB Exception occurred during invocation from home: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw exception: <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
<1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.nextInternal(SelectImpl.java:2209)
at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:35)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

This was actually my first conclusion as well. But when I went to the Data Source for this connection, I found it's a non-transactional driver. That's what made me go back and give the trace a second look. I don't see any references to the Data Source in question. It's OpenJPA stuff and Session persistence stuff.Non-XA drivers can still participate in an XA transaction via a variety of JDBC data source options - for example, labeled "1PC" and "LLR" on the console. (If you want to understand the particulars search for "JTS" or "LLR" in the JDBC edocs).
You seem to be suggesting maybe the setting can be made in a config doc, possibly of the app itself, right? Right. EJBs have a transaction-timeout attribute.
As opposed to setting it in the console. WebLogic has a domain wide default transaction-timeout setting that can be set on the console, but I tend not to recommend using it. In addition, there's something called a "deployment plan" which can be used to override some of the common EJB attributes via configuration, but I'm not personally familiar with its usage.
But isn't the setting vapor if we're using a nonXA driver?No.
I wonder if this thing couldn't be telling me it's waiting on the persistence subsystem to come available to store simple session data? Sometimes the problem is that there are periodic app requests that are more complex/larger than others. Sometimes the system is simply overloaded, and takes 30 seconds to honor a request that might normally take 10 seconds.
That other app is all about persistence. What if app2 is sucking some persistence subsystem dry and app 1 is waiting just to store session data? Could be.
If the nonXA thing really does kill the quick timeout workaround, how could I health-check the persistence subsystem?Don't know. At a wild guess I'd check for CPU's at 100% on all involved serves, and examine database stats.

Transaction time out after 300 seconds..

Hi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJB

Hi guys,
I have very intersting problem. I get transaction time out exception after 300 seconds. I use WLP8.1 SP3. I get this when I try to add a new portlet using admin tool
to home page (which is customized by many users)
Here is the error msg:
<weblogic> <> <BEA-415037> <PortalAdminInstanceManager.addPlaceableToPageInstance() -- java.rmi.RemoteException: EJB Exception: ; nested exception is:
javax.ejb.EJBException: SQL Error while trying to getLayoutDefinition on 2004: SQL [select LAY.MARKUP_DEFINITION_ID, LAY.INTERSECTION_ID, PL.PLACEHOLDER_DEFINITION_ID, PL.MARKUP_DEFINITION_ID, PL.LAYOUT_LOCATION, PL.INTERSECTION_ID, LAY.ICON_URI, LAY.HTML_LAYOUT_URI, LAY.WEBAPP_NAME, LAY.LAYOUT_FILE, LAY.IS_LAYOUT_FILE_DELETED from PF_LAYOUT_DEFINITION LAY, PF_PLACEHOLDER_DEFINITION PL where LAY.LAYOUT_DEFINITION_ID = ? and PL.LAYOUT_DEFINITION_ID = LAY.LAYOUT_DEFINITION_ID] database error code [0] SQL state [null] 040.; nested exception is: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
Name=[EJB

Firefox keeps timing out after 10 seconds. this is too short for big sites, how can I change this?

I regularly use a very busy download site and find that Firefox closes me out of any part of the site, not just the current tab, when it times out after a max.10 seconds - seems less! I want to be able to allow the page to continue loading until it opens - because it will, just not in 10 seconds during busy times.

"Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
If clearing the cookies doesn't help then it is possible that the file ''cookies.sqlite'' that stores the cookies is corrupted.
You can rename (or delete) '''cookies.sqlite''' (cookies.sqlite.old) and delete '''cookies.sqlite-journal''' and '''cookies.txt''', if they exist, in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Profile Folder] in case cookies.sqlite got corrupted.
See [[Cannot log in to websites]] (Remove corrupt cookies file) - See also http://kb.mozillazine.org/Websites_report_cookies_are_disabled (Other Solutions)

Deployment Error: Deployment Timed Out after 60 seconds

I am having problems simply deploying my webapp
through creator. The application that I am working on was
completely developed in the creator IDE and at some
point took a really log time to deploy. Now it actually times
out. This is my ide.log file. Any ideas?
Thanks,
Joelle
Log Session: Sunday, April 17, 2005 9:03:46 PM PDT
System Info: Product Version = Java Studio Creator (Build 040903)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.4.2_04; Java HotSpot(TM) Client VM 1.4.2_04-b05; Sun Microsystems Inc.
Java Home = C:\Sun\Creator\java\jre
System Locale; Encod. = en_US; Cp1252
Home Dir; Current Dir = C:\Documents and Settings\Administrator; C:\Sun\Creator\bin
IDE Install; User Dir = C:\Sun\Creator; C:\Documents and Settings\Administrator\.Creator\1_0
CLASSPATH = C:\Sun\Creator\lib\ext\boot.jar;C:\Sun\Creator\lib\ext\jgraph.jar;C:\Sun\Creator\lib\ext\naming.jar;C:\Sun\Creator\lib\ext\pbclient.jar;C:\Sun\Creator\lib\ext\pbtools.jar;C:\Sun\Creator\lib\ext\rowset.jar;C:\Sun\Creator\lib\ext\smbase.jar;C:\Sun\Creator\lib\ext\smdb2.jar;C:\Sun\Creator\lib\ext\sminformix.jar;C:\Sun\Creator\lib\ext\smoracle.jar;C:\Sun\Creator\lib\ext\smresource.jar;C:\Sun\Creator\lib\ext\smsqlserver.jar;C:\Sun\Creator\lib\ext\smsybase.jar;C:\Sun\Creator\lib\ext\smutil.jar;C:\Sun\Creator\lib\ext\sql.jar;C:\Sun\Creator\lib\ext\sqlx.jar;C:\Sun\Creator\lib\ext\locale\boot_ja.jar;C:\Sun\Creator\lib\ext\locale\boot_zh_CN.jar;C:\Sun\Creator\lib\ext\locale\naming_ja.jar;C:\Sun\Creator\lib\ext\locale\naming_zh_CN.jar;C:\Sun\Creator\lib\ext\locale\sqlx_ja.jar;C:\Sun\Creator\lib\ext\locale\sqlx_zh_CN.jar;C:\Sun\Creator\lib\ext\locale\sql_ja.jar;C:\Sun\Creator\lib\ext\locale\sql_zh_CN.jar;C:\Sun\Creator\java\lib\dt.jar;C:\Sun\Creator\java\lib\tools.jar
Boot & ext classpath = C:\Sun\Creator\java\jre\lib\rt.jar;C:\Sun\Creator\java\jre\lib\i18n.jar;C:\Sun\Creator\java\jre\lib\sunrsasign.jar;C:\Sun\Creator\java\jre\lib\jsse.jar;C:\Sun\Creator\java\jre\lib\jce.jar;C:\Sun\Creator\java\jre\lib\charsets.jar;C:\Sun\Creator\java\jre\classes;C:\Sun\Creator\java\jre\lib\ext\dnsns.jar;C:\Sun\Creator\java\jre\lib\ext\ldapsec.jar;C:\Sun\Creator\java\jre\lib\ext\localedata.jar;C:\Sun\Creator\java\jre\lib\ext\sunjce_provider.jar
Dynamic classpath = C:\Sun\Creator\lib\core.jar;C:\Sun\Creator\lib\openfile-cli.jar;C:\Sun\Creator\lib\openide-loaders.jar;C:\Sun\Creator\lib\openide.jar;C:\Sun\Creator\lib\ravelnf.jar;C:\Sun\Creator\lib\locale\core_ja.jar;C:\Sun\Creator\lib\locale\core_zh_CN.jar;C:\Sun\Creator\lib\locale\openide-loaders_ja.jar;C:\Sun\Creator\lib\locale\openide-loaders_zh_CN.jar;C:\Sun\Creator\lib\locale\openide_ja.jar;C:\Sun\Creator\lib\locale\openide_zh_CN.jar;C:\Sun\Creator\lib\locale\ravelnf_ja.jar;C:\Sun\Creator\lib\locale\ravelnf_zh_CN.jar
[org.netbeans.core.modules #4] Warning: the extension C:\Sun\Creator\modules\ext\sac.jar may be multiply loaded by modules: [C:\Sun\Creator\modules\css.jar, C:\Sun\Creator\modules\insync.jar]; see: http://www.netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/classpath.html#class-path
Turning on modules:
 org.openide/1 [4.26.2 040903]
 org.openide.loaders [4.11.1 040903]
 org.netbeans.core/1 [1.21.2 040903]
 com.sun.rave.layoutmgr/1 [1.1 040903]
 org.netbeans.modules.schema2beans/1 [1.7.1 040903]
 org.netbeans.api.xml/1 [1.3.1.3.6.0 3.6.0 040903]
 org.openide.src [1.1.1 040903]
 org.openide.io [1.1.2 040903]
 org.openide.execution [1.1.1 040903]
 org.openide.compiler [1.2.1 040903]
 org.netbeans.lib.terminalemulator [1.1.1 040903]
 org.netbeans.core.output/1 [1.1.1 040903]
 org.netbeans.core.compiler/1 [1.4.1 040903]
 org.openide.debugger [1.1.1 040903]
 org.netbeans.core.execution/1 [1.3.1 040903]
 org.netbeans.modules.debugger.core/3 [2.10.2 040903]
 org.netbeans.modules.debugger.jpda/1 [1.17.2 040903]
 org.netbeans.modules.editor/1 [1.14.4 040903]
 org.netbeans.modules.css/2 [1.1.1.3.6.0 3.6.0 040903]
 org.netbeans.core.ui/1 [1.3.1 040903]
 org.netbeans.modules.javahelp/1 [2.1.1 040903]
 org.netbeans.api.java/1 [1.3.1 040903]
 org.netbeans.libs.xerces/1 [1.4.1 2.6.0]
 org.apache.tools.ant.module/3 [3.6.1 040903]
 org.netbeans.modules.j2eeapis/1 [1.0 040903]
 org.netbeans.modules.settings/1 [1.4.1 040903]
 org.netbeans.libs.j2eeeditor/1 [1.1.1 040903]
 org.netbeans.modules.j2eeserver/3 [1.1.4 040903]
 org.netbeans.api.web.dd/1 [1.1.1 1.0 040903]
 com.sun.rave.project/1 [1.0.3 040903]
 com.sun.rave.welcome/1 [1.0.2 040903]
 com.sun.rave.beans2/1 [1.0.2 040903]
 com.sun.rave.jsfcl/1 [1.0.3 040903]
 com.sun.rave.jsfsupport/1 [1.0.3 040903]
 com.sun.rave.insync/1 [1.0.3 040903]
 com.sun.rave.jsfmetadata/1 [1.0.1 040903]
 com.sun.rave.toolbox/1 [1.0.3 040903]
 com.sun.rave.plaf/1 [0.1 040903]
 com.sun.rave.servernav/1 [1.0 040903]
 com.sun.rave.ravehelp/1 [1.0.2 040903]
 org.netbeans.modules.servletapi24/1 [2.0.1 2.0.1 040903]
 org.netbeans.modules.web.jspparser/2 [2.0.1 040903]
 org.netbeans.modules.diff/1 [1.7.1 040903]
 org.netbeans.modules.classfile/1 [1.8 040903]
 org.netbeans.modules.java/1 [1.16.2 040903]
 com.sun.rave.designer/1 [1.0.3 040903]
 com.sun.rave.navigation/1 [1.0.2 040903]
 org.netbeans.modules.xml.core/2 [1.1.1.3.6.0 3.6.0 040903]
 org.netbeans.modules.xml.text/2 [1.1.1.3.6.0 3.6.0 040903]
 org.netbeans.modules.html/1 [1.12.3 040903]
 org.netbeans.modules.web.core.syntax/1 [1.13.1 040903]
 com.sun.rave.licensemgr/1 [1.2 040903]
 org.netbeans.modules.extbrowser/1 [1.3.2 040903]
 org.netbeans.modules.xml.catalog/2 [1.1.1.3.6.0 3.6.0 040903]
 org.netbeans.modules.schema2beansdev/1 [1.1.1 040903]
 com.sun.rave.errorhandler.server/1 [0.1 040903]
 org.openidex.util/2 [2.7.1 040903]
 org.netbeans.modules.utilities/1 [1.15.1 040903]
 org.netbeans.modules.clazz/1 [1.13.1 040903]
 org.netbeans.modules.autoupdate/1 [2.8.2 040903]
 com.sun.rave.raveupdate/1 [1.0.1 040903]
 org.netbeans.modules.properties/1 [1.11.2 040903]
 org.netbeans.core.ide/1 [1.3.1 040903]
 com.sun.rave.jwsdpsupport/1 [1.0 040903]
 com.sun.rave.sam/1 [1.0.3 040903]
 com.sun.rave.websvc/1 [1.0.3 040903]
 com.sun.rave.dataconnectivity/1 [1.0.3 040903]
 org.netbeans.modules.properties.syntax/1 [1.11 040903]
 com.sun.tools.appserver/1 [2.0.1 20040903-1052]
 org.netbeans.modules.image/1 [1.11.1 040903]
 org.netbeans.modules.text/1 [1.12.1 040903]
 com.sun.rave.windowmgr/1 [1.1 040903]
 org.netbeans.modules.beans/1 [1.11.2 040903]
 com.sun.rave.jspsyntaxint/1 [1.0 040903]
Caught java.lang.InstantiationException: java.util.List in BU.instantiateBean for:java.util.List
java.lang.InstantiationException: java.util.List
 at java.lang.Class.newInstance0(Class.java:293)
 at java.lang.Class.newInstance(Class.java:261)
 at com.sun.rave.insync.beans.BeansUnit.instantiateBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.ressurectLiveBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.resurrect(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.sync(Unknown Source)
 at com.sun.rave.insync.models.FacesModel.sync(Unknown Source)
 at com.sun.rave.insync.ModelSet.syncAll(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.<init>(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.getInstance(Unknown Source)
 at com.sun.rave.outline.OutlineTopComp.projectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.fireProjectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.addProject(Unknown Source)
 at com.sun.rave.project.ProjectManager.openProject(Unknown Source)
 at com.sun.rave.welcome.WelcomePanel2$1.run(Unknown Source)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Caught java.lang.InstantiationException: java.util.List in BU.instantiateBean for:java.util.List
java.lang.InstantiationException: java.util.List
 at java.lang.Class.newInstance0(Class.java:293)
 at java.lang.Class.newInstance(Class.java:261)
 at com.sun.rave.insync.beans.BeansUnit.instantiateBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.ressurectLiveBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.resurrect(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.sync(Unknown Source)
 at com.sun.rave.insync.models.FacesModel.sync(Unknown Source)
 at com.sun.rave.insync.ModelSet.syncAll(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.<init>(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.getInstance(Unknown Source)
 at com.sun.rave.outline.OutlineTopComp.projectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.fireProjectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.addProject(Unknown Source)
 at com.sun.rave.project.ProjectManager.openProject(Unknown Source)
 at com.sun.rave.welcome.WelcomePanel2$1.run(Unknown Source)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Caught java.lang.InstantiationException: java.util.List in BU.instantiateBean for:java.util.List
java.lang.InstantiationException: java.util.List
 at java.lang.Class.newInstance0(Class.java:293)
 at java.lang.Class.newInstance(Class.java:261)
 at com.sun.rave.insync.beans.BeansUnit.instantiateBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.ressurectLiveBean(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.resurrect(Unknown Source)
 at com.sun.rave.insync.live.LiveUnit.sync(Unknown Source)
 at com.sun.rave.insync.models.FacesModel.sync(Unknown Source)
 at com.sun.rave.insync.ModelSet.syncAll(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.<init>(Unknown Source)
 at com.sun.rave.insync.models.FacesModelSet.getInstance(Unknown Source)
 at com.sun.rave.outline.OutlineTopComp.projectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.fireProjectOpened(Unknown Source)
 at com.sun.rave.project.model.Portfolio.addProject(Unknown Source)
 at com.sun.rave.project.ProjectManager.openProject(Unknown Source)
 at com.sun.rave.welcome.WelcomePanel2$1.run(Unknown Source)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Hi,
It appears to be a time out issue.
1. Delete the server log, because the log file getting bigger it would not start.
2. How many deployed projects do you see (in the server navigator you can open up the deployed server and see what's out there)? Undeploy some unwanted projects.
a)Undeploy, You could try that from the server admin interace.
b)Undeploy from the server navigator-> deploymentserver by right clicking.
Hope this helps.
Regards,
Creator Team.

Weblogic.transaction.RollbackException: Transaction timed out after 32 seconds

following is the scenario.
EJB1{
method1{
createTransaction();
connectToDiffrentWebloic();
updateTransaction();

following is the scenario.
EJB1{
method1{
createTransaction();
connectToDiffrentWebloic();
updateTransaction();

Login timed out from Socket Listener?

Does anyone have a clue on why I got the following error?
Thanks.
Mon Sep 18 18:50:42 PDT 2000:<W> <ListenThread> Connection rejected: 'Login timed out after: '5000' ms on socket: 'Socket[addr=qelab3.ariba.com/10.10.16.104,port=1298,localport=8001]''

We do not support ssl between plugins and weblogic yet. Currently if you send a https request, plugins will just downgrade them to http.
Srikant, [email protected], http://weblogic.bea.com/, etc.
Prabhu Kannan wrote:
Hi,
I am facing the same problem. I have configured NSAPI plugin in our NES server and the WebLogic 5.1. I am trying to connect to Weblogic through the SSL port. It times out. I see the following message in the NES log.
[08/Nov/2000:15:51:56] failure (16491): for host 10.203.3.78 trying to GET /weblogic/index.html, wl-proxy reports: Error reading WebLogic Response from 10.203.1.226:7021 at line 764 of proxy.cpp, errMsg='File not found'
Both the web server and weblogic have SSL certificates installed in them.
Can you give me some ideas as to how to get this to work?
Thanks,
Prabhu
Srikant Subramaniam <[email protected]> wrote:
From an earlier posting:
This sounds like a slow client to me. Specifically the client isn't sending enough data (something like 7 bytes) within the first 5 seconds for the server to determine which protocol the
client is using. I believe that future versions of the server squelch this message by default because logging errors caused by poorly behaving clients seems to cause a good deal of noise
in the logs, especially when running a public site.
the client timeout parameter can be increased, see:
http://www.weblogic.com/docs51/admindocs/properties.html#login
Srikant, [email protected], http://weblogic.bea.com/, etc.
John Xiao wrote:
Does anyone have a clue on why I got the following error?
Thanks.
Mon Sep 18 18:50:42 PDT 2000:<W> <ListenThread> Connection rejected: 'Login timed out after: '5000' ms on socket: 'Socket[addr=qelab3.ariba.com/10.10.16.104,port=1298,localport=8001]''

Re: Connection Rejected:Login Timed Out

This sounds like a slow client to me. Specifically the client isn't sending
enough data within the first 9 seconds for the server to determine which
protocol the client is using.
Srikant, [email protected], http://weblogic.bea.com/, etc.
Ajit wrote:
"Hi, I went through the various versions of Login Timed Out problems.This is my version. My Web server currently running on Weblogic Web Server 5.1.0 with service pack 9 is shutting down frequently.My server platform is SUN SOLARIS 2.6 5/98. The following messages reflect in the weblogic.log Thu Aug 02 08:49:52 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.3,port=19431,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 08:50:13 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.5,port=10656,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 09:23:18 EDT
2001:<!> <SSLListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <SSLListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown commencing NOWThu Aug 02 09:23:18 EDT 2001:<A> <ListenThread> ListenThread.run() failed:java.lang.ThreadDeathThu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:19 EDT 2001: <HTTP> Destroying servlets in default servlet context.Thu Aug 02 09:23:19 EDT 2001: <ServletContext-General> proxy: destroyThu Aug 02 09:23:19 E

hi srikanth i am facing some problem in weblogic for a particular port.weblogic
is shutting down for that port .this port
is configured for SSL.
when i have reviewed the logs i could trace
following error.i dont know whether this error is linked to the shutting down of weblogic.
ERROR:on Apr 08 13:30:36 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=192.193.118.137/192.193.118.
137,port=33280,localport=7003}''
Each and everytime restarting the weblogic
instance is not a proper solution so please
let me know what can i do for this weblogic
shutting down abnormally.
waiting for ur reply
Best Regards
Surender
Wipro Limited.

JSP Timeout after 300 seconds

"Hi all,
 Need your help. My JSP always got timeout after 300 seconds. I already set the Timeout Secs (in web app descriptor) to 600 seconds and Invalidation Interval Secs to 180 seconds. Where this 300 secs setting come from ? Below is the error message. Thanks.
 Transaction Rolledback.; nested exception is:
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 Start server side stack trace:
 java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1124)
 at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:466)
 at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1604)
 at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:429)
 at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1570)
 at java.lang.Thread.run(Thread.java:484)
 End serve


 Hi Hendry,
 Get in to weblogic console
 Click JTA from your left pane
 JTA and increase the timeout seconds there.
 Hope this helps you.
 Arul
 Rob Woollen <[email protected]> wrote:
 >That's the transaction timing out. What version of WLS are you using?
 >
 >In < 6.0, the default tx timeout is 300 seconds. In >= 6.0, the default
 >
 >tx timeout is 30 seconds.
 >
 >What are you doing in a transaction that takes more than 5 minutes?
 >
 >-- Rob
 >
 >Hendry Janto wrote:
 >> "Hi all,
 >>
 >>
 >> Need your help. My JSP always got timeout after 300 seconds. I already
 >set the Timeout Secs (in web app descriptor) to 600 seconds and Invalidation
 >Interval Secs to 180 seconds. Where this 300 secs setting come from
 >? Below is the error message. Thanks.
 >>
 >> Transaction Rolledback.; nested exception is:
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >>
 >> Start server side stack trace:
 >> java.rmi.RemoteException: Transaction Rolledback.; nested exception
 >is:
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >> at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1124)
 >> at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:466)
 >> at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1604)
 >> at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:429)
 >> at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1570)
 >> at java.lang.Thread.run(Thread.java:484)
 >> End serve
 >

The request has timed out after 00:00:00 milliseconds.

Hello,
I am having weird exception when I try to send a message to a topic and there's nothing on the internet I could "google with Bing" about it.
Here's the error message
The request has timed out after 00:00:00 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded.
There are two things weird about it:
The timeout period is 0 miliseconds
The number of miliseconds is given in format 00:00:00
Here's the whole stack
Timestamp: 5.5.2014. 11:15:58
Message: HandlingInstanceID: b9fcc3c8-c167-47ab-8473-ae45bfb62311
An exception of type 'System.TimeoutException' occurred and was caught.
05/05/2014 11:15:58
Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : The request has timed out after 00:00:00 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded.
Source : Microsoft.ServiceBus
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : TAsyncResult End[TAsyncResult](System.IAsyncResult)
HResult : -2146233083
Stack Trace :
Server stack trace:
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderHelper.EndGetAccessTokenCore(IAsyncResult result, String& expiresIn)
at Microsoft.ServiceBus.TokenProviderHelper.EndGetAccessTokenByAssertion(IAsyncResult result)
at Microsoft.ServiceBus.SharedSecretTokenProvider.OnEndGetToken(IAsyncResult result, DateTime& cacheUntil)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult.OnEndTokenProviderCallback(IAsyncResult result, DateTime& cacheUntil)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResultBase`1.OnCompletion(IAsyncResult result)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResultBase`1.<GetAsyncSteps>b__f(T thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [1]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationToken(String appliesTo, String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext, RequestInfo requestInfo)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessage(String action, Object body, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext, RequestInfo requestInfo)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.SendCommandAsyncResult.CreateWcfMessage()
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpTransactionalAsyncResult`1.<GetAsyncSteps>d__40.MoveNext()
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
Exception rethrown at [2]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.EndSendCommand(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.<.ctor>b__1(IAsyncResult result, Boolean forceCleanUp)
at Microsoft.ServiceBus.Messaging.BatchManager`1.PerformFlushAsyncResult.OnSingleOperationCompleted(IAsyncResult result)
Exception rethrown at [3]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManager`1.BatchedObjectsAsyncResult.End(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManager`1.EndBatchedOperation(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManagerAsyncResult`1.OnBatchedCallback(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
Exception rethrown at [4]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.OnEndSend(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.MessageSender.RetrySenderAsyncResult.<GetAsyncSteps>b__f(RetrySenderAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
Exception rethrown at [5]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.TopicClient.EndSend(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Framework.Azure.Bus.AzureServiceBus.<EnqueueAsync>d__0.MoveNext() in c:\nivatech\papiri\source\framework\Azure\Bus\AzureServiceBus.cs:line 98
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Framework.Analytics.BusinessActivityLogRepository.<EnqueueAddAsync>d__29.MoveNext() in c:\nivatech\papiri\source\framework\Core\Analytics\BusinessActivityLogRepository.cs:line 51
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Papiri.Web.Controllers.BaseController.<RegisterActivityAsync>d__4.MoveNext() in c:\nivatech\papiri\source\web\site\Controllers\BaseController.cs:line 102
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Papiri.Web.Controllers.HomeController.<Index>d__0.MoveNext() in c:\nivatech\papiri\source\web\site\Controllers\HomeController.cs:line 35
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeAsynchronousActionMethod>b__36(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass48.<InvokeActionMethodFilterAsynchronouslyRecursive>b__41()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass33.<BeginInvokeActionMethodWithFilters>b__32(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.<BeginInvokeAction>b__1c()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult)
Additional Info:
TimeStamp : 5.5.2014. 11:15:58
FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
AppDomainName : /LM/W3SVC/2/ROOT-1-130437489467023302

We had the same issue and solved it.
We changed the authorization of the servicebus to SAS and all is working fine now.
1. Check Azure Portal select your ServiceBus and go to register configuration
2. You need the Name and Key of existing Rule (here RootManageSharedAccessKey) or insert a new Rule. We created a new rule with no manage access.
3.1 In Code:
Replace the SharedSecretCredentials with SAS Tokenprovider and add it to the endpoint behaviors like before
TransportClientEndpointBehavior sas = new TransportClientEndpointBehavior();
sas.TokenProvider = TokenProvider.CreateSharedAccessSignatureTokenProvider("NAMEofRULE","KEYofRULE");
3.2 App.Config:
Simply change the tokenprovider line from
<behaviors>
 <endpointBehaviors>
 <behavior name="sharedSecretClientCredentials">
 <transportClientEndpointBehavior>
 <tokenProvider><sharedSecret issuerName="ACSNAME" issuerSecret="ACSKEY"/></tokenProvider>...
to
<sharedAccessSignature keyName="NAMEofRule" key="KEYofRULE"/>
Hope it helps!

My itunes is up to date on windows vista but my iphone 3gs wont download the new 4.3 sofeware saying that network connection timed out after downloading for 7 minutes. can anyone help?

my itunes is up to date on windows vista but my iphone 3gs wont download the new 4.3 sofeware saying that network connection timed out after downloading for 7 minutes. can anyone help?

I have manage to update. You need to disable windows firewall and
You have any other anti virus (I have kaspersky) you need to disable that as well

[SOLVED] error: Resolving timed out after 10000 milliseconds

EDIT: it was a DNS lookup problem. I don't know why but it is better to manually specify nameservers in resolv.conf than in the home router control panel (a NETGEAR DGN2200v3). See the #3 post.
Hi
I just installed arch and I need to downgrade to xorg 1.12 to be able to use catalyst proprietary driver (legacy).
As I read into the wiki, I added the two required repos:
[catalyst-hd234k]
Server = http://catalyst.wirephire.com/repo/catalyst-hd234k/$arch
[xorg112]
Server = http://catalyst.wirephire.com/repo/xorg112/$arch
when I try to do an update, I get "database file does not exist".
In logs appears a curl error 28, timeout error, but the repository is online (I can ping it and I can browse its contents with firefox).
What can I do?
sudo LANG=C pacman -Syy
warning: database file for 'xorg112' does not exist
warning: database file for 'catalyst-hd234k' does not exist
:: Synchronizing package databases...
error: failed retrieving file 'xorg112.db' from catalyst.wirephire.com : Resolving timed out after 10000 milliseconds
error: failed to update xorg112 (download library error)
error: failed retrieving file 'catalyst-hd234k.db' from catalyst.wirephire.com : Resolving timed out after 10000 milliseconds
error: failed to update catalyst-hd234k (download library error)
core 105.0 KiB 122K/s 00:01 [######################] 100%
extra 1412.9 KiB 418K/s 00:03 [######################] 100%
community 1929.7 KiB 447K/s 00:04 [######################] 100%
multilib 95.7 KiB 115K/s 00:01 [######################] 100%
Last edited by yell! (2013-03-10 14:16:22)

yell! wrote:
thanks for replying. I edited the first post.
Solved:
After a lot of hours trying wget, aria2 and curl, with a lot of options, I just stopped observing pacman output behaviour in the console.
Seemed that it was a DNS lookup problem but, in my resolv.conf, the specified nameserver was my home router.
Anyway, I changed that specifying google's nameservers; is working now. It's a weird thing because in my homerouter I was already using google's nameservers.
Now I can open the repos in browser without lag.
Example of my resolv.conf:
Before:
# home router nameserver
nameserver 192.168.0.1
After:
#Google nameservers
nameserver 8.8.8.8
nameserver 8.8.4.4
Thanks you help me so much love you

Connection to partner timed out after 60s

Hi,
I have a scenario HTTP to RFC. Where the user posts the data using the URL I have provided to get the response back from SAP system.
Everything is working fine. But today we had a strange problem. When the user tries to post the data to integration server he is getting the response as below,
SAP Web Application Server
==========================
500 Connection timed out (-5)
Error: -5
Version: 6040
Component: ICM
Date/Time: Mon Oct 22 05:01:00 2007
Module: icxxthr_mt.c
Line: 2603
Server: ABCD_XWD_11
Detail: Connection to partner timed out after 60s
But after some time its working fine (without doing anything) without any problem. I am searching for the root cause of this problem. Any ideas on this?
Please help me out in this.
Thanks in advance,
Prasad Babu.

The target system might be too busy to accept any new requests and that the reason it gave the error message.
VJ

JMS Exception DisconnectMonitor timed out after 299s.

Hi,
Could anone please suggest regarding below exception and the parameter which can be configured for this timeout in JMS.
Thanks,
JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
weblogic.jms.common.LostServerException: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
     at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1436)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.ExecuteThreadLite.execute(ExecuteThreadLite.java:72)
     at weblogic.work.ExecuteThreadLite.run(ExecuteThreadLite.java:56)
Caused by: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
     at weblogic.messaging.dispatcher.DispatcherWrapperState.onDisconnect(DispatcherWrapperState.java:396)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.deliverDisconnectEvent(AbstractDisconnectMonitorDelegate.java:156)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.access$400(AbstractDisconnectMonitorDelegate.java:25)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate$Timer.run(AbstractDisconnectMonitorDelegate.java:234)
     at java.lang.Thread.run(Unknown Source)

Hi,
The Error message :
JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
Indicates that the server hosting the remote JMS resource has been disconnected and a Disconnection error message has been delivered to the JMS resource listerners.
This can happen due to following reasons:
1: The network connection has gone down in such a way that only Weblogic's internal heartbeat mechanism manages to detect the problem. Among other possibilities, this can be due to a hardware failure, server crash, or even an overly enthusiastic firewall.
2: You have a slow network connection and are receiving a very large message, so Weblogic's internal heartbeats fail to get through (they end up queued up behind the large message).
This causes Weblogic to think the connection is lost even though it is actively receiving packets.
you can try increasing the following JMS property values:
Click on the Name of the server (On which you have deployed your application and queues etc...)in the left Pane
Goto --> Protocols-->General--> Advanced Options
Increase the following Parameters
Complete Message Timeout:
Idle Connection Timeout:
Maximum Message Size:
Thanks,
Sandeep

Terminal.app Annoyance: Login timed out after 300 seconds

Similar Messages

Maybe you are looking for