[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-4029 at 3/9/16 5:12 AM:
------------------------------------------------------------
After some investigation, I think the issue caused by wrong operation in design time with Teiid Designer.
Customer want to merge/union two tables, but not trigger the union, I guess if design correct, there should be SQL like
{code}
SELECT a."1", a."2", a."3", a."4", a."5", a."6", a."7", a."8", a."9", a."10", a."11", a."12", a."13", a."14", a."15", a."16", a."17", a."18", a."19", a."20" FROM ViewModel.csv1 AS a UNION ALL SELECT b."1", b."2", b."3", b."4", b."5", b."6", b."7", b."8", b."9", b."10", b."11", b."12", b."13", b."14", b."15", b."16", b."17", b."18", b."19", b."20" FROM ViewModel.csv2 AS b;
{code}
in ViewModel, but I can not find, the only I can find is
{code}
SELECT COUNT(*) AS count FROM ViewModel.csv1 AS a, ViewModel.csv2 AS b
{code}
In my test, the merge is correct, "select * from combinedcsv" will continue several mins due to Printstream output, but "select count(*) from combinedcsv" will get result in several seconds.
was (Author: kylin):
After some investigation, I think the issue caused by wrong operation in design time with Teiid Designer.
Customer want to merge/union two tables, but not trigger the union, I guess if design correct, there should be SQL like
{code}
SELECT a."1", a."2", a."3", a."4", a."5", a."6", a."7", a."8", a."9", a."10", a."11", a."12", a."13", a."14", a."15", a."16", a."17", a."18", a."19", a."20" FROM ViewModel.csv1 AS a UNION ALL SELECT b."1", b."2", b."3", b."4", b."5", b."6", b."7", b."8", b."9", b."10", b."11", b."12", b."13", b."14", b."15", b."16", b."17", b."18", b."19", b."20" FROM ViewModel.csv2 AS b;
{code}
In my test, "select * from combinedcsv" will continue several mins due to Printstream output, but "select count(*) from combinedcsv" will get result in several seconds.
> After terminating long running queries remains CPU load > 100% on JBoss java process
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4029
> URL: https://issues.jboss.org/browse/TEIID-4029
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.4
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
> Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml
>
>
> Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.
> 1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
> 2. Created two source and view models and VDB
> SQL statement is a carthesion product
> 3. Deploy VDB
> 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
> 5. Goto admin console
> 6. Go to the cancelLongRunningQueries VDB
> 7. Goto tab Requests and select Terminate
> 8. Goto tab Sessions and select Terminate JDBC session
> 9. CPU% load on JBoss java process remains > 100%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4029:
------------------------------------
After some investigation, I think the issue caused by wrong operation in design time with Teiid Designer.
Customer want to merge/union two tables, but not trigger the union, I guess if design correct, there should be SQL like
{code}
SELECT a."1", a."2", a."3", a."4", a."5", a."6", a."7", a."8", a."9", a."10", a."11", a."12", a."13", a."14", a."15", a."16", a."17", a."18", a."19", a."20" FROM ViewModel.csv1 AS a UNION ALL SELECT b."1", b."2", b."3", b."4", b."5", b."6", b."7", b."8", b."9", b."10", b."11", b."12", b."13", b."14", b."15", b."16", b."17", b."18", b."19", b."20" FROM ViewModel.csv2 AS b;
{code}
In my test, "select * from combinedcsv" will continue several mins due to Printstream output, but "select count(*) from combinedcsv" will get result in several seconds.
> After terminating long running queries remains CPU load > 100% on JBoss java process
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4029
> URL: https://issues.jboss.org/browse/TEIID-4029
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.4
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
> Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml
>
>
> Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.
> 1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
> 2. Created two source and view models and VDB
> SQL statement is a carthesion product
> 3. Deploy VDB
> 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
> 5. Goto admin console
> 6. Go to the cancelLongRunningQueries VDB
> 7. Goto tab Requests and select Terminate
> 8. Goto tab Sessions and select Terminate JDBC session
> 9. CPU% load on JBoss java process remains > 100%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4032) Olingo V4
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-4032?page=com.atlassian.jira.plugin... ]
Juraj Duráni updated TEIID-4032:
--------------------------------
Description:
This is the root JIRA for all bugs in Oingo V4 we have found during testing. We will add separate JIRAs for every issue as a subtask.
All sub-JIRAs have in common:
*DDL for H2 database:*
{code:sql}
-- simple table for basic tests
DROP TABLE IF EXISTS SimpleTable;
CREATE TABLE SimpleTable(
intkey int PRIMARY KEY,
intnum int,
stringkey varchar(20),
stringval varchar(20),
booleanval boolean,
decimalval decimal(20, 10),
timeval time,
dateval date,
timestampval timestamp,
clobval clob);
INSERT INTO SimpleTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
(1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
(2, 2, null, 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
(3, 3, '3', null, 'true', 20.3, '00:00:03', '2000-03-03', '2003-01-01 00:00:03.03', 'clob_value_00003'),
(4, 4, '4', 'value_4', null, -20.4, '00:00:04', '2000-04-04', '2004-01-01 00:00:04.04', 'clob_value_00004'),
(5, 5, '5', 'value_5', 'true', null, '00:00:05', '2000-05-05', '2005-01-01 00:00:05.05', 'clob_value_00005'),
(6, 6, '6', 'value_6', 'false', -20.6, null, '2000-06-06', '2006-01-01 00:00:06.06', 'clob_value_00006'),
(7, 7, '7', 'value_7', 'true', 20.7, '00:00:07', null, '2007-01-01 00:00:07.07', 'clob_value_00007'),
(8, 8, '8', 'value_8', 'false', -20.8, '00:00:08', '2000-08-08', null, 'clob_value_00008'),
(9, 9, '9', 'value_9', 'true', 20.9, '00:00:09', '2000-07-09', '2009-01-01 00:00:09.09', null),
(10, null, null, null, null, null, null, null, null, null),
(11, 11, '11', 'value_0', 'true', 21.1, '00:00:11', '2000-11-11', '2011-11-11 00:00:11.11', 'clob_value_00011');
-- end simple table
-- simple data table for filter functions tests
DROP TABLE IF EXISTS SimpleDataTable;
CREATE TABLE SimpleDataTable(
intkey int PRIMARY KEY,
doubleval double,
realval real,
decimalval decimal(20, 10),
stringval varchar(20),
timeval time,
dateval date,
timestampval timestamp);
INSERT INTO SimpleDataTable (intkey, doubleval, realval, decimalval, stringval, timeval, dateval, timestampval) VALUES
(1, 42.22, 42.22, 42.22, 'value_contains', '01:01:01', '2001-01-01', '2001-01-01 01:01:01.01'),
(2, -42.22, -42.22, -42.22, 'value_endswith', '02:02:02', '2002-02-02', '2002-02-02 02:02:02.02'),
(3, 42.32, 42.32, 42.32, 'value_startswith', '03:03:03', '2003-03-03', '2003-03-03 03:03:03.03'),
(4, -42.32, -42.32, -42.32, 'value_length', '04:04:04', '2004-04-04', '2004-04-04 04:04:04.04'),
(5, 42.42, 42.42, 42.42, 'VALUE_LOWER', '05:05:05', '2015-05-05', '2015-05-05 05:05:05.05'),
(6, -42.42, -42.42, -42.42, ' value_trim ', '06:06:06', '2016-06-06', '2016-06-06 06:06:06.06'),
(7, 42.52, 42.52, 42.52, ' value_trim_l', '17:17:17', '2017-07-07', '2017-07-07 17:17:17.07'),
(8, -42.52, -42.52, -42.52, 'value_trim_r ', '18:18:18', '2018-08-08', '2017-08-08 18:18:18.08'),
(9, 42.62, 42.62, 42.62, 'value_abcd', '19:19:19', '2019-09-09', '2018-09-09 19:19:19.09'),
(10, -42.62, -42.62, -42.62, 'value_asdf', '20:20:20', '2020-10-20', '2019-10-20 20:20:20.10'),
(11, 42.72, 42.72, 42.72, 'value_dabc', '21:21:21', '2021-11-25', '2021-11-25 21:21:21.11'),
(12, -42.72, -42.72, -42.72, 'value_end', '23:23:23', '2042-12-30', '2042-12-30 23:23:23.12');
-- end simple data table
-- CUD tables
-- delete
DROP TABLE IF EXISTS DeleteTable;
CREATE TABLE DeleteTable(id int PRIMARY KEY, name varchar(10));
INSERT INTO DeleteTable (id, name) VALUES
(1, 'name1'),
(2, 'name2'),
(3, 'name3');
DROP TABLE IF EXISTS DeletePropTable;
CREATE TABLE DeletePropTable(id int PRIMARY KEY, name varchar(10));
INSERT INTO DeletePropTable (id, name) VALUES
(1, 'name1');
-- put
DROP TABLE IF EXISTS PutTable;
CREATE TABLE PutTable(
intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
INSERT INTO PutTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
(1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
(2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
(3, null, null, null, null, null, null, null, null, null);
DROP TABLE IF EXISTS PutPropTable;
CREATE TABLE PutPropTable(id int PRIMARY KEY, name varchar(10));
INSERT INTO PutPropTable (id, name) VALUES
(1, 'name1');
-- patch
DROP TABLE IF EXISTS PatchTable;
CREATE TABLE PatchTable(
intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
INSERT INTO PatchTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
(1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
(2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
(3, null, null, null, null, null, null, null, null, null);
-- post
DROP TABLE IF EXISTS PostTable;
CREATE TABLE PostTable(
intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
INSERT INTO PostTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
(1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
(2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
(3, null, null, null, null, null, null, null, null, null);
-- end CUD tables
-- not updatable
DROP TABLE IF EXISTS DeleteTableUnmod;
CREATE TABLE DeleteTableUnmod(id int PRIMARY KEY, name varchar(10));
INSERT INTO DeleteTableUnmod (id, name) VALUES
(1, 'name1');
DROP TABLE IF EXISTS PutTableUnmod;
CREATE TABLE PutTableUnmod(id int PRIMARY KEY, name varchar(10));
INSERT INTO PutTableUnmod (id, name) VALUES
(1, 'name1');
DROP TABLE IF EXISTS PostTableUnmod;
CREATE TABLE PostTableUnmod(id int PRIMARY KEY, name varchar(10));
INSERT INTO PostTableUnmod (id, name) VALUES
(1, 'name1');
DROP TABLE IF EXISTS PatchTableUnmod;
CREATE TABLE PatchTableUnmod(id int PRIMARY KEY, name varchar(10));
INSERT INTO PatchTableUnmod (id, name) VALUES
(1, 'name1');
-- table Customers and table Orders
DROP TABLE IF EXISTS Customers;
DROP TABLE IF EXISTS Orders;
CREATE TABLE Customers(id int PRIMARY KEY, name varchar(10));
CREATE TABLE Orders(id int PRIMARY KEY, customerid int, place varchar(10), FOREIGN KEY (customerid) REFERENCES Customers(id));
INSERT INTO Customers (id, name) VALUES
(1, 'customer1'),
(2, 'customer2'),
(3, 'customer3'),
(4, 'customer4');
INSERT INTO Orders (id, customerid, place) VALUES
(1, 1, 'town'),
(2, 1, 'state'),
(3, 1, 'country'),
(4, 1, 'abroad'),
(5, 2, 'state'),
(6, 2, 'country'),
(7, 3, 'town'),
(8, 3, 'town');
-- end table Customers and table Orders
{code}
*VDB:*
{code:xml}
<vdb name="olingo_basic" version="1">
<model name="Source" type="PHYSICAL">
<source name="local_h2_db" connection-jndi-name="java:/localH2DB" translator-name="h2"/>
<metadata type="DDL">
CREATE FOREIGN TABLE SimpleTable(
intkey integer PRIMARY KEY,
intnum integer,
stringkey varchar(20),
stringval varchar(20),
booleanval boolean,
decimalval decimal(20, 10),
timeval time,
dateval date,
timestampval timestamp,
clobval clob) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.SIMPLETABLE');
CREATE FOREIGN TABLE SimpleDataTable(
intkey integer PRIMARY KEY,
doubleval double,
realval real,
decimalval decimal(20, 10),
stringval varchar(20),
timeval time,
dateval date,
timestampval timestamp) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.SIMPLEDATATABLE');
CREATE FOREIGN TABLE PutTable(
intkey integer PRIMARY KEY,
intnum integer,
stringkey varchar(20),
stringval varchar(20),
booleanval boolean,
decimalval decimal(20, 10),
timeval time,
dateval date,
timestampval timestamp,
clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTTABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE PostTable(
intkey integer PRIMARY KEY,
intnum integer,
stringkey varchar(20),
stringval varchar(20),
booleanval boolean,
decimalval decimal(20, 10),
timeval time,
dateval date,
timestampval timestamp,
clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.POSTTABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE PatchTable(
intkey integer PRIMARY KEY,
intnum integer,
stringkey varchar(20),
stringval varchar(20),
booleanval boolean,
decimalval decimal(20, 10),
timeval time,
dateval date,
timestampval timestamp,
clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PATCHTABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE DeleteTable (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETETABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE DeletePropTable (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETEPROPTABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE PutPropTable (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTPROPTABLE', UPDATABLE 'TRUE');
CREATE FOREIGN TABLE DeleteTableUnmod (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETETABLEUNMOD', UPDATABLE 'FALSE');
CREATE FOREIGN TABLE PutTableUnmod (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTTABLEUNMOD', UPDATABLE 'FALSE');
CREATE FOREIGN TABLE PostTableUnmod (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.POSTTABLEUNMOD', UPDATABLE 'FALSE');
CREATE FOREIGN TABLE PatchTableUnmod (
id integer PRIMARY KEY,
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PATCHTABLEUNMOD', UPDATABLE 'FALSE');
CREATE FOREIGN TABLE Customers (
idcust integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'),
name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS');
CREATE FOREIGN TABLE Orders (
idords integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'),
customerid integer,
place varchar(10),
FOREIGN KEY (customerid) REFERENCES Customers(idcust)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS');
CREATE VIEW SimpleTableView(
intkey integer PRIMARY KEY,
intnum integer,
stringkey string,
stringval string,
booleanval boolean,
decimalval bigdecimal,
timeval time,
dateval date,
timestampval timestamp,
clobval object)
AS
SELECT
intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, convert(clobval, object)
FROM
SimpleTable;
</metadata>
</model>
</vdb>
{code}
was:This is the root JIRA for all bugs in Oingo V4 we have found during testing. We will add separate JIRAs for every issue as a subtask.
> Olingo V4
> ---------
>
> Key: TEIID-4032
> URL: https://issues.jboss.org/browse/TEIID-4032
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> This is the root JIRA for all bugs in Oingo V4 we have found during testing. We will add separate JIRAs for every issue as a subtask.
> All sub-JIRAs have in common:
> *DDL for H2 database:*
> {code:sql}
> -- simple table for basic tests
> DROP TABLE IF EXISTS SimpleTable;
> CREATE TABLE SimpleTable(
> intkey int PRIMARY KEY,
> intnum int,
> stringkey varchar(20),
> stringval varchar(20),
> booleanval boolean,
> decimalval decimal(20, 10),
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval clob);
> INSERT INTO SimpleTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
> (1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
> (2, 2, null, 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
> (3, 3, '3', null, 'true', 20.3, '00:00:03', '2000-03-03', '2003-01-01 00:00:03.03', 'clob_value_00003'),
> (4, 4, '4', 'value_4', null, -20.4, '00:00:04', '2000-04-04', '2004-01-01 00:00:04.04', 'clob_value_00004'),
> (5, 5, '5', 'value_5', 'true', null, '00:00:05', '2000-05-05', '2005-01-01 00:00:05.05', 'clob_value_00005'),
> (6, 6, '6', 'value_6', 'false', -20.6, null, '2000-06-06', '2006-01-01 00:00:06.06', 'clob_value_00006'),
> (7, 7, '7', 'value_7', 'true', 20.7, '00:00:07', null, '2007-01-01 00:00:07.07', 'clob_value_00007'),
> (8, 8, '8', 'value_8', 'false', -20.8, '00:00:08', '2000-08-08', null, 'clob_value_00008'),
> (9, 9, '9', 'value_9', 'true', 20.9, '00:00:09', '2000-07-09', '2009-01-01 00:00:09.09', null),
> (10, null, null, null, null, null, null, null, null, null),
> (11, 11, '11', 'value_0', 'true', 21.1, '00:00:11', '2000-11-11', '2011-11-11 00:00:11.11', 'clob_value_00011');
> -- end simple table
> -- simple data table for filter functions tests
> DROP TABLE IF EXISTS SimpleDataTable;
> CREATE TABLE SimpleDataTable(
> intkey int PRIMARY KEY,
> doubleval double,
> realval real,
> decimalval decimal(20, 10),
> stringval varchar(20),
> timeval time,
> dateval date,
> timestampval timestamp);
> INSERT INTO SimpleDataTable (intkey, doubleval, realval, decimalval, stringval, timeval, dateval, timestampval) VALUES
> (1, 42.22, 42.22, 42.22, 'value_contains', '01:01:01', '2001-01-01', '2001-01-01 01:01:01.01'),
> (2, -42.22, -42.22, -42.22, 'value_endswith', '02:02:02', '2002-02-02', '2002-02-02 02:02:02.02'),
> (3, 42.32, 42.32, 42.32, 'value_startswith', '03:03:03', '2003-03-03', '2003-03-03 03:03:03.03'),
> (4, -42.32, -42.32, -42.32, 'value_length', '04:04:04', '2004-04-04', '2004-04-04 04:04:04.04'),
> (5, 42.42, 42.42, 42.42, 'VALUE_LOWER', '05:05:05', '2015-05-05', '2015-05-05 05:05:05.05'),
> (6, -42.42, -42.42, -42.42, ' value_trim ', '06:06:06', '2016-06-06', '2016-06-06 06:06:06.06'),
> (7, 42.52, 42.52, 42.52, ' value_trim_l', '17:17:17', '2017-07-07', '2017-07-07 17:17:17.07'),
> (8, -42.52, -42.52, -42.52, 'value_trim_r ', '18:18:18', '2018-08-08', '2017-08-08 18:18:18.08'),
> (9, 42.62, 42.62, 42.62, 'value_abcd', '19:19:19', '2019-09-09', '2018-09-09 19:19:19.09'),
> (10, -42.62, -42.62, -42.62, 'value_asdf', '20:20:20', '2020-10-20', '2019-10-20 20:20:20.10'),
> (11, 42.72, 42.72, 42.72, 'value_dabc', '21:21:21', '2021-11-25', '2021-11-25 21:21:21.11'),
> (12, -42.72, -42.72, -42.72, 'value_end', '23:23:23', '2042-12-30', '2042-12-30 23:23:23.12');
> -- end simple data table
> -- CUD tables
> -- delete
> DROP TABLE IF EXISTS DeleteTable;
> CREATE TABLE DeleteTable(id int PRIMARY KEY, name varchar(10));
> INSERT INTO DeleteTable (id, name) VALUES
> (1, 'name1'),
> (2, 'name2'),
> (3, 'name3');
> DROP TABLE IF EXISTS DeletePropTable;
> CREATE TABLE DeletePropTable(id int PRIMARY KEY, name varchar(10));
> INSERT INTO DeletePropTable (id, name) VALUES
> (1, 'name1');
> -- put
> DROP TABLE IF EXISTS PutTable;
> CREATE TABLE PutTable(
> intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
> decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
> INSERT INTO PutTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
> (1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
> (2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
> (3, null, null, null, null, null, null, null, null, null);
> DROP TABLE IF EXISTS PutPropTable;
> CREATE TABLE PutPropTable(id int PRIMARY KEY, name varchar(10));
> INSERT INTO PutPropTable (id, name) VALUES
> (1, 'name1');
> -- patch
> DROP TABLE IF EXISTS PatchTable;
> CREATE TABLE PatchTable(
> intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
> decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
> INSERT INTO PatchTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
> (1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
> (2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
> (3, null, null, null, null, null, null, null, null, null);
> -- post
> DROP TABLE IF EXISTS PostTable;
> CREATE TABLE PostTable(
> intkey int PRIMARY KEY, intnum int, stringkey varchar(20), stringval varchar(20), booleanval boolean,
> decimalval decimal(20, 10), timeval time, dateval date, timestampval timestamp, clobval clob);
> INSERT INTO PostTable (intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, clobval) VALUES
> (1, null, '1', 'value_1', 'true', 20.1, '00:00:01', '2000-01-01', '2001-01-01 00:00:01.01', 'clob_value_00001'),
> (2, 2, '2', 'value_2', 'false', -20.2, '00:00:02', '2000-02-02', '2002-01-01 00:00:02.02', 'clob_value_00002'),
> (3, null, null, null, null, null, null, null, null, null);
> -- end CUD tables
> -- not updatable
> DROP TABLE IF EXISTS DeleteTableUnmod;
> CREATE TABLE DeleteTableUnmod(id int PRIMARY KEY, name varchar(10));
> INSERT INTO DeleteTableUnmod (id, name) VALUES
> (1, 'name1');
> DROP TABLE IF EXISTS PutTableUnmod;
> CREATE TABLE PutTableUnmod(id int PRIMARY KEY, name varchar(10));
> INSERT INTO PutTableUnmod (id, name) VALUES
> (1, 'name1');
> DROP TABLE IF EXISTS PostTableUnmod;
> CREATE TABLE PostTableUnmod(id int PRIMARY KEY, name varchar(10));
> INSERT INTO PostTableUnmod (id, name) VALUES
> (1, 'name1');
> DROP TABLE IF EXISTS PatchTableUnmod;
> CREATE TABLE PatchTableUnmod(id int PRIMARY KEY, name varchar(10));
> INSERT INTO PatchTableUnmod (id, name) VALUES
> (1, 'name1');
> -- table Customers and table Orders
> DROP TABLE IF EXISTS Customers;
> DROP TABLE IF EXISTS Orders;
> CREATE TABLE Customers(id int PRIMARY KEY, name varchar(10));
> CREATE TABLE Orders(id int PRIMARY KEY, customerid int, place varchar(10), FOREIGN KEY (customerid) REFERENCES Customers(id));
> INSERT INTO Customers (id, name) VALUES
> (1, 'customer1'),
> (2, 'customer2'),
> (3, 'customer3'),
> (4, 'customer4');
> INSERT INTO Orders (id, customerid, place) VALUES
> (1, 1, 'town'),
> (2, 1, 'state'),
> (3, 1, 'country'),
> (4, 1, 'abroad'),
> (5, 2, 'state'),
> (6, 2, 'country'),
> (7, 3, 'town'),
> (8, 3, 'town');
> -- end table Customers and table Orders
> {code}
> *VDB:*
> {code:xml}
> <vdb name="olingo_basic" version="1">
> <model name="Source" type="PHYSICAL">
> <source name="local_h2_db" connection-jndi-name="java:/localH2DB" translator-name="h2"/>
> <metadata type="DDL">
> CREATE FOREIGN TABLE SimpleTable(
> intkey integer PRIMARY KEY,
> intnum integer,
> stringkey varchar(20),
> stringval varchar(20),
> booleanval boolean,
> decimalval decimal(20, 10),
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval clob) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.SIMPLETABLE');
>
> CREATE FOREIGN TABLE SimpleDataTable(
> intkey integer PRIMARY KEY,
> doubleval double,
> realval real,
> decimalval decimal(20, 10),
> stringval varchar(20),
> timeval time,
> dateval date,
> timestampval timestamp) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.SIMPLEDATATABLE');
> CREATE FOREIGN TABLE PutTable(
> intkey integer PRIMARY KEY,
> intnum integer,
> stringkey varchar(20),
> stringval varchar(20),
> booleanval boolean,
> decimalval decimal(20, 10),
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTTABLE', UPDATABLE 'TRUE');
> CREATE FOREIGN TABLE PostTable(
> intkey integer PRIMARY KEY,
> intnum integer,
> stringkey varchar(20),
> stringval varchar(20),
> booleanval boolean,
> decimalval decimal(20, 10),
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.POSTTABLE', UPDATABLE 'TRUE');
> CREATE FOREIGN TABLE PatchTable(
> intkey integer PRIMARY KEY,
> intnum integer,
> stringkey varchar(20),
> stringval varchar(20),
> booleanval boolean,
> decimalval decimal(20, 10),
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval object) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PATCHTABLE', UPDATABLE 'TRUE');
> CREATE FOREIGN TABLE DeleteTable (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETETABLE', UPDATABLE 'TRUE');
>
>
> CREATE FOREIGN TABLE DeletePropTable (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETEPROPTABLE', UPDATABLE 'TRUE');
> CREATE FOREIGN TABLE PutPropTable (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTPROPTABLE', UPDATABLE 'TRUE');
>
>
> CREATE FOREIGN TABLE DeleteTableUnmod (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.DELETETABLEUNMOD', UPDATABLE 'FALSE');
> CREATE FOREIGN TABLE PutTableUnmod (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PUTTABLEUNMOD', UPDATABLE 'FALSE');
> CREATE FOREIGN TABLE PostTableUnmod (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.POSTTABLEUNMOD', UPDATABLE 'FALSE');
> CREATE FOREIGN TABLE PatchTableUnmod (
> id integer PRIMARY KEY,
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.PATCHTABLEUNMOD', UPDATABLE 'FALSE');
>
>
> CREATE FOREIGN TABLE Customers (
> idcust integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'),
> name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS');
> CREATE FOREIGN TABLE Orders (
> idords integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'),
> customerid integer,
> place varchar(10),
> FOREIGN KEY (customerid) REFERENCES Customers(idcust)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS');
> CREATE VIEW SimpleTableView(
> intkey integer PRIMARY KEY,
> intnum integer,
> stringkey string,
> stringval string,
> booleanval boolean,
> decimalval bigdecimal,
> timeval time,
> dateval date,
> timestampval timestamp,
> clobval object)
> AS
> SELECT
> intkey, intnum, stringkey, stringval, booleanval, decimalval, timeval, dateval, timestampval, convert(clobval, object)
> FROM
> SimpleTable;
> </metadata>
> </model>
> </vdb>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4029:
-------------------------------
Attachment: heap.1
heap.2
heap.3
heap.4
heap.5
High cpu thread nid is 0x2e9f, all 5 heap are collected sequentially with a time interval.
> After terminating long running queries remains CPU load > 100% on JBoss java process
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4029
> URL: https://issues.jboss.org/browse/TEIID-4029
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.4
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
> Attachments: Archive.zip, Case01593403.java, heap.1, heap.2, heap.3, heap.4, heap.5, highcpu-vdb.xml
>
>
> Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.
> 1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
> 2. Created two source and view models and VDB
> SQL statement is a carthesion product
> 3. Deploy VDB
> 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
> 5. Goto admin console
> 6. Go to the cancelLongRunningQueries VDB
> 7. Goto tab Requests and select Terminate
> 8. Goto tab Sessions and select Terminate JDBC session
> 9. CPU% load on JBoss java process remains > 100%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4029:
-------------------------------
Attachment: Case01593403.java
highcpu-vdb.xml
It seems we can reproduce via Embedded, the Batch Processing are suspicious,
{code}
java.lang.Thread.State: RUNNABLE
at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:256)
at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:211)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:89)
at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:405)
at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:336)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278)
at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136)
{code}
it always keep the cpu, never release the process thread.
> After terminating long running queries remains CPU load > 100% on JBoss java process
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4029
> URL: https://issues.jboss.org/browse/TEIID-4029
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.4
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
> Attachments: Archive.zip, Case01593403.java, highcpu-vdb.xml
>
>
> Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.
> 1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
> 2. Created two source and view models and VDB
> SQL statement is a carthesion product
> 3. Deploy VDB
> 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
> 5. Goto admin console
> 6. Go to the cancelLongRunningQueries VDB
> 7. Goto tab Requests and select Terminate
> 8. Goto tab Sessions and select Terminate JDBC session
> 9. CPU% load on JBoss java process remains > 100%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4029?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4029:
-------------------------------
Attachment: Archive.zip
Just copy attached reproduce file from support case
> After terminating long running queries remains CPU load > 100% on JBoss java process
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4029
> URL: https://issues.jboss.org/browse/TEIID-4029
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.4
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
> Attachments: Archive.zip
>
>
> Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.
> 1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
> 2. Created two source and view models and VDB
> SQL statement is a carthesion product
> 3. Deploy VDB
> 4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
> 5. Goto admin console
> 6. Go to the cancelLongRunningQueries VDB
> 7. Goto tab Requests and select Terminate
> 8. Goto tab Sessions and select Terminate JDBC session
> 9. CPU% load on JBoss java process remains > 100%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4034) date parsing in google spreadsheet translator expects soecific timestamp format
by Marco Ardito (JIRA)
Marco Ardito created TEIID-4034:
-----------------------------------
Summary: date parsing in google spreadsheet translator expects soecific timestamp format
Key: TEIID-4034
URL: https://issues.jboss.org/browse/TEIID-4034
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.3
Reporter: Marco Ardito
Assignee: Steven Hawkins
A VDB connecting to a google spreadsheet datasource fails to create the model, and thus fails, probably due to the fact that one of the spreadhseet fields is formatted timestamp, but uses a different format (dd/MM/yyyy hh:mm:ss) than the one the translator expects (yyyy-mm-dd hh:mm:ss).
This spreadsheet cited in the forum reference is, in particular, directly generated by google forms, and the timestamp field is created by the form engine to record when the form if fille dby a user with a timestamp, so no control on the field is possible in the source...
see forum reference for full details/description
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3994) AliasSymbol wrapping AliasSymbol error
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3994?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3994:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1314909|https://bugzilla.redhat.com/show_bug.cgi?id=1314909] from NEW to MODIFIED
> AliasSymbol wrapping AliasSymbol error
> --------------------------------------
>
> Key: TEIID-3994
> URL: https://issues.jboss.org/browse/TEIID-3994
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
> Attachments: Oracle.PNG, SQLServer.PNG
>
>
> I've defined a view and overrode the default triggers for Select, Insert, Update, and Delete. I overrode the triggers because the select is returning "hardcoded" values for a few fields (calling them virtual columns). The Update and Insert triggers will ignore these hardcoded values just in case the caller tries to update a virtual column.
> I'm trying to run a insert into <tableA> select * from <tableB> query. When I run this, I get an error org.teiid.jdbc.TeiidSQLException: Cannot create AliasSymbol wrapping AliasSymbol.
> Facts:
> -- I can insert a record if I only select one column from tableB.
> -- If I select two or more columns, it throws the error every time.
> -- If I remove the overridden triggers, the insert into <tableA> select * from <tableB> works fine.
> -- I can insert one or more columns into <tableA> when *not* using a insert into <tableA> select * from <tableB> query
> -- Table A is Oracle
> -- Table B is SQL Server
> My hunch is the generated query (hibernate, or whatever SQL generator) is choking with the overridden trigger. Perhaps this use-case slipped through testing, or even more probable, I made a mistake in the trigger creation.
> Here's a snip of the insert trigger, with a lot of fields removed for simplicity.
> {code}
> FOR EACH ROW
> BEGIN ATOMIC
> INSERT INTO <schema>.<tableA> (SourceSystemID, RecordTypeID, BatchID ...)
> VALUES (
> convert("NEW".SourceSystemID, short),
> convert("NEW".RecordTypeID, short),
> convert("NEW".BatchID, integer)
> ...
> )
> END
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3978) Remove AddressWrapper
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3978?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3978:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1308959|https://bugzilla.redhat.com/show_bug.cgi?id=1308959] from ASSIGNED to MODIFIED
> Remove AddressWrapper
> ---------------------
>
> Key: TEIID-3978
> URL: https://issues.jboss.org/browse/TEIID-3978
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2
>
>
> AddressWrapper was introduced to handle an earlier jgroups version where address objects were not directly serializable. However the deserialization code is using the thread context class loader which is not guaranteed to have the JGroups classes in the classpath. The resulting exception (where the original exception is simply swallowed) looks like:
> {code}
> 2016-02-16 08:45:30,140 ERROR [Incoming-1,shared=tcp-teiid-1] org.teiid.replication.jgroups.JGroupsObjectReplicator$ReplicatorRpcDispatcher - exception marshalling object
> java.lang.IllegalStateException: unread block data
> at java.io.ObjectInputStream$BlockDataInputStream.setBlockDataMode(ObjectInputStream.java:2421)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1382)
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1706)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1344)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at org.jgroups.blocks.MethodCall.readExternal(MethodCall.java:430)
> at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at org.teiid.replication.jgroups.JGroupsObjectReplicator$ContextAwareMarshaller.objectFromBuffer(JGroupsObjectReplicator.java:611)
> at org.teiid.replication.jgroups.JGroupsObjectReplicator$ReplicatorRpcDispatcher.handle(JGroupsObjectReplicator.java:106)
> at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:484)
> at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391)
> at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249)
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600)
> at org.jgroups.JChannel.up(JChannel.java:707)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month