Bug 1314103 - Bugmail serialization error in post_bug.cgi
Summary: Bugmail serialization error in post_bug.cgi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Database
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: 4.4
Assignee: Matt Tyson 🤬
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-02 23:31 UTC by Matt Tyson 🤬
Modified: 2018-12-09 06:29 UTC (History)
6 users (show)

Fixed In Version: 4.4.11050.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-29 00:29:06 UTC


Attachments (Terms of Use)

Description Matt Tyson 🤬 2016-03-02 23:31:48 UTC
This is closely related to bug 1287318

The serialization errors in bug 1287318 were caused by bug updates.  This is caused by bug creation.

UPDATE bugs SET lastdiffed = ? WHERE bug_id = ? at /var/www/html/bugzilla/Bugzilla/BugMail.pm line 324 Bugzilla::BugMail::Send(1313903, 'HASH(0x7ff80dcb6e50)') called at /var/www/html/bugzilla/post_bug.cgi line 259 ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_post_bug_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7ff80db7dc48)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204 eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204 ModPerl::RegistryCooker::run('Bugzilla::ModPerl::ResponseHandler=HASH(0x7ff80d704390)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 170 ModPerl::RegistryCooker::default_handler('Bugzilla::ModPerl::ResponseHandler=HASH(0x7ff80d704390)') called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 31 ModPerl::Registry::handler('Bugzilla::ModPerl::ResponseHandler', 'Apache2::RequestRec=SCALAR(0x7ff80db7dc48)') called at /var/www/html/bugzilla/mod_perl.pl line 134 Bugzilla::ModPerl::ResponseHandler::handler('Bugzilla::ModPerl::ResponseHandler', 'Apache2::RequestRec=SCALAR(0x7ff80db7dc48)') called at -e line 0 eval {...} called at -e line 0

Comment 1 Rony Gong 🔥 2016-03-08 12:11:21 UTC
Verified on build 4.4.11050-2

Could reproduced this error by run below script against the server not upgrade yet, and couldn't happened again when run against the build 4.4.11050-2.

#!/usr/bin/python

import thread
import time
import xmlrpclib

# Define a function for the thread
def print_time( threadName, delay):
   count = 0
   while count < 5:
      time.sleep(delay)
      count += 1
      print "%s: %s" % ( threadName, time.ctime(time.time()) )

def xmlrpc_access( threadName, delay):
   count = 0
   while count < 10:
      time.sleep(delay)
      proxy = xmlrpclib.ServerProxy('https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/xmlrpc.cgi')
#      proxy = xmlrpclib.ServerProxy('https://bzperfweb01.app.qa.eng.nay.redhat.com/xmlrpc.cgi')
      
#      response = proxy.User.login({'Bugzilla_login': 'redhat1', 'Bugzilla_password': '*******'})
      response = proxy.Bug.create({'Bugzilla_login':'redhat1','Bugzilla_password':'*******','summary':'xmlrpc test','product':'Red Hat Enterprise Linux 6','component':'openvswitch','version':'6.8'})
      count += 1
      print "%s: %s: %s" % ( response, threadName, time.ctime(time.time()) )

# Create two threads as follows
try:
   thread.start_new_thread( xmlrpc_access, ("Thread-1", 2, ) )
   thread.start_new_thread( xmlrpc_access, ("Thread-2", 2, ) )
#   thread.start_new_thread( xmlrpc_access, ("Thread-3", 0, ) )
#   thread.start_new_thread( xmlrpc_access, ("Thread-4", 0, ) )
except:
   print "Error: unable to start thread"

while 1:
   pass


Note You need to log in before you can comment on or make changes to this bug.