Well... Any other solution would change the result. If for example we set this
to pessimistic locking, we would have contentions. I think it would be worse.
If you find any other solution, please let me know!
thanks,
Clebert
View the original post :
Thank you, Clebert, for looking at this problem.
It looks like this java exception is a timing related issue. I found there is
1/3 of chance the exception would not appear when the injection rate is low,
e.g 1. But if I increase the injection rate to 10, I run into it everytime.
If the
It's funny, because I was running in the same problem. (Coincidence, isn't?)
I talked to Alexey who was working with Specj2002 here at JBoss, and he told me
that this is okay, because this is the sequence generation and the application
tries to recover it based on number for tries.
I wanted to
Have you take a look at www.spec.org lately?
09/24/2004 The SPECjAppServer2002 expiration date has been extended by three
months from the original date of October 27; submissions will now be accepted
for review and publication until January 26, 2005.
Clebert Suconic
View the original post :
Clebert,
After I changed those ; to : and recompiled the package, it works. Thank you.
I think the original Benchmark developer worked on Windows system, so ';' was
used to separate classpath. but on Unix, ':' should be used.
I run into another problem, does it ring a bell again?
My test
I had this same problem when running the driver into linux.
It was and wasn't related to classpath.
At jboss32.env at /config directory you have the Classpath line.
The default file has ; instead of :
That makes the driver.sh read some variables wrongly at jboss32.env what make
it fail.
