I do JSF development using Myfaces, Primefaces, Tomcat in Eclipse IDE. When testing thru I used to get exceptions thrown by Myfaces/Primefaces in the Eclipse Console.
Recently I enhanced my development environment by adding MyFaces CODI and OpenWebBeans. Ever since I have done this, I stopped gettting any error messages in my eclipse console. I have no idea why.
Even basic errors like nullpointerexception, method/variable not found etc. are not thrown. I have set Myface CODI stage as Development. I get MyFace CODI messages related to start and stop of conversations, but all exceptions and errors are never thrown.
It is frustrating to debug myfaces/primefaces/bean code to discover these simple errors.
Can somebody suggest what could I do to get the exceptions back again in the Eclipse environment.
Need some urgent help as this issue has slow down development very significantly.
That's an issue with your setup. We are using all of those libs as well and none of them can cause something like that.
Related
I am facing 503 AuthenticationSupport service missing. Cannot authenticate request error every time server is started. This happened many times. There is no such broken error information on the error log file. I have even deleted the repository but didn't help much. I even use oak but still no use. I had set up it multiple times to skip this error but I don't feel confident with this approach. For better information, I am attaching the latest error log file.
https://drive.google.com/file/d/1aXEcZP_Tvk1ebBxfOmR9Q1ffk2KLeW66/view?usp=sharing
NOTE: I am a beginner in AEM. Please be gentle
java -Xmx6000m -jar oak-run-1.8.0.jar check --bin=-1 C:\Users\mahinder.singh\Documents\Projects\Adobe\author\crx-quickstart\repository\segmentstore
This is usual. Might be taking a little longer time than usual to load. Wait for a while.
If the issue still persists reinstall the instance and allow the aem to get kicked up on it's own.
I've recently deployed a Unity application to the web using WebGL. I have Sentry integrated on the frontend logging exceptions, and I've added the Sentry SDK to Unity. The frontend seems to log no problem, however Unity seems to be struggling. Sometimes I'll get errors reported but a lot of the time I don't. To my knowledge there's no explicit onerror callback I can hook into. I've tried catching the exception in managed code and then reporting that to the frontend, but that doesn't seem to work either.
Any help would be appreciated
I post this merely as a reference for others that might end up being in the same situation and since I spent almost 3 days trying to figure out the root cause of the problem, I thought it would be a good idea to post the solution here.
My situation was as follows:
I tried to build a deployment package for a .net application and got TypeLoadExceptions, FileNotFoundExceptions (regarding DLLs), Side-By-Side configuration errors, etc. once I tried to run it on a vanilla test machine.
[edit]: stackoverflow won't let me answer my own question within 8 hours of it being posted, the answer follows in ~8 hours ;)
The problem was that one of the dependency projects of my application was set to "Debug" build in the Visual Studio configuration manager, therefore the debug dll of the dependency ended up being used for release builds as well. On any development machine this was no problem after all since all debug runtimes were available.
On the vanilla test machine however only the release runtimes were present which caused so much trouble to me and gave me unmeaning exceptions that lead me to so many wrong directions via google, etc.
In my case it was SlimDX that was set to build a debug build in the VS configuration manager, even when doing release builds. Since SlimDX makes use of the VC runtimes I got the above problem, but this could happen with any .net assembly that uses the VC runtimes.
I hope this will eventually safe someone some hours ;)
Im finding after a few weeks of GWT development my Development Mode compilations suddenly slow down at the stage where you see this in the Development Mode console log:
Validating newly compiled units
I've found a related question but this seemed a little vague compared to my issue
Eclipse getting too slow - workspace recreation helped
Since I lose window/toolbar layout settings (even if export/import prefs) and other useful things when I recreate the workspace I want to find out which files I can clean?
I've raised a bug with GWT..
Another answer which really solved it in my case.
Is it possible that you are operating behind a proxy which has to be configured in Preferences->General->Network Connections (e.g. for installing plugins)?
That's true in my case but I had deactivated the proxy settings to reach the in-house SVN. As it seemed, the Validation routine always tries to download ui binder XSDs without success which takes a lot of time.
Concerning my comment in my first answer: yes, it run a lot faster after reinstallation but the reason was that I had to activate the proxy settings for reinstallation. Once I deactivated it again for an SVN commit, it ran slow again ;-)
I have similar problems with Eclipse (Indigo Service Release 1 Build id: 20110916-0149)
and the GWT plugin. Especially when starting Eclipse, Validating the GWT components in my project takes ages.
Googling revealed that the GWT designer in combination with a 64Bit Eclipse Indigo causes this issue.
http://code.google.com/p/google-web-toolkit/issues/detail?id=6602
I wil try to reinstall the GWT plugin without Designer.
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.