You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org> on 2012/02/17 19:51:59 UTC
[jira] [Updated] (DERBY-5220) Output from
org.apache.derby.drda.NetworkServerControl runtimeinfo are truncated if the
amount of data exceeds some threshold
[ https://issues.apache.org/jira/browse/DERBY-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5220:
----------------------------------
Urgency: Low
Labels: derby_triage10_9 (was: )
Soren Vejrup Carlsen, can you verify this problem is fixed with 10.8.2.2 which has the fix for DERBY-5326?
Knut mentioned that fix may correct this problem.
Also triage for 10.9. Mark low for now. Awaiting fix verification.
> Output from org.apache.derby.drda.NetworkServerControl runtimeinfo are truncated if the amount of data exceeds some threshold
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5220
> URL: https://issues.apache.org/jira/browse/DERBY-5220
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.3.0
> Environment: java -Xmx1536m -cp /home/test/CSRTEST7/lib/db/derbynet.jar:/home/test/CSRTEST7/lib/db/derby.jar org.apache.derby.drda.NetworkServerControl sysinfo -p 8128
> --------- Derby Network Server Information --------
> Version: CSS10050/10.5.3.0 - (802917) Build: 802917 DRDA Product Id: CSS10050
> -- listing properties --
> derby.drda.maxThreads=0
> derby.drda.sslMode=off
> derby.drda.keepAlive=true
> derby.drda.minThreads=0
> derby.drda.portNumber=8128
> derby.drda.logConnections=false
> derby.drda.timeSlice=0
> derby.drda.startNetworkServer=false
> derby.drda.host=localhost
> derby.drda.traceAll=false
> ------------------ Java Information ------------------
> Java Version: 1.6.0_21
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/java/jdk1.6.0_21/jre
> Java classpath: /home/test/CSRTEST7/lib/db/derbynet.jar:/home/test/CSRTEST7/lib/db/derby.jar
> OS name: Linux
> OS architecture: i386
> OS version: 2.6.18-53.el5PAE
> Java user name: test
> Java user home: /home/test
> Java user dir: /home/test/CSRTEST7
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.6
> --------- Derby Information --------
> JRE - JDBC: Java SE 6 - JDBC 4.0
> [/home/test/CSRTEST7/lib/db/derby.jar] 10.5.3.0 - (802917)
> [/home/test/CSRTEST7/lib/db/derbynet.jar] 10.5.3.0 - (802917)
> ------------------------------------------------------
> ----------------- Locale Information -----------------
> ------------------------------------------------------
> Reporter: Soren Vejrup Carlsen
> Labels: derby_triage10_9
>
> When using the runtimeinfo command with the org.apache.derby.drda.NetworkServerControl program
> It seems that the output is truncated, as if the output exceeeds some threshold or met some internal timeout, so that it does not wait for the rest of the data.
> In that case, the output starts with
> {code}
> -- Derby Network Server Runtime Information ---
> ---------- Session Information ---------------
> Session # :1
> Database :harvestDatabase/fullhddb
> User :APP
> # Statements:12
> {code}
> but does not end with something like
> {code}
> -------------------------------------------------------------
> # Connection Threads : 3
> # Active Sessions : 3
> # Waiting Sessions : 0
> Total Memory : 64356352 Free Memory : 62239544
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira