|
Glenn Engstrand opened 1 decade ago
|
|
Too little information and details to proceed with investigation. If the problem happens from time to time, it might be due to some OS configuration issues like too low number of open files, too short TCP/IP port range or something like this. From time to time the system may run out of this kind of resources and problem occurs. This is just a guess though. Thorough investigation with log analysis is required to find out what really happens. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
257
|
| Version |
tigase-server-5.1.0
|
Issue Votes (0)
Watchers (0)
I have discovered that chrome is not as CORS compliant ( see http://groups.google.com/group/strophe/browse_thread/thread/957f119a5caa9b45 ) as I had hoped so I started using the Apache reverse proxy trick to make the Tigase BOSH end point look like it is on the same origin as the web server. Now I am getting intermittent proxy errors where Apache claims that it is getting an error reading from the remote server. Cannot see anything of relevance in the full debug Tigase logs.
http://ec2-174-129-96-242.compute-1.amazonaws.com:8080/site/news/2011/remote-proxy-errors--1124592511.html
Please advise.