-
Notifications
You must be signed in to change notification settings - Fork 25
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
CEF connectivity test - "No transmission is provided" #85
Comments
Hmm - I retried the CEF connectivity test without problems. But I also see that you only have one minus before the protocol argument in the command line. It should read --protocol |
Good catch, I tried with "--protocol", but I get the same error. |
Can you show me the complete oxalis log? |
C:\Oxalis\AS4_Outbound>java -classpath "standalone/;as4/" eu.sendregning.oxalis.Main -cert cefsupportgw.cer -f CEF.xml --protocol peppol-transport-as4-v2_0 -u "http://40.115.23.114:8080/domibus/services/msh?domain=static" |
For sending you need to remove the following line from your oxalis.conf: oxalis.header.parser=dummy However, this is needed for your receiving AP. Keep separate oxalis.conf for inbound and outbound. |
Thanks, that got me further. :) I've encountered another error now. I've attached the file I'm trying to send. 2020-02-10 11:12:30,470 INFO [org.apache.cxf.services.DummyImpl.FAULT_IN] [] FAULT_IN 2020-02-10 11:12:30,486 ERROR [no.difi.oxalis.commons.error.QuietErrorTracker] [] [a83960db-045e-4f8a-8052-d7ea97d71b67] An error occurred while processing your request. Please check the message header for more details. |
The file looks good as far as I can see. By adding an argument like -DOXALIS_HOME=/c/dev/cef/.oxalis you can specify a different OXALIS_HOME for the outbound |
I see that I get the same error as you if I omit the following line in oxalis.conf: oxalis.as4.type=cef-connectivity Can you assure that it is there, please? |
Then I do not know what is wrong. Maybe you could ask CEF support, to check which field they do not like and what the value is? |
I will do that. :) Thanks for the swift and good support! |
Hey @numguyen thanks, this whole thread was helpful, I am currently trying to achieve the CEF testbed sending scenario and had the same problems. I still have this problem:
If you manage to somehow get past this problem I would very much appreciate a comment here what was wrong in your case? I'm trying to send something like in the example for payload.xml in the guide https://github.com/difi/Oxalis-AS4/blob/master/docs/cef-connectivity/index.md Thanks in advance! |
I see that you are using a different URL than I have received for the static CEF connection scenario. Are you sure that it is correct? |
Hi, the feedback I got from CEF was the following:
The Identifier and InstanceIdentifier in the payload adress this, but should this be configured in the oxalis.conf? |
Can you show me the outgoing SOAP message? |
Here you go: SOAP.txt :) Looks like <Service @type is not correct, should be e-delivery right? |
I will have to get back to you on Thursday. I am currently out of office, only answering questions from my mobile phone. |
Can you try with oxalis 4.1.0 and as4 4.1.3? Is there any difference? |
It behaves as you are missing the following config: |
I will try to reproduce this tommorow. |
Hi Frode, I set up the test-environment from scratch, and then it worked without any issues. :) Thanks for all the swift replies! |
Hello,
I'm running:
Oxalis 4.1.1
Oxalis-AS4 4.1.3
I'm receiving the error "No transmission is provided" when attempting the CEF connectivity test even though I followed the guide to the letter.
Any idea what I'm doing wrong?
oxalis.conf:
oxalis.keystore {
path = ceftestpartyXXgwkeystore.jks
password = "XXXXXX"
key.alias = "ceftestpartyXXgw"
key.password = "XXXXXX"
}
security.truststore.ap=ceftestpartyXXgwtruststore.jks
security.truststore.password=XXXXXX
oxalis.as4.type=cef-connectivity
oxalis.header.parser=dummy
lookup.locator.hostname="acc.edelivery.tech.ec.europa.eu/edelivery-sml/"
lookup.locator.class = no.difi.vefa.peppol.lookup.locator.BusdoxLocator
security.validator.class = no.difi.vefa.peppol.security.util.EmptyCertificateValidator
oxalis.path.inbound=/Oxalis/Inbound_messages_Oxalis
oxalis.logging.config=logback-oxalis.xml
Command:
java -classpath "standalone/*;as4/*" eu.sendregning.oxalis.Main -cert cefsupportgw.cer -f CEF.xml --protocol peppol-transport-as4-v2_0 -u "http://40.115.23.114:8080/domibus/services/msh?domain=static"
Error:
Message failed : null
2020-02-08 22:51:03,691 ERROR [eu.sendregning.oxalis.Main] Execution failed: no.difi.oxalis.api.lang.OxalisTransmissionException: No transmission is provided.
java.util.concurrent.ExecutionException: no.difi.oxalis.api.lang.OxalisTransmissionException: No transmission is provided.
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at eu.sendregning.oxalis.Main.main(Main.java:225)
Caused by: no.difi.oxalis.api.lang.OxalisTransmissionException: No transmission is provided.
at no.difi.oxalis.outbound.transmission.DefaultTransmitter.perform(DefaultTransmitter.java:116)
at no.difi.oxalis.outbound.transmission.DefaultTransmitter.transmit(DefaultTransmitter.java:93)
at eu.sendregning.oxalis.TransmissionTask.performTransmission(TransmissionTask.java:166)
at eu.sendregning.oxalis.TransmissionTask.call(TransmissionTask.java:94)
at eu.sendregning.oxalis.TransmissionTask.call(TransmissionTask.java:48)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Total time spent: 0s
Attempted to send 0 files
Failed transmissions: 1
Testfile attached (tried editing CreationDateAndTime as referenced here)
Obfuscated XX in ceftestpartyXXgw
CEF.log
The text was updated successfully, but these errors were encountered: