|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 6323 | minor | always | 02-04-20 01:54 | 02-19-20 13:58 | |
|
|
|||||
| Reporter: | nam | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.63 | ||
| Product Build: | Resolution: | won't fix | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| Summary: | 0006323: cannot enable JniSelectManager on solaris | ||||
| Description: |
(rep by Q. Jian) JniSelectManager fails to initialize with the following message: "JniSelectManager[max=130816] is not available on this system" It looks like it's because the select implemention depends on epoll, which is only supported on Linux. Solaris on the other hand uses "event ports". May want to add a more informative error message. logs: [20-02-04 01:45:28.950] {main} Host[production/host/default] active [20-02-04 01:45:28.950] {main} ProServer[id=app-0,cluster=app] active [20-02-04 01:45:28.951] {main} JniSelectManager[max=130816] is not available on this system. [20-02-04 01:45:28.951] {main} JNI keepalive: disabled for unknown reasons [20-02-04 01:45:28.951] {main} JNI: file, socket which maps to the following code in JniSelectManager: /** * Starts the manager. */ @Override public boolean start() { if (! _lifecycle.toStarting()) { return false; } _fd = createNative(); if (_fd == 0) { _lifecycle.toDestroy(); log.finer(this + " is not available on this system."); return false; } |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||