[activecluster-user] ActiveCluster 1.1 and SonicMQ

[ben.kibler]

I'm trying to use ActiveCluster 1.1 with SonicMQ 6.1, with no success.  The
following error occurs at startup:

7389 [Timer-0] ERROR impl.StateServiceStub  - Could not send JMS message:
javax.jms.MessageFormatException: progress.message.jimpl.Connection
javax.jms.MessageFormatException: progress.message.jimpl.Connection
      at progress.message.jimpl.ObjectMessage.setObject(Unknown Source)
      at progress.message.jimpl.Session.createObjectMessage(Unknown Source)
      at org.activecluster.impl.StateServiceStub.keepAlive(
StateServiceStub.java:54)
      at org.activecluster.impl.ReplicatedLocalNode.pingRemoteNodes(
ReplicatedLocalNode.java:49)
      at org.activecluster.impl.DefaultCluster$1.run(DefaultCluster.java:74
)
      at org.activecluster.impl.StateServiceImpl.checkForTimeouts(
StateServiceImpl.java:150)
      at org.activecluster.impl.StateServiceImpl$1.run(
StateServiceImpl.java:165)
      at java.util.TimerThread.mainLoop(Unknown Source)
      at java.util.TimerThread.run(Unknown Source)

I'm fairly sure the problem is due to the fact that SonicMQ JMS objects
don't implement Serializable, while ActiveMQ JMS objects do.  The
ActiveCluster NodeImpl class assumes it can be serialized via
Session.createObjectMessage(), but contains a member variable with a
Destination object, implemented by the JMS provider.

Has anyone ever tried to use this with Sonic MQ before?

Thanks,
Ben

---------------------------------------------
ben.kibler@...
[phone]



This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

[rajdavies]

Hi Ben,

the latest in CVS head of ActiveCluster has changed to use Strings in  
the serialized nodes instead of jms Destinations.
I haven't tried it with SonicMQ - so I don't know if it will fix  
everything - but fingers crossed :)

cheers,

Rob
On 9 Nov 2005, at 17:03, ben.kibler@... wrote:

>
> I'm trying to use ActiveCluster 1.1 with SonicMQ 6.1, with no  
> success.  The
> following error occurs at startup:
>
> 7389 [Timer-0] ERROR impl.StateServiceStub  - Could not send JMS  
> message:
> javax.jms.MessageFormatException: progress.message.jimpl.Connection
> javax.jms.MessageFormatException: progress.message.jimpl.Connection
>       at progress.message.jimpl.ObjectMessage.setObject(Unknown  
> Source)
>       at progress.message.jimpl.Session.createObjectMessage(Unknown  
> Source)
>       at org.activecluster.impl.StateServiceStub.keepAlive(
> StateServiceStub.java:54)
>       at org.activecluster.impl.ReplicatedLocalNode.pingRemoteNodes(
> ReplicatedLocalNode.java:49)
>       at org.activecluster.impl.DefaultCluster$1.run
> (DefaultCluster.java:74
> )
>       at org.activecluster.impl.StateServiceImpl.checkForTimeouts(
> StateServiceImpl.java:150)
>       at org.activecluster.impl.StateServiceImpl$1.run(
> StateServiceImpl.java:165)
>       at java.util.TimerThread.mainLoop(Unknown Source)
>       at java.util.TimerThread.run(Unknown Source)
>
> I'm fairly sure the problem is due to the fact that SonicMQ JMS  
> objects
> don't implement Serializable, while ActiveMQ JMS objects do.  The
> ActiveCluster NodeImpl class assumes it can be serialized via
> Session.createObjectMessage(), but contains a member variable with a
> Destination object, implemented by the JMS provider.
>
> Has anyone ever tried to use this with Sonic MQ before?
>
> Thanks,
> Ben
>
> ---------------------------------------------
> ben.kibler@...
> [phone]
>
>
>
> This communication is for informational purposes only. It is not  
> intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All  
> market prices,
> data and other information are not warranted as to completeness or  
> accuracy and
> are subject to change without notice. Any comments or statements  
> made herein
> do not necessarily reflect those of JPMorgan Chase & Co., its  
> subsidiaries
> and affiliates.
>

[ben.kibler]

Thanks Rob,

I made the same change (switching to String) locally, and that resolves the
serialization problems with SonicMQ 6.1.

Regards,
Ben



|---------+---------------------------->
|         |           Rob Davies       |
|         |           <rajdavies@gmail.|
|         |           com>             |
|         |                            |
|         |           11/15/2005 12:51 |
|         |           PM               |
|         |           Please respond to|
|         |           user             |
|         |                            |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       user@...                                                                              |
  |       cc:                                                                                                                    |
  |       Subject:  Re: [activecluster-user] ActiveCluster 1.1 and SonicMQ                                                       |
  >------------------------------------------------------------------------------------------------------------------------------|




Hi Ben,

the latest in CVS head of ActiveCluster has changed to use Strings in
the serialized nodes instead of jms Destinations.
I haven't tried it with SonicMQ - so I don't know if it will fix
everything - but fingers crossed :)

cheers,

Rob
On 9 Nov 2005, at 17:03, ben.kibler@... wrote:

>
> I'm trying to use ActiveCluster 1.1 with SonicMQ 6.1, with no
> success.  The
> following error occurs at startup:
>
> 7389 [Timer-0] ERROR impl.StateServiceStub  - Could not send JMS
> message:
> javax.jms.MessageFormatException: progress.message.jimpl.Connection
> javax.jms.MessageFormatException: progress.message.jimpl.Connection
>       at progress.message.jimpl.ObjectMessage.setObject(Unknown
> Source)
>       at progress.message.jimpl.Session.createObjectMessage(Unknown
> Source)
>       at org.activecluster.impl.StateServiceStub.keepAlive(
> StateServiceStub.java:54)
>       at org.activecluster.impl.ReplicatedLocalNode.pingRemoteNodes(
> ReplicatedLocalNode.java:49)
>       at org.activecluster.impl.DefaultCluster$1.run
> (DefaultCluster.java:74
> )
>       at org.activecluster.impl.StateServiceImpl.checkForTimeouts(
> StateServiceImpl.java:150)
>       at org.activecluster.impl.StateServiceImpl$1.run(
> StateServiceImpl.java:165)
>       at java.util.TimerThread.mainLoop(Unknown Source)
>       at java.util.TimerThread.run(Unknown Source)
>
> I'm fairly sure the problem is due to the fact that SonicMQ JMS
> objects
> don't implement Serializable, while ActiveMQ JMS objects do.  The
> ActiveCluster NodeImpl class assumes it can be serialized via
> Session.createObjectMessage(), but contains a member variable with a
> Destination object, implemented by the JMS provider.
>
> Has anyone ever tried to use this with Sonic MQ before?
>
> Thanks,
> Ben
>
> ---------------------------------------------
> ben.kibler@...
> [phone]
>
>
>
> This communication is for informational purposes only. It is not
> intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All
> market prices,
> data and other information are not warranted as to completeness or
> accuracy and
> are subject to change without notice. Any comments or statements
> made herein
> do not necessarily reflect those of JPMorgan Chase & Co., its
> subsidiaries
> and affiliates.
>

This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates