[jira] [Commented] (AMQNET-440) IObjectMessage.ToObject is not working

[ https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730292#comment-13730292 ] Claudio Corsi commented on AMQNET-440: -- The reason that your code is not working is t

[jira] [Commented] (AMQ-3785) ActiveMQSslConnectionFactory does not detect ssl request in failover URIs when creating transports

[ https://issues.apache.org/jira/browse/AMQ-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534029#comment-13534029 ] Claudio Corsi commented on AMQ-3785: I have created a new issue, AMQ-4227, to track the

[jira] [Commented] (AMQ-3785) ActiveMQSslConnectionFactory does not detect ssl request in failover URIs when creating transports

[ https://issues.apache.org/jira/browse/AMQ-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534029#comment-13534029 ] Claudio Corsi commented on AMQ-3785: I have created a new issue, AMQ-4227, to track the

[jira] [Created] (AMQ-4227) ActiveMQSslConnectionFactory does not allow for regular files to be found unless a valid URL is provided or is located on the classpath

Claudio Corsi created AMQ-4227: -- Summary: ActiveMQSslConnectionFactory does not allow for regular files to be found unless a valid URL is provided or is located on the classpath Key: AMQ-4227 URL: https://issues.apac

[jira] [Updated] (AMQ-4227) ActiveMQSslConnectionFactory does not allow for regular files to be found unless a valid URL is provided or is located on the classpath

[ https://issues.apache.org/jira/browse/AMQ-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-4227: --- Attachment: server.keystore client.keystore ssltruststore.patch This pa

[jira] [Created] (AMQ-4227) ActiveMQSslConnectionFactory does not allow for regular files to be found unless a valid URL is provided or is located on the classpath

Claudio Corsi created AMQ-4227: -- Summary: ActiveMQSslConnectionFactory does not allow for regular files to be found unless a valid URL is provided or is located on the classpath Key: AMQ-4227 URL: https://issues.apac

[jira] [Updated] (AMQ-3785) ActiveMQSslConnectionFactory does not detect ssl request in failover URIs when creating transports

[ https://issues.apache.org/jira/browse/AMQ-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3785: --- Attachment: server.keystore client.keystore ssltruststore.patch This pa

[jira] [Commented] (AMQ-4051) IOException: Could not locate data file .\db-10.log

[ https://issues.apache.org/jira/browse/AMQ-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477154#comment-13477154 ] Claudio Corsi commented on AMQ-4051: Hi Edwin, I was looking at the configuration file

[jira] [Updated] (AMQ-3980) Websocket transport: support increasing the max size of websocket messages

[ https://issues.apache.org/jira/browse/AMQ-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3980: --- Attachment: websocket.diffs This updated patch also includes a fix that allows you to set the different

[jira] [Updated] (AMQ-3980) Websocket transport: support increasing the max size of websocket messages

[ https://issues.apache.org/jira/browse/AMQ-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3980: --- Attachment: websocket.diffs This patch will allow you to set any init parameters that you need to set o

[jira] [Commented] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430390#comment-13430390 ] Claudio Corsi commented on AMQ-3451: @Sergey The issue is more fundamental than your pa

[jira] [Commented] (AMQ-3891) Durable subscribers receiving duplicate messages

[ https://issues.apache.org/jira/browse/AMQ-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398753#comment-13398753 ] Claudio Corsi commented on AMQ-3891: Can you include the client uri that you used and al

[jira] [Comment Edited] (AMQ-3669) Pending producer with qMirror, messages are not spooled to disk

[ https://issues.apache.org/jira/browse/AMQ-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279666#comment-13279666 ] Claudio Corsi edited comment on AMQ-3669 at 5/20/12 5:22 AM: - Th

[jira] [Updated] (AMQ-3669) Pending producer with qMirror, messages are not spooled to disk

[ https://issues.apache.org/jira/browse/AMQ-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3669: --- Attachment: mirroredqueue.diffs This patch contains a test and the fix to this issue.

[jira] [Commented] (AMQ-3669) Pending producer with qMirror, messages are not spooled to disk

[ https://issues.apache.org/jira/browse/AMQ-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279665#comment-13279665 ] Claudio Corsi commented on AMQ-3669: I was able to determine what the problem was with t

[jira] [Commented] (AMQ-3822) The current sslContext element does not provide the ability to define the keystore key password key.

[ https://issues.apache.org/jira/browse/AMQ-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268392#comment-13268392 ] Claudio Corsi commented on AMQ-3822: Tim, I did not mention it in the original comment

[jira] [Updated] (AMQ-3827) The SslContext definition is not used by the https transport protocol.

[ https://issues.apache.org/jira/browse/AMQ-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3827: --- Attachment: activemq-https.xml Here is the missing configuration file that I missed.

[jira] [Updated] (AMQ-3827) The SslContext definition is not used by the https transport protocol.

[ https://issues.apache.org/jira/browse/AMQ-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3827: --- Attachment: https.diffs This patch contains the fix that allows a user to use the SslContext instance

[jira] [Created] (AMQ-3827) The SslContext definition is not used by the https transport protocol.

Claudio Corsi created AMQ-3827: -- Summary: The SslContext definition is not used by the https transport protocol. Key: AMQ-3827 URL: https://issues.apache.org/jira/browse/AMQ-3827 Project: ActiveMQ

[jira] [Updated] (AMQ-3822) The current sslContext element does not provide the ability to define the keystore key password key.

[ https://issues.apache.org/jira/browse/AMQ-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated AMQ-3822: --- Attachment: client.ts keystore.ks sslcontext.diffs This is the patch th

[jira] [Created] (AMQ-3822) The current sslContext element does not provide the ability to define the keystore key password key.

Claudio Corsi created AMQ-3822: -- Summary: The current sslContext element does not provide the ability to define the keystore key password key. Key: AMQ-3822 URL: https://issues.apache.org/jira/browse/AMQ-3822

[jira] [Issue Comment Edited] (AMQ-3506) Access to ConnectionPool.createSession needs to be synchronized

[ https://issues.apache.org/jira/browse/AMQ-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108855#comment-13108855 ] Claudio Corsi edited comment on AMQ-3506 at 9/20/11 5:49 PM: - We

[jira] [Issue Comment Edited] (AMQ-3506) Access to ConnectionPool.createSession needs to be synchronized

[ https://issues.apache.org/jira/browse/AMQ-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108855#comment-13108855 ] Claudio Corsi edited comment on AMQ-3506 at 9/20/11 5:48 PM: - We

[jira] [Commented] (AMQ-3506) Access to ConnectionPool.createSession needs to be synchronized

[ https://issues.apache.org/jira/browse/AMQ-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108855#comment-13108855 ] Claudio Corsi commented on AMQ-3506: We might consider redefining the cache field from M

[jira] [Commented] (AMQ-3487) Topic message rollback memory leak (XA transaction)

[ https://issues.apache.org/jira/browse/AMQ-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103626#comment-13103626 ] Claudio Corsi commented on AMQ-3487: Thomas, can you re-run the leak and generate two or

[jira] [Commented] (AMQ-3254) Can't use updateURIsURL, because the entry is missing in the xsd and so the activeMq instance cannot start

[ https://issues.apache.org/jira/browse/AMQ-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015463#comment-13015463 ] Claudio Corsi commented on AMQ-3254: Just do the following: This should work. > Can

[jira] [Commented] (AMQ-3254) Can't use updateURIsURL, because the entry is missing in the xsd and so the activeMq instance cannot start

[ https://issues.apache.org/jira/browse/AMQ-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014113#comment-13014113 ] Claudio Corsi commented on AMQ-3254: How do you set this value for the transport connect

[jira] [Commented] (AMQ-2496) journaledJDBC not creating ACTIVEMQ_MSGS with MS SQL 2008

[ https://issues.apache.org/jira/browse/AMQ-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010241#comment-13010241 ] Claudio Corsi commented on AMQ-2496: Gary, unfortunately I cannot verify this because I

[jira] [Commented] (AMQ-2496) journaledJDBC not creating ACTIVEMQ_MSGS with MS SQL 2008

[ https://issues.apache.org/jira/browse/AMQ-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010161#comment-13010161 ] Claudio Corsi commented on AMQ-2496: Gary, The microsoft driver name is com.microsoft.s