To my knowledge this is not deliberate, it's a bug :-) It looks like this particular case has been this way since at least 2014...
Have you found any other cases? -- Rob On 16 October 2017 at 11:22, Adel Boutros <[email protected]> wrote: > Hello, > > > While using the Qpid Java Broker, I have noticed that sometimes the causes > of the exceptions are silenced and thus I don't know why my broker failed. > I had to remote debug it to find out. > > I wanted to know if this was on purpose or not? > > > You can check for example: GenericJDBCMessageStore.java (line 107) > > > Exception shown > > -------------------------------------- > > Failed to create connection provider for connectionUrl: > jdbc:derby://localhost:10452/sample and username: user > > > Exception after remote debugging > > --------------------------------------- > > Unable to open a test connection to the given database. JDBC url = > jdbc:derby://localhost:10452/sample, username = user. Terminating > connection pool. Original Exception: ------ > java.sql.SQLNonTransientConnectionException: Password length (0) is > outside the range of 1 to 255. > at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown > Source) > at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) > at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source) > at java.sql.DriverManager.getConnection(DriverManager.java:664) > at java.sql.DriverManager.getConnection(DriverManager.java:247) > at com.jolbox.bonecp.BoneCP.obtainRawInternalConnection(BoneCP.java:256) > > > Regards, > > Adel >
