Comments on: WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs http://blog.danzrobok.com/2008/07/23/websphere-application-server-non-deterministic-error-when-configuring-default-messaging-activation-specs/ Business Integration and SOA with an IBM WebSphere slant Sat, 10 Jan 2009 00:22:05 +0000 http://wordpress.org/?v=2.6.3 By: dan http://blog.danzrobok.com/2008/07/23/websphere-application-server-non-deterministic-error-when-configuring-default-messaging-activation-specs/#comment-611 dan Sun, 27 Jul 2008 19:01:33 +0000 http://blog.danzrobok.com/2008/07/23/websphere-application-server-non-deterministic-error-when-configuring-default-messaging-activation-specs/#comment-611 Hi David, I think the problem came because I created my activation specs before I created my queue definitions. I believe the bus gets automatically populated based on the queue definitions (or maybe it's a default, I'm unsure). What I do know is that I normally don't specify the value and when I come back to look at it, it's populated. Something must be fixing it for me in the background.. Hi David,

I think the problem came because I created my activation specs before I created my queue definitions. I believe the bus gets automatically populated based on the queue definitions (or maybe it’s a default, I’m unsure). What I do know is that I normally don’t specify the value and when I come back to look at it, it’s populated. Something must be fixing it for me in the background..

]]> By: David Currie http://blog.danzrobok.com/2008/07/23/websphere-application-server-non-deterministic-error-when-configuring-default-messaging-activation-specs/#comment-610 David Currie Sun, 27 Jul 2008 18:33:29 +0000 http://blog.danzrobok.com/2008/07/23/websphere-application-server-non-deterministic-error-when-configuring-default-messaging-activation-specs/#comment-610 FYI: None of the activation spec properties were originally meant to be required in the UI as they can all be specified via the activation-config properties in the MDB's deployment descriptor if desired. I'm not quite sure how the admin team decided that some should and shouldn't be in the end. FYI: None of the activation spec properties were originally meant to be required in the UI as they can all be specified via the activation-config properties in the MDB’s deployment descriptor if desired. I’m not quite sure how the admin team decided that some should and shouldn’t be in the end.

]]>