RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 868447 - Runtime Error Could not execute JDBC batch update at sun.reflect.NativeConstructorAccessorImpl.newInstance0:-2
Summary: Runtime Error Could not execute JDBC batch update at sun.reflect.NativeConstr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 7.0
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2012-10-19 21:38 UTC by Matt Reid
Modified: 2013-10-11 19:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-11 19:36:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matt Reid 2012-10-19 21:38:16 UTC 
Description of problem:
I think I had just clicked on Subscribe to attach a subscription to my system (may have clicked Update though). Instead of it doing that, I got a crazy Runtime error "Runtime Error Could not execute JDBC batch update at sun.reflect.NativeConstructorAccessorImpl.newInstance0:-2" which showed up in our standard error dialog format (check rhsm.log for more info. [Error Message]).

This is the first time I've seen such a message. I was registered to prod, and probably trying to subscribe to the Red Hat Partner, Red Hat Employee, or some 60 day RHEV Eval subscription. I'm not sure if/how we can see the prod logs to get more info...

Here's what I got from my logs - 
2012-10-19 10:54:22,001 [DEBUG] @connection.py:305 - Loading CA certificate: '/etc/rhsm/ca/candlepin-stage.pem'
2012-10-19 10:54:22,001 [DEBUG] @connection.py:305 - Loading CA certificate: '/etc/rhsm/ca/redhat-uep.pem'
2012-10-19 10:54:22,002 [DEBUG] @connection.py:344 - Making request: GET /subscription/consumers/ebec29a8-d801-42f5-b02f-927213870bf8/owner
2012-10-19 10:54:22,847 [DEBUG] @connection.py:357 - Response status: 500
2012-10-19 10:54:22,848 [ERROR] @utils.py:56 - Runtime Error Could not execute JDBC batch update at sun.reflect.NativeConstructorAccessorImpl.newInstance0:-2
    Traceback (most recent call last):
    File "/usr/sbin/subscription-manager-gui", line 48, in ?
    from dbus.bus import REQUEST_NAME_REPLY_PRIMARY_OWNER
    ImportError: No module named bus
2012-10-19 10:54:23,581 [DEBUG] @connection.py:357 - Response status: 200
2012-10-19 10:54:23,588 [DEBUG] @connection.py:323 - Loading CA PEM certificates from: /etc/rhsm/ca/

Not really sure what else I can provide to help, let me know if you need anything. This seems like it could be tough to try and track down.

If it makes any difference, my auto-heal interval was set to 1 at the time :)

Version-Release number of selected component (if applicable):
subscription-manager-1.1.2-1.git.83.76f3b7f

How reproducible:
????
Could be a once in a blue moon thing, not sure how to reproduce
If it happens again, I'll be sure to update this BZ

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 RHEL Program Management 2012-10-19 21:58:12 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 2 Bryan Kearney 2013-10-11 19:36:18 UTC 
Pretty old, and more then likely environmental at the time. Please re-open if you see it again.
Note You need to log in before you can comment on or make changes to this bug.