I just tried using Java 8 and I observe the following in the WebServer's
log file:
=====
Problem accessing /system.daemons.jsp. Reason:
PWC6033: Unable to compile class for JSP
PWC6197: An error occurred at line: 24 in the jsp file:
/$banner/$testpattern.jsp
PWC6199: Generated servlet error:
The type java.util.Map$Entry cannot be resolved. It is indirectly
referenced from required .class files
=====
Please try Java 7. The Java used is specified in
$DUCC_HOME/resources/site.ducc.properties, for example:
ducc.jvm = /share/ibm-jdk1.7/bin/java
Lou.
On Thu, Oct 22, 2015 at 3:59 PM, Burn Lewis <[email protected]> wrote:
> Being stuck at WaitingForDriver may mean that the Agent nodes have not come
> online so the RM is not able to assign resources.
> Your "WS.DuccHandlerProxy" error is probably because the webserver has
> failed to start
> I have not been able to reproduce your compile jsp problem by specifying an
> inaccessible directory, but that is certainly worth checking.
>
> Also have you run ./check_ducc and verified that all the daemons are
> running on the head node (or ws pm rm sm & maybe an agent)
>
> ~Burn
>
>
> On Thu, Oct 22, 2015 at 7:50 AM, Lou DeGenaro <[email protected]>
> wrote:
>
> > re: PWC6033: Unable to compile class for JSP
> >
> > In $DUCC_HOME/resources/ducc.properties you can find this:
> >
> > # Specify the ducc jsp comp dir
> > ducc.ws.jsp.compilation.directory = /tmp/ducc/jsp
> >
> > Your choices are:
> >
> > 1. insure that your "ducc" user has r/w access to that directory
> > 2. make an entry in site.ducc.properties (NOT ducc.properties!!!) with a
> > different directory that is r/w by user "ducc"
> >
> > Lou.
> >
> > On Thu, Oct 22, 2015 at 3:55 AM, Yi-Wen Liu <[email protected]> wrote:
> >
> > > Hi,
> > >
> > > Thanks for those helps! They work :) Now I am able to submit job file.
> > > When I submitted the job, it was always showing WaitingForDriver, and
> in
> > > the $DUCC_HOME/logs/ws.<hostname>.log file I got multiple
> > >
> > > 21 Oct 2015 22:09:47,133 INFO WS.DuccHandlerProxy - N/A
> > > handleServletJobStatus [GET
> > > /ducc-servlet/proxy-job-status?id=3]@1627539128
> > > org.eclipse.jetty.server.Request@610246b8
> > >
> > > and the job status didn't move forward to Waiting For Services, Waiting
> > For
> > > Resources, Initializing etc, it was waiting for the driver like
> forever.
> > >
> > > I tried to check DUCC web server, which should be at http://
> > > <hostname>:42133
> > > from the docs.
> > > However I got this:
> > > HTTP ERROR: 500
> > >
> > > Problem accessing /jobs.jsp. Reason:
> > >
> > > PWC6033: Unable to compile class for JSP
> > >
> > > PWC6197: An error occurred at line: 24 in the jsp file:
> > /$banner/$image.jsp
> > > PWC6199: Generated servlet error:
> > > The type java.util.Map$Entry cannot be resolved. It is indirectly
> > > referenced from required .class files
> > >
> > >
> > > Do I need one more step to browse this page, or should start the driver
> > > first?
> > >
> > >
> > > Thanks,
> > > Yi-Wen
> > >
> > > On Wed, Oct 21, 2015 at 6:31 AM, Burn Lewis <[email protected]>
> wrote:
> > >
> > > > Are you starting DUCC from the head node?
> > > > You could try starting just the broker with "./ducc.py -c broker" and
> > see
> > > > if any error messages appear on the console.
> > > > Or try starting a default broker using the AMQ commands directly,
> e.g.
> > cd
> > > > apache-uima/apache-activemq; ./bin/activemq start
> > > > This should produce an error in the logs about a missing
> activemq.xml,
> > > but
> > > > would at least show that AMQ is installed. AMQ creates the data
> > > directory
> > > > and logs when the broker starts, and also saves the pid.
> > > >
> > > > ~Burn
> > > >
> > > > On Wed, Oct 21, 2015 at 6:12 AM, Lou DeGenaro <
> [email protected]>
> > > > wrote:
> > > >
> > > > > From $DUCC_HOME/admin/start_ducc here's how the broker is started:
> > > > >
> > > > > 41 def start_broker(self):
> > > > > 42
> > > > > 43 broker_host =
> > > > self.ducc_properties.get('ducc.broker.hostname')
> > > > > 44 print 'Starting broker on', broker_host
> > > > > 45 lines = self.ssh(broker_host, True, "'",
> self.DUCC_HOME +
> > > > > '/admin/ducc.py', '-c', 'broker', "'")
> > > > >
> > > > > Is ducc.broker.hostname defined correctly in
> > $DUCC_HOME/resources/ducc
> > > > > .properties?
> > > > >
> > > > > Can you ssh to that host? You may need to set up password-less ssh
> > if
> > > > you
> > > > > haven't already.
> > > > >
> > > > > Lou.
> > > > >
> > > > > On Tue, Oct 20, 2015 at 5:10 PM, Yi-Wen Liu <[email protected]>
> > wrote:
> > > > >
> > > > > > No I didn't turn on firewall, and no process is using 61617.
> > > > > >
> > > > > > However in $DUCC_HOME/apache-uima/apache-activemq, I don't have
> the
> > > > > > activemq.log and even the data directory.
> > > > > > I checked other folders but didn't find activemq.log, does that
> > mean
> > > I
> > > > > > probably missed some steps?
> > > > > >
> > > > > > Thanks,
> > > > > > Yi-Wen
> > > > > >
> > > > > > On Tue, Oct 20, 2015 at 4:36 AM, Lou DeGenaro <
> > > [email protected]>
> > > > > > wrote:
> > > > > >
> > > > > > > Yi-Wen,
> > > > > > >
> > > > > > > Do you have a firewall blocking ports?
> > > > > > >
> > > > > > > Is the port already in-use by another process?
> > > > > > >
> > > > > > > Anything interesting in
> > > > > > > $DUCC_HOME/apache-uima/apache-activemq/data/activemg
> > > > > > > .log?
> > > > > > >
> > > > > > > Lou.
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Oct 20, 2015 at 2:28 AM, Yi-Wen Liu <[email protected]>
> > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I was trying to install UIMA DUCC 2.0.0 on my machine (follow
> > > > > > > > https://cwiki.apache.org/confluence/display/UIMA/DUCC), and
> > came
> > > > > > across
> > > > > > > > some problems(ActiveMQ), hope somebody can help, thanks!
> > > > > > > >
> > > > > > > >
> > > > > > > > The ducc_post_install and ducc_check look fine, for
> > > > > ducc_post_install I
> > > > > > > > got:
> > > > > > > > ActiveMQ is automanaged on node yiwenlius-mbp
> > > > > > > > ...........
> > > > > > > > ducc_ling is installed for architecture x86_64. See the
> > > > installation
> > > > > > > guide
> > > > > > > > for additional modifications needed to run user processes
> with
> > > > their
> > > > > OS
> > > > > > > > user credentials.
> > > > > > > > Initial DUCC setup complete.
> > > > > > > >
> > > > > > > >
> > > > > > > > and results from ducc_check which looks very similar to the
> > doc:
> > > > > > > > JVM: /usr/bin/java
> > > > > > > > ENV: Java is configured as: /usr/bin/java
> > > > > > > > ENV java full version "1.8.0_60-b27"
> > > > > > > > ENV: Threading enabled: True
> > > > > > > > ENV: system is Darwin
> > > > > > > > ActiveMQ broker is not running on tcp://yiwenlius-mbp:61617
> > > > > > > > Checking 1 nodes
> > > > > > > > Waiting for Completion
> > > > > > > > Checking yiwenlius-mbp ...
> > > > > > > > no processes found.
> > > > > > > > Node health checks return.
> > > > > > > > All threads returned
> > > > > > > >
> > > > > > > >
> > > > > > > > The reason why I point out activeMQ is that when I do
> > start_ducc,
> > > > it
> > > > > > > seems
> > > > > > > > the broker is not running:
> > > > > > > >
> > > > > > > > allnodes
> > /Users/ducc/apache-uima-ducc-2.0.0/resources/ducc.nodes
> > > > > > > > Class definition file is ducc.classes
> > > > > > > > OK: Class and node definitions validated.
> > > > > > > > OK: Class configuration checked
> > > > > > > > Starting broker on yiwenlius-mbp
> > > > > > > > Waiting for broker ..... 0
> > > > > > > > Waiting for broker ..... 1
> > > > > > > > Waiting for broker ..... 2
> > > > > > > > Waiting for broker ..... 3
> > > > > > > > Waiting for broker ..... 4
> > > > > > > > Waiting for broker ..... 5
> > > > > > > > Waiting for broker ..... 6
> > > > > > > > Waiting for broker ..... 7
> > > > > > > > Waiting for broker ..... 8
> > > > > > > > ActiveMQ broker cannot be found on yiwenlius-mbp:61617
> > > > > > > >
> > > > > > > >
> > > > > > > > And it stopped.
> > > > > > > >
> > > > > > > > Does somebody know what it is going on and how to fix it?
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Yi-Wen
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
