(Context: Moving a single user tracd to apache server based
solution(linux-sled)).
Everything works fine except mylyn connections over https. With
mylyn/http to trac I get sub-second responses whereas over https I'm
getting 30-50 seconds for each "submit" or "synchronise" in mylyn.
I'm wondering if anyone else has encountered this effect and can offer
any pointers to solutions / debugging etc.
///////////////////
Detail: For a "submit" of a changed ticket in mylyn I see (in the
apache error_log) that 12 HTTPS requests over 50 seconds are made,
(all Initial) e.g.:
...........................
[Wed Dec 17 21:19:07 2008] [info] Initial (No.1) HTTPS request
received
for child 5
:
[Wed Dec 17 21:19:10 2008] [info] [client 192.168.1.36] Connection
closed to child 5 with standard shutdown (server :443)
:
( ... and so on until (end of 12th request)... )
:
[Tue Dec 16 21:19:57 2008] [info] Initial (No.1) HTTPS request
received
for child 9
...........................
For info, when using trac in firefox client and doing e.g. "submit" of
a changed ticket -> response time is sub-second for http and 1 to 2
seconds with https. (for https in error_log there are fewer https
requests and not all are Initial)
Config
-python 2.5
-latest mod_wsgi for apache
-xmlrpc.../trunk for trac
-eclipse 3.4 latest updates -
latest mylyn trac connector
-logtype = stderr
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
