db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laura Stewart (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1381) Document ij.exceptionTrace property
Date Tue, 27 Mar 2007 16:18:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484494
] 

Laura Stewart commented on DERBY-1381:
--------------------------------------

Help me understand the first line in the example. Specifically what does the 
flag -Dij do?  Or is the entire flag -Dij.exceptionTrace=true ?  and in Java is it called
a "flag"?

As I read the example, you specify that for ij, tracing is on
I'm not sure what the second line does... start if?
The third line you are in ij and connect to the database "wombat"
>From there the error is returned along with the full stack trace.

Pleaes provide any other info that would be good to include in the documentation.

> Document ij.exceptionTrace property
> -----------------------------------
>
>                 Key: DERBY-1381
>                 URL: https://issues.apache.org/jira/browse/DERBY-1381
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.1.2.1
>            Reporter: Kathey Marsden
>            Priority: Trivial
>
> The ij.exceptionTrace property can be used to show full stack traces with ij.
> It would be good to document it so users know how to print the full stack trace when
reporting issues and to help developers debug issues reported in ij.
> Below is an example:
> $ java -Dij.exceptionTrace=true org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:wombat';
> ERROR XJ004: Database 'wombat' not found.
> SQL Exception: Database 'wombat' not found.
>         at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:44)
>         at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:87)
>         at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:93)
>         at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:172)
>         at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(EmbedConnection.java:1955)
>         at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:254)
>         at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(EmbedConnection30.java:72)
>         at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Driver30.java:73)
>         at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:200)
>         at java.sql.DriverManager.getConnection(DriverManager.java:512)
>         at java.sql.DriverManager.getConnection(DriverManager.java:140)
>         at org.apache.derby.impl.tools.ij.ij.dynamicConnection(ij.java:873)
>         at org.apache.derby.impl.tools.ij.ij.ConnectStatement(ij.java:723)
>         at org.apache.derby.impl.tools.ij.ij.ijStatement(ij.java:553)
>         at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:289)
>         at org.apache.derby.impl.tools.ij.Main.go(Main.java:207)
>         at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:173)
>         at org.apache.derby.impl.tools.ij.Main14.main(Main14.java:55)
>         at org.apache.derby.tools.ij.main(ij.java:60)
> ij

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message