generated report.xml contains time=.... with too long values

Question

I´ve invoked the SoapUIProTestCaseRunner during a Maven Build with the '-j' option, that generates JUnit-compatible reports.

This works fine, but the report.xml looks like:
...

...

this very long time information causes another plugin to crash:

org.hibernate.exception.DataException: could not insert: [org.codehaus.mojo.dashboard.report.plugin.beans.SurefireReportBean]
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:77)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2202)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2595)
at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:51)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
at org.codehaus.mojo.dashboard.report.plugin.hibernate.HibernateServiceImpl.saveOrUpdate(HibernateServiceImpl.java:236)
at org.codehaus.mojo.dashboard.report.plugin.DashBoardDBMojo.execute(DashBoardDBMojo.java:79)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.sql.SQLDataException: The resulting value is outside the range for the data type DOUBLE.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.noStateChangeException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setDouble(Unknown Source)
at org.hibernate.type.DoubleType.set(DoubleType.java:36)
at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:83)
at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:60)
at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1932)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2178)
... 31 more
Caused by: java.sql.SQLException: The resulting value is outside the range for the data type DOUBLE.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
... 41 more
Caused by: ERROR 22003: The resulting value is outside the range for the data type DOUBLE.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.iapi.types.NumberDataType.normalizeDOUBLE(Unknown Source)
at org.apache.derby.iapi.types.SQLDouble.setValue(Unknown Source)

=> how can I change the precision of the time attribute?

This information should be round up to 3rd decimal place or something like that.

smartbear_suppo · Answer

Have you tried customising the reports using ant?http://www.soapui.org/userguide/command ... _Exporting/Nenad

torstenreinhard · Answer

the problem is not the generated report, but the report.xml itself, which is exported by soapUI.
The report.xml is read by another plugin, that tries to store its data into a database.
Than, the conversion of the too long 'time=.....' attribut causes the exception shown above.

I think soapUI should "cut" the 'time=....' value.

smartbear_suppo · Answer

Hi!The latest nightly builds of the 3.5 beta should fix this, can you give them a try to see if it works better for you?regards!/oleeviware.com

Forum Discussion

generated report.xml contains time=.... with too long values

3 Replies

Recent Discussions

Save Groovy output to JUnit report

Running ReadyAPI Suite via Command Line / C# took ~ 30 sec to initiate

As of v3.60.0 preloading groovy file from script library breaks cross referencing

Related Content

Generate JSON Schemas

JavaScript - how to get current time but in different time zone(s)

Getting current Time in Specific Time Zone