[jira] [Created] (TRAFODION-2817) Support a maven plugin for SPJ uploading
Kevin Xu created TRAFODION-2817: --- Summary: Support a maven plugin for SPJ uploading Key: TRAFODION-2817 URL: https://issues.apache.org/jira/browse/TRAFODION-2817 Project: Apache Trafodion Issue Type: New Feature Components: connectivity-general Reporter: Kevin Xu Priority: Minor In the past, we have to put the JAR onto the servers via SSH tools. It's good if we could have plugin for uploading. like if we run "mvn clean install", the jar will be uploaded as configured. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TRAFODION-2676) JDBC T2Sample.java test program does not have log after making connection
Kevin Xu created TRAFODION-2676:
---
Summary: JDBC T2Sample.java test program does not have log after
making connection
Key: TRAFODION-2676
URL: https://issues.apache.org/jira/browse/TRAFODION-2676
Project: Apache Trafodion
Issue Type: Bug
Components: client-jdbc-t2
Reporter: Kevin Xu
T2Sample.java coded to load driver class and make a connection,
printing msg after each successful step.
Pgm ends without notice when attempting .getConnection(url)
(This is one of our regression test programs?) source included here for your
convenience.
import java.sql.*;
import java.math.BigDecimal;
public class T2Sample
{
public static void main(String args[])
{
Connection connection;
Statement stmt;
PreparedStatement pStmt;
ResultSet rs;
DatabaseMetaData dbMeta;
int rowNo;
try
{
Class.forName("org.apache.trafodion.jdbc.t2.T2Driver");
System.out.println("Class loaded");
}
catch (Exception e)
{
e.printStackTrace();
System.out.println(e.getMessage());
return;
}
try
{
//String url = "jdbc:default:connection";
String url = "jdbc:t2jdbc:";
System.out.println("Opening connection...");
connection = DriverManager.getConnection(url);
System.out.println("Successfully connected");
}
catch (Exception e)
{
e.printStackTrace();
System.out.println(e.getMessage());
return;
}
}
}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (TRAFODION-2609) make cleanall does not work for jdbc_type2
Kevin Xu created TRAFODION-2609: --- Summary: make cleanall does not work for jdbc_type2 Key: TRAFODION-2609 URL: https://issues.apache.org/jira/browse/TRAFODION-2609 Project: Apache Trafodion Issue Type: Bug Reporter: Kevin Xu Assignee: Kevin Xu On building phase, when using "make cleanall", the issue occurs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2554) JDBC T2 build changes needed for Trafodion release
[ https://issues.apache.org/jira/browse/TRAFODION-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reassigned TRAFODION-2554: --- Assignee: Alex Peng > JDBC T2 build changes needed for Trafodion release > > > Key: TRAFODION-2554 > URL: https://issues.apache.org/jira/browse/TRAFODION-2554 > Project: Apache Trafodion > Issue Type: Task > Components: client-jdbc-t2 >Affects Versions: 2.2-incubating >Reporter: Sandhya Sundaresan >Assignee: Alex Peng > > Need to convert T2 project to use Maven. > Change POM.xml to be consistent with other POM files in Trafodion so we can > publish the T2 jar file. > The group id needs to change to org.apache.trafodion. > The NOTICE and LICENSE files need to be part of the JAR's META INF directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2544) JDBCT4 group id needs to be changed to org.apache.trafodion in JAR
[ https://issues.apache.org/jira/browse/TRAFODION-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reassigned TRAFODION-2544: --- Assignee: Alex Peng > JDBCT4 group id needs to be changed to org.apache.trafodion in JAR > --- > > Key: TRAFODION-2544 > URL: https://issues.apache.org/jira/browse/TRAFODION-2544 > Project: Apache Trafodion > Issue Type: Task > Components: client-jdbc-t4 >Affects Versions: 2.1-incubating, 2.2-incubating >Reporter: Sandhya Sundaresan >Assignee: Alex Peng > > The group id org.trafodion.* needs to be changed to org.apache.trafdoion for > all JAR files since it's a requirement before we can stage and release these > ont he Nexus repository. > Once the group id is changed in the corresponding POM files, code needs to be > changed as well. > Trafci needs to work with the new group id. > POM file where change needs to be made is : > core/conn/jdbcT4/pom.xml > NOTICE and LICENSE files need to be packaged into the JAR file too. According > to apache rules "NOTICE and LICENSE files should be present in the META-INF > directory within the jar " > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (TRAFODION-2269) use JDBC to test getObject API from float type in database error
[ https://issues.apache.org/jira/browse/TRAFODION-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu closed TRAFODION-2269. --- Resolution: Fixed Not a issue as document says. > use JDBC to test getObject API from float type in database error > > > Key: TRAFODION-2269 > URL: https://issues.apache.org/jira/browse/TRAFODION-2269 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.1-incubating > Environment: cenos7,jdbcT4-2.2.0, >Reporter: luoyunpeng > > when used JDBC getObject API to get object from float field in database, > expected:float, but the result was double, -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TRAFODION-2524) phoenix type 2 test on trafodion, return abort error message
[ https://issues.apache.org/jira/browse/TRAFODION-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900559#comment-15900559 ] Kevin Xu commented on TRAFODION-2524: - After investigation, the issue is /proc/PID/cmdLine is longer than before along with a limitation (8193) in the code. Solution is to extend the size. > phoenix type 2 test on trafodion, return abort error message > > > Key: TRAFODION-2524 > URL: https://issues.apache.org/jira/browse/TRAFODION-2524 > Project: Apache Trafodion > Issue Type: Test > Components: client-jdbc-t2 >Affects Versions: 2.1-incubating > Environment: centos 6.8, jdk1.8, trafodion2.1 >Reporter: luoyunpeng >Assignee: Kevin Xu >Priority: Critical > Labels: test > > when i was running phoenix type 2 test on trafodion2.1 with python script, > and error occuced, like this： > > /bin/sh: line 1: 25520 Aborted > > I think this maybe the python sript cause the error, so switch to execute > one test by java command like this： > > java -cp > .:$CLASSPATH:/home/trafodion/apache-trafodion-2.1.0/export/lib/jdbcT2.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/junit/junit-4.11.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/junit/hamcrest-all-1.3.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/thirdparty/google-collections-1.0-rc2.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/thirdparty/commons-lang-2.6.jar > -Duser.timezone=GMT > -Dtrafjdbc.properties=/opt/share/Yunpeng/phxT2_gyvm15/src/jdbcprop > org.junit.runner.JUnitCore > test.java.org.trafodion.phoenix.end2end.AlterTableTest > > But the same error occured again, no more feedback message just "abort", -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2524) phoenix type 2 test on trafodion, return abort error message
[ https://issues.apache.org/jira/browse/TRAFODION-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reassigned TRAFODION-2524: --- Assignee: Kevin Xu > phoenix type 2 test on trafodion, return abort error message > > > Key: TRAFODION-2524 > URL: https://issues.apache.org/jira/browse/TRAFODION-2524 > Project: Apache Trafodion > Issue Type: Test > Components: client-jdbc-t2 >Affects Versions: 2.1-incubating > Environment: centos 6.8, jdk1.8, trafodion2.1 >Reporter: luoyunpeng >Assignee: Kevin Xu >Priority: Critical > Labels: test > > when i was running phoenix type 2 test on trafodion2.1 with python script, > and error occuced, like this： > > /bin/sh: line 1: 25520 Aborted > > I think this maybe the python sript cause the error, so switch to execute > one test by java command like this： > > java -cp > .:$CLASSPATH:/home/trafodion/apache-trafodion-2.1.0/export/lib/jdbcT2.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/junit/junit-4.11.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/junit/hamcrest-all-1.3.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/thirdparty/google-collections-1.0-rc2.jar:/opt/share/Yunpeng/phxT2_gyvm15/src/test/java/lib/thirdparty/commons-lang-2.6.jar > -Duser.timezone=GMT > -Dtrafjdbc.properties=/opt/share/Yunpeng/phxT2_gyvm15/src/jdbcprop > org.junit.runner.JUnitCore > test.java.org.trafodion.phoenix.end2end.AlterTableTest > > But the same error occured again, no more feedback message just "abort", -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TRAFODION-2462) TRAFCI gui installer does not work
[ https://issues.apache.org/jira/browse/TRAFODION-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reassigned TRAFODION-2462: --- Assignee: Alex Peng > TRAFCI gui installer does not work > -- > > Key: TRAFODION-2462 > URL: https://issues.apache.org/jira/browse/TRAFODION-2462 > Project: Apache Trafodion > Issue Type: Bug > Components: client-ci >Affects Versions: 2.1-incubating >Reporter: Anuradha Hegde >Assignee: Alex Peng > Fix For: 2.1-incubating > > > There are several issues with trafci > 1. GUI installer on Windows does not work. Bascially the browse button to > upload the T4 jar file and to specify the location of trafci install dir does > not function. hence installation does not proceed > 2. After a successful install of trafci on Windows or *nix we notice that > lib file contains jdbcT4 and jline jar files.. There is no need to > pre-package these files with the product > 3. Running any sql statements from TRAF_HOME folder returns the following > error > SQL>get tables; > *** ERROR[1394] *** ERROR[16001] No message found for SQLCODE -1394. > MXID11292972123518900177319330906U300_877_SQL_CUR_2 > [2017-01-25 20:44:03] > But executing the same statement when you are in $TRAF_HOME/sql/scripts > folder works. > 4. Executing the wrapper script 'trafci' returns and message as below and > proceeds with successful connection. You don't see this messagewhen executing > trafci.sh > /core/sqf/sql/local_hadoop/dcs-2.1.0/bin/dcs-config.sh: line > 90: .: sqenv.sh: file not found > 5. Executing sql statements in multiples lines causes additional SQL prompt > to be displayed > Connected to Apache Trafodion > SQL>get tables > +>SQL> > 6. on successful connect and disconnect when new mxosrvrs are picked up the > default schema is changed from 'SEABASE' to 'USR' (This might be a server > side issue too but will need to debug and find out) > 7. FC command does not work. Look at trafci manual for examples on how FC > command was displayed back, It was shown back with the SQL prompt > SQL>fc > show remoteprocess; > SQL> i > show re moteprocess; > SQL> > 8. Did the error message format change? This should have been syntax error > > SQL>gett; > *** ERROR[15001] *** ERROR[16001] No message found for SQLCODE -15001. > gett; >^ (4 characters from start of SQL statement) > MXID11086222123521382568755030206U300_493_SQL_CUR_4 > [2017-01-25 21:14:18] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work stopped] (TRAFODION-1786) Update T4 driver code to support TYPE_SCROLL requests
[ https://issues.apache.org/jira/browse/TRAFODION-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1786 stopped by Kevin Xu. --- > Update T4 driver code to support TYPE_SCROLL requests > - > > Key: TRAFODION-1786 > URL: https://issues.apache.org/jira/browse/TRAFODION-1786 > Project: Apache Trafodion > Issue Type: Improvement > Components: client-jdbc-t4 >Reporter: Roberta Marton >Assignee: Kevin Xu > > As part of releasing Apache Trafodion release 1.3.0, GPL licensed files were > removed to meet licensing requirements. However, removing these files caused > some features like scrollable cursors to no longer be supported. Therefore, > these features need to be supported. The following methods need to be > implemented as found in the TrafT4ResultSet.java file found in the T4 driver > directory: >cancelRowUpdates >moveToInsertRows >deleteRow >insertRow >updateRow >refreshRow >rowDeleted >rowInserted >rowUpdated -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TRAFODION-1943) Jar file is not uploaded to all nodes after calling the PUT system spj to upload the jar.
[ https://issues.apache.org/jira/browse/TRAFODION-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1943. - Resolution: Fixed > Jar file is not uploaded to all nodes after calling the PUT system spj to > upload the jar. > - > > Key: TRAFODION-1943 > URL: https://issues.apache.org/jira/browse/TRAFODION-1943 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-general >Reporter: Elaine_WangLing >Assignee: Kevin Xu > Fix For: 2.1-incubating > > > Jar file is not uploaded to all nodes after calling the PUT system spj to > upload the jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TRAFODION-1952) jdbc can not work without config hostname and ip in /etc/hosts on client machine
[ https://issues.apache.org/jira/browse/TRAFODION-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1952. - Resolution: Fixed > jdbc can not work without config hostname and ip in /etc/hosts on client > machine > > > Key: TRAFODION-1952 > URL: https://issues.apache.org/jira/browse/TRAFODION-1952 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 1.3-incubating > Environment: client machine Linux >Reporter: Feng Qiang >Assignee: Kevin Xu >Priority: Minor > > An error occurred while establishing the connection: > Long Message: > *** ERROR[29717] Internal error: Error getting the name of the local host. > Details: >Type: org.trafodion.jdbc.t4.SecurityException >Error Code: 29717 >SQL State: 38001 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TRAFODION-2338) Trafci will take up many connections while loading lookAndFeel property file failed
[ https://issues.apache.org/jira/browse/TRAFODION-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-2338. - Resolution: Fixed > Trafci will take up many connections while loading lookAndFeel property file > failed > --- > > Key: TRAFODION-2338 > URL: https://issues.apache.org/jira/browse/TRAFODION-2338 > Project: Apache Trafodion > Issue Type: Bug > Components: client-ci >Reporter: Kevin Xu >Assignee: Kevin Xu > > Error Message should be: > java.lang.NullPointerException > at java.util.Properties$LineReader.readLine(Unknown Source) > at java.util.Properties.load0(Unknown Source) > at java.util.Properties.load(Unknown Source) > at org.trafodion.ci.LFProperties.loadProperties(LFProperties.java:125) > at > org.trafodion.ci.LFProperties.loadLookAndFeelProps(LFProperties.java:118) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:185) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) > Caught a SQL exception. Error code = -1, msg=The message id: > as_connect_message_error With parameters: server handle not available > org.trafodion.jdbc.t4.TrafT4Exception: The message id: > as_connect_message_errorWith parameters: server handle not available > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:304) > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:243) > at > org.trafodion.jdbc.t4.InterfaceConnection.connect(InterfaceConnection.java:879) > at > org.trafodion.jdbc.t4.InterfaceConnection.(InterfaceConnection.java:176) > at > org.trafodion.jdbc.t4.TrafT4Connection.makeConnection(TrafT4Connection.java:1611) > at > org.trafodion.jdbc.t4.TrafT4Connection.(TrafT4Connection.java:1564) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:132) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:176) > at org.trafodion.jdbc.t4.T4Driver.connect(T4Driver.java:186) > at java.sql.DriverManager.getConnection(Unknown Source) > at java.sql.DriverManager.getConnection(Unknown Source) > at > org.trafodion.ci.SessionInterface.getConnection(SessionInterface.java:1168) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:170) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TRAFODION-2456) TMUDF doesn't work in this scenario with its parallism
Kevin Xu created TRAFODION-2456:
---
Summary: TMUDF doesn't work in this scenario with its parallism
Key: TRAFODION-2456
URL: https://issues.apache.org/jira/browse/TRAFODION-2456
Project: Apache Trafodion
Issue Type: Improvement
Reporter: Kevin Xu
Assignee: Hans Zeller
Priority: Critical
Attachments: ParTest2.java
Attached ParTest2.java.
Expected to print 6 lines, but got only 1 line.
Workaround is to add the following lines:
@Override
public void describeStatistics(UDRInvocationInfo info) throws
UDRException {
info.out().setEstimatedNumRows(100);
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (TRAFODION-2338) Trafci will take up many connections while loading lookAndFeel property file failed
[ https://issues.apache.org/jira/browse/TRAFODION-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2338 started by Kevin Xu. --- > Trafci will take up many connections while loading lookAndFeel property file > failed > --- > > Key: TRAFODION-2338 > URL: https://issues.apache.org/jira/browse/TRAFODION-2338 > Project: Apache Trafodion > Issue Type: Bug > Components: client-ci >Reporter: Kevin Xu >Assignee: Kevin Xu > > Error Message should be: > java.lang.NullPointerException > at java.util.Properties$LineReader.readLine(Unknown Source) > at java.util.Properties.load0(Unknown Source) > at java.util.Properties.load(Unknown Source) > at org.trafodion.ci.LFProperties.loadProperties(LFProperties.java:125) > at > org.trafodion.ci.LFProperties.loadLookAndFeelProps(LFProperties.java:118) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:185) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) > Caught a SQL exception. Error code = -1, msg=The message id: > as_connect_message_error With parameters: server handle not available > org.trafodion.jdbc.t4.TrafT4Exception: The message id: > as_connect_message_errorWith parameters: server handle not available > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:304) > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:243) > at > org.trafodion.jdbc.t4.InterfaceConnection.connect(InterfaceConnection.java:879) > at > org.trafodion.jdbc.t4.InterfaceConnection.(InterfaceConnection.java:176) > at > org.trafodion.jdbc.t4.TrafT4Connection.makeConnection(TrafT4Connection.java:1611) > at > org.trafodion.jdbc.t4.TrafT4Connection.(TrafT4Connection.java:1564) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:132) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:176) > at org.trafodion.jdbc.t4.T4Driver.connect(T4Driver.java:186) > at java.sql.DriverManager.getConnection(Unknown Source) > at java.sql.DriverManager.getConnection(Unknown Source) > at > org.trafodion.ci.SessionInterface.getConnection(SessionInterface.java:1168) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:170) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2338) Trafci will take up many connections while loading lookAndFeel property file
Kevin Xu created TRAFODION-2338: --- Summary: Trafci will take up many connections while loading lookAndFeel property file Key: TRAFODION-2338 URL: https://issues.apache.org/jira/browse/TRAFODION-2338 Project: Apache Trafodion Issue Type: Bug Components: client-ci Reporter: Kevin Xu Assignee: Kevin Xu Error Message should be: java.lang.NullPointerException at java.util.Properties$LineReader.readLine(Unknown Source) at java.util.Properties.load0(Unknown Source) at java.util.Properties.load(Unknown Source) at org.trafodion.ci.LFProperties.loadProperties(LFProperties.java:125) at org.trafodion.ci.LFProperties.loadLookAndFeelProps(LFProperties.java:118) at org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:185) at org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) at org.trafodion.ci.UserInterface.main(UserInterface.java:276) Caught a SQL exception. Error code = -1, msg=The message id: as_connect_message_error With parameters: server handle not available org.trafodion.jdbc.t4.TrafT4Exception: The message id: as_connect_message_errorWith parameters: server handle not available at org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:304) at org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:243) at org.trafodion.jdbc.t4.InterfaceConnection.connect(InterfaceConnection.java:879) at org.trafodion.jdbc.t4.InterfaceConnection.(InterfaceConnection.java:176) at org.trafodion.jdbc.t4.TrafT4Connection.makeConnection(TrafT4Connection.java:1611) at org.trafodion.jdbc.t4.TrafT4Connection.(TrafT4Connection.java:1564) at org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:132) at org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:176) at org.trafodion.jdbc.t4.T4Driver.connect(T4Driver.java:186) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at org.trafodion.ci.SessionInterface.getConnection(SessionInterface.java:1168) at org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:170) at org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) at org.trafodion.ci.UserInterface.main(UserInterface.java:276) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2338) Trafci will take up many connections while loading lookAndFeel property file failed
[ https://issues.apache.org/jira/browse/TRAFODION-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-2338: Summary: Trafci will take up many connections while loading lookAndFeel property file failed (was: Trafci will take up many connections while loading lookAndFeel property file) > Trafci will take up many connections while loading lookAndFeel property file > failed > --- > > Key: TRAFODION-2338 > URL: https://issues.apache.org/jira/browse/TRAFODION-2338 > Project: Apache Trafodion > Issue Type: Bug > Components: client-ci >Reporter: Kevin Xu >Assignee: Kevin Xu > > Error Message should be: > java.lang.NullPointerException > at java.util.Properties$LineReader.readLine(Unknown Source) > at java.util.Properties.load0(Unknown Source) > at java.util.Properties.load(Unknown Source) > at org.trafodion.ci.LFProperties.loadProperties(LFProperties.java:125) > at > org.trafodion.ci.LFProperties.loadLookAndFeelProps(LFProperties.java:118) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:185) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) > Caught a SQL exception. Error code = -1, msg=The message id: > as_connect_message_error With parameters: server handle not available > org.trafodion.jdbc.t4.TrafT4Exception: The message id: > as_connect_message_errorWith parameters: server handle not available > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:304) > at > org.trafodion.jdbc.t4.TrafT4Messages.createSQLException(TrafT4Messages.java:243) > at > org.trafodion.jdbc.t4.InterfaceConnection.connect(InterfaceConnection.java:879) > at > org.trafodion.jdbc.t4.InterfaceConnection.(InterfaceConnection.java:176) > at > org.trafodion.jdbc.t4.TrafT4Connection.makeConnection(TrafT4Connection.java:1611) > at > org.trafodion.jdbc.t4.TrafT4Connection.(TrafT4Connection.java:1564) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:132) > at > org.trafodion.jdbc.t4.TrafT4DataSource.getConnection(TrafT4DataSource.java:176) > at org.trafodion.jdbc.t4.T4Driver.connect(T4Driver.java:186) > at java.sql.DriverManager.getConnection(Unknown Source) > at java.sql.DriverManager.getConnection(Unknown Source) > at > org.trafodion.ci.SessionInterface.getConnection(SessionInterface.java:1168) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:170) > at > org.trafodion.ci.SessionInterface.createSession(SessionInterface.java:147) > at org.trafodion.ci.UserInterface.main(UserInterface.java:276) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2079) [3rd party tool-Squirrel] indexes won't show up on objects panel, sql command line works fine
[ https://issues.apache.org/jira/browse/TRAFODION-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reassigned TRAFODION-2079: --- Assignee: Weiqing Xu (was: Kevin Xu) > [3rd party tool-Squirrel] indexes won't show up on objects panel, sql command > line works fine > - > > Key: TRAFODION-2079 > URL: https://issues.apache.org/jira/browse/TRAFODION-2079 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.1-incubating > Environment: Squirrel 3.7 > server info -- esgynDBadv R2.1, centos 6.7, hbase1.0 cdh5.4.8 >Reporter: Gao, Rui-Xian >Assignee: Weiqing Xu >Priority: Minor > > click table name from objects panel, indexes won't show up. > But checking from sql command line, indexes will be returned. > >>get indexes on table BTSEL04; > Indexes on Table RACHEL_SCH.BTSEL04 > === > BTSEL04A > BTSEL04B -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2018) JDBCT4 does not support procedure list on DBVisualizer
Kevin Xu created TRAFODION-2018: --- Summary: JDBCT4 does not support procedure list on DBVisualizer Key: TRAFODION-2018 URL: https://issues.apache.org/jira/browse/TRAFODION-2018 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Reporter: Kevin Xu Assignee: Kevin Xu 1.Open DBV 2. Connect to Trafodion 3. Show procedure list on the left tree// Error here -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work stopped] (TRAFODION-2014) NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website
[ https://issues.apache.org/jira/browse/TRAFODION-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2014 stopped by Kevin Xu. --- > NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website > > > Key: TRAFODION-2014 > URL: https://issues.apache.org/jira/browse/TRAFODION-2014 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > HTTP ERROR 500 > Problem accessing /servers.jsp. Reason: > > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > Caused by: > java.lang.NoSuchMethodError: > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > at > org.trafodion.dcs.generated.master.servers_jsp._jspx_meth_display_column_0(servers_jsp.java:420) > at > org.trafodion.dcs.generated.master.servers_jsp._jspService(servers_jsp.java:228) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (TRAFODION-2014) NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website
[ https://issues.apache.org/jira/browse/TRAFODION-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu reopened TRAFODION-2014: - > NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website > > > Key: TRAFODION-2014 > URL: https://issues.apache.org/jira/browse/TRAFODION-2014 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > HTTP ERROR 500 > Problem accessing /servers.jsp. Reason: > > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > Caused by: > java.lang.NoSuchMethodError: > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > at > org.trafodion.dcs.generated.master.servers_jsp._jspx_meth_display_column_0(servers_jsp.java:420) > at > org.trafodion.dcs.generated.master.servers_jsp._jspService(servers_jsp.java:228) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2014) NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website
[ https://issues.apache.org/jira/browse/TRAFODION-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-2014. - Resolution: Fixed > NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website > > > Key: TRAFODION-2014 > URL: https://issues.apache.org/jira/browse/TRAFODION-2014 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > HTTP ERROR 500 > Problem accessing /servers.jsp. Reason: > > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > Caused by: > java.lang.NoSuchMethodError: > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > at > org.trafodion.dcs.generated.master.servers_jsp._jspx_meth_display_column_0(servers_jsp.java:420) > at > org.trafodion.dcs.generated.master.servers_jsp._jspService(servers_jsp.java:228) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2014) NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website
[ https://issues.apache.org/jira/browse/TRAFODION-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2014 started by Kevin Xu. --- > NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website > > > Key: TRAFODION-2014 > URL: https://issues.apache.org/jira/browse/TRAFODION-2014 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > HTTP ERROR 500 > Problem accessing /servers.jsp. Reason: > > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > Caused by: > java.lang.NoSuchMethodError: > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; > at > org.trafodion.dcs.generated.master.servers_jsp._jspx_meth_display_column_0(servers_jsp.java:420) > at > org.trafodion.dcs.generated.master.servers_jsp._jspService(servers_jsp.java:228) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2014) NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website
Kevin Xu created TRAFODION-2014: --- Summary: NoSuchMethodError: PageContextImpl.evaluateExpression on DCS website Key: TRAFODION-2014 URL: https://issues.apache.org/jira/browse/TRAFODION-2014 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Reporter: Kevin Xu Assignee: Kevin Xu HTTP ERROR 500 Problem accessing /servers.jsp. Reason: org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; Caused by: java.lang.NoSuchMethodError: org.apache.jasper.runtime.PageContextImpl.evaluateExpression(Ljava/lang/String;Ljava/lang/Class;Ljavax/servlet/jsp/PageContext;Lorg/apache/jasper/runtime/ProtectedFunctionMapper;)Ljava/lang/Object; at org.trafodion.dcs.generated.master.servers_jsp._jspx_meth_display_column_0(servers_jsp.java:420) at org.trafodion.dcs.generated.master.servers_jsp._jspService(servers_jsp.java:228) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2003) Some classes named with the prefix HP instead of Traf
Kevin Xu created TRAFODION-2003: --- Summary: Some classes named with the prefix HP instead of Traf Key: TRAFODION-2003 URL: https://issues.apache.org/jira/browse/TRAFODION-2003 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Reporter: Kevin Xu Some classes named with the prefix HP instead of Traf. It's not consistent while the others start Traf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-532) LP Bug: 1355038 - SPJ w result set failed with ERROR[8841]
[
https://issues.apache.org/jira/browse/TRAFODION-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271793#comment-15271793
]
Kevin Xu commented on TRAFODION-532:
This issue is no long existing on latest code. Anyway, QA will confirm on it.
>>create table testtab(e_code int);
--- SQL operation complete.
>>Call RS292();
--- 0 row(s) selected.
--- SQL operation complete.
>>select * from(delete from testtab where e_code>2 return old.*) as t1;
--- 0 row(s) selected.
>>insert into testtab values(2),(2),(5),(3),(4);
--- 5 row(s) inserted.
>>select * from(delete from testtab where e_code>2 return old.*) as t1;
E_CODE
---
3
4
--- 2 row(s) selected.
>>select * from testtab;
E_CODE
---
2
2
5
--- 3 row(s) selected.
> LP Bug: 1355038 - SPJ w result set failed with ERROR[8841]
> --
>
> Key: TRAFODION-532
> URL: https://issues.apache.org/jira/browse/TRAFODION-532
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
>Reporter: Chong Hsu
>Assignee: Kevin Xu
>Priority: Critical
> Fix For: 1.0 (pre-incubation)
>
>
> SPJ w result set failed with ERROR[8841]
> Tested with Trafodion build, 20140801-0830.
> Calling a SPJ with result set:
>public static void RS292(ResultSet[] paramArrayOfResultSet) throws
> Exception
>{
> String str = "jdbc:default:connection";
>
> Connection localConnection = DriverManager.getConnection(str);
> Statement localStatement = localConnection.createStatement();
> paramArrayOfResultSet[0] = localStatement.executeQuery("select *
> from(delete from testtab where e_code>2 return old.*) as t1");
>}
> it failed with ERROR[8841]:
> *** ERROR[8841] User application committed or aborted a transaction started
> by SQL. This transaction needs to be committed or aborted by calling SQL
> COMMIT or ROLLBACK WORK. [2014-08-11 04:30:14]
> The SPJ Jar file is attached. Here are the steps to produce the error:
>
> set schema testspj;
> create library spjrs file '//Testrs.jar';
> create procedure RS292()
> language java parameter style java
> library spjrs
> dynamic result sets 3
> external name 'Testrs.RS292';
> Call RS292();
> *** ERROR[8841] User application committed or aborted a transaction started
> by SQL. This transaction needs to be committed or aborted by calling SQL
> COMMIT or ROLLBACK WORK. [2014-08-11 04:30:14]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-532) LP Bug: 1355038 - SPJ w result set failed with ERROR[8841]
[
https://issues.apache.org/jira/browse/TRAFODION-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269944#comment-15269944
]
Kevin Xu commented on TRAFODION-532:
Selva, Sure, i'll take a look.
> LP Bug: 1355038 - SPJ w result set failed with ERROR[8841]
> --
>
> Key: TRAFODION-532
> URL: https://issues.apache.org/jira/browse/TRAFODION-532
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
>Reporter: Chong Hsu
>Assignee: Kevin Xu
>Priority: Critical
> Fix For: 1.0 (pre-incubation)
>
>
> SPJ w result set failed with ERROR[8841]
> Tested with Trafodion build, 20140801-0830.
> Calling a SPJ with result set:
>public static void RS292(ResultSet[] paramArrayOfResultSet) throws
> Exception
>{
> String str = "jdbc:default:connection";
>
> Connection localConnection = DriverManager.getConnection(str);
> Statement localStatement = localConnection.createStatement();
> paramArrayOfResultSet[0] = localStatement.executeQuery("select *
> from(delete from testtab where e_code>2 return old.*) as t1");
>}
> it failed with ERROR[8841]:
> *** ERROR[8841] User application committed or aborted a transaction started
> by SQL. This transaction needs to be committed or aborted by calling SQL
> COMMIT or ROLLBACK WORK. [2014-08-11 04:30:14]
> The SPJ Jar file is attached. Here are the steps to produce the error:
>
> set schema testspj;
> create library spjrs file '//Testrs.jar';
> create procedure RS292()
> language java parameter style java
> library spjrs
> dynamic result sets 3
> external name 'Testrs.RS292';
> Call RS292();
> *** ERROR[8841] User application committed or aborted a transaction started
> by SQL. This transaction needs to be committed or aborted by calling SQL
> COMMIT or ROLLBACK WORK. [2014-08-11 04:30:14]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1780) [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
[
https://issues.apache.org/jira/browse/TRAFODION-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Xu resolved TRAFODION-1780.
-
Resolution: Fixed
> [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
> -
>
> Key: TRAFODION-1780
> URL: https://issues.apache.org/jira/browse/TRAFODION-1780
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> //there is 1 row in table t1.
> String query = "SELECT * FROM t1 WHERE id=? AND name=?";
> conn.setAutoCommit(true);
> try {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, "1");
> statement.setString(2, "1");
> ResultSet rs = statement.executeQuery();
> assertTrue(rs.next());
> assertFalse(rs.next());
> rs.close();
> // Run another query through same connection and make sure
> // you can't find the new row
> rs = statement.executeQuery();
> assertTrue(rs.next());//Error here
> } finally {
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (TRAFODION-1780) [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
[
https://issues.apache.org/jira/browse/TRAFODION-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-1780 started by Kevin Xu.
---
> [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
> -
>
> Key: TRAFODION-1780
> URL: https://issues.apache.org/jira/browse/TRAFODION-1780
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> //there is 1 row in table t1.
> String query = "SELECT * FROM t1 WHERE id=? AND name=?";
> conn.setAutoCommit(true);
> try {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, "1");
> statement.setString(2, "1");
> ResultSet rs = statement.executeQuery();
> assertTrue(rs.next());
> assertFalse(rs.next());
> rs.close();
> // Run another query through same connection and make sure
> // you can't find the new row
> rs = statement.executeQuery();
> assertTrue(rs.next());//Error here
> } finally {
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work stopped] (TRAFODION-1780) [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
[
https://issues.apache.org/jira/browse/TRAFODION-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-1780 stopped by Kevin Xu.
---
> [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
> -
>
> Key: TRAFODION-1780
> URL: https://issues.apache.org/jira/browse/TRAFODION-1780
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> //there is 1 row in table t1.
> String query = "SELECT * FROM t1 WHERE id=? AND name=?";
> conn.setAutoCommit(true);
> try {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, "1");
> statement.setString(2, "1");
> ResultSet rs = statement.executeQuery();
> assertTrue(rs.next());
> assertFalse(rs.next());
> rs.close();
> // Run another query through same connection and make sure
> // you can't find the new row
> rs = statement.executeQuery();
> assertTrue(rs.next());//Error here
> } finally {
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (TRAFODION-1780) [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
[
https://issues.apache.org/jira/browse/TRAFODION-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-1780 started by Kevin Xu.
---
> [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
> -
>
> Key: TRAFODION-1780
> URL: https://issues.apache.org/jira/browse/TRAFODION-1780
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> //there is 1 row in table t1.
> String query = "SELECT * FROM t1 WHERE id=? AND name=?";
> conn.setAutoCommit(true);
> try {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, "1");
> statement.setString(2, "1");
> ResultSet rs = statement.executeQuery();
> assertTrue(rs.next());
> assertFalse(rs.next());
> rs.close();
> // Run another query through same connection and make sure
> // you can't find the new row
> rs = statement.executeQuery();
> assertTrue(rs.next());//Error here
> } finally {
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1780) [MTDCS]jPrepareStatement execute twice, second ResultSet is empty
Kevin Xu created TRAFODION-1780:
---
Summary: [MTDCS]jPrepareStatement execute twice, second ResultSet
is empty
Key: TRAFODION-1780
URL: https://issues.apache.org/jira/browse/TRAFODION-1780
Project: Apache Trafodion
Issue Type: Bug
Components: connectivity-dcs
Reporter: Kevin Xu
//there is 1 row in table t1.
String query = "SELECT * FROM t1 WHERE id=? AND name=?";
conn.setAutoCommit(true);
try {
PreparedStatement statement = conn.prepareStatement(query);
statement.setString(1, "1");
statement.setString(2, "1");
ResultSet rs = statement.executeQuery();
assertTrue(rs.next());
assertFalse(rs.next());
rs.close();
// Run another query through same connection and make sure
// you can't find the new row
rs = statement.executeQuery();
assertTrue(rs.next());//Error here
} finally {
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1726) DatabaseMetaData.getIndexInfo does not work
[
https://issues.apache.org/jira/browse/TRAFODION-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Xu resolved TRAFODION-1726.
-
Resolution: Fixed
added metadata info
> DatabaseMetaData.getIndexInfo does not work
> ---
>
> Key: TRAFODION-1726
> URL: https://issues.apache.org/jira/browse/TRAFODION-1726
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t2
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> DatabaseMetaData.getIndexInfo("TRAFODION", "SEABASE", "OSD28DL_Z1", false,
> true)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1727) DatabaseMetaData.getProcedures does not work
[
https://issues.apache.org/jira/browse/TRAFODION-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Xu resolved TRAFODION-1727.
-
Resolution: Fixed
added meta info
> DatabaseMetaData.getProcedures does not work
>
>
> Key: TRAFODION-1727
> URL: https://issues.apache.org/jira/browse/TRAFODION-1727
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t2
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> DatabaseMetaData.getProcedures("TRAFODION", "SEABASE", "%")
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1760) DBVisualizer Procedure Columns list does not show anything with MTDCS on
[ https://issues.apache.org/jira/browse/TRAFODION-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1760. - Resolution: Fixed Root cause: CHAR type messed the buffer. The buffer returned from T2 has already added one more byte, then on DCS-side it's incorrect to add one more again. > DBVisualizer Procedure Columns list does not show anything with MTDCS on > > > Key: TRAFODION-1760 > URL: https://issues.apache.org/jira/browse/TRAFODION-1760 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > On DBVisualizer: > 1.connect to Trafodion > 2.open schema list > 3.open a schema which has procedures > 4. double click one of the procedures -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1760) DBVisualizer Procedure Columns list does not show anything with MTDCS on
[ https://issues.apache.org/jira/browse/TRAFODION-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1760 started by Kevin Xu. --- > DBVisualizer Procedure Columns list does not show anything with MTDCS on > > > Key: TRAFODION-1760 > URL: https://issues.apache.org/jira/browse/TRAFODION-1760 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > On DBVisualizer: > 1.connect to Trafodion > 2.open schema list > 3.open a schema which has procedures > 4. double click one of the procedures -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1760) DBVisualizer Procedure Columns list does not show anything with MTDCS on
Kevin Xu created TRAFODION-1760: --- Summary: DBVisualizer Procedure Columns list does not show anything with MTDCS on Key: TRAFODION-1760 URL: https://issues.apache.org/jira/browse/TRAFODION-1760 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Reporter: Kevin Xu On DBVisualizer: 1.connect to Trafodion 2.open schema list 3.open a schema which has procedures 4. double click one of the procedures -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1737) DCS UI doest work sometime
[ https://issues.apache.org/jira/browse/TRAFODION-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1737. - Resolution: Fixed > DCS UI doest work sometime > -- > > Key: TRAFODION-1737 > URL: https://issues.apache.org/jira/browse/TRAFODION-1737 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > It says NoSuchMethodException javax/el/ExpressionFactory newInstance() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1738) jdbcT4 cannot be built out on Windows platform
[ https://issues.apache.org/jira/browse/TRAFODION-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1738. - Resolution: Fixed > jdbcT4 cannot be built out on Windows platform > -- > > Key: TRAFODION-1738 > URL: https://issues.apache.org/jira/browse/TRAFODION-1738 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Reporter: Kevin Xu > > build.xml does't work on windows platform. > Buildfile: D:\esgyndb\traf\core\conn\jdbc_type4\build.xml > BUILD FAILED > D:\esgyndb\traf\core\conn\jdbc_type4\build.xml:30: Execute failed: > java.io.IOException: Cannot run program "\bin\sh": CreateProcess error=2, > ? > Total time: 464 milliseconds -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1738) jdbcT4 cannot be built out on Windows platform
Kevin Xu created TRAFODION-1738: --- Summary: jdbcT4 cannot be built out on Windows platform Key: TRAFODION-1738 URL: https://issues.apache.org/jira/browse/TRAFODION-1738 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Reporter: Kevin Xu build.xml does't work on windows platform. Buildfile: D:\esgyndb\traf\core\conn\jdbc_type4\build.xml BUILD FAILED D:\esgyndb\traf\core\conn\jdbc_type4\build.xml:30: Execute failed: java.io.IOException: Cannot run program "\bin\sh": CreateProcess error=2, ? Total time: 464 milliseconds -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1737) DCS UI doest work sometime
Kevin Xu created TRAFODION-1737: --- Summary: DCS UI doest work sometime Key: TRAFODION-1737 URL: https://issues.apache.org/jira/browse/TRAFODION-1737 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Reporter: Kevin Xu It says NoSuchMethodException javax/el/ExpressionFactory newInstance() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1737) DCS UI doest work sometime
[ https://issues.apache.org/jira/browse/TRAFODION-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1737 started by Kevin Xu. --- > DCS UI doest work sometime > -- > > Key: TRAFODION-1737 > URL: https://issues.apache.org/jira/browse/TRAFODION-1737 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu > > It says NoSuchMethodException javax/el/ExpressionFactory newInstance() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1727) DatabaseMetaData.getProcedures does not work
[
https://issues.apache.org/jira/browse/TRAFODION-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-1727 started by Kevin Xu.
---
> DatabaseMetaData.getProcedures does not work
>
>
> Key: TRAFODION-1727
> URL: https://issues.apache.org/jira/browse/TRAFODION-1727
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t2
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> DatabaseMetaData.getProcedures("TRAFODION", "SEABASE", "%")
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (TRAFODION-1726) DatabaseMetaData.getIndexInfo does not work
[
https://issues.apache.org/jira/browse/TRAFODION-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-1726 started by Kevin Xu.
---
> DatabaseMetaData.getIndexInfo does not work
> ---
>
> Key: TRAFODION-1726
> URL: https://issues.apache.org/jira/browse/TRAFODION-1726
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t2
>Reporter: Kevin Xu
>Assignee: Kevin Xu
>
> DatabaseMetaData.getIndexInfo("TRAFODION", "SEABASE", "OSD28DL_Z1", false,
> true)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1727) DatabaseMetaData.getProcedures does not work
Kevin Xu created TRAFODION-1727:
---
Summary: DatabaseMetaData.getProcedures does not work
Key: TRAFODION-1727
URL: https://issues.apache.org/jira/browse/TRAFODION-1727
Project: Apache Trafodion
Issue Type: Bug
Components: client-jdbc-t2
Reporter: Kevin Xu
DatabaseMetaData.getProcedures("TRAFODION", "SEABASE", "%")
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1726) DatabaseMetaData.getIndexInfo does not work
Kevin Xu created TRAFODION-1726:
---
Summary: DatabaseMetaData.getIndexInfo does not work
Key: TRAFODION-1726
URL: https://issues.apache.org/jira/browse/TRAFODION-1726
Project: Apache Trafodion
Issue Type: Bug
Components: client-jdbc-t2
Reporter: Kevin Xu
DatabaseMetaData.getIndexInfo("TRAFODION", "SEABASE", "OSD28DL_Z1", false, true)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1719) dcsstart/dcsstop doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1719. - Resolution: Fixed > dcsstart/dcsstop doesn't work > - > > Key: TRAFODION-1719 > URL: https://issues.apache.org/jira/browse/TRAFODION-1719 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu >Priority: Blocker > > bash -x ./bin/stop-dcs.sh > 44 + master='15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries > :3,RetryIntervalMillis:1000 > 45 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 46 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 47 esgvm-8.novalocal' > 48 + errCode=0 > 49 + '[' 0 -ne 0 ']' > 50 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 51 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 52 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 53 esgvm-8.novalocal' == '' ']' > 54 ++ hostname -f > 55 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 56 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 57 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 58 esgvm-8.novalocal' == esgvm-8.novalocal ']' > 59 + remote_cmd='cd /data/esgyndb/traf-plus/dcs/bin/..; > /data/esgyndb/traf-plus/dcs/bin/dcs-daemon.sh --config /data/esgyn > db/traf-plus/dcs/bin/../conf stop master' > 60 + ssh -q -n 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetri > es:3,RetryIntervalMillis:1000 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: > Zookeeper.State=CONNECTING 15/12/22 00:39:02 > DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED esgvm-8.novalocal cd > '/data/esgyndb/traf-plus/dcs/bin/..;' /data/es > gyndb/traf-plus/dcs/bin/dcs-daemon.sh --config > /data/esgyndb/traf-plus/dcs/bin/../conf stop master > 61 + sed 's/^/15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetrie > s:3,RetryIntervalMillis:1000 > 62 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 63 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 64 esgvm-8.novalocal: /' > 65 sed: -e expression #1, char 10: unknown option to `s' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1724) DatabaseMetaData.getTypeInfo() doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1724. - Resolution: Fixed > DatabaseMetaData.getTypeInfo() doesn't work > --- > > Key: TRAFODION-1724 > URL: https://issues.apache.org/jira/browse/TRAFODION-1724 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t2 >Reporter: Kevin Xu >Assignee: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1724) DatabaseMetaData.getTypeInfo() doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1724 started by Kevin Xu. --- > DatabaseMetaData.getTypeInfo() doesn't work > --- > > Key: TRAFODION-1724 > URL: https://issues.apache.org/jira/browse/TRAFODION-1724 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t2 >Reporter: Kevin Xu >Assignee: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1724) DatabaseMetaData.getTypeInfo() doesn't work
Kevin Xu created TRAFODION-1724: --- Summary: DatabaseMetaData.getTypeInfo() doesn't work Key: TRAFODION-1724 URL: https://issues.apache.org/jira/browse/TRAFODION-1724 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t2 Reporter: Kevin Xu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1719) dcsstart/dcsstop doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1719 started by Kevin Xu. --- > dcsstart/dcsstop doesn't work > - > > Key: TRAFODION-1719 > URL: https://issues.apache.org/jira/browse/TRAFODION-1719 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu >Assignee: Kevin Xu >Priority: Blocker > > bash -x ./bin/stop-dcs.sh > 44 + master='15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries > :3,RetryIntervalMillis:1000 > 45 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 46 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 47 esgvm-8.novalocal' > 48 + errCode=0 > 49 + '[' 0 -ne 0 ']' > 50 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 51 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 52 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 53 esgvm-8.novalocal' == '' ']' > 54 ++ hostname -f > 55 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 56 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 57 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 58 esgvm-8.novalocal' == esgvm-8.novalocal ']' > 59 + remote_cmd='cd /data/esgyndb/traf-plus/dcs/bin/..; > /data/esgyndb/traf-plus/dcs/bin/dcs-daemon.sh --config /data/esgyn > db/traf-plus/dcs/bin/../conf stop master' > 60 + ssh -q -n 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetri > es:3,RetryIntervalMillis:1000 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: > Zookeeper.State=CONNECTING 15/12/22 00:39:02 > DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED esgvm-8.novalocal cd > '/data/esgyndb/traf-plus/dcs/bin/..;' /data/es > gyndb/traf-plus/dcs/bin/dcs-daemon.sh --config > /data/esgyndb/traf-plus/dcs/bin/../conf stop master > 61 + sed 's/^/15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetrie > s:3,RetryIntervalMillis:1000 > 62 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 63 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 64 esgvm-8.novalocal: /' > 65 sed: -e expression #1, char 10: unknown option to `s' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1719) dcsstart/dcsstop doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1719: The issue is from dcsstart/dcsstop script. Now already been fixed. [poc@esgvm-8 dcs]$ ./bin/dcs --config /data/esgyndb/traf-plus/dcs/bin/../conf org.trafodion.dcs.zookeeper.ZkUtil /poc/dcs/master 15/12/22 01:33:49 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetries:3,RetryIntervalMillis:1000 15/12/22 01:33:49 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 15/12/22 01:33:50 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED esgvm-8.novalocal > dcsstart/dcsstop doesn't work > - > > Key: TRAFODION-1719 > URL: https://issues.apache.org/jira/browse/TRAFODION-1719 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu >Priority: Blocker > > bash -x ./bin/stop-dcs.sh > 44 + master='15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries > :3,RetryIntervalMillis:1000 > 45 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 46 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 47 esgvm-8.novalocal' > 48 + errCode=0 > 49 + '[' 0 -ne 0 ']' > 50 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 51 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 52 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 53 esgvm-8.novalocal' == '' ']' > 54 ++ hostname -f > 55 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, > RetryIntervalMillis:1000 > 56 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 57 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 58 esgvm-8.novalocal' == esgvm-8.novalocal ']' > 59 + remote_cmd='cd /data/esgyndb/traf-plus/dcs/bin/..; > /data/esgyndb/traf-plus/dcs/bin/dcs-daemon.sh --config /data/esgyn > db/traf-plus/dcs/bin/../conf stop master' > 60 + ssh -q -n 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetri > es:3,RetryIntervalMillis:1000 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: > Zookeeper.State=CONNECTING 15/12/22 00:39:02 > DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED esgvm-8.novalocal cd > '/data/esgyndb/traf-plus/dcs/bin/..;' /data/es > gyndb/traf-plus/dcs/bin/dcs-daemon.sh --config > /data/esgyndb/traf-plus/dcs/bin/../conf stop master > 61 + sed 's/^/15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper > Servers:localhost:2181,SessionTimeout:18,MaxRetrie > s:3,RetryIntervalMillis:1000 > 62 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING > 63 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED > 64 esgvm-8.novalocal: /' > 65 sed: -e expression #1, char 10: unknown option to `s' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1719) dcsstart/dcsstop doesn't work
Kevin Xu created TRAFODION-1719: --- Summary: dcsstart/dcsstop doesn't work Key: TRAFODION-1719 URL: https://issues.apache.org/jira/browse/TRAFODION-1719 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Reporter: Kevin Xu Priority: Blocker bash -x ./bin/stop-dcs.sh 44 + master='15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetries :3,RetryIntervalMillis:1000 45 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 46 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED 47 esgvm-8.novalocal' 48 + errCode=0 49 + '[' 0 -ne 0 ']' 50 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, RetryIntervalMillis:1000 51 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 52 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED 53 esgvm-8.novalocal' == '' ']' 54 ++ hostname -f 55 + '[' '15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetries:3, RetryIntervalMillis:1000 56 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 57 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED 58 esgvm-8.novalocal' == esgvm-8.novalocal ']' 59 + remote_cmd='cd /data/esgyndb/traf-plus/dcs/bin/..; /data/esgyndb/traf-plus/dcs/bin/dcs-daemon.sh --config /data/esgyn db/traf-plus/dcs/bin/../conf stop master' 60 + ssh -q -n 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetri es:3,RetryIntervalMillis:1000 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED esgvm-8.novalocal cd '/data/esgyndb/traf-plus/dcs/bin/..;' /data/es gyndb/traf-plus/dcs/bin/dcs-daemon.sh --config /data/esgyndb/traf-plus/dcs/bin/../conf stop master 61 + sed 's/^/15/12/22 00:39:01 DEBUG zookeeper.ZkClient: ZooKeeper Servers:localhost:2181,SessionTimeout:18,MaxRetrie s:3,RetryIntervalMillis:1000 62 15/12/22 00:39:01 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTING 63 15/12/22 00:39:02 DEBUG zookeeper.ZkClient: Zookeeper.State=CONNECTED 64 esgvm-8.novalocal: /' 65 sed: -e expression #1, char 10: unknown option to `s' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1685) jdbcT2 conn.getMetaData().getSchemas() does not work
[ https://issues.apache.org/jira/browse/TRAFODION-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1685. - Resolution: Fixed > jdbcT2 conn.getMetaData().getSchemas() does not work > > > Key: TRAFODION-1685 > URL: https://issues.apache.org/jira/browse/TRAFODION-1685 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t2 >Reporter: Kevin Xu >Assignee: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-1685) jdbcT2 conn.getMetaData().getSchemas() does not work
[ https://issues.apache.org/jira/browse/TRAFODION-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-1685 started by Kevin Xu. --- > jdbcT2 conn.getMetaData().getSchemas() does not work > > > Key: TRAFODION-1685 > URL: https://issues.apache.org/jira/browse/TRAFODION-1685 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t2 >Reporter: Kevin Xu >Assignee: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1685) jdbcT2 conn.getMetaData().getSchemas() does not work
Kevin Xu created TRAFODION-1685: --- Summary: jdbcT2 conn.getMetaData().getSchemas() does not work Key: TRAFODION-1685 URL: https://issues.apache.org/jira/browse/TRAFODION-1685 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t2 Reporter: Kevin Xu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1668) Cannot upload customer SPJ JARs
[ https://issues.apache.org/jira/browse/TRAFODION-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1668: Summary: Cannot upload customer SPJ JARs (was: cannot upload customer JARs) > Cannot upload customer SPJ JARs > --- > > Key: TRAFODION-1668 > URL: https://issues.apache.org/jira/browse/TRAFODION-1668 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1668) cannot upload customer JARs
[ https://issues.apache.org/jira/browse/TRAFODION-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1668: Summary: cannot upload customer JARs (was: SPJ initialization for customer JARs uploading) > cannot upload customer JARs > --- > > Key: TRAFODION-1668 > URL: https://issues.apache.org/jira/browse/TRAFODION-1668 > Project: Apache Trafodion > Issue Type: Improvement >Reporter: Kevin Xu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1668) SPJ initialization for customer JARs uploading
Kevin Xu created TRAFODION-1668: --- Summary: SPJ initialization for customer JARs uploading Key: TRAFODION-1668 URL: https://issues.apache.org/jira/browse/TRAFODION-1668 Project: Apache Trafodion Issue Type: Improvement Reporter: Kevin Xu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1649) Do not know which row has error while there is PrepareStatement.executeBatch() error
Kevin Xu created TRAFODION-1649: --- Summary: Do not know which row has error while there is PrepareStatement.executeBatch() error Key: TRAFODION-1649 URL: https://issues.apache.org/jira/browse/TRAFODION-1649 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Reporter: Kevin Xu int[] rs = ps.executeStatement(); there is an exception while some error occurs, then it cant get returned array -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1578) Proposal for SPJ management
[ https://issues.apache.org/jira/browse/TRAFODION-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996143#comment-14996143 ] Kevin Xu commented on TRAFODION-1578: - One JVM(process) per Trafodion user by default. User knows how much heap size they need well than us. By the way, it may set limitations on each JVM and only some authorized options can be modified. i'm not saying that it'll have same JVM with DCSServer. DCSServer will create a JVM with a customized IDLE timeout(user may make decision that how long it is existing, maybe never stop). As i said, the new path will be DCSMaster->DCSServer->create new JVM for current user if not exist. Nothing about UDR. Yes, regular users dont have permission to kill DCSServers. They have permission to start/stop SPJ JVM( one for each user by default). > Proposal for SPJ management > --- > > Key: TRAFODION-1578 > URL: https://issues.apache.org/jira/browse/TRAFODION-1578 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu > > JAR upload process: > 1. Initialize JAR upload procedure by default > 2. JAR upload by Trafci(add library LIB_NAME JAR_LOCAL_PATH). Upload and > create library will be done here. And also, you can only upload the JARs by > UPLOAD command on Trafci that it will not create a lib. >Tips: Before put the JAR into HDFS check MD5 first, if the file exists, > only add a record in metadata table in case users upload the same JAR many > times on platform. > 3. On server-side, the JAR will store in HDFS. At the same time JAR > metadata(path in HDFS, MD5 of the file, and others) stores in store procedure > metadata table. > 4. create procedure is the same as now. > JAR perform process: > 1. Send a CALL by Trafci/JDBC/ODBC/ADO.NET. > 2. DCSMaster assign a DCSServer for the CALL. > 3. DCSServer start a JVM for the user. User can modify JVM options, program > properties and JAVA classpath. At the same time, a monitor class will be > starting in the JVM witch will register a node on Zookeeper for this JVM as > well as metadata info( process id, server info and so on) and the node will > be removed while JVM exiting. It allows customer to specify JVM idle time in > case of some realtime senarior like Kafka consumer. > 4. Useful commands on Trafci: list all JVMs in user; kill one of them that no > long in use; Restart JVMs with latest JARs and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1578) Proposal for SPJ management
[ https://issues.apache.org/jira/browse/TRAFODION-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996115#comment-14996115 ] Kevin Xu commented on TRAFODION-1578: - For authority, the checking should be done in DCSServer( check whether current user has privilege to call) by querying metadata tables. One JVM(process) per user by default. For arbitrary code, JVM SecurityManager should be helpful. 1. FilePermission in SecurityManager should be helpful. 2. It should be solved if started JVM only has specified folder priviledge. Eventually, the JARs should be existing in the running node and it's fine to copy from HDFS at the first time. It's very good to hear that Venkat will add a GUI function. 3. If JVM behaves are under control, it's not necessary to run a process with a special user ids(one user id per connection? if not, it will impact each other. Otherwise, you will have many user ids to be created.) Refs: https://en.wikipedia.org/wiki/Java_security#Security_manager http://docs.oracle.com/javase/7/docs/technotes/guides/security/overview/jsoverview.html > Proposal for SPJ management > --- > > Key: TRAFODION-1578 > URL: https://issues.apache.org/jira/browse/TRAFODION-1578 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu > > JAR upload process: > 1. Initialize JAR upload procedure by default > 2. JAR upload by Trafci(add library LIB_NAME JAR_LOCAL_PATH). Upload and > create library will be done here. And also, you can only upload the JARs by > UPLOAD command on Trafci that it will not create a lib. >Tips: Before put the JAR into HDFS check MD5 first, if the file exists, > only add a record in metadata table in case users upload the same JAR many > times on platform. > 3. On server-side, the JAR will store in HDFS. At the same time JAR > metadata(path in HDFS, MD5 of the file, and others) stores in store procedure > metadata table. > 4. create procedure is the same as now. > JAR perform process: > 1. Send a CALL by Trafci/JDBC/ODBC/ADO.NET. > 2. DCSMaster assign a DCSServer for the CALL. > 3. DCSServer start a JVM for the user. User can modify JVM options, program > properties and JAVA classpath. At the same time, a monitor class will be > starting in the JVM witch will register a node on Zookeeper for this JVM as > well as metadata info( process id, server info and so on) and the node will > be removed while JVM exiting. It allows customer to specify JVM idle time in > case of some realtime senarior like Kafka consumer. > 4. Useful commands on Trafci: list all JVMs in user; kill one of them that no > long in use; Restart JVMs with latest JARs and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TRAFODION-1578) Proposal for SPJ management
[ https://issues.apache.org/jira/browse/TRAFODION-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995948#comment-14995948 ] Kevin Xu edited comment on TRAFODION-1578 at 11/9/15 5:04 AM: -- For muti-thread DCS, it's DCSMaster->DCSServer->jdbcT2. For SPJ, it's DCSMaster->DCSServer->SQ Engine -> UDR->jdbcT2(JAVA-> C++ -> JAVA, why not JAVA -> JAVA). it's not necessary to create a new JVM for each connection. But for single JVM, it should load the JARs dynamicly as what UDR is doing and has security issue. So the proposal is to start a new JVM and manage its security by Java SecurityMangement. Contains SQL is trying to reuse JVM, right? As i mentioned, there is a customized idle timeout( contains non-stop) for standing by. yes, the users can modify JVM options directly, but it will have limitation on customized options like max heap size of JVM, the number of connections for one user. And also, allowed to start/restart. i'd like to do an experiment on a new command 'agent'. was (Author: kevinxu021): For muti-thread DCS, it's DCSMaster->DCSServer->jdbcT2. For SPJ, it's DCSMaster->DCSServer->UDR->jdbcT2(JAVA-> C++ -> JAVA, why not JAVA -> JAVA). it's not necessary to create a new JVM for each connection. But for single JVM, it should load the JARs dynamicly as what UDR is doing. Contains SQL is trying to reuse JVM, right? As i mentioned, there is a customized idle timeout( contains non-stop) for standing by. yes, the users can modify JVM options directly, but it will have limitation on customized options like max heap size of JVM, the number of connections for one user. And also, allowed to start/restart. i'd like to do an experiment on a new command 'agent'. > Proposal for SPJ management > --- > > Key: TRAFODION-1578 > URL: https://issues.apache.org/jira/browse/TRAFODION-1578 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu > > JAR upload process: > 1. Initialize JAR upload procedure by default > 2. JAR upload by Trafci(add library LIB_NAME JAR_LOCAL_PATH). Upload and > create library will be done here. And also, you can only upload the JARs by > UPLOAD command on Trafci that it will not create a lib. >Tips: Before put the JAR into HDFS check MD5 first, if the file exists, > only add a record in metadata table in case users upload the same JAR many > times on platform. > 3. On server-side, the JAR will store in HDFS. At the same time JAR > metadata(path in HDFS, MD5 of the file, and others) stores in store procedure > metadata table. > 4. create procedure is the same as now. > JAR perform process: > 1. Send a CALL by Trafci/JDBC/ODBC/ADO.NET. > 2. DCSMaster assign a DCSServer for the CALL. > 3. DCSServer start a JVM for the user. User can modify JVM options, program > properties and JAVA classpath. At the same time, a monitor class will be > starting in the JVM witch will register a node on Zookeeper for this JVM as > well as metadata info( process id, server info and so on) and the node will > be removed while JVM exiting. It allows customer to specify JVM idle time in > case of some realtime senarior like Kafka consumer. > 4. Useful commands on Trafci: list all JVMs in user; kill one of them that no > long in use; Restart JVMs with latest JARs and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1578) Proposal for SPJ management
[ https://issues.apache.org/jira/browse/TRAFODION-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995948#comment-14995948 ] Kevin Xu commented on TRAFODION-1578: - For muti-thread DCS, it's DCSMaster->DCSServer->jdbcT2. For SPJ, it's DCSMaster->DCSServer->UDR->jdbcT2(JAVA-> C++ -> JAVA, why not JAVA -> JAVA). it's not necessary to create a new JVM for each connection. But for single JVM, it should load the JARs dynamicly as what UDR is doing. Contains SQL is trying to reuse JVM, right? As i mentioned, there is a customized idle timeout( contains non-stop) for standing by. yes, the users can modify JVM options directly, but it will have limitation on customized options like max heap size of JVM, the number of connections for one user. And also, allowed to start/restart. i'd like to do an experiment on a new command 'agent'. > Proposal for SPJ management > --- > > Key: TRAFODION-1578 > URL: https://issues.apache.org/jira/browse/TRAFODION-1578 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Reporter: Kevin Xu > > JAR upload process: > 1. Initialize JAR upload procedure by default > 2. JAR upload by Trafci(add library LIB_NAME JAR_LOCAL_PATH). Upload and > create library will be done here. And also, you can only upload the JARs by > UPLOAD command on Trafci that it will not create a lib. >Tips: Before put the JAR into HDFS check MD5 first, if the file exists, > only add a record in metadata table in case users upload the same JAR many > times on platform. > 3. On server-side, the JAR will store in HDFS. At the same time JAR > metadata(path in HDFS, MD5 of the file, and others) stores in store procedure > metadata table. > 4. create procedure is the same as now. > JAR perform process: > 1. Send a CALL by Trafci/JDBC/ODBC/ADO.NET. > 2. DCSMaster assign a DCSServer for the CALL. > 3. DCSServer start a JVM for the user. User can modify JVM options, program > properties and JAVA classpath. At the same time, a monitor class will be > starting in the JVM witch will register a node on Zookeeper for this JVM as > well as metadata info( process id, server info and so on) and the node will > be removed while JVM exiting. It allows customer to specify JVM idle time in > case of some realtime senarior like Kafka consumer. > 4. Useful commands on Trafci: list all JVMs in user; kill one of them that no > long in use; Restart JVMs with latest JARs and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1578) Proposal for SPJ management
Kevin Xu created TRAFODION-1578: --- Summary: Proposal for SPJ management Key: TRAFODION-1578 URL: https://issues.apache.org/jira/browse/TRAFODION-1578 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Reporter: Kevin Xu JAR upload process: 1. Initialize JAR upload procedure by default 2. JAR upload by Trafci(add library LIB_NAME JAR_LOCAL_PATH). Upload and create library will be done here. And also, you can only upload the JARs by UPLOAD command on Trafci that it will not create a lib. Tips: Before put the JAR into HDFS check MD5 first, if the file exists, only add a record in metadata table in case users upload the same JAR many times on platform. 3. On server-side, the JAR will store in HDFS. At the same time JAR metadata(path in HDFS, MD5 of the file, and others) stores in store procedure metadata table. 4. create procedure is the same as now. JAR perform process: 1. Send a CALL by Trafci/JDBC/ODBC/ADO.NET. 2. DCSMaster assign a DCSServer for the CALL. 3. DCSServer start a JVM for the user. User can modify JVM options, program properties and JAVA classpath. At the same time, a monitor class will be starting in the JVM witch will register a node on Zookeeper for this JVM as well as metadata info( process id, server info and so on) and the node will be removed while JVM exiting. It allows customer to specify JVM idle time in case of some realtime senarior like Kafka consumer. 4. Useful commands on Trafci: list all JVMs in user; kill one of them that no long in use; Restart JVMs with latest JARs and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1561) We dont know the default configurations on DCS UI
[ https://issues.apache.org/jira/browse/TRAFODION-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1561: Summary: We dont know the default configurations on DCS UI (was: How to know what kinds of configurations it has and its value on DCS UI?) > We dont know the default configurations on DCS UI > - > > Key: TRAFODION-1561 > URL: https://issues.apache.org/jira/browse/TRAFODION-1561 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1561) How to know what kinds of configurations it has and its value on DCS UI?
[ https://issues.apache.org/jira/browse/TRAFODION-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1561: Issue Type: Improvement (was: Bug) > How to know what kinds of configurations it has and its value on DCS UI? > > > Key: TRAFODION-1561 > URL: https://issues.apache.org/jira/browse/TRAFODION-1561 > Project: Apache Trafodion > Issue Type: Improvement > Components: connectivity-dcs >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1561) how to know what kinds of configurations it has and its value on DCS UI?
[ https://issues.apache.org/jira/browse/TRAFODION-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1561: Summary: how to know what kinds of configurations it has and its value on DCS UI? (was: how to know what kinds of configurations it has and its value on DCS?) > how to know what kinds of configurations it has and its value on DCS UI? > > > Key: TRAFODION-1561 > URL: https://issues.apache.org/jira/browse/TRAFODION-1561 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1561) How to know what kinds of configurations it has and its value on DCS UI?
[ https://issues.apache.org/jira/browse/TRAFODION-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu updated TRAFODION-1561: Summary: How to know what kinds of configurations it has and its value on DCS UI? (was: how to know what kinds of configurations it has and its value on DCS UI?) > How to know what kinds of configurations it has and its value on DCS UI? > > > Key: TRAFODION-1561 > URL: https://issues.apache.org/jira/browse/TRAFODION-1561 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1561) how to know what kinds of configurations it has and its value on DCS?
Kevin Xu created TRAFODION-1561: --- Summary: how to know what kinds of configurations it has and its value on DCS? Key: TRAFODION-1561 URL: https://issues.apache.org/jira/browse/TRAFODION-1561 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Reporter: Kevin Xu Fix For: 2.0-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1552) DCS start incorrectly while incorrect DNS specified in dcs-site.xml
Kevin Xu created TRAFODION-1552: --- Summary: DCS start incorrectly while incorrect DNS specified in dcs-site.xml Key: TRAFODION-1552 URL: https://issues.apache.org/jira/browse/TRAFODION-1552 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Affects Versions: 2.0-incubating Reporter: Kevin Xu Fix For: 2.0-incubating dcs.dns.interface in dcs-site.xml was specified with incorrect DNS interface, but it still can be started. At this time, it will run into weird issues if continue to use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1540) The host name link cannot be accessed on DCS UI home page while host name is not available
Kevin Xu created TRAFODION-1540: --- Summary: The host name link cannot be accessed on DCS UI home page while host name is not available Key: TRAFODION-1540 URL: https://issues.apache.org/jira/browse/TRAFODION-1540 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Reporter: Kevin Xu Fix For: 2.0-incubating Trafodion is on VM. I can open the link on host PC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1526) Incorrect messages for ResultSet cursor before the first row and after the last row
[ https://issues.apache.org/jira/browse/TRAFODION-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu closed TRAFODION-1526. --- Has been verified. Now the message has been separated into 2 messages(before first row and after last row) as JDBCT2. > Incorrect messages for ResultSet cursor before the first row and after the > last row > --- > > Key: TRAFODION-1526 > URL: https://issues.apache.org/jira/browse/TRAFODION-1526 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > > For TrafT4ResultSet: > Incorrect messages for ResultSet cursor before the first row and after the > last row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1525) Locale for JDBCT4 doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu closed TRAFODION-1525. --- Has been verified. It works fine. The only way to specify locale is from t4prop. > Locale for JDBCT4 doesn't work > -- > > Key: TRAFODION-1525 > URL: https://issues.apache.org/jira/browse/TRAFODION-1525 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > > When it has errors, it only show the name the error instead of content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1525) Locale for JDBCT4 doesn't work
[ https://issues.apache.org/jira/browse/TRAFODION-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1525. - Resolution: Fixed Match with the right locale properties file. Locale can only be specified in t4props. > Locale for JDBCT4 doesn't work > -- > > Key: TRAFODION-1525 > URL: https://issues.apache.org/jira/browse/TRAFODION-1525 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > > When it has errors, it only show the name the error instead of content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1526) Incorrect messages for ResultSet cursor before the first row and after the last row
[ https://issues.apache.org/jira/browse/TRAFODION-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Xu resolved TRAFODION-1526. - Resolution: Fixed It was passed incorrect parameters. Now make it correct. > Incorrect messages for ResultSet cursor before the first row and after the > last row > --- > > Key: TRAFODION-1526 > URL: https://issues.apache.org/jira/browse/TRAFODION-1526 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.0-incubating >Reporter: Kevin Xu > Fix For: 2.0-incubating > > > For TrafT4ResultSet: > Incorrect messages for ResultSet cursor before the first row and after the > last row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1526) Incorrect messages for ResultSet cursor before the first row and after the last row
Kevin Xu created TRAFODION-1526: --- Summary: Incorrect messages for ResultSet cursor before the first row and after the last row Key: TRAFODION-1526 URL: https://issues.apache.org/jira/browse/TRAFODION-1526 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.0-incubating Reporter: Kevin Xu Fix For: 2.0-incubating For TrafT4ResultSet: Incorrect messages for ResultSet cursor before the first row and after the last row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1525) Locale for JDBCT4 doesn't work
Kevin Xu created TRAFODION-1525: --- Summary: Locale for JDBCT4 doesn't work Key: TRAFODION-1525 URL: https://issues.apache.org/jira/browse/TRAFODION-1525 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.0-incubating Reporter: Kevin Xu Fix For: 2.0-incubating When it has errors, it only show the name the error instead of content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
