migrating to killbill 0.24.0

33 views
Skip to first unread message

Roger Parkinson

unread,
Mar 12, 2023, 5:55:56 PM3/12/23
to Kill Bill users mailing-list
I'm trying out 0.24.0 and I run into problems with this call:

curl -v \
    -X POST \
    -u admin:admin \
    -H "X-Killbill-ApiKey: Knifethrower" \
    -H "X-Killbill-ApiSecret: abc123" \
    -H "Content-Type: application/json" \
    -H "Accept: application/json" \
    -H "X-Killbill-CreatedBy: snakecharmer" \
    -H "X-Killbill-Reason: external-invoice-A20230308011733386.xlsx" \
    -d '[{"accountId": "8c4d4d71-0f4a-434c-8833-b40ca2a19114", "description": "I20230308011733386", "startDate": "2020-09-01", "amount": 100.00,"currency": "NZD" }]' \
    "http://192.168.1.121:8080/1.0/kb/invoices/charges/e595bb30-c35f-4846-a660-95ad00249683?requestedDate=2020-09-01&autoCommit=true"

The response I get is:

{"className":"java.lang.ArrayIndexOutOfBoundsException","code":null,"message":"Index 1 out of bounds for length 1","causeClassName":null,"causeMessage":null,"stackTrace":[]}

Note that the account id is valid. I can do this command without error:

curl -v \
    -u admin:admin \
    -H "X-Killbill-ApiKey: Knifethrower" \
    -H "X-Killbill-ApiSecret: abc123" \
    -H "Content-Type: application/json" \
    -H "Accept: application/json" \
    "http://192.168.1.121:8080/1.0/kb/accounts/e595bb30-c35f-4846-a660-95ad00249683"

I have seen the same error on a different call but, alas, I don't know which one atm. Hopefully I have the same problem there though.
Thanks for your help

Roger Parkinson

unread,
Mar 14, 2023, 9:04:06 PM3/14/23
to Kill Bill users mailing-list
Any progress on this one? It is holding up our migration to 0.24. Thanks

Reshma Bidikar

unread,
Mar 14, 2023, 10:17:24 PM3/14/23
to Kill Bill users mailing-list
Hi Roger,

I took a look but I'm unable to reproduce the issue. Do you see any errors/exceptions in the logs? If so, could you please share the errors with us?

Thanks,
Reshma

Roger Parkinson

unread,
Mar 15, 2023, 11:18:50 PM3/15/23
to Kill Bill users mailing-list
I tore down the whole test bed and reinstalled everything and the problem has gone away. I guess that's good, though a little worrying.
Nothing you can look at though so I have to proceed as though it was a problem in my install the first time.

Reply all
Reply to author
Forward
0 new messages