The error message in the log that was attached to the initial email was
this:
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'HazardEventLockHandler' defined in class path resource
[res/spring/hazard-request.xml]: Could not resolve matching constructor
(hint: specify index/type/name arguments for simple parameters to avoid
type ambiguities)
On Thu, 2019-08-15 at 18:31 +0000, Devin Eyre wrote:
> I shut down edex with 'edex stop', and EDEXrequest didn't stop. I
> killed the first process ID listed in the output from 'edex status'
> for
> it, and then rebooted the server. When the server booted up again,
> edex wasn't running, so I started it with 'edex start', and all
> processes except EDEXrequest showed they were running. I've attached
> a
> log file from the EDEXrequest process.
>
> Has anyone run into this problem before?
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> awips2-users mailing list
> awips2-users@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership
> options, visit: https://www.unidata.ucar.edu/mailing_lists/
