Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 827455

Summary: Runtime Error Could not execute JDBC batch update
Product: [Retired] Subscription Asset Manager Reporter: Jakub Dorňák <jdornak>
Component: katelloAssignee: Bryan Kearney <bkearney>
Status: CLOSED WORKSFORME QA Contact: SAM QE List <sam-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: esammons, hhorak, tomckay
Target Milestone: rcKeywords: Triaged
Target Release: 1.X   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-24 19:09:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 816564    
Attachments:
Description Flags
RuntimeError.png none

Description Jakub Dorňák 2012-06-01 14:10:48 UTC
Created attachment 588475 [details]
RuntimeError.png

Description of problem:

Unhandled runtime error may appears in web UI.
I wanted to add new Organization, when I got:

{"displayMessage":"Runtime Error Could not execute JDBC batch update at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError:2,573"}

(see attachment)

Version-Release number of selected component (if applicable):
SAM-2012-05-25.1

How reproducible:
I haven't manage to reproduce this situation,

Comment 2 RHEL Program Management 2012-06-01 14:19:49 UTC
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Subscription Asset Manager (SAM). Unfortunately,
we are unable to address this request. Because we are in the final stages
of development in the current release, only significant, release-blocking
issues involving serious regressions and data corruption can be considered.

If you believe this issue meets the release blocking criteria as defined and
communicated to you by your Red Hat Support representative, please ask
your representative to file this issue as a blocker for the current release.
Otherwise, ask that it be evaluated for inclusion in the next release of SAM.

Comment 3 RHEL Program Management 2012-06-01 14:48:31 UTC
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Subscription Asset Manager (SAM). Unfortunately,
we are unable to address this request. Because we are in the final stages
of development in the current release, only significant, release-blocking
issues involving serious regressions and data corruption can be considered.

If you believe this issue meets the release blocking criteria as defined and
communicated to you by your Red Hat Support representative, please ask
your representative to file this issue as a blocker for the current release.
Otherwise, ask that it be evaluated for inclusion in the next release of SAM.

Comment 4 Tom McKay 2012-10-24 19:09:57 UTC
Closing, please re-open if this happens again.