c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <588380@xxxxxxxxxxxxxxxxxx>]

Hello Ruud,

In order to be able to analyze this issue, could you reproduce it while
the server's log level is set to debug_rpc (--log-level=debug_rpc) and
post the actual exception that occurs, so we can find out what exactly
is happening?

Without more debugging info we won't be able to investigate, as the
scenario you describe works perfectly for us.

Thank you!

** Changed in: openobject-server
       Status: New => Incomplete

-- 
database connection refused with 2 databases
https://bugs.launchpad.net/bugs/588380
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Incomplete

Bug description:
Consider the following scenario:

Restart the server
Connect with the server using database db1
Connection OK, server log:
  [date] INFO:web_service:successful login from 'admin' using database 'db1'
Disconnect from the server
Connect with the server using database db2
Connection OK, server log:
  [date] INFO:web_service:successful login from 'admin' using database 'db2'
Disconnect from the server
Connect with the server using database db1
Connection NOT OK!!, server log:
  [date] INFO:web_service:successful login from 'admin' using database 'db1'
  /usr/local/lib/python2.6/dist-packages/openerp-server/tools/misc.py:750: DepreciationWarning: BaseException.message has been deprecated as of Python 2.6
   if hasattr(e, 'message'):
  /usr/local/lib/python2.6/dist-packages/openerp-server/tools/misc.py:751: DepreciationWarning: BaseException.message has been deprecated as of Python 2.6
   return ustr(e.message)

and the connection is refused.

Apparently, there is some state change in the server which makes the depreciation message appear only the second time. By the way, it is still possible to connect to db2.

Server version has been updated to the latest stable version 2057.

db1 and db2 have been updated with the latest addons.

db1 uses the following modules:
 account, account_balance, account_chart, account_followup, account_invoice_layout, account_payment, account_report, account_reporting, account_tax_include, base, base_contact, base_iban, base_partner_relation, base_setup, base_vat, board, board_account, board_document, crm, document, hr, hr_attendance, hr_expense, hr_timesheet, hr_timesheet_invoice, l10n_ch, l10n_ch_chart_c2c_pcg, mrp, process, product, profile_accounting, project, project_grid, purchase, report_account, report_analytic, report_analytic_line, report_document, sale, stock, wiki

db2 uses the following modules:
 account, account_chart, account_followup, account_invoice_layout, account_invoice_payment_term, account_payment, account_report, account_reporting, account_tax_include, base, base_contact, base_iban, base_partner_relation, base_setup, base_vat, board, board_association, crm, crm_configuration, event, hr, hr_expense, l10n_ch, l10n_ch_chart_crc_pcg, label, membership, process, product, profile_association, project, report_crm, tennis, use_control

Note: tennis is a simple, custom module.