Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [smila-user] error after porting

Hi,
you were right...
Afte fixing the deploy.xml another exception raises:

Caused by: java.lang.ClassCastException: org.eclipse.smila.ode.PartnerRoleChannelImpl cannot be cast to org.apache.ode.axis2.ExternalService

In attachment the SMILA.log file.
Thank you for your help,
C

2013/3/18 Jürgen Schumacher <waeller@xxxxxxxxx>
Good Morning,

I see in the SMILA.log, that the 'PhotoProcessingPipeline' has been compiled successfully, but it is not deployed and registered:
There is no message like "Registered process {http://www.eclipse.org/smila/processor}AddPipeline-1."  for it. I suppose
this is because you didn't add the pipeline to the deploy.xml file in configuration/org.eclipse.smila.processig.bpel/pipelines.
At least it looks the same on my system if I remove a pipeline from this file.

Cheers,
Juergen.

Am 18.03.2013, 00:04 Uhr, schrieb Chiara Pasini <pasini@xxxxxxxxxxxxxx>:

After a new update of the configuration files and of the SMILA.launch packege the Crawler finally started.
But it fails to invoke the next Pipeline:

c2838327736e: Error while executing task 37a66784-01cb-4450-b2af-c2838327736e in worker org.eclipse.smila.processing.worker.PipelineProcessorWorker@3700ef6e: Configured pipeline 'PhotoProcessingPipeline' doesn't exist.
java.lang.IllegalArgumentException: Configured pipeline 'PhotoProcessingPipeline' doesn't exist.

The pipeline starts with no errors with:

And it works perfectly with the older version of SMILA.

Any idea?
In attachment the SMILA.log file and all the configuration files.

Tnx,
C

2013/3/15 Jürgen Schumacher <waeller@xxxxxxxxx>
Strange, there are no messages from the JobManager in this log. Did you tweak the log4j.properties somehow so that they got lost? Or have been routed to another log file?
Also, in the smilaconsole.txt I see no message that the fileCrawler worker has been started. This could be caused missing service dependencies. Make sure that bundles
- org.eclipse.smila.importing.compounds.simple
- org.eclipse.smila.importing.state.objecstore
have been started, too.
And we see that the definition of the fieCrawling job is not complete for SMILA 1.1 and above, especially the mapping part is missing. See http://wiki.eclipse.org/SMILA/Documentation/Importing/Crawler/File for details. Also, you must use the workers.json file from the SMILA release you are using. Yours still seems to be the one from SMILA 1.0. Maybe you also need to update the workflows.json to get in sync again.

Regards,
Juergen.

Am 15.03.2013, 15:46 Uhr, schrieb Chiara Pasini <pasini@xxxxxxxxxxxxxx>:

Sure,
C

2013/3/15 Jürgen Schumacher <waeller@xxxxxxxxx>
Hi

An attachment my jobs.json, workflows.json, worker.json and the console output

could you please send the SMILA.log file so that we can see if some errors have occurred? The console output is not sufficient to see anything.

Regards,
Jürgen.

_______________________________________________
smila-user mailing list
smila-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-user





--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

_______________________________________________
smila-user mailing list
smila-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-user





--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/

_______________________________________________
smila-user mailing list
smila-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-user


Attachment: SMILA.log
Description: Binary data


Back to the top