Forum Discussion
richie
4 years agoCommunity Hero
Hey prometheus,
So you have REST API and youre attemping to poke the endpoint via HTTPS rather than HTTP, but when you submit the REST request youre getting an error response that reads something like as follows:
"the definition of URL couldn't import and parsed successfully."
Is my understanding correct?
If it is correct, where is this error response being reported? In the ReadyAPI logs / Error log?
If im not correct could you please clarify? Im sorry im making you repeat yourself.
Regarding jdbc. JDBC stands for java database connectivity and is the java version of odbc and is the.wrapper that includes driver and other stuff to enable connecting to a database and querying (using SQL) a database.
You only need to setup a JDBC connection if you are gonna be using SQL to query a database directly (so either creating, updating, deleting or retrieving data). You do NOT need to setup a JDBC connection if, for example you are making changes to a database (e.g. creating, updating, deleting, or retrieving) but the changes are done via HTTP methods (create=POST, update=PUT/PATCH, delete=DELETE, retrieve data=GET), so from what youve described, i cant see why youd need a JDBC connection
From what you said it appears you piped the logging to output the logging to a log file (is that right?) so you can see whats going on in the logging.
The error log indicates a resource attempting to be updated, but couldnt be updated due to some pessimistic locking.
Exactly what did you do immediately before this log was generated?
The logging reports the db error relates to an h2 database. Is the system youre trying to hit (via the REST endpoint) supported by an h2 database?
Again this brings me back to needing more information. You havent mentioned a database before. Also id be surprised if the ReadyAPI logging included an external database connection issue....making me wonder if this is actually an internal component that supports ReadyAPI itself.
If you could lay everythjnt out in words of 1 letter so people with very small brains can understand, im sure we can nail this down. I juat need a lot more specific info to ensure i understand properly.
Cheers,
Rich
So you have REST API and youre attemping to poke the endpoint via HTTPS rather than HTTP, but when you submit the REST request youre getting an error response that reads something like as follows:
"the definition of URL couldn't import and parsed successfully."
Is my understanding correct?
If it is correct, where is this error response being reported? In the ReadyAPI logs / Error log?
If im not correct could you please clarify? Im sorry im making you repeat yourself.
Regarding jdbc. JDBC stands for java database connectivity and is the java version of odbc and is the.wrapper that includes driver and other stuff to enable connecting to a database and querying (using SQL) a database.
You only need to setup a JDBC connection if you are gonna be using SQL to query a database directly (so either creating, updating, deleting or retrieving data). You do NOT need to setup a JDBC connection if, for example you are making changes to a database (e.g. creating, updating, deleting, or retrieving) but the changes are done via HTTP methods (create=POST, update=PUT/PATCH, delete=DELETE, retrieve data=GET), so from what youve described, i cant see why youd need a JDBC connection
From what you said it appears you piped the logging to output the logging to a log file (is that right?) so you can see whats going on in the logging.
The error log indicates a resource attempting to be updated, but couldnt be updated due to some pessimistic locking.
Exactly what did you do immediately before this log was generated?
The logging reports the db error relates to an h2 database. Is the system youre trying to hit (via the REST endpoint) supported by an h2 database?
Again this brings me back to needing more information. You havent mentioned a database before. Also id be surprised if the ReadyAPI logging included an external database connection issue....making me wonder if this is actually an internal component that supports ReadyAPI itself.
If you could lay everythjnt out in words of 1 letter so people with very small brains can understand, im sure we can nail this down. I juat need a lot more specific info to ensure i understand properly.
Cheers,
Rich
Related Content
- 2 years ago
Recent Discussions
- 5 days ago
- 9 days ago