Forum Discussion

Paul_Reichlin's avatar
Paul_Reichlin
New Contributor
15 years ago

JDBC connection related errors in ver. 3.5.1

soapUI version: 3.5.1

Problem: Exception thrown when executing DataSource test step using a Data Connection.
DBMS: Sybase ASE
Driver: com.sybase.jdbc2.jdbc.SybDriver

Exception message:
com.sybase.jdbc2.utils.UnimplementedOperationException: The method com.sybase.jdbc2.tds.RowFormatToken.getTableName has not been completed and should not be called.

Observations:
The command text I've been using has been well-formed and valid. One such example "select db_name()"
This error occurs when Data Source Test Step's "Stored Procedure" checkbox is not checked. I've found that I can successfully execute queries through this test step if I select that checkbox which makes me a little more suspicious of this being a soapUI bug and not a driver issue.

Furthermore, I've done a little bit more poking around, testing with a valid stored procedure call and have found that the behavior is the inverse of what I've described above (and thus, I have to uncheck this checkbox in order to exec the stored procedure).

Have attempted an equivalent test using a JBDC Request test step and I receive the same exception, regardless of the "Stored Procedure" checkbox state.

(Note: This problem appears to be related in nature to this topic http://www.eviware.com/forum/viewtopic.php?f=4&t=3443.)

2 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi,

    For displaying jdbc TestStep results we use ResultSetMetaData interface whose implementation in specific driver seems to be the problem.
    For DataSource we are using some external libraries, so I'm not sure about their implementation, it might be the same problem!
    Do you have the same problem when using JDBC DataSource (not predefined DataConnection)? Could you provide us the error log content for this?

    Regards,
    Dragica
    /eviware.com
  • Paul_Reichlin's avatar
    Paul_Reichlin
    New Contributor
    15 years ago
    Sure. I've attached the full text from the error log.

    Regarding use of the JDBC Request test step (to which I think you were referring), yes, I do have the same problem. The behavior is not identical though in that I cannot sidestep the error by checking the "Is Stored Procedure" checkbox for my select statements. It occurs in both cases.

    Another observation. I've tested the same project in 3.0.1 and the query executes successfully as part of the DataSource step.