While running Selenium IDE tests on Firefox 4, I seem to get in the FF4-built-in Error Console a number of these messages (meaning Messages, as opposed to Errors, etc.), but I can't quite tell at what point they're occurring or what might be the cause. I'm not sure whether it's even a Selenium issue or something on one of my pages causing it.
CoCreateInstance() FAILED.
Are they cause for alarm?
CoCreateInstance is a function in the Windows implementation of the Component Object Model (COM). Firefox uses a binary-compatible clone of COM as part of its native-code architecture, which is likely the way that Selenium allows you to control parts of Firefox that aren't exposed via JavaScript.
So it's plausible that the CoCreateInstance messages are from Selenium, but it could be Firefox itself. You could create a new Firefox profile without Selenium installed and try navigating to the test page that triggers the log messages, and manually performing the test actions that trigger the messages. If you still get the messages, then Selenium is probably not the source of the errors. You could also try running the tests with Selenium on on Firefox 3.6. If the messages go away, then it's probably a (likely minor) incompatibility between Selenium and the latest build of Firefox.
The messages are probably not cause for alarm, so long as it's not interfering with your tests.
Related
I have created a shiny app on my computer that runs with no error. Now, I deployed the same app to the shiny server we have in our organization, and i cannot initiate the app. I receive the following error message:
transpose listening on http://127.0.0.1:43202
Warning: Error in tabPanel: argument "tabName" is missing, with no default
65: tabPanel
Execution halted
here are my questions:
(1) I do use shinydashboard and shinydashboardplus libraries in my app and both are installed on the shiny server as well so this shouldnt be a problem since tabsetPanel and tabPanel are in these libraries, correct?
(2) tabPanel and tabSetPanel do NOT have a tabName argument. so what is this error specially because the app does work on my computer with no issue.
I know probably I need to provide the code but I cannot at the moment unless i significantly take stuff out of it (government property) but I was hoping someone can help considering the fact that it works on my computer but it doesnt when i deploy it.
Just a quick note that the R version installed on my laptop is 3.5.2 but the one on the server is 3.6! can this be an issue?
Thanks!
I think a library bs4Dash was masking tabSetPanel which is quite confusing because i didnt have that problem running the app on my laptop...
I recently began using GWT 2.7 in Eclipse Luna and I was running my projects seamlessly while testing them in localhost:8888, the thing is, when I tried to test them (any of them, even a new app with only the autogenerated content) with another device on the same local network using (pc running eclipse ip):8888 I get a message like this:
The page at (ip):8888 says: Couldn't load (app) from Super Dev Mode server at http://(ip):9876. Please make sure this server is ready. Do you want to try again?
This also happens when I try to access to the app in the pc running eclipse with (its own ip):8888.
I've checked these four similar questions, but they didn't have any really helpful answers, these are a few things I've tried or discovered already:
I enabled the 9876 port on the firewall
I've deleted the .nocache.js and .devmode.js so that they're generated again
I noticed that when this problem occurs it's because the browser can't get the (ip):9876/recompile-requester/(app) file
I tried deploying the app to GAE and it doesn't work there either, nothing that happens on the modules Java code runs (And for some reason, I get a "Uncaught java.lang.ClassCastException" message on the chrome console, but this only happens on the deployed version, it doesn't happen on localhost:8888 or in (local ip):8888)
But nothing has worked and the four questions I mentioned are pretty much the only things related to this I've found, so I really don't know what else to try.
As Thomas pointed out, the problem I had was that from GWT 2.6 onwards, if you want to test from other devices in the same network, you have to whitelist the addresses you'll be using in each *.gwt.xml file using a command line like this:
<set-configuration-property name="devModeUrlWhitelistRegexp" value="http://(localhost|127\.0\.0\.1|192\.168\.150\.(\d{1,3}))(:\d+)?/?.*" />
I also had to add a -bindAddress 0.0.0.0 attribute to the run config for it to work.
I've got a strange situation; when I run a Flex app from Eclipse (i.e. click run as web app), my remote calls always hang.
In Firefox, they return as failed.
But when I open up a browser and browse to my .html file in the bin-debug folder, the remote calls work.
Why is that?
Thanks for any helpful tips!
p.s. I'm accessing a websphere server and authentication is required but a Java developer hardcoded his ID in.
One thing to check:
Do you have a breakpoint set in your code somewhere? Eclipse may be waiting for you to interact with it so the program execution can continue. On my Win7 machine, when the debugger takes over, eclipse often does not take over focus; so I have to manually minimize IE.
My problem was solved today and the issue was getting through to the IBM websphere server; the authentication was still in place and the java developers had to create a cloned environment where authentication was not required. Thank you everyone for their helpful answers.
I created a web application project. It ran successfully, but shows one message.
i.e. GWT Module needs to BE (re)compiled message displayed. How to solve this error/warning?
"GWT Module need to BE (re)compiled" - that means, you should call the app with the gwt.codesvr parameter, for example:
http://localhost:8080/MyProject/index.html?gwt.codesvr=172.16.0.43:9997
This message must be coming If you are running GWT in Development mode? check if you have installed the GWT browser plugin properly, check if there are any errors shown in the development mode tab(in eclipse).
I'm trying to call a web service in my back end java code when it's
running in hosted mode. Everything loads fine, the GWT RPC call works
and I can see it on the server, then as soon as it tries to call an
external web service (using jax-ws) the jetty falls over with a
Internal Server Error (500).
I have cranked the log all the way up to
ALL but I still don't see any stack traces or cause for this error. I just get one line about the 500 Error with the request header and response.
Does anyone know if the internal jetty keeps a log file somewhere, or
how I can go about debugging what's wrong?
I'm running GWT 1.7 on OS X 10.6.1
Edit: I know that I can use the -noserver option, but I'm genuinely interested in finding out where this thing lives!
From the documentation:
You can also use a real production
server while debugging in hosted mode.
This can be useful if you are adding
GWT to an existing application, or if
your server-side requirements have
become more than the embedded web
server can handle. See this article on
how to use an external server in
hosted mode.
So the simplest solution would be to use the -noserver option and use your own Java server - much less limitations that way, without any drawbacks (that I know of).
If you are using the Google Plugin for Eclipse, it's easily set up in the properties of the project. Detailed information on configuration can be found on the official site.
Edit: you could try bypassing the Hosted Mode TreeLogger, as described here: http://blog.kornr.net/index.php/2009/01/27/gently-asking-the-gwt-hosted-mode-to-not):
Just create a file called
"commons-logging.properties" at the
root of your classpath, and add the
following line:
[to use the Log4j backend]
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
[to use the JDK14 backend]
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
[to use the SimpleLog backend]
org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
Edit2: the trunk of GWT now also supports the -logfile parameter to enable file logging, but it probably won't help in this case, since the problem lies in the way the Hosted Mode treats the exceptions, not the way it presents them.