ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issue with the Group Reload

Post new topic  Reply to topic
 Issue with the Group Reload « View previous topic :: View next topic » 
Author Message
hotrock026
PostPosted: Thu Sep 04, 2014 5:29 am    Post subject: Issue with the Group Reload Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Can anyone help me with the below error

When ever i reload an group iam getting the below error and finally it forces us to restart the broker...

4 16:17:34 web1test WebSphere Broker v7003[12096]: (SAMPLEBROKER)[69]BIP2057E: Execution Group Group02 could not be started: broker name SAMPLEBROKER; UUID f1968407-3601-0000-0080-c01b505fa157; label Group02; Pub-Sub server {4} (1=Yes, 0=No). : SAMPLEBROKER.agent: /build/S700_P/src/AdminAgent/ImbAdminAgent.cpp: 4988: ImbAdminAgent::startAndMonitorADataFlowEngine: :
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Sep 04, 2014 5:39 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

What's deployed to that execution group?

Have you considered moving from v7.0.0.3 to a more fixed version?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Thu Sep 04, 2014 5:55 am    Post subject: Issue with the Group Reload Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi vitor,

thanks for ur reply, we are using 7.0.0.3 vers, only normal flows have been deployed this issue we are getting recently, before it was working fine...

Only one flow is deployed in the group...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Sep 04, 2014 6:08 am    Post subject: Re: Issue with the Group Reload Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
before it was working fine...


So the question is - before what? What changed? New version of the single flow? Maintenance of the OS? What?

This is also interesting:

hotrock026 wrote:
When ever i reload an group


What prompts you to reload the execution group? You shouldn't need to unless you're changing something, and something that's outside the scope of a deploy.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Thu Sep 04, 2014 7:09 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

HI Vitor,

Their was an change in the flow , so i had changed in the mapping level and re deployed the flow , and it got deployed succesfully , we have some properties which are in the Cachea which i have changed one of the property and to update the new value i have reloaded the group , then the group trows the below error...


before means before deploying the latest change


One more important ino:

In the development environment we are using the Ver 7.0.07

where we are facing this issue only in the UAT environment..

this broker hold 50 groups ....
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Sep 04, 2014 7:16 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
we have some properties which are in the Cachea which i have changed one of the property


What cache? v7 doesn't have a cache built in so what's this?

before means before deploying the latest change


hotrock026 wrote:
One more important ino:

In the development environment we are using the Ver 7.0.07

where we are facing this issue only in the UAT environment..


And as I said:

Vitor wrote:
Have you considered moving from v7.0.0.3 to a more fixed version?


So clearly you should certainly consider it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Sat Sep 06, 2014 10:34 pm    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi vitor,

their are some properties whcih we are keeping it in the database and those values we are maintaing in the cachea level...instead of hiting every time database ,

Could you please breif the issue....
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Sep 08, 2014 5:07 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
their are some properties whcih we are keeping it in the database and those values we are maintaing in the cachea level...instead of hiting every time database


It's a cheap solution to just reload the execution group. It's easy enough to make the code which loads the cache detect that the database contents have changed.

hotrock026 wrote:
Could you please breif the issue....


Once again, if this works in your development environment using WMBv7.0.0.7 and not with v7.0.0.3 then you need to upgrade. You shouldn't still be using v7.0.0.3 irrespective of this issue.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hotrock026
PostPosted: Tue Sep 09, 2014 1:55 am    Post subject: Reply with quote

Apprentice

Joined: 23 Feb 2014
Posts: 38

Hi vitor,

Even our code supports to handle the cache properties for every 12 hours...

if we need an imediate changes then their is no other way only reloading the group....


Thanks for that ..

but in the development we doesnt have 45 groups but in the test environment we have 45 groups...
_________________
Think Better & Think Smart then others
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Sep 09, 2014 4:41 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

hotrock026 wrote:
if we need an imediate changes then their is no other way only reloading the group....


Rubbish. If your code can handle reloading the cache every 12 hours it can handle reloading the cache on demand.

hotrock026 wrote:
but in the development we doesnt have 45 groups but in the test environment we have 45 groups...


a) So what?
b) If you think that invalidates my assertion you should upgrade, why do you think that?
c) That's a good reason to have your code reload the cache rather than issue 45 mqsireload commands.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issue with the Group Reload
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.