[JBoss JIRA] (TEIID-4121) Enhancing the External Materialization
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4121?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4121:
------------------------------------
> What is the issue with having multiple tables?
I want to create a global STATUS table, which save all View's status, no matter where materialized table located, status will always goes to that global STATUS table. It should be better if STATUS table can be created automatically in deployment, that the datasource should be verified in advance, like H2, Mysql, Infinspan.
> Enhancing the External Materialization
> --------------------------------------
>
> Key: TEIID-4121
> URL: https://issues.jboss.org/browse/TEIID-4121
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> The intention of move "status" table to physical database is to increase durable and fully control refresh and loading, but it increase the complexity.
> The "status" table by design should unique for whole VDB, if you look the https://teiid.gitbooks.io/documents/content/caching/External_Materializat..., the table structure:
> {code:sql}
> CREATE TABLE status
> (
> VDBName varchar(50) not null,
> VDBVersion integer not null,
> SchemaName varchar(50) not null,
> Name varchar(256) not null,
> TargetSchemaName varchar(50),
> TargetName varchar(256) not null,
> Valid boolean not null,
> LoadState varchar(25) not null,
> Cardinality long,
> Updated timestamp not null,
> LoadNumber long not null,
> PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name)
> );
> {code}
> but currently, one VDB may have multiple "status" table, each view may have it's own "status" table. Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.
> From finishedDeployment logic in MaterializationManager, MATERIALIZED_TABLE be used to determine whether the Mat is internal or external, But we lack the validation in metadata loading, in my previous test, the Internal Mat view configured lots of external view's properties like "status" table, the validation not throw excepton.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3995) SAP HANA materialization:function loadMatView with argument invalidate set to true problem
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3995?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3995:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1311412|https://bugzilla.redhat.com/show_bug.cgi?id=1311412] from MODIFIED to ON_QA
> SAP HANA materialization:function loadMatView with argument invalidate set to true problem
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-3995
> URL: https://issues.jboss.org/browse/TEIID-3995
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
> Attachments: server.log
>
>
> There appears to be an issue with loadMatView function.
> Specifically when the function is invoked with invalidate=>'true' argument, when it is expected, that invocation of this function invalidates the current contents of the materialized view until the initiated load is completed and new data are populated.
> But when calling this function as described, an error occurs:
> {code:plain}
> TEIID20001 The modeled datatype integer for column 0 doesn't match the runtime type "org.teiid.core.types.ArrayImpl". Please ensure that the column's modeled datatype matches the expected data.
> {code}
> Please note, that there is no column of type array in my schema.
> There is declaration of the view:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> )
> {code}
> and the query used to load the view:
> {code:sql}
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> {code}
> Complete definition of the view is:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (
> MATERIALIZED 'TRUE',
> UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000
> ) AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3983:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1311414|https://bugzilla.redhat.com/show_bug.cgi?id=1311414] from MODIFIED to ON_QA
> External Materialization MATVIEW_ONERROR_ACTION WAIT problem
> ------------------------------------------------------------
>
> Key: TEIID-3983
> URL: https://issues.jboss.org/browse/TEIID-3983
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request.
> The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs.
> Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly.
> During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry:
> {code:plain}
> [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING
> [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked
> {code}
> The log appears in 'ttl' determined intervals, each time after materialized table loading related entries.
> The thread mentioned is the one created after the original query execution was initiated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4125) Problem with SOAP war generated in TD
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4125?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4125:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1311608|https://bugzilla.redhat.com/show_bug.cgi?id=1311608] from MODIFIED to ON_QA
> Problem with SOAP war generated in TD
> -------------------------------------
>
> Key: TEIID-4125
> URL: https://issues.jboss.org/browse/TEIID-4125
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Matus Makovy
> Assignee: Van Halbert
> Priority: Critical
> Fix For: 8.12.5
>
> Attachments: ProductInfoVdb.war, Untitled.zip
>
>
> I don't know if this is a Teiid or Teiid Designer issue.
> When I generate a SOAP war from VDB and try to deploy it to server, I get following exception:
> {code}
> Deployment failed: ProductInfoVdb.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL" : "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"ProductInfoVdb.war\"\n Caused by: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory\n Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory from [Module \"org.springframework.spring:main\" from local module loader @ed17bee (finder: local module finder @2a33fae0 (roots: /Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/dv,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.4.3.CP,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base))]"}}, "rolled-back" : true}
> {code}
> The whole "test script" should be accessible here: https://mojo.redhat.com/docs/DOC-995324
> This happens *only with DV-6.3.0.DR3*. When I deploy this war to DV 6.2 server, everything works as expected.
> I attached project in zip file (Untitled.zip) and generated WAR. The WAR file was generated in TD 10.0.0.Beta2, but I tried to generate the war in 9.0.5 Designer and the result was the same.
> I marked this as Critical, but if it is a Designer issue I think it should be marked as blocker.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4022) Materialization issue dynamic SQL command can't be executed due ambiguous group name
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4022?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4022:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1314890|https://bugzilla.redhat.com/show_bug.cgi?id=1314890] from MODIFIED to ON_QA
> Materialization issue dynamic SQL command can't be executed due ambiguous group name
> --------------------------------------------------------------------------------------
>
> Key: TEIID-4022
> URL: https://issues.jboss.org/browse/TEIID-4022
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> The defined model for materialization:
> {code}
> <model name="PersonMatModel" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE view PersonMatView
> (
> name string,
> id integer,
> email string
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
> MATERIALIZED_TABLE 'PersonMatCache.Person',
> "teiid_rel:MATVIEW_TTL" 60000,
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute PersonMatCache.native(''truncate cache'');',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute PersonMatCache.native(''swap cache names'');',
> "teiid_rel:MATERIALIZED_STAGE_TABLE" 'PersonMatCache.Person',
> "teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Accounts.status',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION')
> AS SELECT name, id, email from PersonInfoModel.Person;
> ]]>
> </metadata>
> </model>
> {code}
> causes the following exception:
> {code}
> org.teiid.api.exception.query.QueryProcessingException: TEIID30168 Couldn't
> execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as
> rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with
> the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due
> to: Group specified is ambiguous, resubmit the query by fully qualifying the group
> name: Person
> {code}
> And executing the following internal call that Teiid uses does produce the non-qualifed name
> {ccode}
> SELECT TargetName from SYSADMIN.MatViews WHERE VDBName = 'PeopleMat' AND SchemaName = 'PersonMatModel' AND Name = 'PersonMatView'
> {code}
> returns: Person
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4025) Web admin console typo when setting time-slice-in-milliseconds attribute
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4025?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4025:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1315323|https://bugzilla.redhat.com/show_bug.cgi?id=1315323] from MODIFIED to ON_QA
> Web admin console typo when setting time-slice-in-milliseconds attribute
> ------------------------------------------------------------------------
>
> Key: TEIID-4025
> URL: https://issues.jboss.org/browse/TEIID-4025
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.12.5
> Reporter: Filip Elias
> Assignee: Van Halbert
> Fix For: 9.0, 8.12.x
>
>
> Admin console prints error when editing Threading attributes.
> Typo in attribute name: time-slice-in-millseconds
> {code}
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [{
> "address" => [("subsystem" => "teiid")],
> "operation" => "write-attribute",
> "name" => "time-slice-in-millseconds",
> "value" => 10000
> }]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014792: Unknown attribute time-slice-in-millseconds",
> "rolled-back" => true
> }},
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute time-slice-in-millseconds"}},
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4031) Missing dependency in module com.fasterxml.jackson.dataformat.yaml
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4031?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4031:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1315597|https://bugzilla.redhat.com/show_bug.cgi?id=1315597] from MODIFIED to ON_QA
> Missing dependency in module com.fasterxml.jackson.dataformat.yaml
> ------------------------------------------------------------------
>
> Key: TEIID-4031
> URL: https://issues.jboss.org/browse/TEIID-4031
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> Module "com.fasterxml.jackson.dataformat.yaml" is missing dependency "com.fasterxml.jackson". Due to this error user cannot see swagger metadata in yaml format.
> Exception:
> {code:text}
> 08:53:02,970 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/rest_1].[default]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet default threw exception: org.jboss.resteasy.spi.UnhandledException: java.lang.LinkageError: Failed to link com/fasterxml/jackson/dataformat/yaml/YAMLFactory (Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base)))
> at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:367) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:235) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:211) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:576) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:543) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invokePropagateNotFound(SynchronousDispatcher.java:171) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:212) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:59) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0-internal]
> Caused by: java.lang.LinkageError: Failed to link com/fasterxml/jackson/dataformat/yaml/YAMLFactory (Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base)))
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at io.swagger.jaxrs.listing.ApiListingResource.getListingYaml(ApiListingResource.java:150) [swagger-jaxrs-1.5.2.jar:1.5.2]
> at io.swagger.jaxrs.listing.ApiListingResource.getListing(ApiListingResource.java:114) [swagger-jaxrs-1.5.2.jar:1.5.2]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0-internal]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0-internal]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:561) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> ... 18 more
> Caused by: java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/JsonFactory
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0-internal]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0-internal]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 37 more
> Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.core.JsonFactory from [Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 41 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months