Heshan Suriyaarachchi created AIRAVATA-603:
----------------------------------------------
Summary: Exceptions thrown when accessing workflow information
through Provanance Manager
Key: AIRAVATA-603
URL: https://issues.apache.org/jira/browse/AIRAVATA-603
Project: Airavata
Issue Type: Bug
Components: Airavata Client
Affects Versions: 0.5
Environment: Airavata 0.5
Mysql
Reporter: Heshan Suriyaarachchi
I have a web app that is using Airavata API to access Provenance information.
I'm getting following exception when retrieving information from the backend.
68 airavata_data INFO [http-bio-9080-exec-1] openjpa.Runtime - Starting
OpenJPA 2.2.0
167 airavata_data INFO [http-bio-9080-exec-1] openjpa.jdbc.JDBC - Using
dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary".
506 airavata_data WARN [http-bio-9080-exec-1] openjpa.Enhance - Creating
subclass for "[class
org.apache.airavata.persistance.registry.jpa.model.Gram_Data, class
org.apache.airavata.persistance.registry.jpa.model.Experiment_Data, class
org.apache.airavata.persistance.registry.jpa.model.Application_Descriptor,
class org.apache.airavata.persistance.registry.jpa.model.Experiment, class
org.apache.airavata.persistance.registry.jpa.model.Workflow_Data, class
org.apache.airavata.persistance.registry.jpa.model.Project, class
org.apache.airavata.persistance.registry.jpa.model.Configuration, class
org.apache.airavata.persistance.registry.jpa.model.User_Workflow, class
org.apache.airavata.persistance.registry.jpa.model.Host_Descriptor, class
org.apache.airavata.persistance.registry.jpa.model.Users, class
org.apache.airavata.persistance.registry.jpa.model.Gateway_Worker, class
org.apache.airavata.persistance.registry.jpa.model.Service_Descriptor, class
org.apache.airavata.persistance.registry.jpa.model.Published_Workflow, class
org.apache.airavata.persistance.registry.jpa.model.Experiment_Metadata, class
org.apache.airavata.persistance.registry.jpa.model.Gateway, class
org.apache.airavata.persistance.registry.jpa.model.Node_Data]". This means that
your application will be less efficient and will consume more memory than it
would if you ran the OpenJPA enhancer. Additionally, lazy loading will not be
available for one-to-one and many-to-one persistent attributes in types using
field access; they will be loaded eagerly instead.
org.xml.sax.SAXException: Fatal Error: URI=null Line=1: Content is not allowed
in prolog.
at
org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils.java:389)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:204)
at org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:217)
at
org.apache.airavata.xbaya.util.XBayaUtil.getIOParameterData(XBayaUtil.java:332)
at
org.apache.jsp.monitor_005fexperiment_005fresult_jsp._jspService(monitor_005fexperiment_005fresult_jsp.java:172)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
