Closed pierfrancesco72 closed 2 years ago
@pierfrancesco72 hi - so you want to pass the CEF Connectivity test.
In this case, I think the main problem is the usage of the iso6523-actorid-upis::0211:05901080969
as the participant identifier (or Srrvice Group identifier). If I am not totally mistaken the rules for Connectivity Test participant IDs are different, but I can't recall the details.
If you however try to use this for Peppol: it won't work
Please give me more details on what you want to achieve
Yes phax, I want to pass CEF Connectivity test.
Thanks for your suggestion on participant usage, but phoss-smp-xml
throws the same error with specific CEF participant connectivity-partid-qns::dynceftest2party71gw
:
the certificate seems to be right:
the error is the same:
[2022-01-25T19:57:46,593] [SMP-SERVER] [INFO ] [http-nio-8080-exec-10] Trying to CREATE business connectivity-partid-qns::dynceftest2party71gw for SMP-CONNECTIVITYTEST-71 in SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:120)
[2022-01-25T19:57:46,593] [SMP-SERVER] [INFO ] [http-nio-8080-exec-10] Performing SML query to 'https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/manageparticipantidentifier' -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML._createSMLCaller(RegistrationHookWriteToSML.java:67)
[2022-01-25T19:57:46,677] [SMP-SERVER] [INFO ] [http-nio-8080-exec-10] Trying to create new participant connectivity-partid-qns::dynceftest2party71gw in SMP 'SMP-CONNECTIVITYTEST-71' -- com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:165)
[2022-01-25T19:57:48,879] [SMP-SERVER] [WARN ] [http-nio-8080-exec-10] Technical details -- com.helger.phoss.smp.ui.SMPCommonUI.getTechnicalDetailsUI(SMPCommonUI.java:340)
com.helger.phoss.smp.smlhook.RegistrationHookException: Could not create business connectivity-partid-qns::dynceftest2party71gw in SML
at com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:137) ~[phoss-smp-backend-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.secure.PageSecureServiceGroup$3.handleAction(PageSecureServiceGroup.java:324) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.secure.PageSecureServiceGroup$3.handleAction(PageSecureServiceGroup.java:314) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.photon.uicore.page.AbstractWebPageForm.fillContent(AbstractWebPageForm.java:1326) ~[ph-oton-uicore-8.3.6.jar:8.3.6]
at com.helger.photon.uicore.page.AbstractWebPage.getContent(AbstractWebPage.java:162) ~[ph-oton-uicore-8.3.6.jar:8.3.6]
at com.helger.photon.bootstrap4.uictrls.ext.BootstrapPageRenderer.getPageContent(BootstrapPageRenderer.java:133) ~[ph-oton-bootstrap4-uictrls-8.3.6.jar:8.3.6]
at com.helger.photon.bootstrap4.uictrls.ext.BootstrapPageRenderer.getPageContent(BootstrapPageRenderer.java:160) ~[ph-oton-bootstrap4-uictrls-8.3.6.jar:8.3.6]
at com.helger.phoss.smp.ui.secure.SMPRendererSecure.getContent(SMPRendererSecure.java:215) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.SMPLayoutHTMLProvider.fillBody(SMPLayoutHTMLProvider.java:70) [phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.photon.core.html.AbstractSWECHTMLProvider.fillHeadAndBody(AbstractSWECHTMLProvider.java:104) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.photon.core.html.AbstractHTMLProvider.createHTML(AbstractHTMLProvider.java:164) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.photon.app.html.PhotonHTMLHelper.createHTMLResponse(PhotonHTMLHelper.java:117) [ph-oton-app-8.3.6.jar:8.3.6]
at com.helger.photon.core.servlet.AbstractApplicationXServletHandler.handleRequest(AbstractApplicationXServletHandler.java:101) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.phoss.smp.servlet.SMPApplicationXServletHandler.handleRequest(SMPApplicationXServletHandler.java:81) [phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.xservlet.handler.simple.XServletHandlerToSimpleHandler.onRequest(XServletHandlerToSimpleHandler.java:245) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.xservlet.AbstractXServlet._invokeHandler(AbstractXServlet.java:345) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:533) [ph-xservlet-9.6.3.jar:9.6.3]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [servlet-api.jar:4.0.FR]
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:587) [ph-xservlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-websocket.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.web.servlets.scope.AbstractScopeAwareFilter.doHttpFilter(AbstractScopeAwareFilter.java:81) [ph-web-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.xservlet.AbstractXFilter.doHttpFilter(AbstractXFilter.java:189) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.servlet.filter.CharacterEncodingFilter.doHttpFilter(CharacterEncodingFilter.java:187) [ph-servlet-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) [catalina.jar:9.0.58]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) [catalina.jar:9.0.58]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [catalina.jar:9.0.58]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) [catalina.jar:9.0.58]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) [catalina.jar:9.0.58]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399) [tomcat-coyote.jar:9.0.58]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-coyote.jar:9.0.58]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) [tomcat-util.jar:9.0.58]
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) [tomcat-util.jar:9.0.58]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:9.0.58]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]
Caused by: com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 400: Bad Request
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:307) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:249) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:207) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:120) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:109) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1105) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:1019) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:988) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:846) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.Stub.process(Stub.java:432) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:61) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:131) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.proxy.$Proxy65.create(Unknown Source) ~[?:?]
at com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:170) ~[peppol-sml-client-8.6.4.jar:8.6.4]
at com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:137) ~[peppol-sml-client-8.6.4.jar:8.6.4]
at com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:125) ~[phoss-smp-backend-5.5.3.jar:5.5.3]
... 52 more
Do you think the SML (SMK) configuration is right?
Thanks
In this site: https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/search
if I seek my participant: connectivity-partid-qns::dynceftest2party71gw
it is present:
but when i try to send the message with OXALIS standalone (about this doc) to my participant, the error is "Identifier 'xxx' is not registered in SML.
in my payload.xml
I have try with different combinations:
<Receiver>
<!-- This Sender section describes the PEPPOL Receiver -->
<!-- It corresponds to an FinalRecipient in AS4 -->
<!--Identifier>urn:oasis:names:tc:ebcore:partyid-type:unregistered:dynceftest2party70gw</Identifier-->
<!--Identifier>connectivity-partid-qns::dynceftest2party70gw</Identifier-->
<Identifier>urn:oasis:names:tc:ebcore:partyid-type:unregistered:cefsupportgw</Identifier>
</Receiver>
but the response is the same.
Maybe is there a problem with certificates? Infact when I try to connect to https://acc.edelivery.tech.ec.europa.eu/edelivery-sml from my local pc, the browser opens a popup to choose which certificate to use for the connection:
so after I have selected the correct one, I enter into the site.
What do you think about?
Thanks
Hi @pierfrancesco72
In your SMP example above you use dynceftest2party71gw
but the SML search shows dynceftest2party70gw
- I am confused - which one is yours?
My assumption is, you need to register a participant with scheme urn:oasis:names:tc:ebcore:partyid-type:unregistered
and value dynceftest2party71gw
(different scheme than you provided above)
Regarding Oxalis - no idea. Try using "::" (two colons) to separate scheme and value. So like urn:oasis:names:tc:ebcore:partyid-type:unregistered::dynceftest2party71gw
.
hth
Hi @phax ,
I need to register a participant with sheme: connectivity-partid-qns
and id: dynceftest2party71gw
but phoss-sml do not register it to SMK:
based on AS4ConnectivityTestUserGuide.docx
:
But, if I go to the site: https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/search and I search my participant:
I find it:
Y77IGVVUUFTBTHSW5CWSTWKSFDR5MTHZB4XFJXPLU66HMKZR3MNQ.connectivity-partid-qns.connectivitytest.acc.edelivery.tech.ec.europa.eu. 60 IN NAPTR 100 10 "U" "Meta:SMP" "!.*!http://smp.pantarei-si.it/!" .
but I don't know if this evidence is enought, in fact phoss-smp
not recognize it registered like.
What do you think about?
Thanks
@pierfrancesco72 So it seems like you previously registered it. That might explain the HTTP 400. I assume that this is proof enough, if the SMK-database entry indicates, that your SMP (based on the SMP ID) is owning the participant.
To get this into your SMP, try this:
So far so good. If you are confident, that you are the owner of this DNS entry you may try this:
dig
call to see if the entry is really gone (mind DNS replication delays)dig
call to see if the entry is present gone (mind DNS replication delays)
==> that should be proof enough ;-)hth
thank you @phax for your quick replies.
I have tried the first 5 points, without success. Definitely because the current situation of the SMP configuration, does not start from scratch.
So I tried the second part of your post. Below is the log:
[2022-01-31T18:43:20,215] [SMP-SERVER] [INFO ] [http-nio-8080-exec-9] Trying to DELETE business connectivity-partid-qns::dynceftest2party71gw for SMP-CONNECTIVITYTEST-71 from SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.deleteServiceGroup(RegistrationHookWriteToSML.java:166)
[2022-01-31T18:43:20,215] [SMP-SERVER] [INFO ] [http-nio-8080-exec-9] Performing SML query to 'https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/manageparticipantidentifier' -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML._createSMLCaller(RegistrationHookWriteToSML.java:67)
[2022-01-31T18:43:20,216] [SMP-SERVER] [INFO ] [http-nio-8080-exec-9] Trying to delete participant connectivity-partid-qns::dynceftest2party71gw -- com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.delete(ManageParticipantIdentifierServiceCaller.java:284)
[2022-01-31T18:43:21,142] [SMP-SERVER] [INFO ] [http-nio-8080-exec-9] Succeeded in deleting business connectivity-partid-qns::dynceftest2party71gw from SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.deleteServiceGroup(RegistrationHookWriteToSML.java:174)
[2022-01-31T18:43:21,148] [SMP-SERVER] [INFO ] [http-nio-8080-exec-9] Successfully Deleted ServiceGroup with ID 'connectivity-partid-qns::dynceftest2party71gw' -- com.helger.phoss.smp.domain.servicegroup.LoggingSMPServiceGroupCallback.onSMPServiceGroupDeleted(LoggingSMPServiceGroupCallback.java:45)
[2022-01-31T18:45:30,524] [SMP-SERVER] [INFO ] [http-nio-8080-exec-7] Trying to CREATE business connectivity-partid-qns::dynceftest2party71gw for SMP-CONNECTIVITYTEST-71 in SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:120)
[2022-01-31T18:45:30,524] [SMP-SERVER] [INFO ] [http-nio-8080-exec-7] Performing SML query to 'https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/manageparticipantidentifier' -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML._createSMLCaller(RegistrationHookWriteToSML.java:67)
[2022-01-31T18:45:30,525] [SMP-SERVER] [INFO ] [http-nio-8080-exec-7] Trying to create new participant connectivity-partid-qns::dynceftest2party71gw in SMP 'SMP-CONNECTIVITYTEST-71' -- com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:165)
[2022-01-31T18:45:51,561] [SMP-SERVER] [INFO ] [http-nio-8080-exec-7] Succeeded in CREATE business connectivity-partid-qns::dynceftest2party71gw in SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:127)
[2022-01-31T18:45:51,564] [SMP-SERVER] [INFO ] [http-nio-8080-exec-7] Successfully Created ServiceGroup with ID 'connectivity-partid-qns::dynceftest2party71gw' -- com.helger.phoss.smp.domain.servicegroup.LoggingSMPServiceGroupCallback.onSMPServiceGroupCreated(LoggingSMPServiceGroupCallback.java:32)
[2022-01-31T18:47:01,861] [SMP-SERVER] [INFO ] [http-nio-8080-exec-4] Trying to CREATE business connectivity-partid-qns::dynceftest2party71gw for SMP-CONNECTIVITYTEST-71 in SML -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:120)
[2022-01-31T18:47:01,861] [SMP-SERVER] [INFO ] [http-nio-8080-exec-4] Performing SML query to 'https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/manageparticipantidentifier' -- com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML._createSMLCaller(RegistrationHookWriteToSML.java:67)
[2022-01-31T18:47:01,862] [SMP-SERVER] [INFO ] [http-nio-8080-exec-4] Trying to create new participant connectivity-partid-qns::dynceftest2party71gw in SMP 'SMP-CONNECTIVITYTEST-71' -- com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:165)
[2022-01-31T18:47:02,230] [SMP-SERVER] [WARN ] [http-nio-8080-exec-4] Technical details -- com.helger.phoss.smp.ui.SMPCommonUI.getTechnicalDetailsUI(SMPCommonUI.java:340)
com.helger.phoss.smp.smlhook.RegistrationHookException: Could not create business connectivity-partid-qns::dynceftest2party71gw in SML
at com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:137) ~[phoss-smp-backend-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.secure.PageSecureServiceGroup$3.handleAction(PageSecureServiceGroup.java:324) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.secure.PageSecureServiceGroup$3.handleAction(PageSecureServiceGroup.java:314) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.photon.uicore.page.AbstractWebPageForm.fillContent(AbstractWebPageForm.java:1326) ~[ph-oton-uicore-8.3.6.jar:8.3.6]
at com.helger.photon.uicore.page.AbstractWebPage.getContent(AbstractWebPage.java:162) ~[ph-oton-uicore-8.3.6.jar:8.3.6]
at com.helger.photon.bootstrap4.uictrls.ext.BootstrapPageRenderer.getPageContent(BootstrapPageRenderer.java:133) ~[ph-oton-bootstrap4-uictrls-8.3.6.jar:8.3.6]
at com.helger.photon.bootstrap4.uictrls.ext.BootstrapPageRenderer.getPageContent(BootstrapPageRenderer.java:160) ~[ph-oton-bootstrap4-uictrls-8.3.6.jar:8.3.6]
at com.helger.phoss.smp.ui.secure.SMPRendererSecure.getContent(SMPRendererSecure.java:215) ~[phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.phoss.smp.ui.SMPLayoutHTMLProvider.fillBody(SMPLayoutHTMLProvider.java:70) [phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.photon.core.html.AbstractSWECHTMLProvider.fillHeadAndBody(AbstractSWECHTMLProvider.java:104) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.photon.core.html.AbstractHTMLProvider.createHTML(AbstractHTMLProvider.java:164) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.photon.app.html.PhotonHTMLHelper.createHTMLResponse(PhotonHTMLHelper.java:117) [ph-oton-app-8.3.6.jar:8.3.6]
at com.helger.photon.core.servlet.AbstractApplicationXServletHandler.handleRequest(AbstractApplicationXServletHandler.java:101) [ph-oton-core-8.3.6.jar:8.3.6]
at com.helger.phoss.smp.servlet.SMPApplicationXServletHandler.handleRequest(SMPApplicationXServletHandler.java:81) [phoss-smp-webapp-5.5.3.jar:5.5.3]
at com.helger.xservlet.handler.simple.XServletHandlerToSimpleHandler.onRequest(XServletHandlerToSimpleHandler.java:245) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.xservlet.AbstractXServlet._invokeHandler(AbstractXServlet.java:345) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:533) [ph-xservlet-9.6.3.jar:9.6.3]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [servlet-api.jar:4.0.FR]
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:587) [ph-xservlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-websocket.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.web.servlets.scope.AbstractScopeAwareFilter.doHttpFilter(AbstractScopeAwareFilter.java:81) [ph-web-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.xservlet.AbstractXFilter.doHttpFilter(AbstractXFilter.java:189) [ph-xservlet-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at com.helger.servlet.filter.CharacterEncodingFilter.doHttpFilter(CharacterEncodingFilter.java:187) [ph-servlet-9.6.3.jar:9.6.3]
at com.helger.servlet.filter.AbstractHttpServletFilter.doFilter(AbstractHttpServletFilter.java:66) [ph-servlet-9.6.3.jar:9.6.3]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) [catalina.jar:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) [catalina.jar:9.0.58]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) [catalina.jar:9.0.58]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [catalina.jar:9.0.58]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687) [catalina.jar:9.0.58]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) [catalina.jar:9.0.58]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359) [catalina.jar:9.0.58]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399) [tomcat-coyote.jar:9.0.58]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-coyote.jar:9.0.58]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-coyote.jar:9.0.58]
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) [tomcat-util.jar:9.0.58]
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) [tomcat-util.jar:9.0.58]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:9.0.58]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]
Caused by: com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 400: Bad Request
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:307) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:249) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:207) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:120) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:109) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1105) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:1019) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:988) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:846) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.Stub.process(Stub.java:432) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:61) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:131) ~[jaxws-rt-2.3.5.jar:2.3.5]
at com.sun.proxy.$Proxy65.create(Unknown Source) ~[?:?]
at com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:170) ~[peppol-sml-client-8.6.4.jar:8.6.4]
at com.helger.peppol.smlclient.ManageParticipantIdentifierServiceCaller.create(ManageParticipantIdentifierServiceCaller.java:137) ~[peppol-sml-client-8.6.4.jar:8.6.4]
at com.helger.phoss.smp.smlhook.RegistrationHookWriteToSML.createServiceGroup(RegistrationHookWriteToSML.java:125) ~[phoss-smp-backend-5.5.3.jar:5.5.3]
... 52 more
I think this happens:
[Check DNS State]
you don't see the IP address. I don't know if this is correct, but if I copy the DNS returned from the acceptance site and paste it into a url that looks like this: http://y77igvvuuftbthsw5cwstwksfdr5mthzb4xfjxplu66hmkzr3mnq.connectivity-partid-qns.connectivitytest.acc.edelivery.tech.ec.europa.eu/ I don't get directed to any IP.[Register in SML]
button, phoss-smp makes the request to the acceptance site, but it replies "Bad Request" perhaps because it finds the participant already registered, and phos-smp redirects to a new page:Translated with www.DeepL.com/Translator (free version)
Request URL: http://smp.pantarei-si.it/secure/locale-en_US/menuitem-service_groups?action=register-to-sml&object=connectivity-partid-qns%3A%3Adynceftest2party71gw
Request Method: GET
Status Code: 302
Remote Address: 18.159.216.61:80
Referrer Policy: strict-origin-when-cross-origin
Connection: keep-alive
Content-Length: 0
Date: Mon, 31 Jan 2022 19:05:35 GMT
Location: /secure/locale-en_US/menuitem-service_groups?phprga&action=checkdns
Referrer-Policy: strict-origin-when-cross-origin
Server: nginx/1.18.0 (Ubuntu)
X-Frame-Options: SAMEORIGIN
Perhaps the problem lies in the acceptance site not setting the DNS correctly?
What do you think about this?
Try adding
/?create-in-sml=false
to the URL.
@ri4a this is unfortunately not the REST API call, but the call from the UI @pierfrancesco72 what do you mean the first 5 steps don't work? You should be able to turn off SML integration:
Goto Service Groups and create the new Service Group with scheme connectivity-partid-qns
and value dynceftest2party71gw
If you didn't do this before, it is obvious, that the following steps didn't work. Please contact me by email (philip at helger dot com) and provide me with a username and password ok?
Hi Phax, I performed the procedure you mentioned, and indeed it worked, but the problem of the DNS not returning an IP remained:
Forget the DNS check - that might not work properly with the NAPTR records Use https://peppol.helger.com/public/locale-en_US/menuitem-tools-participant?scheme=connectivity-partid-qns&value=dynceftest2party71gw&sml=smk-connectivitytest&__querybc=true&__showtime=true&xsdvalidation=true&__xsdvalidation=true&verifysignatures=true&__verifysignatures=true&action=perform for checking
@pierfrancesco72 any update from your side?
Hi @phax, thanks for your help. I think that on the phoss-smp side the issue is resolved.
I can't rejoice yet because on the OXALIS side instead, I can't seem to find a way to query the SMK correctly. I still get "unregistered participant".
Anyway, thanks for the prompt help.
Okay. Thanks for the update. Than I am closing this issue.
I think you are missing the configuration for the SML domain connectivitytest.acc.edelivery.tech.ec.europa.eu
in Oxalis. But I have no idea how to do that. Good luck!
Good evening,
we have tried to register a new partecipant id in SML (SMK) and we received the error below:
In connectivitytest documentation we read:
How do I setup the correct subdomain
connectivititest
?