|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5479 | minor | always | 07-05-13 11:48 | 08-05-13 12:51 | |
|
|
|||||
| Reporter: | cowan | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.36 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.37 | ||
|
|
|||||
| Summary: | 0005479: BAM queue threading - BAM queue is full size=16383 | ||||
| Description: |
Customer reports: [13-07-04 11:46:55.799] {resin-port-172.20.11.150:6802-36} MultiworkerMailbox[cluster-cache-mnode@baa.app.admin.resin]: message CallPayload[localPut] {to:cluster-cache-mnode@baa.app.admin.resin, from:cluster-router-app-main@caa.app.admin.resin} com.caucho.bam.QueueFullException: BAM queue is full size=16383 MultiworkerMailbox[cluster-cache-mnode@baa.app.admin.resin] Message[to=cluster-cache-mnode@baa.app.admin.resin,from=cluster-router-app-main@caa.app.admin.resin,com.caucho.bam.proxy.CallPayload] Per Scott: I don't see anything wrong in the thread dump, except that there's no thread processing the queue. I'm thinking of two things: 1) some kind of health check/update (possibly internal to BAM) that will force a restart if the problem persists. 2) also check again the thread-waking logic, specific to BAM. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | Rep by J. Barr | ||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |