Alfresco 4.2 connector failed

1
0
-1

Hello,

I'm using Bonita BPM 6.3.0 on a Windows 7, with Alfresco Comunity locally. And I use the Alfresco42UploadFileByPath.

I can run several times my process, but sometimes it failed and it failed again at the same connector if I tried to launch it after this.

Here is the error in logs :

2014-06-04 15:34:34 org.bonitasoft.engine.execution.work.FailureHandlingBonitaWork
Avertissement: THREAD_ID=104 | HOSTNAME=Emilien-PC | TENANT_ID=1 | org.bonitasoft.engine.core.connector.exception.SConnectorException : "PROCESS_DEFINITION_ID=7949289451107650799 | PROCESS_NAME=Pool7 | PROCESS_VERSION=1.0 | PROCESS_INSTANCE_ID=7 | ROOT_PROCESS_INSTANCE_ID=7 | FLOW_NODE_DEFINITION_ID=-7395947284350468700 | FLOW_NODE_INSTANCE_ID=57 | FLOW_NODE_NAME=Étape1 | CONNECTOR_DEFINITION_IMPLEMENTATION_CLASS_NAME=uploadPJ | CONNECTOR_INSTANCE_ID=19 | org.bonitasoft.engine.connector.exception.SConnectorException: java.util.concurrent.ExecutionException: org.bonitasoft.engine.connector.exception.SConnectorException: org.bonitasoft.engine.connector.ConnectorException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.abdera.parser.stax.FOMFactory"

I have all connector dependencies checked (except for "geronimo-stax-api_1.0_spec-1.0.1.jar" because I can't launch my process with this dependecies checked) for the Alfresco Connector.

I don't understand why it says ClassNotFoundException because the "abdera.parser.stax-1.1.2.jar" is checked.

Someone knows a possible answer ?

Thanks, Emilien

Comments

Submitted by Giro1981 on Mon, 06/30/2014 - 02:35

Hi,

I'm using Bonita Community edition 6.2.6 and get same error.

Anybody has been able to use Alfresco 4.2 connector with BOS 6.2.x?

Submitted by renaud.pichot on Fri, 07/04/2014 - 16:49

Hi - as written in http://community.bonitasoft.com/answers/problem-alfresco-42-connector-bo..., I had a similar issue. Try adding the adbera*.jar in your tomcat\lib directory. Cheers RP

1 answer

1
0
-1

I think the current version 6.5.1 has resolved this problem.

EDIT: It did not.

Notifications