...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<module name="geronimo/rmi-naming/1.1/car">
<gbean name="RMIRegistry">
<attribute name="port">1199</attribute>
</gbean>
<gbean name="NamingProperties">
<!-- Check whether this really works if host name is 0.0.0.0 -->
<attribute name="namingProviderUrl">rmi://0.0.0.0:1199</attribute>
</gbean>
...
<gbean name="JMXService">
<attribute name="protocol">rmi</attribute>
<attribute name="host">0.0.0.0</attribute>
<attribute name="port">9999</attribute>
<attribute name="urlPath">/jndi/rmi://0.0.0.0:1199/JMXConnector</attribute>
</gbean>
</module>
|
...
| Panel | ||
|---|---|---|
| ||
|
You will get the Deployed SPEC/Emulator/1.05/war @ http://geronimo.host:8080/Emulator diagnostic.
...
Sometimes binding exceptions or other problems may occur at the Driver startup. In such a case, interrupt the test run with Ctrl-C and rerun it again. Sometimes it helps.
| Note |
|---|
It's recommended to reload the database tables before each run, particularly if previous run was not finished correctly. Otherwise, errors like this may occur:
No Format bgColor black borderStyle solid
java.rmi.RemoteException: Failure in calling validateInitialValues() java.rmi.RemoteException: Invalid initial Order DB State
at org.spec.jappserver.driver.Auditor.validateInitialValues(Auditor.java:201)
at org.spec.jappserver.driver.Driver.configure(Driver.java:330)
at org.spec.jappserver.driver.Driver.<init>(Driver.java:160)
at org.spec.jappserver.driver.Driver.main(Driver.java:1137)
or
No Format bgColor black borderStyle solid
java.rmi.RemoteException: Failure in calling validateInitialValues() javax.transaction.TransactionRolledbackException: java.sql.SQLException
at org.spec.jappserver.driver.Auditor.validateInitialValues(Auditor.java:201)
at org.spec.jappserver.driver.Driver.configure(Driver.java:330)
at org.spec.jappserver.driver.Driver.<init>(Driver.java:160)
at org.spec.jappserver.driver.Driver.main(Driver.java:1137)
To overcome such problems, you may reload the database tables.
During the run, the following diagnostics may appear in the Driver window:
No Format bgColor black borderStyle solid
During the run, the following diagnostics may appear in the Driver window:
No Format bgColor black borderStyle solid
Error in html org.spec.jappserver.driver.http.SJASHttpException: error while checking html
org.spec.jappserver.driver.http.SJASHttpException: error logging in customer 7308 org.spec.jappserver.driver.http.SJASHttpException: error while checking html
at org.spec.jappserver.driver.http.HttpDealer.login(HttpDealer.java:621)
at org.spec.jappserver.driver.DealerEntry.logIn(DealerEntry.java:935)
at org.spec.jappserver.driver.DealerEntry.loginCtl(DealerEntry.java:880)
at org.spec.jappserver.driver.DealerEntry.doBrowse(DealerEntry.java:790)
at org.spec.jappserver.driver.DealerEntry.run(DealerEntry.java:247)
AbstractSJASLoad> Application error has already been cancelled
AbstractSJASLoad> Application error has already been cancelled
AbstractSJASLoad> Application error has already been cancelled
and in the same time, various TransactionRolledback and other exceptions of the same kind are being printed in the Geronimo shell.printed in the Geronimo shell.
| Warning |
|---|
These diagnostics are probably caused by the fact that TranQL version 1.3 used in Geronimo version 1.1 does not provide the necessary transaction isolation level. Hopefully, this problem will be fixed in TranQL version |
| Warning |
These diagnostics may be normal, but may be errors that invalidate the benchmark results. This still has to be investigated. |
After the run has completed successfuly, you will see the output like this:
...
| Warning |
|---|
For now these values for Geronimo are terribly low (around 1), and don't depend on the hardware being used. Probably this is due to some configuration issues that still exist or due to TranQL issue mentioned above. |
Processing results
...