java报错信息大全_WEB项目之JAVA资源报错信息

该楼层疑似违规已被系统折叠 隐藏此楼查看此楼

The user to connect as The password to use when connecting The name of the class that the driver should use for creating socket connections to the server. This class must implement the interface 'com.mysql.jdbc.SocketFactory' and have public no-args constructor. Timeout for socket connect (in milliseconds), with 0 being no timeout. Only works on JDK-1.4 or newer. Defaults to '0'. Timeout on network socket operations (0, the default means no timeout). Load the comma-delimited list of configuration properties before parsing the URL or applying user-specified properties. These configurations are explained in the 'Configurations' of the documentation. Set the CLIENT_INTERACTIVE flag, which tells MySQL to timeout connections based on INTERACTIVE_TIMEOUT instead of WAIT_TIMEOUT An implementation of com.mysql.jdbc.ConnectionPropertiesTransform that the driver will use to modify URL properties passed to the driver before attempting a connection Use zlib compression when communicating with the server (true/false)? Defaults to 'false'. Should the driver try to re-establish bad connections? Use a reconnection strategy appropriate for connection pools (defaults to 'false') When failing over in autoReconnect mode, should the connection be set to 'read-only'? Maximum number of reconnects to attempt if autoReconnect is true, default is '3'. If autoReconnect is enabled, the initial time to wait between re-connect attempts (in seconds, defaults to '2'). Number of queries to issue before falling back to master when failed over (when using multi-host failover). Whichever condition is met first, 'queriesBeforeRetryMaster' or 'secondsBeforeRetryMaster' will cause an attempt to be made to reconnect to the master. Defaults to 50. How long should the driver wait, when failed over, before attempting to reconnect to the master server? Whichever condition is met first, 'queriesBeforeRetryMaster' or 'secondsBeforeRetryMaster' will cause an attempt to be made to reconnect to the master. Time in seconds, defaults to 30 Allow the use of ';' to delimit multiple queries during one statement (true/false, defaults to 'false' Use SSL when communicating with the server (true/false), defaults to 'false' Require SSL connection if useSSL=true? (defaults to 'false'). Should the driver allow URLs in 'LOAD DATA LOCAL INFILE' statements? Take measures to prevent exposure sensitive information in error messages and clear data structures holding sensitive data when possible? (defaults to 'false') The number of queries to cacheResultSetMetadata for if cacheResultSetMetaData is set to 'true' (default 50) If prepared statement caching is enabled, how many prepared statements should be cached? If prepared statement caching is enabled, what's the largest SQL the driver will cache the parsing for? Should the driver always communicate with the database when Connection.setTransactionIsolation() is called? If set to false, the driver will only communicate with the database when the requested transaction isolation is different than the whichever is newer, the last value that was set via Connection.setTransactionIsolation(), or the value that was read from the server when the connection was established. Should the driver cache the parsing stage of CallableStatements Should the driver cache the parsing stage of PreparedStatements? Should the driver cache ResultSetMetaData for Statements and PreparedStatements? (Req. JDK-1.4+, true/false, default 'false') Should the driver cache the results of 'SHOW VARIABLES' and 'SHOW COLLATION' on a per-URL basis? The JDBC specification requires the driver to automatically track and close resources, however if your application doesn't do a good job of explicitly calling close() on statements or result sets, this can cause memory leakage. Setting this property to true relaxes this constraint, and can be more memory efficient for some applications. Should the driver retrieve the default calendar when required, or cache it per connection/session? If using MySQL-4.1 or newer, should the driver only issue 'set autocommit=n' queries when the server's state doesn't match the requested state by Connection.setAutoCommit(boolean)? Should the driver close result sets on Statement.close() as required by the JDBC specification? Use internal String->Integer conversion routines to avoid excessive object creation? Should the driver refer to the internal values of autocommit and transaction isolation that are set by Connection.setAutoCommit() and Connection.setTransactionIsolation(), rather than querying the database? Should the driver use the java.nio.* interfaces for network communication (true/false), defaults to 'false' Use newer, optimized non-blocking, buffered input stream when reading from the server? The name of a class that implements 'com.mysql.jdbc.log.Log' that will be used to log messages to.(default is 'com.mysql.jdbc.log.StandardLogger', which logs to STDERR) Trace queries and their execution/fetch times to the configured logger (true/false) defaults to 'false' Deprecated, use 'profileSQL' instead. Trace queries and their execution/fetch times on STDERR (true/false) defaults to 'false' Controls the maximum length/size of a query that will get logged when profiling or tracing The maximum number of packets to retain when 'enablePacketDebug' is true If 'logSlowQueries' is enabled, how long should a query (in ms) before it is logged as 'slow'? Should the driver issue 'usage' warnings advising proper and efficient usage of JDBC and MySQL Connector/J to the log (true/false, defaults to 'false')? Should the driver dump the contents of the query sent to the server in the message for SQLExceptions? When enabled, a ring-buffer of 'packetDebugBufferSize' packets will be kept, and dumped when exceptions are thrown in key areas in the driver's code If 'logSlowQueries' is enabled, should the driver automatically issue an 'EXPLAIN' on the server and send the results to the configured log at a WARN level? Should queries that take longer than 'slowQueryThresholdMillis' be logged? Should trace-level network protocol be logged? Should the driver use Unicode character encodings when handling strings? Should only be used when the driver can't determine the character set mapping, or you are trying to 'force' the driver to use a character set that MySQL either doesn't natively support (such as UTF-8), true/false, defaults to 'true' If 'useUnicode' is set to true, what character encoding should the driver use when dealing with strings? (defaults is to 'autodetect') Character set to tell the server to return results as. If set, tells the server to use this collation via 'set connection_collation' Should the driver allow NaN or +/- INF values in PreparedStatement.setDouble()? Should the driver automatically detect and de-serialize objects stored in BLOB fields? Capitalize type names in DatabaseMetaData? (usually only useful when using WebObjects, true/false, defaults to 'false') This will cause a 'streaming' ResultSet to be automatically closed, and any oustanding data still streaming from the server to be discarded if another query is executed before all the data has been read from the server. Should the driver continue processing batch commands if one statement fails. The JDBC spec allows either way (defaults to 'true'). N/A Should the driver detect prepared statements that are not supported by the server, and replace them with client-side emulated versions? Ignore non-transactional table warning for rollback? (defaults to 'false'). Should the driver throw java.sql.DataTruncation exceptions when data is truncated as is required by the JDBC specification when connected to a server that supports warnings(MySQL 4.1.0 and newer)? The maximum number of rows to return (0, the default means return all rows). Don't ensure that ResultSet.getDatetimeType().toString().equals(ResultSet.getString()) Follow the JDBC spec to the letter. If the version of MySQL the driver connects to does not support transactions, still allow calls to commit(), rollback() and setAutoCommit() (true/false, defaults to 'false')? Should the driver issue a rollback() when the logical connection in a pool is closed? Enables workarounds for bugs in Sun's JDBC compliance testsuite version 1.3 Override detection/mapping of timezone. Used when timezone from server doesn't map to Java timezone Used only in older versions of compliance test Should the driver do strict checking (all primary keys selected) of updatable result sets (true, false, defaults to 'true')? Should the driver treat the datatype TINYINT(1) as the BIT type (because the server silently converts BIT -> TINYINT(1) when creating tables)? Create PreparedStatements for prepareCall() when required, because UltraDev is broken and issues a prepareCall() for _all_ statements? (true/false, defaults to 'false') Add '@hostname' to users in DatabaseMetaData.getColumn/TablePrivileges() (true/false), defaults to 'true'. Use the UTF-8 behavior the driver did when communicating with 4.0 and older servers Don't prepend 'standard' SQLState error messages to error messages returned by the server. Use server-side prepared statements if the server supports them? (defaults to 'true'). Use SQL Standard state codes instead of 'legacy' X/Open/SQL state codes (true/false), default is 'true' Honor stream length parameter in PreparedStatement/ResultSet.setXXXStream() method calls (true/false, defaults to 'true')? Convert time/date types between client and server timezones (true/false, defaults to 'false')? Don't use BufferedInputStream for reading data from the server What should happen when the driver encounters DATETIME values that are composed entirely of zeroes (used by MySQL to represent invalid dates)? Valid values are 'exception', 'round' and 'convertToNull'.