Task #4626 (closed)
Opened 14 years ago
Closed 13 years ago
Bug: new LDAP password usage causes exception
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | major | Milestone: | OMERO-Beta4.3 |
Component: | Security | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2011-05-05 (11) |
Description
Wrapped Exception: (org.springframework.jdbc.UncategorizedSQLException): Hibernate operation: could not insert: [ome.model.meta.ExperimenterGroup]; uncategorized SQLException for SQL [insert into experimentergroup (description, external_id, permissions, name, version, id) values (?, ?, ?, ?, ?, ?)]; SQL state [25006]; error code [0]; ERROR: transaction is read-only; nested exception is org.postgresql.util.PSQLException: ERROR: transaction is read-only
Change History (5)
comment:1 Changed 14 years ago by jmoore
comment:2 Changed 13 years ago by jmoore
- Owner set to jmoore
comment:3 Changed 13 years ago by jmoore
- Sprint set to 2011-05-05 (11)
- Status changed from new to accepted
comment:4 Changed 13 years ago by jmoore
There doesn't seem to be a straight-forward way from preventing the ERROR message other than silencing them in log4j (which would have other implications). Instead, we can introduce a new argument to many of the server-side method signatures (..., boolean readOnly) to stop the creation of the LDAP user for a @Transactional(readOnly=true) thread.
comment:5 Changed 13 years ago by jmoore <josh@…>
- Remaining Time set to 0
- Resolution set to fixed
- Status changed from accepted to closed
(In [ef01915b3970c5934c6c0694363d7108e6acc8c1/ome.git] on branch develop) Prevent ERROR log on LDAP login which creates new user (Fix #4626)