-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent Error When Creating New Participant Service Group #67
Comments
@dhixon: For the PEPPOL Directory you have a misconfigured keystore - please check file The HTTP 400 call when trying to create Concerning the HTTP 401 (Unauthorized) for iso6523-actorid-upis::0009:43402724900220 - my interpretation is, that this participant is already registered. Checking at https://peppol.helger.com/public/locale-en_US/menuitem-tools-participant?scheme=iso6523-actorid-upis&value=0009%3A43402724900220&sml=auto&action=perform -> yes it is registered |
Thanks. How do I get the read timeout fix? Will that be a new release, or is there a way I can effect that on my existing SMP? |
According to https://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.html you can set a default timeout: sun.net.client.defaultReadTimeout Else wait for 5.0.4 - scheduled before end of march with PKI update as well |
Thanks Philip. If you don't mind my asking, how did you know that there is a problem with PEPPOL Directory? |
|
Occasionally when I use the GUI or API to create a new participant it fails. I was creating participants with ID's ending in 219, 220 and 221. Sometimes they were successfully created and sometimes they were unsuccessful. I saw a 401 in there from the SML for one attempt. I then retried the attempt
logs.out.zip
and it then worked. I have attached the console log (catalina.out equivalent in docker world).
The text was updated successfully, but these errors were encountered: