You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Adel Boutros <Ad...@live.com> on 2017/10/16 09:22:05 UTC
[Qpid Java Broker 6.1.4] Some expections are hidden
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
Re: [Qpid Java Broker 6.1.4] Some expections are hidden
Posted by Adel Boutros <Ad...@live.com>.
Sorry Keith but I didn't have enough time to create the Jira or provide a fix :(
________________________________
From: Keith W <ke...@gmail.com>
Sent: Wednesday, October 18, 2017 7:02:40 PM
To: users@qpid.apache.org
Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden
I raised this as QPID-7979.
On 16 October 2017 at 12:34, Keith W <ke...@gmail.com> wrote:
> Hi Adel
>
> Please raise a JIRA. Include a patch or pull request if you like.
> I'll try to include in v7.0.
>
> cheers Keith
>
> On 16 October 2017 at 12:06, Adel Boutros <Ad...@live.com> wrote:
>> No, this was the only case I hit while testing my use case.
>>
>>
>> Regards,
>>
>> ADel
>>
>> ________________________________
>> From: Rob Godfrey <ro...@gmail.com>
>> Sent: Monday, October 16, 2017 12:07:56 PM
>> To: users@qpid.apache.org
>> Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden
>>
>> 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 <Ad...@live.com> 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
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [Qpid Java Broker 6.1.4] Some expections are hidden
Posted by Keith W <ke...@gmail.com>.
I raised this as QPID-7979.
On 16 October 2017 at 12:34, Keith W <ke...@gmail.com> wrote:
> Hi Adel
>
> Please raise a JIRA. Include a patch or pull request if you like.
> I'll try to include in v7.0.
>
> cheers Keith
>
> On 16 October 2017 at 12:06, Adel Boutros <Ad...@live.com> wrote:
>> No, this was the only case I hit while testing my use case.
>>
>>
>> Regards,
>>
>> ADel
>>
>> ________________________________
>> From: Rob Godfrey <ro...@gmail.com>
>> Sent: Monday, October 16, 2017 12:07:56 PM
>> To: users@qpid.apache.org
>> Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden
>>
>> 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 <Ad...@live.com> 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
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [Qpid Java Broker 6.1.4] Some expections are hidden
Posted by Keith W <ke...@gmail.com>.
Hi Adel
Please raise a JIRA. Include a patch or pull request if you like.
I'll try to include in v7.0.
cheers Keith
On 16 October 2017 at 12:06, Adel Boutros <Ad...@live.com> wrote:
> No, this was the only case I hit while testing my use case.
>
>
> Regards,
>
> ADel
>
> ________________________________
> From: Rob Godfrey <ro...@gmail.com>
> Sent: Monday, October 16, 2017 12:07:56 PM
> To: users@qpid.apache.org
> Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden
>
> 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 <Ad...@live.com> 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
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [Qpid Java Broker 6.1.4] Some expections are hidden
Posted by Adel Boutros <Ad...@live.com>.
No, this was the only case I hit while testing my use case.
Regards,
ADel
________________________________
From: Rob Godfrey <ro...@gmail.com>
Sent: Monday, October 16, 2017 12:07:56 PM
To: users@qpid.apache.org
Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden
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 <Ad...@live.com> 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
>
Re: [Qpid Java Broker 6.1.4] Some expections are hidden
Posted by Rob Godfrey <ro...@gmail.com>.
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 <Ad...@live.com> 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
>