[MAGNOLIA-1959] Leopard (osx 10.5) issues Created: 11/Dec/07 Updated: 15/Dec/09 Resolved: 15/Dec/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
Leopard's application level firewall :Leopard's (OSX 10.5) firewall behaves significantly differently than the firewall shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable ("kCFErrorDomainCFNetwork:302"), but unfortunately no log message clearly identifies the issue. We've tried a bunch of variations on the firewall settings, but nothing really help. SolutionWell, it's pretty simple! Update to OSX 10.5.8 ! If you're using Snow Leopard, the issue was also present until 10.6.1, but is fixed as from 10.6.2 ! Some interesting links:
"Max.files opened"There might be some "max.files opened" issues, with settings which are different from Tiger(10.4), although this hasn't been reported in a while. |
| Comments |
| Comment by Magnolia International [ 30/Jul/08 ] |
|
– edited issue description and cleaned up comments for clarity and usefulness. |
| Comment by Philipp Bracher [ 05/Feb/09 ] |
|
Thought I share that with you. Quoted from: http://db.tidbits.com/article/9294
An other article saying the same: http://www.heise-online.co.uk/security/Apple-documents-Leopard-firewall-functionality-and-holes--/news/98695
So the application might indeed be blocked by the fact that we write into the repository or change files in the webapp. None of the articles tells clearly how one can get rid of that behavior. |
| Comment by Philipp Bracher [ 05/Feb/09 ] |
|
Consequently I tried to move the website outside of tomcat which didn't help at all. |
| Comment by Philipp Bracher [ 05/Feb/09 ] |
|
It seems to work nicely if one has only one instance (a author or public instance) in the webapp. This might also point to something else than the firewall (to many open files, sockets, to many threads, ..). It is also suspicious that not all requests are blocked. |
| Comment by Boris Kraft [ 05/Feb/09 ] |
|
I have installed two tomcat instances, one with public and one as author and this works without the above issues.
|
| Comment by Tom Wespi [ 05/Feb/09 ] |
|
See http://discussions.apple.com/thread.jspa?threadID=1449787&tstart=195 After this two instances are starting fine. osx 10.5.6 |
| Comment by Boris Kraft [ 05/Feb/09 ] |
|
we might want to add this to the magnolia-control script for osx (if it works) |
| Comment by Christian Ringele [ 05/Feb/09 ] |
|
The "limit maxfiles 4096 unlimited" value didn't help on my machine at all. |
| Comment by Philipp Bärfuss [ 15/Oct/09 ] |
|
Seems as if the so called 'firewall' issue has disappeared with Magnolia 4.1.1 and OSX 10.5.8. In case you still encounter such problems please let us know. |
| Comment by Philipp Bärfuss [ 15/Dec/09 ] |
|
The issue is not occurring anymore on the latest OSX versions: 10.5.8 and 10.6.2 |