You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2018/12/01 04:28:00 UTC
[jira] [Resolved] (OODT-1002) Rename CoreMetKeys.java in filemgr
and workflow to CoreFilemgrMetKeys.java and CoreWorkflowMetKeys.java
respectively
[ https://issues.apache.org/jira/browse/OODT-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney resolved OODT-1002.
----------------------------------------
Resolution: Not A Problem
Hi [~chrismattmann] thanks for commenting here, I appreciate it. I am running OODT 1.9-SNAPSHOT with the AvroRPC services. Apart from a few teething issues things were going reasonably well until I hit the issue described above. When I kick off an ad-hoc workflow, my logs indicate the following
{code}
Workflow Manager started PID file (/usr/local/coal-sds-deploy/workflow/run/cas.workflow.pid).
Resource Manager started PID file (/usr/local/coal-sds-deploy/resmgr/run/cas.resmgr.pid).
Bad level value for property: java.util.logging.FileHandler.level
Bad level value for property: java.util.logging.ConsoleHandler.level
Bad level value for property: .level
Can't set level for java.util.logging.ConsoleHandler
Can't set level for java.util.logging.FileHandler
Nov 30, 2018 8:16:41 PM org.apache.oodt.cas.workflow.system.WorkflowManagerStarter loadProperties
INFO: Loading Workflow Manager Configuration Properties from: [/usr/local/coal-sds-deploy/workflow/etc/workflow.properties]
log4j:WARN Continuable parsing error 53 and column 23
log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,throwableRenderer?,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)".
log4j:WARN Continuable parsing error 53 and column 23
log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,throwableRenderer?,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)".
INFO ResourceManagerFactory - Loading File Manager Configuration Properties from: [/usr/local/coal-sds-deploy/resmgr/etc/resource.properties]
INFO ResourceManagerFactory - Creating resource manager org.apache.oodt.cas.resource.system.AvroRpcResourceManager at port: 9002
INFO ConfigurationManagerFactory - Using standalone configuration management for RESOURCE_MANAGER
Bad level value for property: java.util.logging.FileHandler.level
Bad level value for property: java.util.logging.ConsoleHandler.level
Bad level value for property: .level
log4j:WARN Continuable parsing error 53 and column 23
log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,throwableRenderer?,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)".
INFO AvroRpcWorkflowManager - Starting workflow manager on port: 9001 as lmcgibbn
Nov 30, 2018 8:16:42 PM org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngineFactory getResmgrUrl
INFO: No Resource Manager URL provided or malformed URL: executing jobs locally. URL: []
INFO AvroRpcResourceManager - Resource Manager started by lmcgibbn
INFO ResourceManagerMain - Resource manager started at port: 9002
INFO ConfigurationManagerFactory - Using standalone configuration management for FILE_MANAGER
INFO NettyServer - [id: 0x82c24f16, /127.0.0.1:61349 => /127.0.0.1:9000] OPEN
INFO NettyServer - [id: 0x82c24f16, /127.0.0.1:61349 => /127.0.0.1:9000] BOUND: /127.0.0.1:9000
INFO NettyServer - [id: 0x82c24f16, /127.0.0.1:61349 => /127.0.0.1:9000] CONNECTED: /127.0.0.1:61349
INFO log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
INFO log - jetty-6.1.26
INFO log - Started SelectChannelConnector@0.0.0.0:9001
INFO AvroRpcWorkflowManager - Workflow Manager started by lmcgibbn for url: http://LMC-056430:9001
INFO NettyServer - [id: 0x59c36d2b, /127.0.0.1:61350 => /127.0.0.1:9000] OPEN
INFO NettyServer - [id: 0x59c36d2b, /127.0.0.1:61350 => /127.0.0.1:9000] BOUND: /127.0.0.1:9000
INFO NettyServer - [id: 0x59c36d2b, /127.0.0.1:61350 => /127.0.0.1:9000] CONNECTED: /127.0.0.1:61350
INFO NettyServer - [id: 0x550659ba, /127.0.0.1:61351 => /127.0.0.1:9000] OPEN
INFO NettyServer - [id: 0x550659ba, /127.0.0.1:61351 => /127.0.0.1:9000] BOUND: /127.0.0.1:9000
INFO NettyServer - [id: 0x550659ba, /127.0.0.1:61351 => /127.0.0.1:9000] CONNECTED: /127.0.0.1:61351
INFO AvroRpcWorkflowManager - Received event: pycoal-pge
INFO IterativeWorkflowProcessorThread - Thread created for workflowInstance: fc17a7ab-f51f-11e8-b187-c78ad0d807cf[PycoalWorkflow], instanceRepository class: org.apache.oodt.cas.workflow.instrepo.LuceneWorkflowInstanceRepository, wmgrParentUrl: http://LMC-056430:9001
INFO AvroRpcWorkflowManager - Event: pycoal-pge handled successfully
INFO IterativeWorkflowProcessorThread - All required metadata fields present for task: [PycoalMineralClassification]
INFO IterativeWorkflowProcessorThread - Executing task: PycoalMineralClassification
Exception in thread "Thread-6" java.lang.NoClassDefFoundError: org/apache/oodt/cas/filemgr/metadata/CoreMetKeys
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.apache.oodt.cas.workflow.util.GenericWorkflowObjectFactory.getTaskObjectFromClassName(GenericWorkflowObjectFactory.java:168)
at org.apache.oodt.cas.workflow.engine.IterativeWorkflowProcessorThread.run(IterativeWorkflowProcessorThread.java:215)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: org.apache.oodt.cas.filemgr.metadata.CoreMetKeys
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 30 more
{code}
As you can see, the service is established just fine... and the issue is with the ClassLoader failing to dynamically load org.apache.oodt.cas.filemgr.metadata.CoreMetKeys. This stems from the cas-filemgr attifact... which I had excluded from my RADiX workflow module due to earlier build errors with JDK11.
Having reverted to JDK8 I am back to stable with this so essentially this can be resolved as not a problem. Thank you for commenting.
> Rename CoreMetKeys.java in filemgr and workflow to CoreFilemgrMetKeys.java and CoreWorkflowMetKeys.java respectively
> --------------------------------------------------------------------------------------------------------------------
>
> Key: OODT-1002
> URL: https://issues.apache.org/jira/browse/OODT-1002
> Project: OODT
> Issue Type: Task
> Components: file manager, workflow manager
> Affects Versions: 1.2.4
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Blocker
> Fix For: 1.9
>
>
> Primary context for this thread can be found [here|https://lists.apache.org/thread.html/deb7cc02e41afbc70e76583cc42623ee359a871c5e58271a14bf3234@%3Cdev.oodt.apache.org%3E].
> There is a clear ClassLoading issue for the CoreMetKeys.java file present in filemgr and workflow. I propose to rename the files to CoreFilemgrMetKeys.java and CoreWorkflowMetKeys.java respectively. There are however still a few issues in the following classes
> ./tomcat/webapps/fmprod/WEB-INF/classes/org/apache/oodt/cas/product/CASProductHandler.class
> ./tomcat/webapps/opsui/WEB-INF/classes/org/apache/oodt/cas/product/CASProductHandler.class
> ./tomcat/webapps/pcs/WEB-INF/classes/org/apache/oodt/pcs/services/HealthResource.class
> I have a PR to address this. Coming up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)