Yes, I am aware of the problem, and they will be fixed in the next release, which will be out hopefully by the end of this month.
Otherwise the messages do not affect the game.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any date scheduled for the next release yet? Anxious to start testing it out and trying to see if I can get the MySQL Connector-J working w/ it as well.
-- M
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Upgraded to 2.3.1 & installed JDK 1.5. I still get these messages in the javamud.log file:
[09:29:06pm] (0) get_login(): lib/player#397
Error: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1774)
at java.lang.String.substring(String.java:1741)
at javamud.utils.utils.read_passwd(utils.java:1059)
at javamud.client.client.get_login(client.java:873)
at javamud.client.client.run(client.java:1665)
at java.lang.Thread.run(Thread.java:595)
And
[04:48:06am] (0) get_login(): lib/player#1258
Error: java.lang.NullPointerException
java.lang.NullPointerException
at javamud.incoming_stream.read_line(incoming_stream.java:28)
at javamud.client.client.get_login(client.java:710)
at javamud.client.client.run(client.java:1665)
at java.lang.Thread.run(Thread.java:595)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any idea why the Prolog errors still appear? Last I heard it might be something of an XML file not being in the correct format, thus the errors are reported.
-- M
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I use the start.sh, I see a number of these messages showing up:
[Fatal Error] :1:1: Content is not allowed in prolog.
Is there a way to fix or suppress these mesages?
Yes, I am aware of the problem, and they will be fixed in the next release, which will be out hopefully by the end of this month.
Otherwise the messages do not affect the game.
Any date scheduled for the next release yet? Anxious to start testing it out and trying to see if I can get the MySQL Connector-J working w/ it as well.
-- M
Yes, i think i will be able to fix it by the end of this month.
The next release will be 2.3.1, which has a few enhancements.
regards
Could you post some stacktrace logs, so i can find the XML fragment that is causing the problem?
regards
Upgraded to 2.3.1 & installed JDK 1.5. I still get these messages in the javamud.log file:
[09:29:06pm] (0) get_login(): lib/player#397
Error: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1774)
at java.lang.String.substring(String.java:1741)
at javamud.utils.utils.read_passwd(utils.java:1059)
at javamud.client.client.get_login(client.java:873)
at javamud.client.client.run(client.java:1665)
at java.lang.Thread.run(Thread.java:595)
And
[04:48:06am] (0) get_login(): lib/player#1258
Error: java.lang.NullPointerException
java.lang.NullPointerException
at javamud.incoming_stream.read_line(incoming_stream.java:28)
at javamud.client.client.get_login(client.java:710)
at javamud.client.client.run(client.java:1665)
at java.lang.Thread.run(Thread.java:595)
Thanks for the error report. I will look into it later today.
regards
Istvan David
Just wondering if here is any idea when the next update would be available. I am learning Java and would like to take a look at the next release.
I hope at the end of this month.
Some bugs have been fixed and other enhancements added.
br
Istvan
Any idea why the Prolog errors still appear? Last I heard it might be something of an XML file not being in the correct format, thus the errors are reported.
-- M
It seems that i managed to fix the prolog messages from appearing by creating a custom ErrorHandler which will not display anything.
The bugs fixed were:
- #899773 : XML error during driver startup.
- #1074975 : Prolog Errors in fault.txt
For the list of the files changed, see the bug fixes above.
The fix will be included in build 2.3.7 or it is available by checking out the HEAD in CVS.
Cool deal. Thanks!
-- M