Is it possible to edit the Timeout Alert msg box text when getting a connection timed out? I'm using GeckoFx-45 (WPF)
The operation timed out when attempting to contact some_url
Thank you
Related
I am working on Cytoscape 3.9.1 and have stringApp 2.0.0 installed in my system.
Today, I tried importing 72 genes to String (both by web and in Cytoscape software).
STRING App web says stringApp communication error. Confirm that you have installed the latest version of stringApp (1.6+) and Cytoscape (3.8+).
I am getting an error message in Cytoscape: "This action cannot be performed on the current network as it appears to be an Old STRING network. Would you like to get the latest STRING network for the nodes in your network?
I have three options to solve
OK, upon clicking this, another dialogue box opens to Re-query the network.
Cancel, upon clicking this, the dialogue box closes.
Close the dialogue box, upon clicking this dialogue box closes.
My Cytoscape task history shows like this
Loading data from STRING for 72 identifier(s).
Network error: Unexpected error from server: Server returned HTTP response code: 503 for URL: https://api11.jensenlab.org/network
POSTing JSON from https://api11.jensenlab.org/network
Unexpected error from server: Server returned HTTP response code: 503 for URL: https://api11.jensenlab.org/network
Re-query network
null
Caught exception executing task.
Can someone help me how to solve this problem?
I tried to generate PPI using STRING App and it didn't work.
The backend database was having problems yesterday. It should be fixed now -- can you try again?
-- scooter
When accessing my application on mulesoft, I am getting the following error:
Message : 42|Application|Too many opened conversations. Please close them and try again.
Element : null # my-application-1:null:null
--------------------------------------------------------------------------------
Exception stack is:
42|Application|Too many opened conversations. Please close them and try again. (org.mule.module.ws.consumer.SoapFaultException)
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:84)
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:51)
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:40)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:113)
org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:856)
org.mule.module.cxf.transport.MuleUniversalConduit.sendResultBackToCxf(MuleUniversalConduit.java:359)
org.mule.module.cxf.transport.MuleUniversalConduit.dispatchMuleMessage(MuleUniversalConduit.java:316)
org.mule.module.cxf.transport.MuleUniversalConduit$2.handleMessage(MuleUniversalConduit.java:223)
(227 more...)
(set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
I am not sure where the error originates, is it because some limitation on the backend server, or should I look into internal limitations like "maxThreads"?
It looks like a SOAP fault is being received from remote web service. The description 42|Application|Too many opened conversations. Please close them and try again. seems to be sent by the web service and doesn't look to be generated by Mule.
I've been trying to get the kaazing stock ticker excel demo working, and I'm running into some problems with the websocket connection. I have my gateway running and the stock feed service seems to be working:
[Stock Feed] Stock Ticker demo connected to tcp://localhost:61616
When I attempt to run the javascript JMS messaging demo, I get the following:
CONNECT: ws://localhost:8001/jms
EXCEPTION: ConnectionFailedException: WebSocket connection failed
It typically takes about 30 seconds to fail. In that time, my current sessions on the kaazing dashboard do spike to 1, so I know the connection is at least being attempted.
The same thing is occurring if I use the simple websocket client chrome extension. In my error logs, I'm seeing:
2016-03-11 11:06:18,723 [New I/O worker #6] INFO [ws://localhost:8001/jms x-kaazing-handshake]
[tcp://[0:0:0:0:0:0:0:1]:52340 http/1.1] - [localhost:8001] "GET /jms?.kl=Y HTTP/1.1 " "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0"
2016-03-11 11:06:19,860 [EagerCP_0-1] WARN Unable to establish JMS Connection due to the following exception: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused: connect
The error is addressed on the kaazing site here: http://kaazing.com/doc/jms/4.0/integration-jms/p_jms_integrate_tshoot.html#problem4 but it doesn't really provide a solution. I would try to implement the "workaround" suggested but I can't find the configuration file. None of the gateway configurations contain the given block of XML.
As a last ditch effort, I attempted to modify the activemq service configuration to include websockets by adding the ws to the transportConnector:
<transportConnectors>
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>
<transportConnector name="ssl" uri="ssl://0.0.0.0:61617"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
<transportConnector name="websocket" uri="ws://0.0.0.0:61614"/>
</transportConnectors>
Still no luck. What am I missing? It seems like this should work right out of the box...
The issue was a permission level on the activemq.bat load. The connection never actually establish itself because of admin privileges on our networks. I was able to fix it by tweaking our admin rights.
Of course, I never looked at the activemq batch logs which gave me the hint right away.
http://developer.kaazing.com/documentation/jms/4.0/about/setup-guide.html#localhost_install
After time out i am not able to close the browser ,No matter what i do even if call browser.Quit().The browser just hangs around forever .I am working with IE browser 9 and the latest web driver 2.37.0
This happens when we have time out , an example error as follows
OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL http://localhost:58542/session/0f8faf36-f84f-4035-9cc0-169656bc00c6/element/c841d512-c9ff-4d2a-9a45-87f52359d986/click timed out after 60 seconds.
----> System.Net.WebException : The operation has timed out
I would like to know if any work around for this issue is available ,closing the browser manually is not optimal option like what i am doing now .Thank you in advance and if you need any more info please let me know
I am getting this error in background page when responding to request
from content script.
Does anyone know what can be causing this error?
Full stack trace:
Uncaught Error: Attempting to use a disconnected port object chrome/RendererExtensionBindings:147
chrome.Port.postMessage chrome/RendererExtensionBindings:147
chromeHidden.Port.dispatchOnConnect.connectEvent chrome/RendererExtensionBindings:89
myExtension.foo.sendResponse.state background.js:1573
db.readTransaction.tx.executeSql.paramStr background.js:1038
This only happens after a couple of hours of browsing reloading extension is not helping - not that it would be a solution after restarting chrome browser all gets back to normal for couple of hours content script can keep sending request to background but NO response
from background can be sent back Is there any way I could catch this Uncaught error and reset the listener?
I am using chrome.extension.onRequest.addListener for my communication. Before I respond I query DB and I do not send any other response before query is finished.
Thanks,
Marek
This is caused when a connection get closed. For example if you open a tab that has the content_script injected, it opens a connection, the tab is closed, and then the background_page tries to pass a message. It will fail because the tab is no longer active to receive the message.
In your case I would guess that as tabs close and new tabs open you are attempting to post messages with the old tabId instead of creating a new connection to the new tab. I would recommend reading through the long-lived connections section again.
In my case, however, I needed to provide the sendResponse function to the chrome.runtime.sendMessage(msg, responseCallbackMissingHere), which will give you the "Attempting to use a disconnected port object" error.