-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.IllegalArgumentException: not a boolean : [:] #220
Comments
Actually, I have the features section in my glu-console-webapp.groovy. Can you provide another suggestion? |
Can you post the content of your file? |
Yes, wait a minute to obfuscate the critical data. |
Here is the file.
|
If you want, I can provide version of the mysql jetty library, too. |
Hmmm.. I am a bit puzzled. Your config file looks fine. Could you describe the exact steps you took to go from 4.5.0 to 5.0.0? Maybe that will give me a clue. Also, when I get a chance I will try to reproduce using your config file. A couple of things to check:
|
Actually I found the problem it is the same as this one in Amazon, which I reported 7 or 8 months ago. The console server was not able to find its own hostname. The machine was on included in the DNS records and this lovely java function getLocalHost thrown an exception again. It will be a good idea to investigate what to happen in such condition, maybe you can add some kind of check whether the correct localhost is found? Best, |
I am a bit puzzled that the console would boot if |
Hi sorry for being late, but here was Easter during the last week. Actually, I created DNS server and added a record for console server machine. This solved the problem. I am sure, but this problem can be related to reading the config files via localhost? getLocalHost exception was treated like a WARNING by the jetty server and I am not sure what will be the state of localhost variable in glu after ignoring this warning. |
In regards to the |
As described in the forum thread:
http://glu.977617.n3.nabble.com/Error-on-console-server-upgrade-from-4-5-0-to-5-0-0-td4025673.html
The text was updated successfully, but these errors were encountered: