utPLSQL/utPLSQL-cli

Caught Oracle stuck during creation of Runner-Statement

PriyankaKeer opened this issue · 3 comments

PriyankaKeer commented

Hi Team,

Getting below error while executing utPLSQL jenkins job

Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/workspace/UTPLSQL_UNITTEST_JOB
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] Done
[UTPLSQL_UNITTEST_JOB] $ /bin/sh -xe /var/lib/jenkins/tmp/jenkins5184682729131058305.sh

  • whoami
    appadmin

  • sudo ls -l /var/lib/jenkins
    lrwxrwxrwx. 1 appadmin appadmin 25 Nov 25 2016 /var/lib/jenkins -> /utxciserver/app/jenkins/

  • DB_URL=utpuser/utpuser@//Host:Port/DB

  • utplsql_path=/utxciserver/UTPLSQL-CLI/utPLSQL-cli/bin

  • sudo /utxciserver/UTPLSQL-CLI/utPLSQL-cli/bin/utplsql run -d utpuser/utpuser@//Host:Port/DB -p=utpuser.CALCULATE_PKG_TEST -include=apps.CALCULATE_PKG -f=ut_documentation_reporter -o=run.log -s
    2021-04-29 14:38:33 [main] INFO org.utplsql.cli.RunAction - ############# utPLSQL cli ##############

    utPLSQL-cli 3.1.8-SNAPSHOT.local
    utPLSQL-java-api 3.1.8.546
    Java-Version: 1.8.0_262
    ORACLE_HOME: null
    NLS_LANG: null

    Thanks for testing!

2021-04-29 14:38:33 [main] INFO org.utplsql.cli.RunAction -
2021-04-29 14:38:33 [main] INFO o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:/@//Host:Port/DB
2021-04-29 14:38:34 [main] INFO org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.10.3349
2021-04-29 14:38:34 [main] INFO org.utplsql.cli.RunAction - Oracle-Version: 12.1.0.2.0
2021-04-29 14:38:53 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: C119D80BBA20C478E0530100007F1CA1
2021-04-29 14:38:53 [pool-1-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - Running tests now.
2021-04-29 14:38:53 [pool-1-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2021-04-29 14:38:53 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - TestRunner initialized
2021-04-29 14:38:53 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - Running on utPLSQL v3.1.10.3349
2021-04-29 14:38:53 [pool-1-thread-1] INFO org.utplsql.api.TestRunner - Initializing reporters
2021-04-29 14:38:55 [pool-1-thread-1] ERROR org.utplsql.api.TestRunner - Detected Oracle driver stuck during Statement initialization
2021-04-29 14:38:55 [main] WARN org.utplsql.cli.RunAction - WARNING: Caught Oracle stuck during creation of Runner-Statement. Retrying (1)
2021-04-29 14:38:55 [main] INFO org.utplsql.cli.RunAction - ############# utPLSQL cli ##############

utPLSQL-cli 3.1.8-SNAPSHOT.local
utPLSQL-java-api 3.1.8.546
Java-Version: 1.8.0_262
ORACLE_HOME: null
NLS_LANG: null

Thanks for testing!

2021-04-29 14:38:55 [main] INFO org.utplsql.cli.RunAction -
2021-04-29 14:38:55 [main] INFO o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:/@//Host:Port/DB
2021-04-29 14:38:55 [main] INFO org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.10.3349
2021-04-29 14:38:55 [main] INFO org.utplsql.cli.RunAction - Oracle-Version: 12.1.0.2.0
2021-04-29 14:38:57 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: C119D856BBFEC4AEE0530100007F5117
2021-04-29 14:38:57 [pool-4-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - Running tests now.
2021-04-29 14:38:57 [pool-4-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2021-04-29 14:38:57 [pool-4-thread-1] INFO org.utplsql.api.TestRunner - TestRunner initialized
2021-04-29 14:38:57 [pool-4-thread-1] INFO org.utplsql.api.TestRunner - Running on utPLSQL v3.1.10.3349
2021-04-29 14:38:57 [pool-4-thread-1] INFO org.utplsql.api.TestRunner - Initializing reporters
2021-04-29 14:38:59 [pool-4-thread-1] ERROR org.utplsql.api.TestRunner - Detected Oracle driver stuck during Statement initialization
2021-04-29 14:38:59 [main] WARN org.utplsql.cli.RunAction - WARNING: Caught Oracle stuck during creation of Runner-Statement. Retrying (2)
2021-04-29 14:38:59 [main] INFO org.utplsql.cli.RunAction - ############# utPLSQL cli ##############

utPLSQL-cli 3.1.8-SNAPSHOT.local
utPLSQL-java-api 3.1.8.546
Java-Version: 1.8.0_262
ORACLE_HOME: null
NLS_LANG: null

Thanks for testing!

2021-04-29 14:38:59 [main] INFO org.utplsql.cli.RunAction -
2021-04-29 14:38:59 [main] INFO o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:/@//Host:Port/DB
2021-04-29 14:38:59 [main] INFO org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.10.3349
2021-04-29 14:38:59 [main] INFO org.utplsql.cli.RunAction - Oracle-Version: 12.1.0.2.0
2021-04-29 14:39:02 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: C119D89CC658C4C6E0530100007F91A0
2021-04-29 14:39:02 [pool-7-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - Running tests now.
2021-04-29 14:39:02 [pool-7-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2021-04-29 14:39:02 [pool-7-thread-1] INFO org.utplsql.api.TestRunner - TestRunner initialized
2021-04-29 14:39:02 [pool-7-thread-1] INFO org.utplsql.api.TestRunner - Running on utPLSQL v3.1.10.3349
2021-04-29 14:39:02 [pool-7-thread-1] INFO org.utplsql.api.TestRunner - Initializing reporters
2021-04-29 14:39:04 [pool-7-thread-1] ERROR org.utplsql.api.TestRunner - Detected Oracle driver stuck during Statement initialization
2021-04-29 14:39:04 [main] WARN org.utplsql.cli.RunAction - WARNING: Caught Oracle stuck during creation of Runner-Statement. Retrying (3)
2021-04-29 14:39:04 [main] INFO org.utplsql.cli.RunAction - ############# utPLSQL cli ##############

utPLSQL-cli 3.1.8-SNAPSHOT.local
utPLSQL-java-api 3.1.8.546
Java-Version: 1.8.0_262
ORACLE_HOME: null
NLS_LANG: null

Thanks for testing!

2021-04-29 14:39:04 [main] INFO org.utplsql.cli.RunAction -
2021-04-29 14:39:04 [main] INFO o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:/@//Host:Port/DB
2021-04-29 14:39:04 [main] INFO org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.10.3349
2021-04-29 14:39:04 [main] INFO org.utplsql.cli.RunAction - Oracle-Version: 12.1.0.2.0
2021-04-29 14:39:07 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: C119D8E58353C50DE0530100007F2472
2021-04-29 14:39:07 [pool-10-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - Running tests now.
2021-04-29 14:39:07 [pool-10-thread-1] INFO org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2021-04-29 14:39:07 [pool-10-thread-1] INFO org.utplsql.api.TestRunner - TestRunner initialized
2021-04-29 14:39:07 [pool-10-thread-1] INFO org.utplsql.api.TestRunner - Running on utPLSQL v3.1.10.3349
2021-04-29 14:39:07 [pool-10-thread-1] INFO org.utplsql.api.TestRunner - Initializing reporters
2021-04-29 14:39:09 [pool-10-thread-1] ERROR org.utplsql.api.TestRunner - Detected Oracle driver stuck during Statement initialization
2021-04-29 14:39:09 [main] WARN org.utplsql.cli.RunAction - WARNING: Caught Oracle stuck during creation of Runner-Statement. Retrying (4)
Build step 'Execute shell' marked build as failure
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
Finished: FAILURE

Kindly help on this issue as this need to be resolved on priority.

Thanks in Advance

PriyankaKeer commented

Hi @PhilippSalvisberg

Can you please look into this issue.
We need to integrate the tests in CICD and facing this issue

Any help would be appreciated!
Thanks in Advance!

PhilippSalvisberg commented

Hi @PriyankaKeer,

Unfortunately I can't. First, I didn't contribute a single line to the CLI and second, even if I did, I have no idea how to reproduce the faulty behavior that you describe. The chances of getting help without a reproducible test case are slim.

Since this is a high priority for you, I suggest debugging the CLI yourself. A PR that fixes this issue is greatly appreciated.

Please keep in mind that the work on the utPLSQL framework is done by volunteers in their spare time.

Thanks.

PriyankaKeer commented

Hi @PriyankaKeer,

Unfortunately I can't. First, I didn't contribute a single line to the CLI and second, even if I did, I have no idea how to reproduce the faulty behavior that you describe. The chances of getting help without a reproducible test case are slim.

Since this is a high priority for you, I suggest debugging the CLI yourself. A PR that fixes this issue is greatly appreciated.

Please keep in mind that the work on the utPLSQL framework is done by volunteers in their spare time.

Thanks.

Hi @PhilippSalvisberg

Thanks for the response!
Found your replies to a similar issue and thought that you are one of the contributor to utPLSQL- cli.

Thanks.