Trac - Server committed a protocol violation

[DragDen]

Good day, everyone!

I am trying to configure Plastic SCM integration with an issue tracker Trac. I have Plastic SCM server installed on one PC (Win10x64) and a Trac server installed on virtual machine (Win7 SP1). Trac server has XML-RPC installed, enabled and added to permission list of every user. But every time I press Test Connection in Plastic configuration window:

• Server console returns multiple "code 400, message Bad HTTP/0.9 request type ('<?xml')"
• After about 15 seconds Plastic shows error message: "Test connection failed. Please review entered values. Server committed a protocol violation. Section=ResponseStatusLine"

I've included a screenshot of Plastic settings concerning issue tracker integration. URL is reachable if I put it into browser, and I can login into Trac using the username and password I provided in this window.

The Trac server is launched with the following command: tracd --port 8080 --basic-auth="GameManager,C:\Trac\GameManager\conf\auth-basic.txt,trac" C:\Trac\GameManager

Considering that all instructions I found on the Internet are more than five years old, is the compatibility with Trac still maintained? If so, can you please help me resolve this problem?

 

Plastic version: 8.0.16.2951

Trac version 1.2.3

XML-RPC version 1.1.7

Also, here's a stacktrace from plastic.debug.log:

2019-01-31 18:50:08,233 DERON\DragDen ERROR PlasticThread - Error when performing background operation: Server committed a protocol violation. Section=ResponseStatusLine
2019-01-31 18:50:08,233 DERON\DragDen DEBUG PlasticThread - Stack trace:    in Codice.Client.IssueTracker.Trac.TicketResolver.TestConnection(ITicketHandler tckHandler, Int32 ticketId)
   in Codice.Client.IssueTracker.Trac.TracExtension.TestConnection(IssueTrackerConfiguration configuration)
   in ts.a.a()
   in Codice.Client.Common.Threading.PlasticThread.ThreadWork(Object state)

[DragDen]

Um, anyone?

[calbzam]

Hi, sorry for the delay, there may be a compatibility issue with the last Trac version. We will run some tests to try to debug the issue.

Regards,

Carlos.

[calbzam]

I've been having some issues to run the last Trac version for Windows. Are you using the Bitnami installer?

https://trac.edgewall.org/wiki/BitNami

Anyway, checking your error, the plugin may not be compatible with the last Trac version.

Could you check if the following solution helps? https://stackoverflow.com/questions/2482715/the-server-committed-a-protocol-violation-section-responsestatusline-error

Regards,

Carlos.

[DragDen]

Hello!

Hm, it's been some time... As far as I remember, I've used this method: https://trac.edgewall.org/wiki/TracInstall#Usingeasy_install

For that to work, I had to install python 2.7: https://www.python.org/downloads/release/python-2716/

Then I installed the wheel package of setuptools-40.7: https://pypi.org/project/setuptools/#files

by following this instruction https://packaging.python.org/tutorials/installing-packages/#requirements-for-installing-packages

Finally, I also needed the package XML-RPC, here's the instructions how to install and configure it: https://trac-hacks.org/wiki/XmlRpcPlugin#SimpleInstallation

 

As for that solution, if I understand correctly, you meant adding that node to web.config? The closest to that file I could find was Program Files\PlasticSCM5\server\plasticd.exe.config. However, after adding that node and restarting Plastic Server service, that error still remained

However, while trying that, I've discovered something interesting. If I start Trac server and then try to press Test Connection in Plastic, it won't even be able to connect to Trac (no messages in Trac server console), and will give Timeout error after about a minute. However, if I visit Trac server url with my browser first, and then press Test Connection - only then will those errors in Trac console start appearing.