oxaliscommunity / oxalis Goto Github PK

Oxalis - PEPPOL Access Point open source implementation - Core component

License: Other

Shell 0.63% Java 98.98% Batchfile 0.08% PLSQL 0.10% Dockerfile 0.15% Makefile 0.07%

oxalis's Introduction

Oxalis

Oxalis is the leading open-source software implementation of OpenPeppol eDelivery Access Point (AS4) specifications. This repository was originally developed by Steinar Overbeck Cook(SendRegning) and later looked after by the Norwegian agency for Public Management and eGovernment (Difi) until March 2020.

Starting November 2020, Oxalis is being maintained by NorStella Oxalis Community.

Oxalis Community

Oxalis Community is a not-for-profit organization organized under NorStella Foundation based in Norway, dedicated to the continued support and development of Oxalis, to secure Peppol compliance and value for its users.

Oxalis Community is facilitated by the foundation NorStella. It is organized according to democratic non-for-profit principles and established as an independent and autonomous part of the NorStella association with independent budgets.

The goals of Oxalis Community:

Secure sustainability and managed development of the Oxalis software
Encourage continued implementation of eProcurement using Peppol specifications.
Support innovative Peppol-based services that promotes the goal of harmonized and interoperable processes.

Oxalis can be used either as a complete standalone PEPPOL solution or as an API component from your own code. Standalone component (oxalis-standalone) comes with a basic command line tool for sending messages. It persists inbound messages to the filesystem Out of the box. Persistence have been modularized so you can provide your own implementation if you need to send inbound messages to a message queue, a workflow engine, a document archive or others.

Binary distributions is available both at Maven Central and GitHub.

The Latest version is Oxalis 6.x.x

Java 11 is minimum supported Java version since Oxalis 6.0.0. For detailed documentation, refer: main.adoc

Technical Information

The Latest technical news is available at : https://www.oxalis.network/technical-information

Are you Contributor?

We are actively looking for contributors who can contribute to Oxalis and associated Git repositories. You can start fixing issues by selecting any existing issue or you can add new feature. Please refer Pull request Checklist while generating new pull request. Team will review your code, if it will meet desired goal, and will be according to standards and guidelines then it will be merged to master.

Oxalis components

Component	Type	Description
oxalis-inbound	war	Inbound access point implementation which runs on Tomcat (1)
oxalis-outbound	jar	Outbound component for sending PEPPOL business documents (2)
oxalis-standalone	main	Command line application for sending PEPPOL business documents (3)

(1) Receives messages using AS2 protocol and stores them in the filesystem as default.

(2) Can be incorporated into any system which needs to send PEPPOL documents.

(3) Serves as example code on how to send a business documents using the oxalis-outbound component.

Installation

make sure the latest version of Tomcat is installed. See installation guide for additional details.
make sure that Tomcat is up and running and that manager is available with user manager/manager
make sure that Tomcat is also up and running on SSL at localhost:443 (unless you terminate SSL in front of Tomcat)
make sure that ''your'' keystore is installed in a known directory (separate instructions for constructing the keystore)
Create an OXALIS_HOME directory and edit the file oxalis.conf
Add OXALIS_HOME environment variable to reference that directory
Build Oxalis yourself (see below) or download the binary artifacts provided by Norstella from Maven Central Search for "oxalis" and download the latest version of oxalis-distribution.
Deploy oxalis.war to your Tomcat webapps directory
Send a sample invoice; modify example.sh to your liking and execute it.
See the installation guide for more additional details.
To install or replace the PEPPOL certificate, see the keystore document.
Oxalis is meant to be extended rather than changing the Oxalis source code.

Troubleshooting

Sending failed ... Received fatal alert: handshake_failure happens when Oxalis cannot establish HTTPS connection with the remote server. Usually because destination AccessPoint has "poodle patched" their HTTPS server. Oxalis v3.1.0 contains fixes for this, so you need to upgrade. See the #197 for more info.
Provider net.sf.saxon.TransformerFactoryImpl not found might be an XSLT implementation conflice between Oxalis and the VEFA validator. VEFA needs XSLT 2.0 and explicitly set Saxon 9 as the transformer engine to the JVM. Since Saxon 9 is not used and included with Oxalis you'll end up with that error on the Oxalis side. To get rid of the error make sure you run Oxalis and VEFA in separate Tomcats/JVM processes.
ValidatorException: PKIX path building failed is probably because the receivers SSL certificate does not contain the correct certificate chain. The AS2 implementation needs to validate the SSL certificate chain and any intermediate certificates needs to be present. See the #173 for more info.
Internal error occured: null when receiving might be due to a bug in some Apache Tomcat versions. The full error message logged is ERROR [network.oxalis.as2.inbound.As2Servlet] [] Internal error occured: null followed by a stack trace with java.lang.NullPointerException: null. To resolve this upgrade Tomcat to a newer version, take a look at #179 for more details.

Build from source

Note that the Oxalis "head" revision on master branch is often in "flux" and should be considered a "nightly build". The official releases are tagged and may be downloaded by clicking on Tags.

make sure Maven 3+ is installed
make sure JDK 11 is installed (the version we have tested with)
pull the version of interest from GitHub.
from oxalis root directory run : mvn clean install -Pdist
locate assembled artifacts in oxalis-dist/oxalis-distribution/target/oxalis-distribution-<version.number>-distro/

Securing Oxalis

By default Oxalis publish the web addresss listed in the table below.
The table describes their use and give some hints on how to secure those addresses.
A pretty standard scenario is to use some kind of load balancer and SSL offloader in front of the appserver running Oxalis.
This could be free/open software like Nginx and Apache or commercial software like NetScaler and BigIP.
All such front end software should be able to enforce security like the one suggested below.

URL	Function	Transport	Security
oxalis/as2	AS2 protocol endpoint	HTTPS with proper certificates	Enable inbound access from Internet
oxalis/status	Status information, for internal use and debugging	HTTP/HTTPS	Internet access can be blocked
oxalis/statistics	RAW statistics for DIFI	HTTPS with proper certificates	Used by DIFI to collect statistics

oxalis's People

Contributors

Stargazers

Watchers

Forkers

aleksabl estromsnes daniel-gustafsson terjetyl rogerevans rita-aursoy senikk oriol winoth2004 pavelsbubens bijeshcnair ehfportal descala wickyhasan tbap artur-kacen viaskyse kamalgupta elfogre carlowitz kotiranta fiorenzino josief85 hoanghainguyen jerouris haakonme kdkanishka pabrah jdrew1303 chathur einara virdun linuxatico dam0vm3nt qanders elsand nephosolutions l0ddifyr serxipc blackbaro vishwas8055 gozus19p jannewaren tanyehzheng maventa harshasuranjith pascucci333 aksamit polymorpheus milosh-dev mich282q erwingeirnaert tor-kleiberg darklajid rdehuyss ziriusas thebilge mysupplyorg adarshsrivastava11 kolanot dumpvn mrsulu66 ubrix dragandordevic napramirez oppgjorskontoret showka dukkune1 forrest1001 zumbala francescodiperna janiciconetrail raduraduica bellyfat devilears alfchristensen yoshiki-kinjo thomasberger nemhandel4erst ppotappel ppotappel-co seciq wimmaerevoet-octopus popovicmiroslav woldelig wartab adalard ogiritli

oxalis's Issues

Error while sending invoice using oxalis-standalone.jar

While running follwing command I am facing an error

"java -jar oxalis-standalone.jar -kp=peppol -f D:/oxalis-2.0/oxalis-start-outbound/target/test-classes/ehf-test.xml -d "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4a:ver1.0::2.0" -p "urn:www.cenbii.eu:profile:bii04:ver1.0" -c CH1 -r 9908:810017902 -s 9908:810017902 -u https://localhost/oxalis/accessPointService $TRACE"

The error is changed as I am using Oxalis 2.0.1.
Stack Trace is

SEVERE: WSS1533: Validation of self signed certificate failed.
Jun 11, 2013 11:53:32 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube] __doRun
SEVERE: WSRM1106: Attempt to send a [ CreateSequence ] RM session control message failed with an exception
javax.xml.ws.WebServiceException: com.sun.xml.wss.impl.WssSoapFaultException: Validation of self signed certificate failed
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processResponse(SecurityClientTube.java:365)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1074)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at $Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.sendregning.oxalis.Main.main(Main.java:124)
Caused by: com.sun.xml.wss.impl.WssSoapFaultException: Validation of self signed certificate failed
at com.sun.xml.ws.security.opt.impl.util.SOAPUtil.newSOAPFaultException(SOAPUtil.java:175)
at com.sun.xml.wss.impl.callback.CertificateValidationCallback.getResult(CertificateValidationCallback.java:90)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.validateCertificate(DefaultSecurityEnvironmentImpl.java:813)
at com.sun.xml.ws.security.opt.impl.incoming.X509BinarySecurityToken.validate(X509BinarySecurityToken.java:185)
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.handleSecurityHeader(SecurityRecipient.java:423)
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.cacheHeaders(SecurityRecipient.java:296)
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:245)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:455)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientResponsePacket(SecurityClientTube.java:434)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processResponse(SecurityClientTube.java:362)
... 25 more
Caused by: com.sun.xml.wss.impl.callback.CertificateValidationCallback$CertificateValidationException:

My oxalis-global.properties is

Global configuration file for Oxalis

oxalis.jdbc.driver.class=com.mysql.jdbc.Driver
oxalis.jdbc.class.path=file:///Users/sumanpreetsoh/.m2/repository/mysql/mysql-connector-java/5.1.18/mysql-connector-java-5.1.18.jar
oxalis.jdbc.connection.uri=jdbc:mysql://localhost/oxalis_test
oxalis.jdbc.user=oxalis
oxalis.jdbc.password=Blomster2013
oxalis.ap.identifier=
oxalis.datasource.jndi.name=jdbc/oxalis
oxalis.keystore=C://.oxalis/oxalis-keystore.jks
oxalis.soap.trace=false
oxalis.inbound.log.config = C://.oxalis/logback-oxalis-server.xml
oxalis.app.log.config = C://.oxalis/logback-oxalis-app.xml
oxalis.keystore.password = peppol
oxalis.inbound.message.store=/var/peppol
oxalis.pki.version=V1
oxalis.operation.mode=TEST

Error in Verifying Security in the Inbound Message

WARNING: WSRM1127: An unexpected exception occured while sending acknowledgement request
javax.xml.ws.WebServiceException: WSSTUBE0025: Error in Verifying Security in the Inbound Message.
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientResponsePacket(SecurityClientTube.java:439)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processResponse(SecurityClientTube.java:362)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1074)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:764)
at com.sun.xml.ws.api.server.ThreadLocalContainerResolver$2$1.run(ThreadLocalContainerResolver.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No Security header in message
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:715)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:733)
... 10 more
Caused by: com.sun.xml.wss.impl.WssSoapFaultException: Security Requirements not met - No Security header in message
at com.sun.xml.wss.impl.SecurableSoapMessage.newSOAPFaultException(SecurableSoapMessage.java:349)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:729)
... 10 more
Caused by: com.sun.xml.wss.XWSSecurityException: Security Requirements not met - No Security header in message
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.createMessage(SecurityRecipient.java:938)
at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.validateMessage(SecurityRecipient.java:252)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMessage(SecurityTubeBase.java:455)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientResponsePacket(SecurityClientTube.java:434)
... 9 more
Jun 21, 2013 7:09:52 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube] closeSequences

eu.peppol.start.persistence.SimpleMessageRepositoryTest is failing

When I run mvn clean install -Dit-test

I get this message:

testPrepareMessageStore java.lang.IllegalStateException: Unable to create directory A:\tmp\X\9908_976098897\9908_123456789
    at eu.peppol.start.persistence.SimpleMessageRepository.prepareMessageDirectory(SimpleMessageRepository.java:57)
    at eu.peppol.start.persistence.SimpleMessageRepositoryTest.testPrepareMessageStore(SimpleMessageRepositoryTest.java:74)
... Removed 34 stack frames

I have no idea where the reference A: might come from.
Should I worry ?

Fault if incoming message properties do not correspond to SMP meta data

Verify that DocumentID and ProfileID corresponds to the meta data in the SMP for the receiver.

problem with persisting statistics.

Today (for the very first time) we got a problem with oxalis, that made us send 2 ehf invoices to the customer instead of one.

Ther problem weas that when I used the DocumentSender to send the EHF, I got an exception, (and my code then assumed that NO ehf document was sent)

Now I could probably have made a better exception handling in my code, but I still think that the exception should also be better handled inside oxalis.

The problem was with the persistStatistics in Documentsender.

take a look at the send method, in document sender, at the end it has

    soapDispatcher.send(destination, messageHeader, soapBody);
    persistStatistics(messageHeader);

Now what will happen if there is any exception in the persistSTatistics method?
Well we would get an exception back to our code, BUT the invoice would already been sent.

the problem for me was a short glitch in the network, that made persistStatistics not beeing able to get a database connection. and I therefore got an IllegalStateException (Unable to retrieve connection ...)

Now, in my code to be able to see that this exception comes from persisting the statistics, I would have to read the message inside the statistics, this is not good.

A better solution would be to have a specific StatisticPersistionException (of some kind) is that my code could see that the sending of the EHF worked, but the persisting of the statistics did not work.

In Oxalis, we could also depending on type of error add code that will better handle exceptions, for example in the getConnection method, instead of just throwing an exception, we could add code that would retry a couple of times before throwing an exception.

to also minimize problems with the database we could also use database transactions. ie getting the connection, update the stats before we send it, and after, do a commit.

now, to get an error in the commit is less likely, then to get an error in all the other code for persisting the statistics.

Suddenly getting exception "Cannot resolve element with ID SamlID1374231640368"

Hello,

While sending a sample invoice given in the Oxalis distribution,I am getting following error.

Jul 19, 2013 4:30:40 PM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl populateSAMLPolicy
SEVERE: WSS0237: An Error occurred while populating SAML Policy in Dynamic Policy Callback
java.lang.RuntimeException: Error while handling SAML callbacks
at eu.peppol.security.callbacks.SAMLCallbackHandler.handle(SAMLCallbackHandler.java:109)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.populateAssertion(DefaultCallbackHandler.java:733)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:674)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.populateSAMLPolicy(DefaultSecurityEnvironmentImpl.java:1598)
at com.sun.xml.wss.impl.filter.ExportSamlAssertionFilter.process(ExportSamlAssertionFilter.java:128)
at com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.processSamlToken(AuthenticationTokenFilter.java:121)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:122)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)

I am using following command.

java -jar oxalis-standalone.jar -kp=peppol -f D:\Projects\trunk\oxalis-oxalis-2.0.1\oxalis-start-outbound\src\test\resources\ehf-test-SendRegning-HelseVest2.xml -d "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4a:ver1.0::2.0" -p "urn:www.cenbii.eu:profile:bii04:ver1.0" -c "$CHANNEL" -r 9908:810017902 -s 9908:810017902 -u https://localhost/oxalis/accessPointService $TRACE

Chain of trust for certificate in SMP response should be checked

Currently the signature in the SMP response is checked. However; since there is no way of inspecting the chain of trust for the SMP certificate, there is not much preventing an impostor ("man in the middle") from signing with a self signed certificate.

infinite loop causing tomcat to crash

13:11:35.132 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Requested SAML callback handling
13:11:35.134 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Creating and setting the SAML Sender Vouches Assertion
13:11:35.135 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-com - Initialising OCSP validator
13:11:35.152 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-com - Initialising OCSP validator
13:11:35.152 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Keystore callback handler: returning private key
13:11:36.038 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Requested SAML callback handling
13:11:36.038 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Creating and setting the SAML Sender Vouches Assertion
13:11:36.038 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-com - Initialising OCSP validator
13:11:36.052 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-com - Initialising OCSP validator
13:11:36.052 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Keystore callback handler: returning private key
13:11:36.083 [rm-client-tube-communicator-fiber-executor-thread-2] DEBUG oxalis-out - Requested SAML callback handling

Something is causing an infinite loop logging these lines over and over causing tomcat to crash after a while. Is it something you what could be the reason for or something that is fixed in newer versions of Oxalis? Even reboot didn't help.

Tests failing StatisticsKeyToolTest,MessageRepositoryFactoryTest and MessageRepositoryFactoryTest

I am trying to run the tests by using following command,

mvn clean
mvn install

But getting this

Failed tests:
test01(eu.peppol.security.OcspValidatorCacheTest)
loadPrivateKeyFromOxalisHome(eu.peppol.security.StatisticsKeyToolTest)
loadPublicKeyFromClassPath(eu.peppol.security.StatisticsKeyToolTest)
createClassLoader(eu.peppol.start.persistence.MessageRepositoryFactoryTest)

I looked at the surefire reports, it is saying

For OcspValidatorCacheTest

For StatisticsKeyToolTest

In case of StatisticsKeyToolTest, I dont know why it is looking for

oxalis.statistics.private.key=

This property is commented.

Please guide.

WSS1717: Error occurred while doing digest verification of body/payload

This is caused by interoperability problems between Metro version 2.1 and 2.2

Both parties need to upgrade to the latest and greatest version of Oxalis in order to remedy the problem.

See these Metro issues for further explanation:

oxalis-statistics-web missing class

Running "Download in CSV format" I get missing class below:

java.lang.NoClassDefFoundError: Could not initialize class eu.peppol.statistics.StatisticsRepositoryFactoryProvider
eu.peppol.statistics.guice.RepositoryModule.provideStatisticsRepository(RepositoryModule.java:24)

I'm building Oxalis on another VM than the one running it so I could be missing something, but the oxalis-api jar inside webapps/oxalis-statistics-web/WEB-INF/lib contains this missing class :S

SMP-responses with national characters fails signature validation

SMP-responses containing national characters like for instance æ,ø,å fails signature validation due to the code relying upon the use of default character set encoding.

The XML in the SMP-response should always be parsed using UTF-8

Load persistence implementation from separate class loader

The current implementation requires the persistence plug-in to be placed in a directory which is shared by all class loaders. This could cause problems in the future.

Only the properties file should be available in the shared directory, allowing the persistence plugin to be loaded from a location, which is not shared by all class loaders, nor overwritten when a new version is installed.

Question regarding some files in the inbound folder

In the oxalis.inbound.message.store folder I found some files after doing a few tests of sending EHF.

They are stored in \recipient_id\sender_id\uuid_[GUID].txt.

Are these confirmation messages from the other access point or mine ?

Problem when receiving document from a .Net-access point - WSS1717 Error occurred while doing digest verification of body/payload

I realize that this exception already exists in issue #10 , but as we're getting this exception when using Metro 2.2.1 (we've also tried 2.1.1), when communicating with a .Net 2.13 access point, I'm creating a separate issue.

Exception:

15.02.2013 08:52:15.450 [postman-executor-thread-42] ERROR c.s.x.w.logging.impl.opt.signature - WSS1717: Error occurred while doing digest verification of body/payload
javax.xml.crypto.dsig.XMLSignatureException: WSS1717: Error occurred while doing digest verification of body/payload
at com.sun.xml.ws.security.opt.impl.incoming.processor.StreamingPayLoadDigester.accept(StreamingPayLoadDigester.java:111) ~[webservices-rt-2.2.1-1.jar:2.2.1-1]
at org.codehaus.stax2.ri.Stax2FilteredStreamReader.next(Stax2FilteredStreamReader.java:37) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.stream.buffer.stax.StreamReaderBufferCreator.storeElementAndChildrenNoEx(StreamReaderBufferCreator.java:266) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.stream.buffer.stax.StreamReaderBufferCreator.storeElementAndChildren(StreamReaderBufferCreator.java:198) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.stream.buffer.stax.StreamReaderBufferCreator.store(StreamReaderBufferCreator.java:163) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.stream.buffer.stax.StreamReaderBufferCreator.create(StreamReaderBufferCreator.java:103) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.message.stream.StreamMessage.copy(StreamMessage.java:498) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.api.message.MessageWrapper.copy(MessageWrapper.java:208) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.api.message.Packet.copy(Packet.java:215) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.rx.rm.runtime.ServerDestinationDeliveryCallback.deliver(ServerDestinationDeliveryCallback.java:168) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.rx.rm.runtime.ServerDestinationDeliveryCallback.deliver(ServerDestinationDeliveryCallback.java:157) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at com.sun.xml.ws.rx.rm.runtime.delivery.Postman$1.run(Postman.java:101) [webservices-rt-2.2.1-1.jar:2.2.1-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_26]

Message flow

See https://gist.github.com/aleksabl/4959498 for a complete message log.

First incoming Request (WsRm)
Response to WsRm
Incoming request (with actual payload).
Crash with exception (we don't send a response back).
Payload is resent
We respond to second payload
They respond with a Rm-fault (since we're acking the second message, but haven't acked the first)
We respond that the Rm-fault has an invalid security header.

I think only 1-4 is interesting with regards to this bug, but I included everything in case I'm wrong.

Improve performance of outbound messages by implementing parallell transmission of messages

Problem with SAMLCallbackHandler on windows - with solution.

When using standalone client on windows with the latest libraries, the request is not constructed correctly: the signing identifier attribute for the document is missing from the XML, while the reference is present. This causes an error on the server side when validating the signature. The problem does not occur on Ubuntu.

The issue seems to stem from a difference in the JDK implementation (7u25 on windows).
We found this in 2.0.1. and master, and Mark Baaijens (Innopay) found a solution:
in oxalis-commons/src/main/java/eu/peppol/security/callbacks/SAMLCallbackHandler.java, add

assertionElement.setIdAttribute("ID", true);

on line 267 (in 2.0.1). This ensures the missing ID attribute on windows, and should not impact versions where the ID is set already.

--Gait.

How much work does Oxalis do for me ?

Sorry if this is not the right place to ask but apart from the installation instructions I have had a hard time finding any other documentation on the code and Difi's homepage doesn't mention it either.

AFAIK the Oxalis accessPointService is to be used by other access points to send EHF documents to the customers connected to us. Provided everything is working well and we are registered in ELMA other access points can locate our access point by the recipients id and deliver documents via the web service.

I want the most straightforward way to get an access point up and running and be able to service out customers with delivery, and later on receival, of EHF documents.

Is the best (or only) approach to create a separate webservice/wrapper that uses the Oxalis START outbound JAR component to validate the EHF and send it to the recipient via our accessPointService ?

Inbound message - Error during saving a multipart message

07:27:36.863 [rm-server-tube-communicator-fiber-executor-thread-1] DEBUG e.p.inbound.soap.InboundSoapHandler - Inbound message:
Jun 12, 2013 7:27:36 AM com.sun.xml.messaging.saaj.soap.MessageImpl saveChanges
SEVERE: SAAJ0540: Error during saving a multipart message

Security loophole with certificates

Thanks to Daniel Gustafsson from InExchange, we have discovered a potential security problem related to certificates.

In order to prevent anybody from exploiting it until it has been fixed, the detailed description is kept out of the issue list.

Loading truststore from truststore.jks

hi,

compiled oxalis, pushed myself through installation steps and got stuck in testing. both compiled and standalone jars are looking for truststore.jks in the unknown location. in installation description keystore is called oxalis-keystore.jks

<...>
2013-06-04 15:38:13,617 DEBUG [eu.peppol.util.OxalisHomeDirectory] Attempting to locate home dir.... 
Oxalis home directory: /usr/share/oxalis
2013-06-04 15:38:13,627 INFO [eu.peppol.util.GlobalConfiguration] oxalis.keystore = /usr/share/oxalis/oxalis-keystore.jks 
<...>

<...>
2013-06-04 15:38:13,657 DEBUG [eu.peppol.start.identifier.KeystoreManager] trust store resource name: truststore.jks 
2013-06-04 15:38:13,657 INFO [eu.peppol.start.identifier.KeystoreManager] Loading truststore from  truststore.jks 
Exception in thread "main" java.lang.ExceptionInInitializerError
    at eu.peppol.outbound.api.DocumentSenderBuilder.build(DocumentSenderBuilder.java:41)
    at eu.sendregning.oxalis.Main.main(Main.java:95)
Caused by: java.lang.NullPointerException
<...>

it looks like it does not care for -kf, or the issue is someplace else?

What kind of identifier should oxalis.ap.identifier contain?

New configuration in Oxalis 2.0 oxalis.ap.identifier:

smp.difi.no username? Some identifier created by Difi? or something we create ourself?

Make artifacts available in public repository

Use of ehCache prevents stand-alone programs from terminating

Due to the fact that ehCache creates threads by default, the stand-alone sender program does not terminate once the transmission has completed.

Missing BIS Corrective Invoice in PeppolDocumentTypeIdAcronym.java

When you add "Standalone Credit Note according to EHF" in ELMA Web Interface you also get some additional document types and one of those like BIS Correcitve Invoice:

urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm015:ver1.0:#urn:www.peppol.eu:bis:peppol5a:ver1.0::2.0

But this one doesn't exist in PeppolDocumentTypeIdAcronym.java

We have received some of those type of documents on our accesspoint so I just checked this part of Oxalis.

Solved

MySQL auto reconnect

After some hours without using our new Oxalis 2.0 AP I got this error message on first sending:

19:27:30.310 [http-bio-443-exec-3] INFO no.unimicro.ap.UniOutbox - Sending failed Unable to retrieve connection com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 44,421,336 milliseconds ago. The last packet sent successfully to the server was 44,421,353 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

Its from our no.unimicro.ap.UniOutbox module doing almost the same as oxalis-standalone. Is there any configuration for this?

is it a good idea to place oxalis global property file in USER_HOME

Hello,

I recently upgraded to Oxalis 2.0. And I found a new class GlobalConfiguration.java. So, I placed a .oxalis folder at my usre home.But is it a good practice to do the similar thing in Jenkins?

Do you recommend loading the property file from classpath.

Question about access point confirmation

From Difi on sending documents with the START protocol:

Delivering accesspoint shall receive a transfer confirmation winthin 5 minutes and verify that the transfer is successful.

I found this in eu.peppol.outbound.api.DocumentSender.send(...)

soapDispatcher.send(destination, messageHeader, soapBody);
persistStatistics(messageHeader);

I read this as

Message sent successfully, all OK. Persist statistics.
or
Message was not sent successfully. soapDispather.send will throw an exception.

I imagined the infrastructure was a real-time system, and the code in Oxalis indicates this too. Am I correct if I treat the log entry from statistics as a transfer confirmation ?

Problem retrieving private key from keystore

I'm trying to send a document to my own access point using the oxalis-standalone program using the following commandline:

java -jar oxalis-standalone.jar ^
 -kf .keystore ^
 -kp=xxxyyzz ^
 -f ehf-test.xml ^
 -p INVOICE_ONLY ^
 -c CH1 ^
 -r 9908:976098897 ^
 -s 9908:976098897 ^
 -u https://localhost:9443/oxalis/accessPointService

The following exception occurs:

java.lang.RuntimeException: java.lang.RuntimeException: Failed to get our private key
    at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1468)
    at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:551)
    at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
    at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
    at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
    at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
    at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
    at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
    at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:386)
    at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
    at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
    at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
    at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
    at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:564)
    at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:424)
    at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:347)
    at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:188)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
    at com.sun.xml.ws.client.Stub.process(Stub.java:323)
    at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
    at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
    at $Proxy43.create(Unknown Source)
    at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:136)
    at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:91)
    at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:165)
    at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:119)
    at eu.sendregning.oxalis.Main.main(Main.java:107)
Caused by: java.lang.RuntimeException: Failed to get our private key
    at eu.peppol.start.identifier.KeystoreManager.getOurPrivateKey(KeystoreManager.java:109)
    at eu.peppol.outbound.callbacks.KeyStoreCallbackHandler.handle(KeyStoreCallbackHandler.java:34)
    at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getPrivateKey(DefaultCallbackHandler.java:2394)
    at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1457)
    ... 35 more
Caused by: java.lang.RuntimeException: Private key is not first element in keystore at .keystore
    at eu.peppol.start.identifier.KeystoreManager.getOurPrivateKey(KeystoreManager.java:105)
    ... 38 more

I have done some simple debugging in the KeystoreManager.getOurPrivateKey method and here's what happens:

The alias is "peppol_ap" which is the alias I used when adding the certificate to my keystore.

But when trying to retrieve the corresponding key the following call returns null which causes the exception to be thrown:

Key key = keystore.getKey(alias, keystorePassword.toCharArray());

Any ideas what's causing this?

oxalis-statistics-web does not work properly in chrome and https

Chrome is more strict when it comes to what it allows and what it does not allow in regards of content if you access the site using https, ie content tht comes from http is not allowed..

[blocked] The page at https://localhost/oxalis-statistics-web/ ran insecure content from http://code.jquery.com/ui/1.10.2/themes/smoothness/jquery-ui.css.

[blocked] The page at https://localhost/oxalis-statistics-web/ ran insecure content from http://code.jquery.com/jquery-1.9.1.js.

[blocked] The page at https://localhost/oxalis-statistics-web/ ran insecure content from http://code.jquery.com/ui/1.10.2/jquery-ui.js.

Therefore the datepicker is not working properly if you access the statistics via https and chrome. the same goes for IE 10, Opera 15 (the beta version based on chromium)

however it works in firefox, safari, and current version of opera.

Strange issue, inbound folder is no longer populated

Starting the final tests before production today, then I noticed that the inbound folder is no longer populated.

This has worked before, I have some old items there.
The only thing I have altered is assigning a second IP address, configured Tomcat to listen on IP#1 and IIS to listen on IP#2 and added a commercial SSL certificate to Tomcat.
** The Oxalis keystore and Tomcat keystore are two different files so the Oxalis keystore is unaffected by this.
I tried to perform a rollback of the entire server to the previous working state (before introducing the second IP) but that gave the same result.
The accesspoint can send documents, I got that confirmed by sending to another accesspoint.
I have tried to send both with and without the -u parameter, there is no difference.

Example:

java -jar 
"E:\src\oxalis-oxalis-2.0.1\oxalis-distribution\target\oxalis-distribution-2.0.1-distro\bin\oxalis-standalone.jar" 
-kp=*****
 -f "E:\oxalis_test\res\810017902(sendregning.no)_14_24.xml" 
-d "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4a:ver1.0::2.0" -p "urn:www.cenbii.eu:profile:bii04:ver1.0"
-r 9908:981672577 
-s 9908:810017902
-u https://ehf.reknes.no/oxalis/accessPointService
-t

E:\oxalis_test>"Test_til-981672577(reknes)_fra-810017902(sendregning.no)_-u.cmd" >> log.log
jul 03, 2013 9:01:57 AM [com.sun.xml.ws.policy.parser.PolicyConfigParser]  parse
INFO: WSP5018: Loaded WSIT configuration from file: jar:file:/E:/src/oxalis-oxalis-2.0.1/oxalis-distribution/target/oxalis-distribution-2.0.1-distro/bin/oxalis-standalone.jar!/META-INF/wsit-client.xml.
Initializing the TrustStoreCallbackHandler
jul 03, 2013 9:02:07 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube]  closeSequences
INFO: WSRM1157: Waiting for sequence [ uuid:3909c739-ef90-41fa-9d6f-16576d27c79e ] state change to [ CLOSED ] has timed out after 3á000 milliseconds
jul 03, 2013 9:02:11 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube]  closeRmSession
INFO: WSRM1157: Waiting for sequence [ uuid:3909c739-ef90-41fa-9d6f-16576d27c79e ] state change to [ TERMINATING ] has timed out after 3á000 milliseconds

The logfile is too large to paste it all here but the essential parts seem to be that eu.peppol.util.OxalisHomeDirectory does locate the home dir and eu.peppol.util.GlobalConfiguration initializes all properties correctly.

Further down I have some debug message from oxalis-out where the document destination and WDSL files are loaded

INFO [oxalis-out] Document destination is https://ehf.reknes.no/oxalis/accessPointService 
DEBUG [oxalis-out] Constructing document body 
DEBUG [oxalis-out] Constructing SOAP header 
DEBUG [oxalis-out] Constructing service proxy 
DEBUG [oxalis-out] Found WSDL file at jar:file:/E:/src/oxalis-oxalis-2.0.1/oxalis-distribution/target/oxalis-distribution-2.0.1-distro/bin/oxalis-standalone.jar!/META-INF/wsdl/wsdl_v2.0.wsdl 
DEBUG [oxalis-out] Getting remote resource binding port 
DEBUG [oxalis-out] setting connectTimeout 5000 readTimeout 5000 
INFO [oxalis-out] Performing SOAP request to: https://ehf.reknes.no/oxalis/accessPointService 
DEBUG [oxalis-out] SOAP outbound handler called 
DEBUG [oxalis-out] Adding BUSDOX headers to SOAP-envelope

June 24 was the last time I tested message sending and that day it all went well.

The log file for Oxalis has not been modified since june 24.
None of the Tomcat logs contains any errors.

The IN and OUT transactions are properly logged in the default statistics reposiroty (MySQL database table raw_stats)

ap, tstamp, direction, sender, receiver
981672577   2013-07-03 09:27:06 OUT 9908:981672577  9908:810017902
987210818   2013-07-03 09:26:59 IN  9908:981672577  9908:810017902

Except from the console output I logged the only trace I have that something has happened is the localhost_access_log_2013_07_03 from Tomcat

94.75.247.144 - - [03/Jul/2013:08:29:42 +0200] "HEAD /info/ HTTP/1.1" 404 -
213.184.199.212 - - [03/Jul/2013:09:02:02 +0200] "POST /oxalis/accessPointService HTTP/1.1" 200 4331
213.184.199.212 - - [03/Jul/2013:09:02:04 +0200] "POST /oxalis/accessPointService HTTP/1.1" 200 8950
213.184.199.212 - - [03/Jul/2013:09:02:04 +0200] "POST /oxalis/accessPointService HTTP/1.1" 200 4527
213.184.199.212 - - [03/Jul/2013:09:02:08 +0200] "POST /oxalis/accessPointService HTTP/1.1" 200 4535

Clearly something has happened but since I don't have any tracers or error messages to hunt down I don't have a clue where to start.

keystore problem after upgrading java

After upgrading java to 1.7.0_25-b15 I get the error attached below. It doesn't occur with version 1.7.0.21.

Some helpful resources:
http://stackoverflow.com/questions/17331187/xml-dig-sig-error-after-upgrade-to-java7u25
https://issues.apache.org/jira/browse/SANTUARIO-312

The error is:
SEVERE: WSS0237: An Error occurred while populating SAML Policy in Dynamic Policy Callback
java.lang.RuntimeException: Error while handling SAML callbacks
at eu.peppol.security.callbacks.SAMLCallbackHandler.handle(SAMLCallbackHandler.java:109)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.populateAssertion(DefaultCallbackHandler.java:733)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:674)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.populateSAMLPolicy(DefaultSecurityEnvironmentImpl.java:1598)
at com.sun.xml.wss.impl.filter.ExportSamlAssertionFilter.process(ExportSamlAssertionFilter.java:128)
at com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.processSamlToken(AuthenticationTokenFilter.java:121)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:122)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.sendregning.oxalis.Main.main(Main.java:124)
Caused by: com.sun.xml.wss.saml.SAMLException: com.sun.xml.wss.saml.SAMLException: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1375354517316
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:219)
at eu.peppol.security.callbacks.SAMLCallbackHandler.createSenderVouchesSAMLAssertion(SAMLCallbackHandler.java:166)
at eu.peppol.security.callbacks.SAMLCallbackHandler.handle(SAMLCallbackHandler.java:105)
... 37 more
Caused by: com.sun.xml.wss.saml.SAMLException: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1375354517316
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:276)
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:216)
... 39 more
Caused by: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1375354517316
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:412)
at org.jcp.xml.dsig.internal.dom.DOMReference.digest(DOMReference.java:338)
at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.digestReference(DOMXMLSignature.java:471)
at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.sign(DOMXMLSignature.java:367)
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:270)
... 40 more
Caused by: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1375354517316
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:124)
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:404)
... 44 more
Caused by: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1375354517316
at com.sun.org.apache.xml.internal.security.utils.resolver.implementations.ResolverFragment.engineResolve(ResolverFragment.java:90)
at com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolver.resolve(ResourceResolver.java:283)
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:117)
... 45 more

FileNotFoundException log file

07:57:13,841 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[logfile] - Active log file name: ./oxalis-logs/oxalis.log
07:57:13,841 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[logfile] - File property is set to [./oxalis-logs/oxalis.log]
07:57:13,842 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[logfile] - Failed to create parent directories for [/var/lib/tomcat7/./oxalis-logs/oxalis.log]
07:57:13,843 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[logfile] - openFile(./oxalis-logs/oxalis.log,true) call failed. java.io.FileNotFoundException: ./oxalis-logs/oxalis.log (No such file or directory)
at java.io.FileNotFoundException: ./oxalis-logs/oxalis.log (No such file or directory)

Later on it finds my config file described in
07:57:14,620 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will scan for changes in [[/home/ubuntu/oxalis/logback-oxalis-inbound.xml]] every 30 seconds.

But shouldn't this error on missing default ./oxalis-logs/oxalis.log been catched?

Problem with SMP lookup

As a test I registered us in ELMA with the invoice profile. I used another accesspoint service(SendRegning) to send us an invoice. That went well, the invoice arrived shortly after.

Then, I took the same invoice and tried to send it to ourselves with SMP lookup, that failed:

2013-07-03 13:12:27,920 DEBUG [oxalis-com] Constructed SMP url: http://B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A981672577/services/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0
java.lang.RuntimeException: Problem with SMP lookup
        at eu.peppol.smp.SmpLookupManager.getEndpointType(SmpLookupManager.java:101)
        at eu.peppol.smp.SmpLookupManager.getEndpointAddress(SmpLookupManager.java:53)
        at eu.peppol.outbound.api.DocumentSender.getEndpointAddress(DocumentSender.java:133)
        at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
        at eu.sendregning.oxalis.Main.main(Main.java:126)
Caused by: eu.peppol.smp.SmpSignedServiceMetaDataException: Unable to find information for participant: 9908:981672577, documentType: urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4a:ver1.0::2.0, at url: http://B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A981672577/services/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0 ; Unable to connect to http://B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A981672577/services/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0 ; B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org
        at eu.peppol.smp.SmpLookupManager.getServiceMetaData(SmpLookupManager.java:120)
        at eu.peppol.smp.SmpLookupManager.getEndpointType(SmpLookupManager.java:88)
        ... 4 more
Caused by: java.lang.IllegalStateException: Unable to connect to http://B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A981672577/services/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0 ; B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org
        at eu.peppol.util.Util.getUrlContent(Util.java:68)
        at eu.peppol.smp.SmpLookupManager.getServiceMetaData(SmpLookupManager.java:118)
        ... 5 more
Caused by: java.net.UnknownHostException: B-72d0dc83b9e65b4cfe464c4e569be2e5.iso6523-actorid-upis.sml.peppolcentral.org
        at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at sun.net.NetworkClient.doConnect(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.<init>(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
        at eu.peppol.util.Util.getUrlContent(Util.java:66)
        ... 6 more

This is the command I am using to send:

java 
    -jar "E:\src\oxalis-oxalis-2.0.1\oxalis-distribution\target\oxalis-distribution-2.0.1-distro\bin\oxalis-standalone.jar" 
    -kp=*hidden* 
    -f "E:\oxalis_test\res\981672577(reknes).xml" 
    -d "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4a:ver1.0::2.0" 
    -p "urn:www.cenbii.eu:profile:bii04:ver1.0" 
    -r 9908:981672577 
    -s 9908:810017902 -t

error with eu.peppol.jdbc.OxalisDataSourceFactory for oxalis-jdbc-jndi

the file oxalis-jdbc-jndi\src\main\resources\META-INF\services\eu.peppol.jdbc.OxalisDataSourceFactory references the eu.peppol.jdbc.OxalisDataSourceFactoryProviderJndiImpl class, although this class does not exist.

the correct class reference should probably be eu.peppol.jdbc.OxalisDataSourceFactoryJndiImpl

Unable to persist

What could be the cause of this suddenly happening?

11:18:45.915 [rm-server-tube-communicator-fiber-executor-thread-6] ERROR oxalis-inb - Unable to persist
java.lang.NoClassDefFoundError: Could not initialize class eu.peppol.start.persistence.MessageRepositoryFactory$MessageRepositorySingleton
at eu.peppol.start.persistence.MessageRepositoryFactory.getInstance(MessageRepositoryFactory.java:47) ~[oxalis-commons-2.0.1-SNAPSHOT.jar:na]
at eu.peppol.inbound.server.accessPointService.persistMessage(accessPointService.java:203) [accessPointService.class:na]
at eu.peppol.inbound.server.accessPointService.create(accessPointService.java:121) [accessPointService.class:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:616) ~[na:1.6.0_24]
at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:250) [na:2.2.1-1]
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:149) [na:2.2.1-1]
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:88) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:764) [na:2.2.1-1]
at com.sun.xml.ws.api.server.ThreadLocalContainerResolver$2$1.run(ThreadLocalContainerResolver.java:112) [na:2.2.1-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [na:1.6.0_24]

Connection timed out

Jan 2, 2013 2:18:04 PM [com.sun.xml.ws.rx.rm.runtime.ClientTube] createSequences
WARNING: WSRM1106: Attempt to send a [ CreateSequence ] RM session control message failed with an exception
com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection timed out

When sending EHF document to a specific receiver which also is connected to an accesspoint running Oxalis we get the error above. The bad part is that even though it fails on our accesspoint the EHF document is received on the receivers accesspoint and delivered.

Oxalis-standalone error

Hi,

I have been trying to push a message from my local machine to Accesspoint/oxalis as apparently configuration seems to me fine and oxalis-keystore is also placed under my .oxalis folder with Oxalis-global.properties.

I find this error please suggest me how can I solve this:

NFO: WSP5018: Loaded WSIT configuration from file: jar:file:/C:/Users/wha/.oxalis/oxalis-standalone.jar!/META-INF/wsit-client.xml.
013-07-26 11:02:56,238 DEBUG [oxalis-out] Getting remote resource binding port
nitializing the TrustStoreCallbackHandler
013-07-26 11:02:56,956 DEBUG [oxalis-out] setting connectTimeout 5000 readTimeout 5000
013-07-26 11:02:56,956 INFO [oxalis-out] Performing SOAP request to: https://aksesspunkt.compello.com/oxalis/accessPointService
013-07-26 11:02:56,970 DEBUG [oxalis-out] SOAP outbound handler called
013-07-26 11:02:56,970 DEBUG [oxalis-out] Adding BUSDOX headers to SOAP-envelope
013-07-26 11:02:57,058 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Requested SAML callback handling
013-07-26 11:02:57,058 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Creating and setting the SAML Sender Vouches Assertion
ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl populateSAMLPolicy
EVERE: WSS0237: An Error occurred while populating SAML Policy in Dynamic Policy Callback
ava.lang.RuntimeException: Error while handling SAML callbacks
at eu.peppol.security.callbacks.SAMLCallbackHandler.handle(SAMLCallbackHandler.java:109)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.populateAssertion(DefaultCallbackHandler.java:733)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:674)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.populateSAMLPolicy(DefaultSecurityEnvironmentImpl.java:1598)
at com.sun.xml.wss.impl.filter.ExportSamlAssertionFilter.process(ExportSamlAssertionFilter.java:128)
at com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.processSamlToken(AuthenticationTokenFilter.java:121)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:122)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: com.sun.xml.wss.saml.SAMLException: com.sun.xml.wss.saml.SAMLException: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.
ecurity.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1374829377059
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:219)
at eu.peppol.security.callbacks.SAMLCallbackHandler.createSenderVouchesSAMLAssertion(SAMLCallbackHandler.java:166)
at eu.peppol.security.callbacks.SAMLCallbackHandler.handle(SAMLCallbackHandler.java:105)
... 38 more
aused by: com.sun.xml.wss.saml.SAMLException: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceReso
verException: Cannot resolve element with ID SamlID1374829377059
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:276)
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:216)
... 40 more
aused by: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve elemen
with ID SamlID1374829377059
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:412)
at org.jcp.xml.dsig.internal.dom.DOMReference.digest(DOMReference.java:338)
at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.digestReference(DOMXMLSignature.java:471)
at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.sign(DOMXMLSignature.java:367)
at eu.peppol.security.callbacks.SAMLCallbackHandler.sign(SAMLCallbackHandler.java:270)
... 41 more
aused by: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1374829377059
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:124)
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:404)
... 45 more
aused by: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID SamlID1374829377059
at com.sun.org.apache.xml.internal.security.utils.resolver.implementations.ResolverFragment.engineResolve(ResolverFragment.java:90)
at com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolver.resolve(ResourceResolver.java:283)
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:117)
... 46 more

ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.HarnessUtil processWSSPolicy
ARNING: java.lang.RuntimeException: Error while handling SAML callbacks
013-07-26 11:02:57,168 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning keystore
ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.misc.DefaultCallbackHandler getDefaultPrivKeyCert
EVERE: WSS1512: An Error occurred while locating default certificate and private key in KeyStore.
ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.misc.DefaultCallbackHandler getDefaultPrivKeyCert
EVERE: WSS1505: IO Exception occured: failed to get key/certificate from KeyStore (not necessarily i/o exception)
ava.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)

ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl getDefaultPrivKeyCertRequest
EVERE: WSS0216: An Error occurred using CallbackHandler for : SignatureKeyCallback.DefaultPrivKeyCertRequest
ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl getDefaultPrivKeyCertRequest
EVERE: WSS0217: An Error occurred using CallbackHandler handle() Method.
ava.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1474)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
... 36 more

ul 26, 2013 11:02:57 AM com.sun.xml.wss.impl.filter.SignatureFilter process
EVERE: WSS1417: Error while processing signature [Ljava.lang.Object;@4ee358
ul 26, 2013 11:02:57 AM com.sun.xml.wss.jaxws.impl.SecurityTubeBase secureOutboundMessage
EVERE: WSSTUBE0024: Error in Securing Outbound Message.
om.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey
n KeyStore
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:321)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:266)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
... 33 more
aused by: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1474)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
... 34 more
aused by: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
... 36 more

ul 26, 2013 11:02:57 AM com.sun.xml.wss.jaxws.impl.SecurityClientTube processClientRequestPacket
EVERE: WSSTUBE0024: Error in Securing Outbound Message.
om.sun.xml.wss.impl.WssSoapFaultException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and priva
eKey in KeyStore
at com.sun.xml.wss.impl.SecurableSoapMessage.newSOAPFaultException(SecurableSoapMessage.java:349)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:393)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and
rivateKey in KeyStore
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:321)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
... 28 more
aused by: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:266)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
... 33 more
aused by: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1474)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
... 34 more
aused by: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
... 36 more

ul 26, 2013 11:02:57 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube] __doRun
EVERE: WSRM1106: Attempt to send a [ CreateSequence ] RM session control message failed with an exception
avax.xml.ws.WebServiceException: WSSTUBE0024: Error in Securing Outbound Message.
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:328)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: javax.xml.ws.soap.SOAPFaultException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and
rivateKey in KeyStore
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:715)
... 28 more
aused by: com.sun.xml.wss.impl.WssSoapFaultException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificat
and privateKey in KeyStore
at com.sun.xml.wss.impl.SecurableSoapMessage.newSOAPFaultException(SecurableSoapMessage.java:349)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:393)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
... 27 more
aused by: com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and
rivateKey in KeyStore
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:321)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
... 28 more
aused by: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:266)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
... 33 more
aused by: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1474)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
... 34 more
aused by: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
... 36 more

om.sun.xml.ws.rx.RxRuntimeException: WSRM1106: Attempt to send a [ CreateSequence ] RM session control message failed with an exception
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:559)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:415)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:338)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:179)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.client.Stub.process(Stub.java:443)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:174)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:154)
at com.sun.proxy.$Proxy44.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:297)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:237)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:171)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:125)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:81)
at eu.sendregning.oxalis.Main.main(Main.java:130)
aused by: javax.xml.ws.WebServiceException: WSSTUBE0024: Error in Securing Outbound Message.
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:328)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:247)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:555)
... 19 more
aused by: javax.xml.ws.soap.SOAPFaultException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and
rivateKey in KeyStore
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:715)
... 28 more
aused by: com.sun.xml.wss.impl.WssSoapFaultException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificat
and privateKey in KeyStore
at com.sun.xml.wss.impl.SecurableSoapMessage.newSOAPFaultException(SecurableSoapMessage.java:349)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:393)
at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:323)
... 27 more
aused by: com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and
rivateKey in KeyStore
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:321)
at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:99)
at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:278)
at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:194)
at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:155)
at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:388)
... 28 more
aused by: com.sun.xml.wss.XWSSecurityException: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:266)
at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:235)
... 33 more
aused by: java.lang.RuntimeException: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1474)
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.handle(DefaultCallbackHandler.java:553)
at com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getDefaultPrivKeyCertRequest(DefaultSecurityEnvironmentImpl.java:261)
... 34 more
aused by: java.lang.RuntimeException: An Error occurred while locating default certificate and privateKey in KeyStore
at com.sun.xml.wss.impl.misc.DefaultCallbackHandler.getDefaultPrivKeyCert(DefaultCallbackHandler.java:1469)
... 36 more

Best regards,
Waqar Hassan
Compello AS '
Oslo

handshake alert: unrecognized_name ????

C:\a>java -jar C:/difi/oxalis-standalone.jar -f C:/difi/HelseVest2.xml -s 9908:985206732 --kf C:/apache-tomcat-7.0.25/conf/tomcat.keystore --kp password -r 9908:976098897

2012-02-22 20:35:06,525 DEBUG [oxalis-out] Constructed SMP url: http://B-3ef88229f33cab598f9bad0185bad411.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis::9908:9760
98897/services/busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:www.peppol.eu:bis:peppol4
a:ver1.0::2.0
2012-02-22 20:35:07,755 INFO [oxalis-out] Found endpoint address for 9908:976098897 from SMP: https://aksesspunkt.sendregning.no/oxalis/accessPointService
2012-02-22 20:35:07,756 INFO [oxalis-out] Document destination is https://aksesspunkt.sendregning.no/oxalis/accessPointService
2012-02-22 20:35:07,780 DEBUG [oxalis-out] Constructing document body
2012-02-22 20:35:07,781 DEBUG [oxalis-out] Constructing SOAP header
2012-02-22 20:35:07,856 DEBUG [oxalis-out] Constructing service proxy
2012-02-22 20:35:07,859 INFO [oxalis-com] /oxalis.properties --> jar:file:/C:/difi/oxalis-standalone.jar!/oxalis.properties
2012-02-22 20:35:07,859 INFO [oxalis-com] Loading properties from /oxalis-web.properties, which will fallback to /oxalis.properties if properties do not exist.
2012-02-22 20:35:07,860 INFO [oxalis-com] No properties loaded from /oxalis-web.properties, file was not found in classpath
2012-02-22 20:35:07,862 INFO [oxalis-com] ======= Properties in effect: =======
2012-02-22 20:35:07,863 INFO [oxalis-com] peppol.servicename = accessPointService
2012-02-22 20:35:07,864 INFO [oxalis-com] oxalis.wsdl = wsdl_v2.0
2012-02-22 20:35:07,866 INFO [oxalis-com] peppol.senderid = busdox:sender
2012-02-22 20:35:07,867 INFO [oxalis-com] ======================================
2012-02-22 20:35:07,869 INFO [oxalis-com] Configuration loaded.
2012-02-22 20:35:07,871 DEBUG [oxalis-out] Found WSDL file at jar:file:/C:/difi/oxalis-standalone.jar!/META-INF/wsdl/wsdl_v2.0.wsdl
feb 22, 2012 8:35:08 PM [com.sun.xml.ws.policy.parser.PolicyConfigParser] parse
INFO: WSP5018: Loaded WSIT configuration from file: jar:file:/C:/difi/oxalis-standalone.jar!/META-INF/wsit-client.xml.
2012-02-22 20:35:08,344 DEBUG [oxalis-out] Getting remote resource binding port
2012-02-22 20:35:09,712 DEBUG [oxalis-out] SOAP outbound handler called
2012-02-22 20:35:09,713 DEBUG [oxalis-out] Adding BUSDOX headers to SOAP-envelope
2012-02-22 20:35:09,876 DEBUG [oxalis-out] Requested SAML callback handling
2012-02-22 20:35:09,877 DEBUG [oxalis-out] Creating and setting the SAML Sender Vouches Assertion
2012-02-22 20:35:10,432 DEBUG [oxalis-out] Keystore callback handler: returning keystore
2012-02-22 20:35:10,433 DEBUG [oxalis-out] Keystore callback handler: returning private key
feb 22, 2012 8:35:11 PM [com.sun.xml.ws.rx.rm.runtime.ClientTube] createSequences
WARNING: WSRM1106: Attempt to send a [ CreateSequence ] RM session control message failed with an exception
com.sun.xml.ws.client.ClientTransportException: HTTP transport error: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name
at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:132)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:209)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:137)
at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:138)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
at com.sun.xml.ws.rx.util.FiberExecutor.runSync(FiberExecutor.java:94)
at com.sun.xml.ws.rx.util.Communicator.send(Communicator.java:423)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.sendSessionControlMessage(ClientTube.java:564)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:424)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:347)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:188)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
at com.sun.xml.ws.client.Stub.process(Stub.java:323)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
at $Proxy43.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:136)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:91)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:165)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:119)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:75)
at eu.sendregning.oxalis.Main.main(Main.java:109)
Caused by: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name
at sun.security.ssl.ClientHandshaker.handshakeAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:120)
... 29 more

Problem with oxalis-inb

What could cause this one?

19:53:51.303 [rm-server-tube-communicator-fiber-executor-thread-1] ERROR oxalis-inb - Problem while handling inbound document: ReadWriteSerializationCopyStrategy doesn't implement net.sf.ehcache.store.compound.CopyStrategy
java.lang.RuntimeException: ReadWriteSerializationCopyStrategy doesn't implement net.sf.ehcache.store.compound.CopyStrategy
at net.sf.ehcache.config.CopyStrategyConfiguration.getCopyStrategyInstance(CopyStrategyConfiguration.java:83) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.config.CacheConfiguration.getCopyStrategy(CacheConfiguration.java:1000) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.store.compound.impl.OverflowToDiskStore.(OverflowToDiskStore.java:48) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.store.compound.impl.OverflowToDiskStore.create(OverflowToDiskStore.java:66) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.Cache.initialise(Cache.java:1113) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.CacheManager.addCacheNoCheck(CacheManager.java:1095) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.CacheManager.addCacheIfAbsent(CacheManager.java:1589) ~[ehcache-core-2.4.7.jar:na]
at net.sf.ehcache.CacheManager.addCacheIfAbsent(CacheManager.java:1612) ~[ehcache-core-2.4.7.jar:na]
at eu.peppol.persistence.sql.dao.DimensionJdbcHelper.(DimensionJdbcHelper.java:32) ~[oxalis-sql-2.0.1-SNAPSHOT.jar:na]
at eu.peppol.persistence.sql.StatisticsRepositoryJdbcImpl.(StatisticsRepositoryJdbcImpl.java:33) ~[oxalis-sql-2.0.1-SNAPSHOT.jar:na]
at eu.peppol.persistence.sql.StatisticsRepositoryFactoryJdbcImpl.getInstance(StatisticsRepositoryFactoryJdbcImpl.java:32) ~[oxalis-sql-2.0.1-SNAPSHOT.jar:na]
at eu.peppol.inbound.server.accessPointService.persistStatistics(accessPointService.java:303) ~[accessPointService.class:na]
at eu.peppol.inbound.server.accessPointService.create(accessPointService.java:126) ~[accessPointService.class:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_24]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.6.0_24]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:616) ~[na:1.6.0_24]
at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:250) [na:2.2.1-1]
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:149) [na:2.2.1-1]
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:88) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950) [na:2.2.1-1]
at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:764) [na:2.2.1-1]
at com.sun.xml.ws.api.server.ThreadLocalContainerResolver$2$1.run(ThreadLocalContainerResolver.java:112) [na:2.2.1-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [na:1.6.0_24]
Caused by: java.lang.ClassCastException: net.sf.ehcache.store.compound.ReadWriteSerializationCopyStrategy cannot be cast to net.sf.ehcache.store.compound.ReadWriteCopyStrategy
at net.sf.ehcache.config.CopyStrategyConfiguration.getCopyStrategyInstance(CopyStrategyConfiguration.java:74) ~[ehcache-core-2.4.7.jar:na]
... 27 common frames omitted

Oxalis does not accept both V1 and V2 certificates during the transition period

Due to a mistake on my side, Oxalis will only support either V1 or V2 certificates.

However during the migration/transition period, from Sept 1, 2013 to Sept 31, 2013 both versions must be accepted.

Oxalis-standalone sending ID Behaviour error

I hope you are doing perfect. Which parameter would command-line take first into oxalis-standalone pushup message either –r or –s?
As we witness into command line we pass first parameter recipient -s 9908:984408854 and then-r 9908:987700912 parameter into command-line BUT down into log it shows like as different ID values and order too:

2013-08-07 10:12:45,274 INFO [oxalis-out] Sender: 9908:810304642
2013-08-07 10:12:45,275 INFO [oxalis-out] Recipient: 9908:987700912

Is that error, please write us?

C:>java -jar C:\Users\wha\Desktop\serverJarfile\oxalis-standalone\oxalis-standalone.jar -f C:\Users\wha.oxalis\InternalToEhf.xml -s 9908:984408854 -r 9908:987700912 -kp Comp20+-12
2013-08-07 10:35:19,998 DEBUG [oxalis-com] Constructed SMP url: http://B-3e3b7c56d786753a39b73b60396487bd.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A987700912/services
/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis
%3Apeppol4a%3Aver1.0%3A%3A2.0
Searching the class path for an instance of StatisticsRepositoryFactory
2013-08-07 10:35:20,584 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryProvider] Loading instance of eu.peppol.jdbc.OxalisDataSourceFactory from class path using META-INF/services idiom
2013-08-07 10:35:20,586 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] Configuring DataSource wrapped in a Database Connection Pool, using custom loader
Initialising the Oxalis global configuration ....
2013-08-07 10:35:20,587 DEBUG [eu.peppol.util.OxalisHomeDirectory] Attempting to locate home dir....
Oxalis home directory: C:\Users\wha.oxalis
2013-08-07 10:35:20,590 INFO [eu.peppol.util.GlobalConfiguration] oxalis.keystore = c:/users/wha/.oxalis/oxalis.keystore
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.keystore.password = Comp20+-12
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.inbound.message.store = /var/peppol
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.persistence.class.path =
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.soap.trace = false
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.jdbc.driver.class = com.mysql.jdbc.Driver
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.jdbc.connection.uri = jdbc:mysql://localhost/oxalis
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.jdbc.user = oxalis
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.jdbc.password = Blomster2013
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.jdbc.class.path = file:///Users/wha/.m2/repository/mysql/mysql-connector-java/5.1.18/mysql-connector-java-5.1.18.jar
2013-08-07 10:35:20,591 INFO [eu.peppol.util.GlobalConfiguration] oxalis.datasource.jndi.name = jdbc/oxalis
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.statistics.private.key =
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.inbound.log.config = c:/users/wha/.oxalis/logback-oxalis-server.xml
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.app.log.config = c:/users/wha/.oxalis/logback-oxalis-app.xml
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.ap.identifier = NO-SR
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.pki.version = V1
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.operation.mode = TEST
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.connection.timeout = 5000
2013-08-07 10:35:20,592 INFO [eu.peppol.util.GlobalConfiguration] oxalis.read.timeout = 5000
Verifying properties ....
2013-08-07 10:35:20,593 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] Loading JDBC Driver with custom class path: file:///Users/wha/.m2/repository/mysql/mysql-connector-java/5.1.18/mysql-conn
ector-java-5.1.18.jar
2013-08-07 10:35:20,593 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] className=com.mysql.jdbc.Driver
2013-08-07 10:35:20,593 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] connectURI=jdbc:mysql://localhost/oxalis
2013-08-07 10:35:20,593 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] userName=oxalis
2013-08-07 10:35:20,593 DEBUG [eu.peppol.jdbc.OxalisDataSourceFactoryDbcpImpl] password=Blomster2013
2013-08-07 10:35:20,605 DEBUG [eu.peppol.start.identifier.KeystoreManager] trust store resource name: truststore.jks
2013-08-07 10:35:20,605 INFO [eu.peppol.start.identifier.KeystoreManager] Loading truststore from truststore.jks
2013-08-07 10:35:20,620 WARN [net.sf.ehcache.config.ConfigurationFactory] No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/C:/Users/wha/Desktop/
serverJarfile/oxalis-standalone/oxalis-standalone.jar!/ehcache-failsafe.xml
2013-08-07 10:35:20,620 DEBUG [net.sf.ehcache.config.ConfigurationFactory] Configuring ehcache from URL: jar:file:/C:/Users/wha/Desktop/serverJarfile/oxalis-standalone/oxalis-standalone.jar!/ehcache-f
ailsafe.xml
2013-08-07 10:35:20,621 DEBUG [net.sf.ehcache.config.ConfigurationFactory] Configuring ehcache from InputStream
2013-08-07 10:35:20,650 DEBUG [net.sf.ehcache.config.BeanHandler] Ignoring ehcache attribute xmlns:xsi
2013-08-07 10:35:20,651 DEBUG [net.sf.ehcache.config.BeanHandler] Ignoring ehcache attribute xsi:noNamespaceSchemaLocation
2013-08-07 10:35:20,652 DEBUG [net.sf.ehcache.config.DiskStoreConfiguration] Disk Store Path: C:\Users\wha\AppData\Local\Temp
2013-08-07 10:35:20,666 DEBUG [net.sf.ehcache.CacheManager] Creating new CacheManager with default config
2013-08-07 10:35:20,670 DEBUG [net.sf.ehcache.util.PropertyUtil] propertiesString is null.
2013-08-07 10:35:20,679 DEBUG [net.sf.ehcache.config.ConfigurationHelper] No CacheManagerEventListenerFactory class specified. Skipping...
2013-08-07 10:35:20,711 DEBUG [net.sf.ehcache.Cache] No BootstrapCacheLoaderFactory class specified. Skipping...
2013-08-07 10:35:20,711 DEBUG [net.sf.ehcache.Cache] CacheWriter factory not configured. Skipping...
2013-08-07 10:35:20,713 DEBUG [net.sf.ehcache.config.ConfigurationHelper] No CacheExceptionHandlerFactory class specified. Skipping...
2013-08-07 10:35:20,730 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for AccessPointIdentifier
2013-08-07 10:35:20,738 DEBUG [net.sf.ehcache.DiskStorePathManager] Using diskstore path C:\Users\wha\AppData\Local\Temp
2013-08-07 10:35:20,738 DEBUG [net.sf.ehcache.DiskStorePathManager] Holding exclusive lock on C:\Users\wha\AppData\Local\Temp.ehcache-diskstore.lock
2013-08-07 10:35:20,739 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0041ccess%0050oint%0049dentifier.index
2013-08-07 10:35:20,745 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0041ccess%0050oi
nt%0049dentifier.index
2013-08-07 10:35:20,745 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0041ccess%0050oint%0049dentifier.index
2013-08-07 10:35:20,750 DEBUG [net.sf.ehcache.Cache] Initialised cache: AccessPointIdentifier
2013-08-07 10:35:20,750 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'AccessPointIdentifier'.
2013-08-07 10:35:20,752 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for ParticipantId
2013-08-07 10:35:20,753 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050articipant%0049d.index
2013-08-07 10:35:20,754 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0050articipant%0
049d.index
2013-08-07 10:35:20,754 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050articipant%0049d.index
2013-08-07 10:35:20,755 DEBUG [net.sf.ehcache.Cache] Initialised cache: ParticipantId
2013-08-07 10:35:20,755 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'ParticipantId'.
2013-08-07 10:35:20,756 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for PeppolDocumentTypeId
2013-08-07 10:35:20,757 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050eppol%0044ocument%0054ype%0049d.index
2013-08-07 10:35:20,757 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0050eppol%0044oc
ument%0054ype%0049d.index
2013-08-07 10:35:20,757 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050eppol%0044ocument%0054ype%0049d.index
2013-08-07 10:35:20,758 DEBUG [net.sf.ehcache.Cache] Initialised cache: PeppolDocumentTypeId
2013-08-07 10:35:20,758 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'PeppolDocumentTypeId'.
2013-08-07 10:35:20,759 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for ChannelId
2013-08-07 10:35:20,760 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0043hannel%0049d.index
2013-08-07 10:35:20,761 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0043hannel%0049d
.index
2013-08-07 10:35:20,761 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0043hannel%0049d.index
2013-08-07 10:35:20,761 DEBUG [net.sf.ehcache.Cache] Initialised cache: ChannelId
2013-08-07 10:35:20,761 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'ChannelId'.
2013-08-07 10:35:20,762 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for PeppolProcessTypeId
2013-08-07 10:35:20,763 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050eppol%0050rocess%0054ype%0049d.index
2013-08-07 10:35:20,764 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0050eppol%0050ro
cess%0054ype%0049d.index
2013-08-07 10:35:20,764 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0050eppol%0050rocess%0054ype%0049d.index
2013-08-07 10:35:20,766 DEBUG [net.sf.ehcache.Cache] Initialised cache: PeppolProcessTypeId
2013-08-07 10:35:20,768 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'PeppolProcessTypeId'.
2013-08-07 10:35:20,770 DEBUG [net.sf.ehcache.store.MemoryStore] Initialized net.sf.ehcache.store.MemoryStore for Date
2013-08-07 10:35:20,771 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0044ate.index
2013-08-07 10:35:20,772 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Matching data file missing (or empty) for index file. Deleting index file C:\Users\wha\AppData\Local\Temp%0044ate.index
2013-08-07 10:35:20,775 DEBUG [net.sf.ehcache.store.disk.DiskStorageFactory] Failed to delete file %0044ate.index
2013-08-07 10:35:20,777 DEBUG [net.sf.ehcache.Cache] Initialised cache: Date
2013-08-07 10:35:20,778 DEBUG [net.sf.ehcache.config.ConfigurationHelper] CacheDecoratorFactory not configured for defaultCache. Skipping for 'Date'.

2013-08-07 10:35:20,782 DEBUG [oxalis-com] Constructed SMP url: http://B-3e3b7c56d786753a39b73b60396487bd.iso6523-actorid-upis.sml.peppolcentral.org/iso6523-actorid-upis%3A%3A9908%3A987700912/services
/busdox-docid-qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3Aubl%3Aschema%3Axsd%3AInvoice-2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww.peppol.eu%3Abis
%3Apeppol4a%3Aver1.0%3A%3A2.0
2013-08-07 10:35:20,837 INFO [oxalis-com] Found endpoint address for 9908:987700912 from SMP: https://aksesspunkt.compello.com/oxalis/accessPointService
2013-08-07 10:35:20,838 INFO [oxalis-out] Document destination is https://aksesspunkt.compello.com/oxalis/accessPointService
2013-08-07 10:35:20,857 DEBUG [oxalis-out] Constructing document body
2013-08-07 10:35:20,858 DEBUG [oxalis-out] Constructing SOAP header
2013-08-07 10:35:20,920 DEBUG [oxalis-out] Constructing service proxy
2013-08-07 10:35:20,921 DEBUG [oxalis-out] Found WSDL file at jar:file:/C:/Users/wha/Desktop/serverJarfile/oxalis-standalone/oxalis-standalone.jar!/META-INF/wsdl/wsdl_v2.0.wsdl
aug 07, 2013 10:35:21 AM [com.sun.xml.ws.policy.parser.PolicyConfigParser] parse
INFO: WSP5018: Loaded WSIT configuration from file: jar:file:/C:/Users/wha/Desktop/serverJarfile/oxalis-standalone/oxalis-standalone.jar!/META-INF/wsit-client.xml.
2013-08-07 10:35:21,218 DEBUG [oxalis-out] Getting remote resource binding port
Initializing the TrustStoreCallbackHandler
2013-08-07 10:35:22,131 DEBUG [oxalis-out] setting connectTimeout 5000 readTimeout 5000
2013-08-07 10:35:22,131 INFO [oxalis-out] Performing SOAP request to: https://aksesspunkt.compello.com/oxalis/accessPointService
2013-08-07 10:35:22,147 DEBUG [oxalis-out] SOAP outbound handler called
2013-08-07 10:35:22,147 DEBUG [oxalis-out] Adding BUSDOX headers to SOAP-envelope
2013-08-07 10:35:22,246 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Requested SAML callback handling
2013-08-07 10:35:22,247 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Creating and setting the SAML Sender Vouches Assertion
2013-08-07 10:35:22,475 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning keystore
2013-08-07 10:35:22,476 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning private key
2013-08-07 10:35:22,687 DEBUG [oxalis-out] Inspecting peer certificate CN=.compello.com, OU=PremiumSSL Wildcard, OU=Hosted by Secorio ApS, OU=Sandefjord, O=Compello AS, STREET=Skolmar 32 C, L=Sandefj
ord, ST=Vestfold, OID.2.5.4.17=3232, C=NO, issued by CN=COMODO High-Assurance Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB
2013-08-07 10:35:22,732 WARN [oxalis-out] Server SSL sertificate [
[
Version: V3
Subject: CN=.compello.com, OU=PremiumSSL Wildcard, OU=Hosted by Secorio ApS, OU=Sandefjord, O=Compello AS, STREET=Skolmar 32 C, L=Sandefjord, ST=Vestfold, OID.2.5.4.17=3232, C=NO
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5

Key: Sun RSA public key, 2048 bits
modulus: 173385790482966224832904514352944549288410011819442147779333747005805724405468092130152594654311357860059421038934733634959062688693614432156059501433839475430818437169525716878773279216838
52724043635347371605907393910668371947817266267626897132768392011285775461891884383657691183949971062661860829652126160663041229215653816671644508567424639643271279685564726565748968561829394126338825
22571401924920203817025276307392832035032689245581602260403843784219636868797773919480159387008123933671644123700680435678355234822350082585875770674169575857342854208234867555177539796708048418276896
1369566211966839274840855921
public exponent: 65537
Validity: [From: Mon Jul 30 02:00:00 CEST 2012,
To: Thu Jul 31 01:59:59 CEST 2014]
Issuer: CN=COMODO High-Assurance Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB
SerialNumber: [ 0b51f8ff 1bab776d 12a0f8ef ba8113a1]

Certificate Extensions: 9
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
[
accessMethod: caIssuers
accessLocation: URIName: http://crt.comodoca.com/COMODOHigh-AssuranceSecureServerCA.crt
,
accessMethod: ocsp
accessLocation: URIName: http://ocsp.comodoca.com
]
]

[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 3F D5 B5 D0 D6 44 79 50 4A 17 A3 9B 8C 4A DC B8 ?....DyPJ....J..
0010: B0 22 64 6B ."dk
]
]

[3]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:false
PathLen: undefined
]

[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
[URIName: http://crl.comodoca.com/COMODOHigh-AssuranceSecureServerCA.crl]
]]

[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [1.3.6.1.4.1.6449.1.2.1.3.4]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: 0000: 16 1D 68 74 74 70 73 3A 2F 2F 73 65 63 75 72 65 ..https://secure
0010: 2E 63 6F 6D 6F 64 6F 2E 63 6F 6D 2F 43 50 53 .comodo.com/CPS

]] ]
]

[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
]

[7]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Key_Encipherment
]

[8]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: *.compello.com
DNSName: compello.com
]

[9]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 71 D4 5E 4B 36 C9 37 4D 2C EA 9B B0 DF 02 D3 EA q.^K6.7M,.......
0010: 16 5F C0 EA ._..
]
]

]
Algorithm: [SHA1withRSA]
Signature:
0000: B1 FA A9 40 BD 79 5B 51 B0 73 AD 78 52 33 0F 9C [email protected][Q.s.xR3..
0010: 80 AF 63 C0 4C 8B F7 F1 41 DE 94 16 92 4A D2 F1 ..c.L...A....J..
0020: 73 5A ED AF E6 6D 2B 31 0C E4 83 6E 02 76 76 8F sZ...m+1...n.vv.
0030: 70 AB CD DE 2A 08 80 8E 04 02 7E A6 39 F8 A1 88 p...*.......9...
0040: 9F 45 FB 57 86 A1 7B E4 D2 8F 32 BF CD 72 AF E0 .E.W......2..r..
0050: 2E 2B 34 00 7C FA 68 04 0E 18 E8 67 38 86 54 34 .+4...h....g8.T4
0060: 13 95 41 98 32 FD ED 0B 6E 8A 2E 9B 5C 9C 9F CB ..A.2...n......
0070: F9 D7 51 AB 64 4B 65 45 96 B7 70 90 41 3F B0 C0 ..Q.dKeE..p.A?..
0080: E3 26 A5 7D A5 54 65 3D 2B EB D6 94 C6 8A B1 62 .&...Te=+......b
0090: 99 FD A9 2C 60 4D 06 82 47 12 11 58 74 0A 1B 34 ...,`M..G..Xt..4
00A0: C8 2F C4 94 58 97 5E 5F 4A 6E 9C 39 DA 3A DF E2 ./..X.^_Jn.9.:..
00B0: 0C 1A 74 F9 65 3F F4 75 FF 13 67 3E DB 4A 9D 96 ..t.e?.u..g>.J..
00C0: 18 86 32 00 AD 03 E9 5E AF 62 89 EF 7B FB DC E4 ..2....^.b......
00D0: AC 0E 86 B8 CC A4 E3 78 24 BE 27 F1 9E 37 D0 6F .......x$.'..7.o
00E0: EB 5C 49 21 54 84 B0 CF 31 BC 0D AC E8 9F 05 09 .\I!T...1.......
00F0: B3 A6 93 B3 CE B7 08 B4 43 48 7C 33 14 28 FD BB ........CH.3.(..

] is not trusted: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested
target
This cause might be a missing root certificate in your local truststore
2013-08-07 10:35:22,851 DEBUG [oxalis-out] Void SSL server certificate check performed.
2013-08-07 10:35:22,852 DEBUG [oxalis-out] Returning trusted root certificates
2013-08-07 10:35:24,457 DEBUG [eu.peppol.security.callbacks.TrustStoreCallbackHandler] Returning truststore
2013-08-07 10:35:24,502 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Requested SAML callback handling
2013-08-07 10:35:24,502 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Creating and setting the SAML Sender Vouches Assertion
2013-08-07 10:35:24,514 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning private key
2013-08-07 10:35:26,007 DEBUG [oxalis-out] SOAP outbound handler called
2013-08-07 10:35:26,008 INFO [oxalis-out] Sender: 9908:810304642
2013-08-07 10:35:26,008 INFO [oxalis-out] Recipient: 9908:987700912
2013-08-07 10:35:26,008 INFO [oxalis-out] Destination: https://aksesspunkt.compello.com/oxalis/accessPointService
2013-08-07 10:35:26,008 INFO [oxalis-out] Message uuid:c0824b40-6d66-4db2-89c3-5cdf47df90e1 has been successfully delivered
2013-08-07 10:35:26,021 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Requested SAML callback handling
2013-08-07 10:35:26,021 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Creating and setting the SAML Sender Vouches Assertion
2013-08-07 10:35:26,032 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning private key
aug 07, 2013 10:35:29 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube] closeSequences
INFO: WSRM1157: Waiting for sequence [ uuid:5bf01c23-5c1b-42ec-82a9-02c85b79fba8 ] state change to [ CLOSED ] has timed out after 3á000 milliseconds
2013-08-07 10:35:29,117 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Requested SAML callback handling
2013-08-07 10:35:29,117 DEBUG [eu.peppol.security.callbacks.SAMLCallbackHandler] Creating and setting the SAML Sender Vouches Assertion
2013-08-07 10:35:29,129 DEBUG [eu.peppol.security.callbacks.KeyStoreCallbackHandler] Keystore callback handler: returning private key
aug 07, 2013 10:35:32 AM [com.sun.xml.ws.rx.rm.runtime.ClientTube] closeRmSession
INFO: WSRM1157: Waiting for sequence [ uuid:5bf01c23-5c1b-42ec-82a9-02c85b79fba8 ] state change to [ TERMINATING ] has timed out after 3á000 milliseconds
Message sent, assigned message id:uuid:c0824b40-6d66-4db2-89c3-5cdf47df90e1

Assertion failure on oxalis deploy

On deployment of Oxalis.war v. 1.18 I get an assertion failure from Tomcat 7.0.34. Oxalis was built on Windows 7 with jdk 7.1.7 and metro 2.2.1 and maven 3..0.4
extract from catalina.out:

INFO: Deploying web application archive C:\tomcat\apache-tomcat-7.0.34\webapps\oxalis.war
jan 09, 2013 11:32:39 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener parseAdaptersAndCreateDelegate
SEVERE: WSSERVLET11: failed to parse runtime descriptor: javax.xml.ws.WebServiceException: com.sun.xml.ws.policy.PolicyException: WSP1015: Server side assertion validation failed for "{http://docs.oasis-open.org/ws-rx/wsrmp/200702}RMAssertion" assertion. Assertion was evaluated as "UNKNOWN".

Implement support for new certificate scheme

Reporting statistics to regional authority

START: ChannelIdentifier

After setting up our access point, we are ready to receive invoices etc with the Norwegian EHF format for electronic invoices. In that regard, we are unsure what ChannelIdentifier is used for?

Does anyone use it? What do the What do you put in this id?
How Difi recommend it to be used in Norway?

Change request for SmpLookupManager

As far as I know current implementation of getServiceGroups() throws an exception if there are no document types participant can receive.

We would like to separate this scenario from one when ELMA is actually down.

Perfect solution would be:

return Collection.emptyList when the result set is empty
throw an exception when ELMA is down.

And also, SmpLookupException extends Throwable. Is there any particular reason it doesn't just extend Exception? We hardly ever catch Throwable which contain errors as well.

Thanks

Error sending testXML

I am trying to send a test locally.
Has this anything to do with sertificates

java -jar oxalis-standalone.jar -f C:\difi\HelseVest2.xml -r 9908:985206732 -s 9908:985206732 --kf C:\apache-tomcat-7.0.25\bin\tomcat.keystore --kp password -u https://localhost:8443/oxalis/accessPointService?wsdl

2012-02-14 13:47:04,269 INFO [oxalis-out] Document destination is https://localhost:8443/oxalis/accessPointService?wsdl
2012-02-14 13:47:04,299 DEBUG [oxalis-out] Constructing document body
2012-02-14 13:47:04,299 DEBUG [oxalis-out] Constructing SOAP header
2012-02-14 13:47:04,409 DEBUG [oxalis-out] Constructing service proxy
2012-02-14 13:47:04,409 INFO [oxalis-com] /oxalis.properties --> jar:file:/C:/apache-tomcat-7.0.25/oxalis/oxalis-standalone/oxalis-standalone.jar!/oxalis.properties
2012-02-14 13:47:04,409 INFO [oxalis-com] Loading properties from /oxalis-web.properties, which will fallback to /oxalis.properties if properties do not exist.
2012-02-14 13:47:04,409 INFO [oxalis-com] No properties loaded from /oxalis-web.properties, file was not found in classpath
2012-02-14 13:47:04,409 INFO [oxalis-com] ======= Properties in effect: =======
2012-02-14 13:47:04,409 INFO [oxalis-com] peppol.servicename = accessPointService
2012-02-14 13:47:04,409 INFO [oxalis-com] oxalis.wsdl = wsdl_v2.0
2012-02-14 13:47:04,409 INFO [oxalis-com] peppol.senderid = busdox:sender
2012-02-14 13:47:04,419 INFO [oxalis-com] ======================================
2012-02-14 13:47:04,419 INFO [oxalis-com] Configuration loaded.
2012-02-14 13:47:04,419 DEBUG [oxalis-out] Found WSDL file at jar:file:/C:/apache-tomcat-7.0.25/oxalis/oxalis-standalone/oxalis-standalone.jar!/META-INF/wsdl/wsdl_v2.0.wsdl
feb 14, 2012 1:47:05 PM [com.sun.xml.ws.policy.parser.PolicyConfigParser] parse
INFO: WSP5018: Loaded WSIT configuration from file: jar:file:/C:/apache-tomcat-7.0.25/oxalis/oxalis-standalone/oxalis-standalone.jar!/META-INF/wsit-client.xml.
2012-02-14 13:47:05,099 DEBUG [oxalis-out] Getting remote resource binding port
2012-02-14 13:47:06,539 DEBUG [oxalis-out] SOAP outbound handler called
2012-02-14 13:47:06,539 DEBUG [oxalis-out] Adding BUSDOX headers to SOAP-envelope
2012-02-14 13:47:06,699 DEBUG [oxalis-out] Requested SAML callback handling
2012-02-14 13:47:06,699 DEBUG [oxalis-out] Creating and setting the SAML Sender Vouches Assertion
2012-02-14 13:47:07,049 DEBUG [oxalis-out] Keystore callback handler: returning keystore
2012-02-14 13:47:07,049 DEBUG [oxalis-out] Keystore callback handler: returning private key
2012-02-14 13:47:07,329 DEBUG [oxalis-out] Void SSL server certificate check OK
2012-02-14 13:47:07,359 DEBUG [oxalis-out] Void hostname verification OK feb 14, 2012 1:47:07 PM [com.sun.xml.ws.rx.rm.runtime.ClientTube] createSequences
SEVERE: WSRM1115: CreateSequence was refused by the RMDestination feb 14, 2012 1:47:07 PM [com.sun.xml.ws.rx.rm.runtime.ClientTube] __doRun
SEVERE: WSRM1115: CreateSequence was refused by the RMDestination

com.sun.xml.ws.rx.RxRuntimeException: WSRM1115: CreateSequence was refused by the RMDestination
at com.sun.xml.ws.rx.rm.runtime.ClientTube.verifyResponse(ClientTube.java:664)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.createSequences(ClientTube.java:425)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.openRmSession(ClientTube.java:347)
at com.sun.xml.ws.rx.rm.runtime.ClientTube.processRequest(ClientTube.java:188)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
at com.sun.xml.ws.client.Stub.process(Stub.java:323)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
at $Proxy43.create(Unknown Source)
at eu.peppol.outbound.soap.SoapDispatcher.sendSoapMessage(SoapDispatcher.java:136)
at eu.peppol.outbound.soap.SoapDispatcher.send(SoapDispatcher.java:91)
at eu.peppol.outbound.api.DocumentSender.send(DocumentSender.java:165)
at eu.peppol.outbound.api.DocumentSender.sendInvoice(DocumentSender.java:119)
at eu.sendregning.oxalis.Main.main(Main.java:121)

Fast Infoset decoding is not accepted

11:32:44.844 [http-bio-8443-exec-42] DEBUG no.unimicro.ap.UniOutbox - sender: 9908:954676250
11:32:44.844 [http-bio-8443-exec-42] DEBUG no.unimicro.ap.UniOutbox - receiver: 9908:889640782

11:33:17.705 [http-bio-8443-exec-42] INFO no.unimicro.ap.UniOutbox - Sending failed Couldn't create SOAP message due to exception: java.lang.RuntimeException: Fast Infoset decoding is not accepted

What could cause this error? The same sender sent another invoice to the same receiver 13 minutes earlier without any error.