0005479: BAM queue threading - BAM queue is full size=16383

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005479

[Resin]

minor

always

07-05-13 11:48

08-05-13 12:51

Reporter

cowan

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

4.0.37

Product Version

4.0.36

Product Build

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

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
07-05-13 11:48	cowan	New Issue
08-05-13 12:51	ferg	Assigned To	=> ferg
08-05-13 12:51	ferg	Status	new => closed
08-05-13 12:51	ferg	Resolution	open => fixed
08-05-13 12:51	ferg	Fixed in Version	=> 4.0.37

Mantis 1.0.0rc3[^]

27 total queries executed.
25 unique queries executed.