When I start up the asemon_logger logger for Sybase ASE 15.5 server, it all works except for one error:
2017/01/31 09:59:26.287 main - parseMetricFile : (/home/sybasesa/scripts/sybase/sladebe/asemon_logger/conf/DeadLock.xml) java.lang.StringIndexOutOfBoundsException: String index out of range: -13
java.lang.StringIndexOutOfBoundsException: String index out of range: -13
at java.lang.AbstractStringBuilder.substring(AbstractStringBuilder.java:935)
at java.lang.StringBuffer.substring(StringBuffer.java:480)
at asemon_logger.MetricDescriptor.parseArchiveMDA(MetricDescriptor.java:219)
at asemon_logger.MetricDescriptor.parseMetricFile(MetricDescriptor.java:389)
at asemon_logger.MetricDescriptor.loadMetricFile(MetricDescriptor.java:481)
at asemon_logger.Config.loadMetricdescriptor(Config.java:500)
at asemon_logger.Asemon_logger.main(Asemon_logger.java:530)
I've attached the corresponding Deadlock.xml file being used.
Unfortunately, the error message doesn't specify what string or what line has the problem in the XML file.
Thanks in advance
Ben Slade
Bethesda MD, USA
Anonymous
Hi Benjamin,
I don't see any diff between your Deadlock.xml.txt file and mine (V3.0.4) except it is in DOS format (CR/LF at end of lines, rather than LF) May be it is just due to the .txt you sent me, and the original file is in UNIX format (did you just renamed the file ?) Can you check ? All config files must be in UNIX format.
What is your Java version ?
What is your asemon_logger version ?
Best regards
JPM
View and moderate all "support-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Support Requests"
The original DeadLock.xml is regular ascii text with normal Linux LF line
endings. Yes, I renamed the file when I sent it to you to prevent
intelligent tools from trying to parse the XML.
My Java version is 1.8.0_121
This is not critical/urgent. It's just frustrating to me that the Java
libraries aren't able to give some hint of what was out of range.
If it would be helpful, I could add some println statements just
before MetricDescriptor.java, line 219 (but I have to figure out how to
recompile the .java files)
Ben Slade
Bethesda MD, USA
On Tue, Jan 31, 2017 at 10:24 AM, Jean-Paul Martin jpm-jpm@users.sf.net
wrote:
Related
Support Requests: #12
Hi,
I recompiled and tested with jdk 1.8.0_121. I have no error.
Download V3.0.4a and test if you still have error
You can activate debug 105 (asemon_logger ... -d 105) You'll get string before row 219
Anyway you can try rebuild asemon wiith the script "build.bat " or "build.sh"
Best regards
JPM
View and moderate all "support-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Support Requests"
I've downloaded/extraced v3.0.4a. When I run build.sh, I get the error
(directory names edited for privacy):
myhost[5:27pm] ~mylogin/asemon_logger> ./build.sh
Ben Slade
Kensington, MD
On Mon, Feb 6, 2017 at 3:49 AM, Jean-Paul Martin jpm-jpm@users.sf.net
wrote:
Related
Support Requests: #12
Ok, directories "build" and "build/classes" must be created before runing build.sh, and the final library must be name "Asemon_logger_V3.jar" rather than "Asemon_logger.jar"
Find attached a new version of the build.sh containing these changes
Regards
JPM
View and moderate all "support-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Support Requests"
Got it to compile, and ran it with the -d 105" debug option.. but it looks
like the contents of "ct" were empty (null or zero length string?).
I verified this by putting delimiting slash characters before and after the
printing of "aArchive_table.createTable" in the DBG105 debug line
(MetricDescriptor.java line 220).
Here's the output, including some debug output before and after because it
looks like some threading is doing multiple things at the same time:
2017/02/08 14:26:38.468 main - DEBUG - parseMetricFile.
On Tue, Feb 7, 2017 at 5:56 AM, Jean-Paul Martin jpm-jpm@users.sf.net
wrote:
Related
Support Requests: #12
Ok, I found the problem : the "DeadLock.xml" file is bad !!!
I didn't see the problem before because I test asemon mostly with ASE 15.7 and 16 and no longer with previous versions. It seems you are using a ASE version older than 15.7 and in that case the "DeadLock.xml" file is used rather than "DeadLock_V157.xml".
In "DeadLock.xml" I left a bad sequence of xml tags which produce the error when it is loaded.
So, find attached the correct version on "DeadLock.xml"
Thanks for signaling this error
Best regards
JPM
View and moderate all "support-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Support Requests"
That was it! Thanks very much for all your help.
FYI, we'll be upgrading to ASE 16 later in the year.
Ben Slade
Senior DBA @ NCBI.NLM.NIH.gov
Bethesda, MD USA
On Thu, Feb 9, 2017 at 4:39 AM, Jean-Paul Martin jpm-jpm@users.sf.net
wrote:
Related
Support Requests: #12