| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2057 Execution Group <insert_1> could not be starte |
« View previous topic :: View next topic » |
| Author |
Message
|
| esbdeveloper |
 Posted: Sun Oct 01, 2017 1:39 pm Post subject: BIP2057 Execution Group <insert_1> could not be starte |
 |
|
Newbie
Joined: 01 Oct 2017
Posts: 6
|
Hi,
We have Websphere Message Broker v8.0.0.3 on Redhat Linux env, and we encounterd the following runtime error message:
BIP2057
Execution Group <insert_1> could not be started: broker name <insert_2>; UUID <insert_3>; label <insert_4>; Pub-Sub server <insert_5> (1=Yes, 0=No).
The situation is that one of the execution groups stopped (without any trace/log about it) and the wmb could not auto start with the BIP2057 error.
the weird part occurs when another EG restarted (unlinked reason to the first problem, because of some applicative errors) and then the first EG "took its place", started successfully, and now the second EG could not start for the same reason.
We have checked for user permissions or the logs without any success in identifying the problem.
Any help would be much appreciated.
Thanks! |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Oct 01, 2017 4:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could it be that they both share the same port? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| esbdeveloper |
| Posted: Sun Oct 01, 2017 7:49 pm Post subject: |
|
|
Newbie
Joined: 01 Oct 2017
Posts: 6
|
| fjb_saper wrote: |
| Could it be that they both share the same port? |
Nope, the EGs created long time ago and the ports weren't changed |
|
| Back to top |
|
|
| esbdeveloper |
| Posted: Sat Mar 10, 2018 2:41 am Post subject: The problem still occurres in IIB 10.0.0.6 ! |
|
|
Newbie
Joined: 01 Oct 2017
Posts: 6
|
Hi,
I have upgraded the WMB to the IIB 10.0.0.6 version,
but the problem of Integration server <insert_1> could not be started: integration node name <insert_2>; UUID <insert_3>; label <insert_4>.
came back.
Also, I have noticed that before this error occures, there is an error of
"Cannot allocate memory"
The server has lots of RAM (even more than before), enough FS for the IIB's directories and seems to have all permissions it needs.
any ideas?  |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Mon Mar 12, 2018 1:19 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
| Quote: |
| Cannot allocate memory |
hi...as the error suggests for some reason the iib application user id is not able to allocate more memory. Even though the server may have enough RAM the application user id might be limited to use it.
Try checking the user limits (ulimit -a) and also worth running the 'mqconfig' (<MQ installed path>/bin/mqconfig) which should show the minimum memory settings required (even though it is for MQ it should give an idea for iib as well) |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
