Hi ,florin
if i add many message once in a while, svm_queue_add will deadlock due to
q->cursize == q->maxsize?
Maybe this reason cause deadlock
int
svm_queue_add (svm_queue_t * q, u8 * elem, int nowait)
{
i8 *tailp;
int need_broadcast = 0;
if (nowait)
{
/* zero on success */
Hi, florin
i have study jvpp code and found that maybe jvpp is ok, error occurs in vpp
svm_queue
jvpp connect vpp by vl_client_connect_to_vlib function
(vpp/src/vlibmemory/memory_client.c)
int
vl_client_connect_to_vlib (const char *svm_name,
const char *client_name, int rx_queue_size)
{
Hi Wanghe,
The only api bindings supported today are c, python and golang. Maybe somebody
familiar with the jvpp code can help you out but otherwise I’d recommend to
switch if possible.
Regards,
Florin
> On Jun 3, 2022, at 7:55 AM, NUAA无痕 wrote:
>
> Hi, florin
>
> About this question, i
Hi, florin
About this question, i compare c++ code with jvpp code， then i found that
jvpp maybe have a bug and even if update vpp also cannot resolve it
jvpp code according to vpp version 1901, that has jvpp example
Hi florin,
Thanks for your suggestion, i will update vpp to new version for this
question
In addition that is vpp has example for c++/java binary api use， so i can
compare it with our project code
our c++ code refer to https://pantheon.tech/vpp-101-plugins-binary-api/
Thank u very much
Best
Hi wanghe,
Neither vpp 21.01 nor jvpp are supported, so your only options are to try back
porting fixes from newer versions, if any exist, or to debug the problem.
As previously mentioned, the deadlock seem to be in a reply message, so the
issue is probably in the java/c++ implementation of
Hi，florin
I would appreciate it if you can resolve it
My project use java web to control vpp, many binary api are used, such as
interfaces, ip, our customize api etc.
half a year ago， i use one c++ restful framework ( google‘s pistache) to
use vpp binary api, there also has deadlock problem ,
Hi wanghe,
Unfortunately, jvpp is no longer supported so probably there’s no recent fix
for the issue you’re hitting. By the looks of it, an api msg handler is trying
to enqueue something (probably a reply towards the client) and ends up stuck
because the svm queue is full and a condvar
