As xrg says, this is not a bug. It is expected that connecting to a service using the wrong protocol will fail. Actually a service that would respond is such a situation should be considered as buggy.
** Changed in: openobject-server Status: New => Invalid ** Changed in: openobject-server Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework) -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/785009 Title: Server stop responding on xmlrpc service with port 8070(if netrpc service running on this port) Status in OpenERP Server: Invalid Bug description: Server version: 6.0.2, revision: 3426 When server is running on default ports(8070 NET-RPC, 8069 XML-RPC). If I connect to server with xmlrpc service and port 8070. Server stop responding. This is working in earlier version 5.0 of OpenERP server(Responds with error). You can test it with following code for localhost in python terminal. import xmlrpclib sock = xmlrpclib.ServerProxy('http://localhost:8070/xmlrpc/db') sock.list() Same bug can be generated in gtk-client with 8070 port and protocol 'XML-RPC'. _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : c2c-oerpscenario@lists.launchpad.net Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp