4:07 a.m.
[
https://issues.jboss.org/browse/TEIID-5096?page=com.atlassian.jira.plugin...
]
Bram Gadeyne edited comment on TEIID-5096 at 5/3/18 5:06 AM:
-------------------------------------------------------------
[~shawkins],
It seems like I'm again encountering this issue but for version 10.2.1. The strange
thing is that it sometimes happens and sometimes not.
I have a VDB where I now and then add new schema's, views and procedures to. It has
worked for months now (even with the /*+ MAKEDEP */ in it and suddenly the Wildfly server
stopped accepting new deployments (where a new schema was added). Sometimes it hangs and
sometimes the CLI exits with a CancellationException error. I don't see any further
errors or even other entries in the log file. A server restart does not help.
There was one /*+ MAKEDEP */ in one of the views. After removing this and restarting the
server, the deployment is again accepted.
was (Author: gadeyne.bram):
[~shawkins],
It seems like I'm again encountering this issue but for version 10.2.1. The strange
thing is that it sometimes happens and sometimes not.
I have a VDB where I now and then add new schema's, views and procedures to. It has
worked for months now and suddenly the Wildfly server stopped accepting new deployments.
Sometimes it hangs and sometimes the CLI exits with a CancellationException error. I
don't see any further errors of even other entries in the log file. A server restart
does not help.
There was one /*+ MAKEDEP */ in one of the views. After removing this and restarting the
server, the deployment is again accepted.
Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based
vdb
----------------------------------------------------------------------
Key: TEIID-5096
URL: https://issues.jboss.org/browse/TEIID-5096
Project: Teiid
Issue Type: Bug
Affects Versions: 9.3.3
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Attachments: threaddump.txt
Hi,
I've created a vdb that is depoyed using a vdb-ddl.ddl file.
The deployment just stops and returned no error message when adding the SQL part below.
Subsequent deployments are not handles. It seems like the deployment process just hangs.
The only way to resolve this was to stop the wildfly server, remove the latest added
content from the standalone/data/content directory and restart wildfly.
{code:sql}
CREATE VIEW tv_retrieve_monvals(
admissionid integer not null,
VariableID integer not null,
Datetime timestamp not null,
Entertime timestamp not null,
varvalue double not null,
primary key (admissionid, VariableID, Datetime)
)
AS
SELECT v.PatientID AS admissionid, v.VariableID, v.Datetime, v.Entertime,
v."Value" AS varvalue
FROM (
SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value",
ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY
mv.Entertime DESC) AS rang
FROM izisprod.P_GeneralData AS gd
INNER JOIN /*+ MAKEDEP */ izisprod.P_MonVals AS mv ON
gd.PatientID = mv.PatientID AND
bitand(mv.Status, 8) = 8 AND
bitand(mv.Status, 2) <> 2
WHERE gd.Status = 1 OR (gd.Status >= 4 AND gd.Status <> 5)
UNION
SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value",
ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY
mv.Entertime DESC) AS rang
FROM iziswh.P_GeneralData AS gd
INNER JOIN /*+ MAKEDEP */ iziswh.P_MonVals AS mv ON
gd.PatientID = mv.PatientID AND
bitand(mv.Status, 8) = 8 AND
bitand(mv.Status, 2) <> 2
) AS v
WHERE v.rang = 1;
{code}
Removing the /*+ MAKDEP */ references resolves the issue.
I've tried creating a small ddl script that uses /*+ MAKEDEP */ to reproduce this
issue but this script does deploy so currently I can not make a small example.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
2430
days inactive
2430
days old
0 comments
1 participants
participants (1)
-
Bram Gadeyne (JIRA)