I am using docker to deploy and run my application. Everything is fine during deployment and running my application.I am using dockerDeploy and restartWas commends in order to deploy and run my application.
After I run my application , my login and password comes to my screen. Everything is fine at that step as well but after I write my login and password, I come across with the error below. I did not change anything in the code but after I restart docker I come across with the following error.
I restarted docker and also computer several times but I still come across with that. I would be glad if you can help me.
Regards
Error Page Exception
SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below.
Original Exception:
Error Message: SRVE0190E: File not found: {0}
Error Code: 404
Target Servlet:
Error Stack:
com.ibm.ws.webcontainer.webapp.WebAppErrorReport: SRVE0190E: File not found: {0}
I'm running grails 2.5.4(I cannot upgrade the version), it successfully runs in my IDE (intellij) but I cannot get any grails command to run from the terminal. Even if I type just "grails" and nothing else, it will throw an error.
The error is:Exception: java.lang.StackOverflowError thrown from the UncaughtExceptionHandler in thread "main"
I can't seem to get anymore information out of it with --verbose
Also, I am running java 8
so I found out what was going on through excessive trial an error. The issue was that I had db2 installed on my machine. I don't know why that was causing the issue. But for anyone that might be running into this issue, that's what the problem was for me.
We had the same problem; in our case, all it took was an empty .inputrc file in the user's home directory to make grails work.
I unpacked the tar file of Neo4j linux version.
When running the server (./bin start) it seems like the server is up, but I cant access the browser (although I get a message it is ready).
Running the console (./bin console) - returns an error: "Error: Could not find or load main class org.neo4j.server.CommunityEntryPoint"
Did anyone also encountered this issue? How can I solve this?
Thank you
How did you run ./bin console? I'm curious since such a thing does not exist.
To start up the database you use bin/neo4j start - then you point your browser to localhost:7474.
For command line based access use bin/neo4j-shell.
This is the error i am getting from mod_mam, i need help to understand this
Error Log :
[error] <0.27129.40> CRASH REPORT Process <0.27129.40> with 0 neighbours exited with reason: {process_limit,{max_queue,5590}} in p1_fsm:terminate/8 line 755
2015-12-07 07:25:47.714 [error] <0.336.0> Supervisor ejabberd_c2s_sup had child undefined started with {ejabberd_c2s,start_link,undefined} at <0.27129.40> exit with reason {process_limit,{max_queue,5590}} in context child_terminated
2015-12-07 07:25:53.209 [error] <0.479.0>#gen_iq_handler:process_iq:128 {badarg,[{erlang,binary_to_atom,[null,utf8],[]},{jlib,binary_to_atom,1,[{file,"src/jlib.erl"},{line,934}]},{mod_mam,'-select/8-fun-2-',3,[{file,"src/mod_mam.erl"},{line,675}]},{lists,map,2,[{file,"lists.erl"},{line,1237}]},{mod_mam,select,8,[{file,"src/mod_mam.erl"},{line,669}]},{mod_mam,select_and_send,10,[{file,"src/mod_mam.erl"},{line,569}]},{gen_iq_handler,process_iq,6,[{file,"src/gen_iq_handler.erl"},{line,127}]},{gen_iq_handler,handle_info,2,[{file,"src/gen_iq_handler.erl"},{line,171}]}]}
This is related with querying archive due to lack of my knowledge of erlang i am not able to understand.please help me to understand this .
Reason for the first error is that your service is overloaded:
{process_limit,{max_queue,5590}
Note that ejabberd process_limit error message is about a per process limit of the number of message in the queue. This is to avoid having a slow process or message receiver take all server resources.
It has nothing to do with Erlang number of allowed process per node.
Regarding your second error in logs, I guess this is because you have upgrade your instance from older version and have old messages in archive. We improved the code of ejabberd to support the old stored messages.
This is already committed in ejabberd head and fix will be published in ejabberd 15.12 release.
I am trying to package up a mixed Python/C++ application using py2app. My setup.py is
from setuptools import setup
setup(app=['voxpopuli.py'],data_files=[],options=
{'py2app'{'argv_emulation':True}},setup_requires=['py2app'])
and I invoke py2app via
python setup.py py2app --no-strip --iconfile /Users/irving/otherlab/other/bin/OLicon.icns --resources /opt/local/lib/Resources/qt_menu.nib
This completes without warnings or errors, but when I try to run the resuling app a window pops up that simply says "voxpopuli Error". It has an "Open Console" button, but the only console messages are
9/21/12 11:43:14.691 AM voxpopuli[52765]: voxpopuli Error
9/21/12 11:43:15.926 AM com.apple.launchd.peruser.501[158]: ([0x0-0x177d77c].org.pythonmac.unspecified.voxpopuli[52765]) Exited with code: 255
Are there standard ways to get more information out of py2app to help diagnosing this error?
I believe this is a problem with the app rather than the py2app.
If the app hits an unhandled exception it will exit out like this. Which version of osx are you using? In 10.8 they stopped automatically forwarding stderr to the console, so might be an idea to pipe the applications stdout and stderr to a file to see if you have a stack trace.
Although if it's an error in the C++ part I'm guessing you wouldn't see a stack trace, but the error could be in that part of the application.
If you really can't find the issue, try stripping large parts out the app until it runs then add bits back in until it doesn't run, then strip etc. (like a binary search) to try and find the offending part.
With the package built you can still run the 'application' from the command line.
For example for your project in ~/Projects/MyApp built into folder ~/Projects/MyApp/dist you should find you can run the following from commandline: ~/Projects/MyApp/dist/MyApp.app/Contents/MacOS/MyApp
This will output all the normal stderr messages to the console so you can see what is going wrong.