The problem is not about explicitly supplying UIMA in the classpath. But
DUCC's JD is not able to initialize the required jars from the path
defined in Job descriptor file using "classpath".
It is showing the lib folder in the userClasspath variable in JD's log
but not actually initialize its jars.
Thanks,
Reshu.
On 09/21/2015 04:55 PM, reshu.agarwal wrote:
Hi,
As you said: "In DUCC 2.0 you must explicitly supply UIMA in the
classpath of your submission. This was not the case in DUCC 1.x where
UIMA was added by DUCC under the covers."
I defined the same but still facing the error. In JD initialization, I
defined the java class library path required in classpath parameter in
job specification. But it was showing error until I added the same in
resources/jobdriver.classpath. After this It was initialized and then
started showing error of "Missing the -Dducc.deploy.JdURL property".
I was getting java.lang.RuntimeException: Missing the
-Dducc.deploy.JdURL property even in 1.job. Why this error is coming?
Thanks in Advance.
Reshu.
On 09/18/2015 02:47 PM, Lou DeGenaro wrote:
Reshu,
In DUCC 2.0 you must explicitly supply UIMA in the classpath of your
submission. This was not the case in DUCC 1.x where UIMA was added
by DUCC
under the covers.
In fact this gives you more flexibility in that you are no loner tied to
using a particular version of UIMA.
Lou.
On Fri, Sep 18, 2015 at 12:24 AM, reshu.agarwal
<reshu.agar...@orkash.com>
wrote:
Jerry,
I have tried DUCC 2.0.0 to run same job on it. I don't know why but
same
job descriptor didn't work. It showed some exception at
initialization time
which was not in case of 1.1.0.
Is there any changes regarding job descriptor or service descriptor?
The
both did not work in my case for DUCC 2.0.0 but for DUCC 1.0.0 and DUCC
1.1.0.
In Service descriptor it shows some spring Framework's class not found
exception. See below:
*java.lang.NoClassDefFoundError:
org/springframework/context/ApplicationListener*
Thanks in advance.
Reshu.
On 09/17/2015 08:15 PM, Jaroslaw Cwiklik wrote:
Hi, can you try Ducc 2.0.0? It was recently released into Apache.
One of
the key changes was to remove queues as means of transport between
JD (Job
Driver) and JP (Job Process). Instead, each JP uses HTTP to request
a Work
Item (CAS) from a JD.
DUCC 1.1.0 has a concept of a WI timeout which I think is 24 hours by
default. A timer is started in a JD when each WI is dispatched to a
JP. If
the WI does not come back for whatever reason, the timer pops and a JD
will
attempt to retry that WI.
To debug your problem with DUCC 1.1.0 I suggest attaching JMX
console to a
running JP to see where its threads are. Before doing this, check
JP logs
to see if there is an exception.
Jerry
On Thu, Sep 17, 2015 at 4:32 AM, reshu.agarwal
<reshu.agar...@orkash.com>
wrote:
My DUCC version is 1.1.0.
On 09/17/2015 11:35 AM, reshu.agarwal wrote:
Hi,
I am facing a problem in DUCC that some documents were shown in
queue
but
did not get processed. In Job, work item list shows a particular
work
item's status "queued" and queueing time is "4115 seconds".
I want to set queueing time of work item not more then 1 minute.
What is
the reason for the same? Is there any method to solve this? How
can I
set
maximum queueing time for work item?
Thanks in advance.
Reshu.
