|
| Re: string index error when launching app within TPTP profiler [message #916669 is a reply to message #915565] |
Wed, 19 September 2012 09:42   |
 Heiner Westphal
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hello Jean,
what I can see is, that Repast Simphony tries to call substring with an
index of -1 on something.
Without a single line of tptp in the stacktrace, it is hard to guess,
how "launching via TPTP" makes this happen.
You should check the file servicelog.log in the config folder of your
TPTP-Agent to see if the agent had some trouble loading the app.
If that log is too terse, change the logging level DEBUG in
<install directory>/config/serviceconfig.xml and give it another try.
Best regards,
Heiner
Am 17.09.2012 16:40, schrieb Jean Le Fur:
> Hello, I run a simulation model (using repast-Simphony 2)within eclipse.
> The application runs fine but when I schedule it within TPTP, I get an
> error message from the application of the type below. I see that there
> may be a problem at the level of WatcheeInstrumentor but I do not know
> where to search for the error: does TPTP defines watch annotations or
> produce any config file or else (this error might occur when the
> instrumentor is recursing into directories to look for @Watch annotated
> classes.
> On an other side, the error is of the type "string index out of range",
> could it be linked to a specific directory or jar not properly adressed
> when TPTP launches?. Any suggestion ? sincerely, Jean
|
|
|
|
| Re: string index error when launching app within TPTP profiler [message #917532 is a reply to message #916790] |
Thu, 20 September 2012 07:04 |
Heiner Westphal
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hello Jean,
what I forgot to suggest was Logging format "Simple".
The default log format is common base event (CBE), which is intended for
interpretation by software. I find it difficult to read.
(I am only human :) ).
Given the number of lines in the log, I suspect the launch itself
worked.
From the Agent's point of view, this is just a fork of the jvm,
which is happy with its parameters and exits with zero.
The agent does look into the jvm there - IIRC.
Another possibility is, that TPTPdid not understand the Logging-config
and fell back to defaults (e.g. level="Debug", oder "debug" might not work).
Perhaps you try something like:
<Logging directory="%TPTP_AC_CONFIG_HOME%" format="Simple" level="DEBUG"/>
If this does not change anything, I see three other approaches to get
some more info:
a) Enable fine grained logging within Repast-Simphony
b) Look into the sources of Repast-Simphony.
Possibly remote debugging and connecting before tptp
times out helps as well.
c) Add jvm-parameters, that show which classes are loaded.
Compare the output with and without TPTP.
This may sound like a Herkules-task, but if you use some of the good
old unix-tools like sort and comm, you can gain a quick overview of
the differences within an hour.
Hope this helps,
Heiner
Am 19.09.2012 15:15, schrieb Jean Le Fur:
> Hello Heiner,
> thank you for this quick answer.
> I changed the logging level to DEBUG and obtained the attached servicelog.log. Unfortunately I am not used to these messages. Do you think it sheds any light on the problem ?
> sincerely,
> Jean
>
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09126 seconds
] 
Search
Help
Register
Login
Home
