Details
-
Improvement
-
Status: Closed
-
Trivial
-
Resolution: Fixed
-
10.1.2.1
-
None
Description
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
Attachments
Attachments
Issue Links
- is duplicated by
-
DERBY-1778 Document ij.exceptionTrace=true property in tools guide.
- Closed