[solved] dhcpcd: timed out after reinstalling arch

Hi erveryone!
After reinstalling arch I can't connect to my wireless network anymore.
Typed:
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant_vienna.conf
dhcpcd wlan0
Got:
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
wpa_supplicant_vienna.conf (ssid and psk deleted):
network={
ssid=""
proto=RSN
pairwise=CCMP TKIP
key_mgmt=WPA-PSK
psk=
I reinstalled arch on my netbook at the same time and there's everything working fine (even with the same wireless-card). The only difference between the two systems is that my laptop has an i686 installation while on my netbook I've installed x86_64.
Things I've tried:
+ Update the system via wired-connection (mirrors.kernel.org) --> the download never gets faster than 10KB/s (?).
+ Configure the wireless interface via netcfg --> same problem
+ Reinstalled again and only changed LOCALE in /etc/rc.conf --> same problem
So you may see, I have no idea what I could be doing wrong and hope that theres anybody out there who knows what to do!
P.S. Well, i have now by-passed my problem.
1.) Created a list of packages installed during system-update on my netbook.
2.) In this list I changed package-name-x86_64.tar.gz to package-name-i686.tar.gz
3.) Downloaded the list with wget.
4.) Ccopied the packages to my laptop
5.) Created a local repository and made a system-update.
Last edited by kronfeld (2010-05-04 17:34:43)

Hi trusktr
This might seem stupid but are you sure you are using "eth0" and not "eth1" etc.? As an example I have two on-board lans and I'm plugged into eth1. I had to change rc.conf as it defaults to using eth0.
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(eth1)
Since I am using eth1 and not eth0 here is what I get when I try:
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:04:4B:00:88:0E
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:23 Base address:0x6000
Look familiar?
I'm not saying this is the case but it could be something as simple as that.
ifconfig -a
should show you how many lans you have.
Thought I would drop the obvious first in case that's all it is.

Similar Messages

[SOLVED] dhcpcd: timed out

I want to install Arch using wifi. I'm trying to connect to my WPA network before I even begin.
I did this (with my own network and passphrase in place)
wpa_passphrase mywireless "secretpassphrase"
wpa_passphrase mywireless "secretpassphrase" > /etc/wpa_supplicant.conf
ifconfig wlan0 up
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
dhcpcd wlan0
And got:
dhcpcd: version 5.2.2 starting
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
What's wrong?
EDIT: Long story. Wrong key
Last edited by RocketLauncher (2010-07-21 09:36:10)

Before starting dhcpd, make sure you are connected - run wpa_supplicant without the -B switch to check for errors.

[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

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!

Resolving timed out after 10000 milliseconds

i keep getting this error when trying to run pacman but my internet is working fine
if you need more detailed info please ask
error: failed retrieving file 'core.db' from mir.archlinux.fr : Resolving timed out after 10000 milliseconds
error: failed retrieving file 'core.db' from mir1.archlinux.fr : Resolving timed out after 10000 milliseconds
error: failed retrieving file 'core.db' from archlinux.limun.org : Resolving timed out after 10000 milliseconds

Happens to me as well, however only on my home network. If i am on another connection it works, which really confuses me
Edit : Found the solution to this, as I suspected it was a DNS lookup issue, caused by my router being the one doing the resolution.
Follow these steps to solve it.
Last edited by dpm3g10 (2013-03-25 09:50:59)

Re: 907 Invalid COD Local connection timed out after ~ 120000

I tried to download facebook, it just said “907 Invalid COD
Local connection timed out after ~ 120000”
I really need it with all of my heart, can anyone pls help me out?????

its a network issue most likely.
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter

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.

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

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

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

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

Iwconfig wlan1 dhcpcd:timed out

hi,
I manage to connect to my wifi using
iwconfig wlan1 essid "mywlan" key 1234567890
then iwconfig wlan1 gives me:
wlan1 IEEE 802.11bg ESSID: "mywlan"
Mode:Manager Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encrytion key:1234-5678-90
Power Management:off
dhcpcd wlan1
dhcpcd: version 5.2.2 starting
dhcpcd: wlan1: waiting for carrier
dhcpcd: timed out
Im using a Adla Awus036h wifi dongel.
what obvius thing am i missing?
Cheers
Soff
Last edited by Sofflock (2010-11-19 17:08:44)

Snowknight wrote:
Make sure you bring up the interface with ifconfig before you run dhcpcd.
Try:
# ifconfig wlan1 up
And then run dhcpcd on that interface.
should i run
#ifconfig wlan1 up
just before i run dhcpcd? Becuse ive followed the wireless guide on the wiki without luck.
I get the feeling i am just missing something stupid tbh.
Tnx for your answers!

Require help to solve Connection timed out error while reload initial data

Dear Developers,
I have installed SAP NetWeaver and SAP ME SDK 2.0 on my laptop and working from offshore, the SAP ME WIP and ODS database is situated at onsite. The installation is working fine, however, after developing Activity Hooks, at the step where I need to Reload Initial Data for the Site where I want the Activity to be used I get the below error message:
500 Connection timed out
Error: -5
Version: 7011
Component: ICM
Date/Time: Wed Mar 07 12:37:38 2012
Module: icxxthr.c
Line: 4184
Server: <laptop_hostname>_<SID>_00
Error Tag: {-}
Detail: Connection to partner timed out after 600s
© 2001-2009, SAP AG
How to find out what is causing this error? When I use the hostname of the onsite SAP ME application pointing to the same database, Reload Initial Data works fine. I need to reload initial data from laptop SAP ME application only, beacause the activity hook classes reside on my laptop, before I send the SAPME.sca files for common server build.

Hello,
Please try to increase PROCTIMEOUT ICM parameter for the corresponding server\port. If it does not help, please, check NW default traces for ME errors and share your results with us.
Best regards,
Alex.

Update to Muse CC 2014.3 still have problem upload to FTP: Server not responding in time, FTP may not be supported on this server [Connection timed out after 15001 millseconds.] I have no problem with CC 2014. Can you suggest what do I have to do?

Update to Muse CC 2014.3 still have problem upload to FTP: Server not responding in time, FTP may not be supported on this server [Connection timed out after 15001 millseconds.] I have no problem with CC 2014. Can you suggest what do I have to do?

Hello.
Today I got the opportunity to work with a Muse user with the same issue after performing the troubleshooting steps in the post above we decided to contact the host.
Later i came to know that host took Muse user's IP and they were able to unblock it and muse started connecting to FTP host.
I another scenario Host suggested Muse user to add :21 to the FTP address and then Muse was able to connect.
Eg ftp.domain.com:21
Please try the 2 suggestion above and let me know if it works.
Regards
Vivek

Transaction timed out after 29seconds

          hi,
          I am using 2pc with XA, for MQ and Sybase
          I am getting following exception.
          [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
          after 29seconds
          can somebody help me on this ?
          TIA
          Chidambar


default value of transaction timeout is 30 secs.
          Your tx may be running more than the default tx timeout.
          Either increase your tx timeout or re-consider your
          design.
          Kumar
          chidambar wrote:
          > hi,
          > I am using 2pc with XA, for MQ and Sybase
          > I am getting following exception.
          > ................................................................
          >
          > [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
          > after 29seconds
          >
          > ................................................................
          > can somebody help me on this ?
          > TIA
          > Chidambar

[solved] dhcpcd: timed out after reinstalling arch

Similar Messages

Maybe you are looking for