Hi i'm a new bee in Selendroid can someone please tell me why im getting this error when i launch the URL http://localhost:4444/inspector .. my automation works fine but im unable to view the app in http://localhost:4444/inspector link (during added a break point into the test code and run the test in debug mode) can someone please help on this.
INFO: inspector screenshot handler, sessionId: b93ee863-3b05-0fed-73a3-eaeadb6fa1c5
io.selendroid.exceptions.AndroidDeviceException: Device not accessible via ddmlib.
at io.selendroid.android.impl.AbstractDevice.takeScreenshot(AbstractDevice.java:363)
at io.selendroid.server.model.SelendroidStandaloneDriver.takeScreenshot(SelendroidStandaloneDriver.java:531)
at io.selendroid.server.handler.InspectorScreenshotHandler.handle(InspectorScreenshotHandler.java:56)
at io.selendroid.server.SelendroidServlet.handleRequest(SelendroidServlet.java:140)
at io.selendroid.server.BaseServlet.handleHttpRequest(BaseServlet.java:70)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.PathMatchHandler.handleHttpRequest(PathMatchHandler.java:33)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.DateHeaderHandler.handleHttpRequest(DateHeaderHandler.java:21)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.ServerHeaderHandler.handleHttpRequest(ServerHeaderHandler.java:25)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:67)
at org.webbitserver.netty.NettyHttpChannelHandler$2.run(NettyHttpChannelHandler.java:72)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Thanks in advance
I am also having the same issue , but I am using physical device. I slowed this issue, solunion is clenched the temp folder and really start the selendroid server, then it works fine. This thing working fine with me, try this way may be it helps hope so..
Related
It appears that vimeo-networking-java is no longer working and no one has answered a ticket in the issues section of their Github project since Aug 2021. There does seem to be people updating it though as the last update to the project was a few days ago.
Anyway... I wanted to see if anyone else was having this issue. It appears that the download link that you plug into ExoPlayer no longer is valid. My app, which I haven't updated in about a month, all of a sudden stopped playing videos and ExoPlayer now gives this error:
E/ExoPlayerImplInternal: Playback error
com.google.android.exoplayer2.ExoPlaybackException: Source error
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:579)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:246)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 410
at com.google.android.exoplayer2.upstream.DefaultHttpDataSource.open(DefaultHttpDataSource.java:383)
at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:201)
at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
at com.google.android.exoplayer2.source.ProgressiveMediaPeriod$ExtractingLoadable.load(ProgressiveMediaPeriod.java:1015)
at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:415)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
I tried copy and pasting the download link into my browser and the webpage it brings you to says "Sorry we're having a little trouble"
When I do the same thing for iOS it plays the video.
This URL scheme which android uses, appears to be down:
https://player.vimeo.com/progressive_redirect/download/ .....
Its interesting though because iOS Vimeo networking pod works fine. iOS seems to use a different URL scheme:
https://player.vimeo.com/progressive_redirect/playback/....
All of the other data for the video loads, it is just the download link appears to be corrupt. I think this started around 12:00am EST March 20th.
This was the previous working code I've been using to get the URI for ExoPlayer.
...
public void success(com.vimeo.networking.model.Video video) {
String videoFile = video.getDownload().get(0).getLink();
...
}
This is the 2nd time in the past few months a server error seems to have caused an issue with my app. I'm thinking of ditching Vimeo if anyone has any other alternatives as well.
My UWP apps suddenly throw the following exception on Win 10 Mobile Build 10.0.14342.1001. They still work fine in the emulators.
Is anybody experiencing the same problem? Is there a workaround?
Exception thrown: 'System.ArgumentException' in mscorlib.ni.dll
WinRT information: user
Additional information: The parameter is incorrect.
user
To ensure the problem is not related to something specific with the apps email messages I sent the following simple message which causes the same problem.
Dim em As New Windows.ApplicationModel.Email.EmailMessage
em.To.Add(New EmailRecipient("a#b.c"))
em.Subject = "test"
Await EmailManager.ShowComposeNewEmailAsync(em)
Link to test case.
This is a bug in the insider build. No workaround known.
MS was informed about it via feedback and the MS forum.
Got fixed with Windows 10 Mobile Insider Preview Build 14356.
Build 14342 is an insider 'fast' build, meaning it is not production-ready and you are likely to hit errors from time to time. Please file feedback using the Feedback Hub, and wait for the next build. Thanks for being an Insider!
I am trying to import large files of size more than 500 mb to some gbs in mean while getting this error unexpected exception encontered during query though I am using <cfsettting requesttimeout = 1000000 >. when i have changed in Railo web admin it works but I want to do it by using cfsetting tag. can anyone help me what i have to do for using cffsetting tag inside the page ? Thanks.
I am using
MySQL 5.5.35
Railo 4.2.0 on ubuntu 12.04.
requestimeout.log
"Severity","ThreadID","Date","Time","Application","Message"
"ERROR","Thread-3","03/06/2014","04:05:24","controler","stop thread (3) because run into a timeout .;java.lang.Throwable;java.lang.Throwable
at railo.runtime.tag.Http4._doEndTag(Http4.java:611)
at railo.runtime.tag.Http4.doEndTag(Http4.java:596)
at admin.resources.text_cfm$cf.call(/railo-context-compiled/admin/resources/text.cfm:48)
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:885)
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:793)
at admin.web_cfm$cf.call(/railo-context-compiled/admin/web.cfm:124)
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:885)
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:837)
at railo.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:208)
at railo.runtime.listener.ModernAppListener.onRequest(ModernAppListener.java:86)
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2182)
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2149)
at railo.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:332)
at railo.loader.servlet.CFMLServlet.service(CFMLServlet.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:307)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
"
Here is what is quoted in Google Railo group by (Michael Offner-Streit,CTO,Railo Technologies GmbH)
we can not begin with the execution of cfml files before we have recieved the request header.
because the railo servlet is not invoked before.
you can set also timeouts on the servlet engines (resin,tomcat ...) most of them support this.
there is also a other way to set per page requesttimeout. simply add the following to the url of the call like index.cfm?RequestTimeout=100
for security reasion this feature is not enabled by default, you have to enabe it as follows,
got to the railo admin to settings/application (/railo-context/admin/web.cfm?action=server.application), there you find "Request timeout in URL" enable this.
but also this takes only effect when railo is invoked.
/micha
btw: index.cfm?RequestTimeout=100 works also on ACF5,ACF7,ACF8,ACF9 but not on ACF6, they have also removed this for security reasion in ACF6 but silently added again in version 7.
Note: I think that should explain your problem. You can do it by adding it in url and modifying the settings (enabeling request time out) in railo web admin, it will also ensure that setting is not applicable on all the pages if done from railo admin.
We are using the Google Docs List API to export different document types and we encountered the following error for a specific spreadsheet when trying to ask for it in xls format:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Caused by: com.google.gdata.util.ServiceException: Conversion failed unexpectedly
<HTML>
<HEAD>
<TITLE>Conversion failed unexpectedly</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Conversion failed unexpectedly</H1>
<H2>Error 500</H2>
</BODY>
</HTML>
at com.google.gdata.client.http.HttpGDataRequest.handleErrorResponse(HttpGDataRequest.java:624)
at com.google.gdata.client.http.GoogleGDataRequest.handleErrorResponse(GoogleGDataRequest.java:563)
at com.google.gdata.client.http.HttpGDataRequest.checkResponse(HttpGDataRequest.java:552)
at com.google.gdata.client.http.HttpGDataRequest.execute(HttpGDataRequest.java:530)
at com.google.gdata.client.http.GoogleGDataRequest.execute(GoogleGDataRequest.java:535)
at com.google.gdata.client.media.MediaService.getMediaResource(MediaService.java:234)
at com.google.gdata.client.media.MediaService.getMedia(MediaService.java:276)
at com.google.gdata.client.media.MediaService.getMedia(MediaService.java:302)
This error has persisted for several days for that same spreadsheet. We have investigated a bit on our own and concluded that the formats that fail to export are xls/xlsx and ods, but that for example csv and html works. This is how our REST calls look:
fails: https://docs.google.com/feeds/download/spreadsheets/Export?key={ID}&xoauth_requestor_id={email}&exportFormat=xls
fails: https://docs.google.com/feeds/download/spreadsheets/Export?key={ID}&xoauth_requestor_id={email}&exportFormat=ods
succeeds: https://docs.google.com/feeds/download/spreadsheets/Export?key={ID}&xoauth_requestor_id={email}&exportFormat=csv
We also tried adding the old format= attribute but it did not change the behaviour so we removed it again.
Since the Google Docs is being replaced by Google Drive we are going to look at converting to the Google Drive API next year, which might work, but in the meantime it would be nice to be able to solve this in the current version.
On our side, I am trying to get in contact with the customer to see if they can see anything odd in the actual spreadsheet. I will add any information I find as I get it.
Searches on Google do not come up with much, so I hope that someone here has seen this before and knows some scenarios where this can happen. Any comments from anyone who saw this before and what you did to get around it will be helpful!
Thanks in advance!
I'm developing an Internet Explorer command button that will open a specific web page once clicked. Here's a snippet of code (IEApp is a reference to an instance of IE.WebBrowser):
IEApp.Navigate(sURL, ref one, ref two, ref three, ref four);
The above line throws the following COMException:
Exception Source: Interop.SHDocVw
Exception Type: System.Runtime.InteropServices.COMException
Exception Message: The requested resource is in use. (Exception from HRESULT: 0x800700AA)
Exception Target Site: Navigate
This wasn't a problem on IE6 or IE7. Any ideas on what's going wrong? I'm using AddInExpress for creating the command button.
Cheers!
Christian
That's ERROR_BUSY usually happens when IE is doing something else, e.g. displaying a window.alert message box.
Try suppress script errors and Implement IDocHostShowUI and return S_OK without blocking the message pump
could this help: turning off UAC in Windows, if you are using a server kind version:
screen-shoots here: http://blog.vincentbrouillet.com/post/2011/02/10/watin%3A-The-requested-resource-is-in-use
I had this error, and it was quite random. I tried killing IE before running the tests. It kind of work, but not all the time.