Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Translating the error in english it says:</p> <pre><code>DSRA9010E: 'setReadOnly' is not supported in the WebSphere implementation java.sql.Connection </code></pre> <p>Which is not a bug, it's simply that they are not implementing read-only. And that is also understandable if using a Connection Pooling because readonly is usually a connection creation scoped attribute.</p> <p>Moreover readonly is only a "suggestion" for the jdbc provider: the jdbc provider can ignore it and as far as I know many providers don't really do anything for it.</p> <p>Simply don't specify readonly.</p> <hr> <p>To answer Sam comment below: Hibernate has nothing to do with that error, it is the Websphere Component implementing <strong>java.sql.Connection</strong> that emits <strong>DSRA9010E</strong> error when using Websphere with Oracle, after June 2003, as explained <a href="http://www-01.ibm.com/support/docview.wss?uid=swg21194913" rel="nofollow"><strong>here</strong></a> by IBM itself about specifically that error code DSRA9010E and description <code>"'setReadOnly' is not supported on the IBM WebSphere Application Server java.sql.Connection implementation"</code>: </p> <blockquote> <p><strong>Resolving the problem</strong></p> <p>In June 2003, there was a change made to the Application Server code defect 168102. Prior to June 2003, the setReadOnly(true) method set an internal flag in Application Server, <strong>but did not convey this information to the Oracle database. In versions after June 2003, Application Server issues the error as described above.</strong></p> </blockquote> <p>My understanding of the entire article is that they added that error later, to resolve the problem, as a solution to defect 168102, for clarity purpose: to let the client know that setting that flag has no effect on the underlying database connection because Oracle is not supporting it.</p> <p>At the end of the article they suggest to upgrade to the latest version (the one that emits the error). </p>
    singulars
    1. This table or related slice is empty.
    1. POSpring ReadOnly Transaction with Propagation.SUPPORTS with WebSphere and Oracle
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTony Rad
    1. USTony Rad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSpring ReadOnly Transaction with Propagation.SUPPORTS with WebSphere and Oracle
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COIs it WebSphere 8 or Hibernate 4 who displays this new warning? I am wondering, because in Tomcat or with Hibernate 3.6 there is no excpetion and no warning in the console.
      singulars
      1. PO
      1. USSam
    2. COI Updated the answer text to answer your comment.
      singulars
      1. PO
      1. USTony Rad
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload