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 » BIP8019E after system restore

Post new topic  Reply to topic
 BIP8019E after system restore « View previous topic :: View next topic » 
Author Message
crossland
PostPosted: Mon Aug 09, 2010 7:03 am    Post subject: BIP8019E after system restore Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

My client is getting the following error after they performed a system restore:

BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.


The message is produced for the following commands:

mqsistop (any type),
mqsilist BROKER -e <execution group> and
mqsichangetrace.

After deleting and recreating the broker and configuration manager (this is WMB 6.1 on AIX), along with their queue managers, the error is still produced even after I created an execution group and deployed a flow onto it. The message flow is working fine; you can put messages onto the input queue and they go the output queue and the toolkit is showing the flow as running on the execution group.

There are no error messages in the log and the SYSTEM.BROKER.* queues are all empty.

Would be very grateful for any pointers!
Back to top
View user's profile Send private message
mqmatt
PostPosted: Mon Aug 09, 2010 9:05 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Do the services for the brokers and config managers still exist in the Services section of the Control Panel's Administrative Tools?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Aug 09, 2010 9:06 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mqmatt wrote:
Do the services for the brokers and config managers still exist in the Services section of the Control Panel's Administrative Tools?


...

On AIX?
Back to top
View user's profile Send private message
crossland
PostPosted: Mon Aug 09, 2010 11:55 am    Post subject: Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

Sorry, mqmatt, the broker and configuration manager are both on AIX.

From an AIX perspective, the bip* and Data* processes are all running. My text message flow can even handle messages arriving on its MQInput queue.
The toolkit shows the flow as running in the execution group.
It is just when I try to issue mqsi* commands that I hit this problem, with a userid that is in the mqbrkrs and mqm group.
Back to top
View user's profile Send private message
crossland
PostPosted: Mon Aug 09, 2010 9:30 pm    Post subject: Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

One thing that I have noticed is that issuing 'mqsilist BROKER' works fine, but issuing 'mqsilist BROKER -e execution_group' results in the following:


BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 10, 2010 2:49 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

A utility trace of mqsilist may provide some insight...
http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177043

And you're sure there's nothing in syslog?
Back to top
View user's profile Send private message
mqmatt
PostPosted: Tue Aug 10, 2010 3:32 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Apols, I saw "system restore" and immediately thought of Windows(!)

In V6.1, the difference between mqsilist and mqsilist -e is that mqsilist -e prods the DataFlowEngine for status, whereas mqsilist just uses the bipbroker process. (BTW it's completely different in V7 because mqsilist uses the CMP.)

To get to the bottom of why you're getting the error you are, I'd suggest raising a PMR.
Back to top
View user's profile Send private message
crossland
PostPosted: Tue Aug 10, 2010 4:10 am    Post subject: Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

mqjeff wrote:
A utility trace of mqsilist may provide some insight...
http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177043

And you're sure there's nothing in syslog?


Thanks for the pointer to the trace.

After reinstalling MQ and WMB on AIX, the error recurred and this is what the trace produced:

Timestamps are formatted in local time, 240 minutes past GMT.
Trace written by version 6101; formatter version 6101

2010-08-10 15:40:57.006908 1 { ImbPlatformSupport::getEnvironmentVariable , 'MQSI_UTILITY_TRACESIZE'
2010-08-10 15:40:57.006968 1 } ImbPlatformSupport::getEnvironmentVariable , ''
2010-08-10 15:40:57.006980 1 { mqsi::main , 'mqsilist'
2010-08-10 15:40:57.006992 1 mqsi::main 'current locale is' , 'en_US en_US en_US en_US en_US en_US'
2010-08-10 15:40:57.007008 1 { ImbCmdBase::processCommandString
2010-08-10 15:40:57.007032 1 { ImbCmdmqsilist::processCommand
2010-08-10 15:40:57.007072 1 { ImbCmdBase::validateComponentType
2010-08-10 15:40:57.007084 1 { ImbCmdLibUnix::testBrokerExistence , 'UBTBK1', 0
2010-08-10 15:40:57.007124 1 } ImbCmdLibUnix::testBrokerExistence , true
2010-08-10 15:40:57.007204 1 } ImbCmdBase::validateComponentType , 0
2010-08-10 15:40:57.007216 1 { ImbCmdLibUnix::isBrokerServiceRunning , 'UBTBK1', 0
2010-08-10 15:40:57.007236 1 { ImbCmdLibUnix::testBrokerExistence , 'UBTBK1', 0
2010-08-10 15:40:57.007268 1 } ImbCmdLibUnix::testBrokerExistence , true
2010-08-10 15:40:57.007284 1 { ImbProcessBase::ImbProcessBase
2010-08-10 15:40:57.007288 1 } ImbProcessBase::ImbProcessBase
2010-08-10 15:40:57.007296 1 { ImbProcessUnix::ImbProcessUnix
2010-08-10 15:40:57.007320 1 { ImbProcessUnix::terminateSignal
2010-08-10 15:40:57.007332 1 } ImbProcessUnix::terminateSignal
2010-08-10 15:40:57.007344 1 } ImbProcessUnix::ImbProcessUnix
2010-08-10 15:40:57.007364 1 { ImbProcess::FindProc
2010-08-10 15:40:57.017376 1 } ImbProcess::FindProc
2010-08-10 15:40:57.017404 1 { ImbProcessUnix::~ImbProcessUnix
2010-08-10 15:40:57.017412 1 } ImbProcessUnix::~ImbProcessUnix
2010-08-10 15:40:57.017420 1 } ImbCmdLibUnix::isBrokerServiceRunning , 19
2010-08-10 15:40:57.017436 1 } ImbCmdmqsilist::processCommand , 19
2010-08-10 15:40:57.017452 1 } ImbCmdBase::processCommandString , 19
2010-08-10 15:40:57.017460 1 { ImbCmdBase::outputMessage , 19
2010-08-10 15:40:57.017484 1 { ImbCmdMessageSet::getMessageInsertForRC , 19
2010-08-10 15:40:57.017492 1 } ImbCmdMessageSet::getMessageInsertForRC , false
2010-08-10 15:40:57.017500 1 { ImbCmdMessageSet::setMessageInsertsForRC , 19, 0
2010-08-10 15:40:57.017528 1 } ImbCmdMessageSet::setMessageInsertsForRC
2010-08-10 15:40:57.017536 1 } ImbCmdBase::outputMessage
2010-08-10 15:40:57.017548 1 { ImbCmdBase::outputStackedMessageDescriptions
2010-08-10 15:40:57.017556 1 { ImbPlatformSupportBase::ImbPlatformSupportBase , 'UBTBK1'
2010-08-10 15:40:57.017692 1 } ImbPlatformSupportBase::ImbPlatformSupportBase
2010-08-10 15:40:57.017704 1 { ImbCmdMessageSet::getNextMessage , 'H'
2010-08-10 15:40:57.017712 1 ImbCmdMessageSet::getNextMessage 'checking for a stack messages'
2010-08-10 15:40:57.017724 1 ImbCmdMessageSet::getNextMessage 'message ignored, incrementing iterator'
2010-08-10 15:40:57.017732 1 } ImbCmdMessageSet::getNextMessage , false
2010-08-10 15:40:57.017740 1 { ImbCmdMessageSet::getNextMessage
2010-08-10 15:40:57.017748 1 ImbCmdMessageSet::getNextMessage 'checking for a stack messages'
2010-08-10 15:40:57.017756 1 ImbCmdMessageSet::getNextMessage 'message ignored, incrementing iterator'
2010-08-10 15:40:57.017764 1 } ImbCmdMessageSet::getNextMessage , false
2010-08-10 15:40:57.017772 1 { ImbCmdMessageSet::getNextMessage , 'R'
2010-08-10 15:40:57.017780 1 ImbCmdMessageSet::getNextMessage 'checking for a stack messages'
2010-08-10 15:40:57.017792 1 } ImbCmdMessageSet::getNextMessage , true
2010-08-10 15:40:57.017820 1 { ImbCmdBase::getMessage
2010-08-10 15:40:57.017828 1 ImbCmdBase::getMessage 'Formatting message' , 8019
2010-08-10 15:40:57.017860 1 { ImbCmdLibUnix::getCatalogPath , ''
2010-08-10 15:40:57.017868 1 } ImbCmdLibUnix::getCatalogPath , ''
2010-08-10 15:40:57.017888 1 { ImbLanguage::getLanguage
2010-08-10 15:40:57.017904 1 } ImbLanguage::getLanguage , 'en'
2010-08-10 15:40:57.017912 1 { ImbLanguage::getCountry
2010-08-10 15:40:57.017916 1 } ImbLanguage::getCountry , 'US'
2010-08-10 15:40:57.017944 1 { ImbLanguage::getCatalogueCodePage
2010-08-10 15:40:57.017952 1 { ImbLanguage::getLanguage
2010-08-10 15:40:57.017960 1 } ImbLanguage::getLanguage , 'en'
2010-08-10 15:40:57.017976 1 } ImbLanguage::getCatalogueCodePage , 437
2010-08-10 15:40:57.018756 1 ImbCmdBase::getMessage 'retrieved message, data length is' , 165
2010-08-10 15:40:57.018768 1 } ImbCmdBase::getMessage , 'BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted. '
2010-08-10 15:40:57.018776 1 ImbCmdBase::outputStackedMessageDescriptions 'final message length' , 165
2010-08-10 15:40:57.018788 1 { ImbLanguage::contact admin
2010-08-10 15:40:57.018796 1 } ImbLanguage::contact admin , 'ISO-8859-1'
2010-08-10 15:40:57.018812 1 { ImbPlatformSupport::getEnvironmentVariable , 'MQSI_UTILITY_OUTPUT_CP'
2010-08-10 15:40:57.018824 1 } ImbPlatformSupport::getEnvironmentVariable , ''
2010-08-10 15:40:57.019308 1 ImbCmdBase::outputStackedMessageDescriptions 'locating the final return code message'
2010-08-10 15:40:57.019316 1 { ImbCmdMessageSet::getNextMessage , 'R'
2010-08-10 15:40:57.019324 1 } ImbCmdMessageSet::getNextMessage , false
2010-08-10 15:40:57.019336 1 } ImbCmdBase::outputStackedMessageDescriptions
2010-08-10 15:40:57.019392 1 { ImbReadWriteLockInterface::WriteLock::WriteLock , ffffffffffffc00, 0,
2010-08-10 15:40:57.019400 1 { ImbReadWriteLock::writeLock ,
2010-08-10 15:40:57.019408 1 } ImbReadWriteLock::writeLock , 0,
2010-08-10 15:40:57.019416 1 } ImbReadWriteLockInterface::WriteLock::WriteLock ,
2010-08-10 15:40:57.019432 1 { ImbReadWriteLockInterface::WriteLock::~WriteLock ,
2010-08-10 15:40:57.019440 1 { ImbReadWriteLock::writeUnlock ,
2010-08-10 15:40:57.019452 1 } ImbReadWriteLock::writeUnlock , 0,
2010-08-10 15:40:57.019460 1 } ImbReadWriteLockInterface::WriteLock::~WriteLock ,
2010-08-10 15:40:57.019468 1 { ImbReadWriteLock::~ImbReadWriteLock ,
2010-08-10 15:40:57.019476 1 } ImbReadWriteLock::~ImbReadWriteLock ,
2010-08-10 15:40:57.019488 1 { ImbReadWriteLockInterface::~ImbReadWriteLockInterface ,
2010-08-10 15:40:57.019496 1 } ImbReadWriteLockInterface::~ImbReadWriteLockInterface ,
2010-08-10 15:40:57.019508 1 { ImbThreadManager::~ImbThreadManager
2010-08-10 15:40:57.019516 1 } ImbThreadManager::~ImbThreadManager
2010-08-10 15:40:57.019524 1 { ImbReadWriteLock::~ImbReadWriteLock ,
2010-08-10 15:40:57.019532 1 } ImbReadWriteLock::~ImbReadWriteLock ,
2010-08-10 15:40:57.019540 1 { ImbReadWriteLockInterface::~ImbReadWriteLockInterface ,
2010-08-10 15:40:57.019548 1 } ImbReadWriteLockInterface::~ImbReadWriteLockInterface ,

Threads encountered in this trace:
1

As for the syslog, this is all that it contains (I had to define a new queue for my test app so there were a couple of errors about this before it was defined):


Aug 10 15:24:58 oupsmqs01 user:info WebSphere Broker v6101[50638]: (UBTCFGMGR)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6101; process ID 53850. : UBTCFGMGR.service: /build/S610_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Aug 10 15:25:09 oupsmqs01 user:info WebSphere Broker v6101[25830]: (UBTBK1)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6101; process ID 45314. : UBTBK1.service: /build/S610_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Aug 10 15:25:11 oupsmqs01 user:info WebSphere Broker v6101[53850]: (UBTCFGMGR)[1]BIP8255I: User Name Services are disabled. : UBTCFGMGR.agent: /build/S610_P/src/DataFlowEngine/ImbSecClient.cpp: 101: ImbSecClient::ImbSecClient: :
Aug 10 15:25:13 oupsmqs01 user:info WebSphere Broker v6101[53850]: (UBTCFGMGR)[1]BIP1003I: The Configuration Manager is available for use. : UBTCFGMGR.agent: /build/S610_P/src/Config/ImbConfigMgrAgent.cpp: 713: ImbConfigMgrAgent::employJavaConfigManager: :
Aug 10 15:35:44 oupsmqs01 user:info WebSphere Broker v6101[54064]: (UBTBK1.$SYS_mqsi)[1]BIP2208I: Execution Group (large) started: process '54064'; thread '1'; additional information: brokerName 'UBTBK1'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'UBTBK1XM'; trusted 'false'; dataSourceName 'UBTBK1DB'; userId 'wmbadmin'; migrationNeeded 'false'; brokerUUID '91cac85b-2a01-0000-0080-f27d9474c80d'; filePath '/opt/IBM/mqsi/6.1'; workPath '/var/mqsi'. : UBTBK1.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S610_P/src/DataFlowEngine/ImbMain.cpp: 435: ImbMain::start: :
Aug 10 15:36:30 oupsmqs01 user:info WebSphere Broker v6101[41904]: (UBTBK1.test)[1]BIP2201I: Execution Group started: process '41904'; thread '1'; additional information: brokerName 'UBTBK1'; executionGroupUUID '9e09c95b-2a01-0000-0080-f27d9474c80d'; executionGroupLabel 'test'; defaultExecutionGroup 'false'; queueManagerName 'UBTBK1XM'; trusted 'false'; dataSourceName 'UBTBK1DB'; userId 'wmbadmin'; migrationNeeded 'false'; brokerUUID '91cac85b-2a01-0000-0080-f27d9474c80d'; filePath '/opt/IBM/mqsi/6.1'; workPath '/var/mqsi'; ICU Converter Path ''. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/DataFlowEngine/ImbMain.cpp: 456: ImbMain::start: :
Aug 10 15:37:11 oupsmqs01 user:err|error WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP2623E: Unable to open queue 'TESTIN1' on WebSphere MQ queue manager 'UBTBK1XM': completion code 2; reason code 2085. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/DataFlowEngine/ImbMqManager.cpp: 611: ImbMqConnection::getQueue: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Aug 10 15:37:11 oupsmqs01 user:err|error WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP2604E: Node failed to open WebSphere MQ queue 'TESTIN1' owned by queue manager 'UBTBK1XM': completion code 2; reason code 2085. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp: 879: ImbMqInputNode::readData: ComIbmMQInputNode: Test1#FCMComposite_1_1
Aug 10 15:39:15 oupsmqs01 user:err|error WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP2628E: Exception condition detected on input node 'Test1.MQInput'. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1562: ImbCommonInputNode::run: ComIbmMQInputNode: Test1#FCMComposite_1_1
Aug 10 15:39:15 oupsmqs01 user:err|error WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP2230E: Error detected whilst processing a message in node 'Test1.HTTP Request'. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/WebServices/WSLibrary/ImbWSRequestNode.cpp: 914: ImbWSRequestNode::evaluate: ComIbmWSRequestNode: Test1#FCMComposite_1_4
Aug 10 15:39:15 oupsmqs01 user:info WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP3162S: An HTTP error occurred. The HTTP Request-Line was: 'POST /url HTTP/1.0^M: UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/WebServices/WSLibrary/ImbWSRequestNode.cpp: 828: ImbWSRequestNode::evaluate: :
Aug 10 15:39:15 oupsmqs01 user:info WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP3152S: Socket error detected whilst invoking Web service located at host 10.137.3.7, port 443, path /eOmaneServicesPortalTomCat/services/ViewFarm. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/WebServices/WSLibrary/ImbWSRequest.cpp: 556: ImbWSRequest::makeWSRequest: :
Aug 10 15:39:15 oupsmqs01 user:info WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP3165S: An error occurred whilst performing an SSL socket operation. Operation: connect. Error Text: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/WebServices/WSLibrary/ImbSocket.cpp: 2127: ImbSocketJNIManager::handleGeneralJavaException: :
Aug 10 15:39:16 oupsmqs01 user:err|error WebSphere Broker v6101[41904]: (UBTBK1.test)[6940]BIP2648E: Message backed out to a queue; node 'Test1.MQInput'. : UBTBK1.9e09c95b-2a01-0000-0080-f27d9474c80d: /build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp: 2043: ImbCommonInputNode::eligibleForBackout: ComIbmMQInputNode: Test1#FCMComposite_1_1
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 10, 2010 4:43 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You're pretty much in PMR country here...

Does ps show that the DFEs are running as root, perhaps?
Back to top
View user's profile Send private message
crossland
PostPosted: Tue Aug 10, 2010 5:01 am    Post subject: Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

mqjeff wrote:
You're pretty much in PMR country here...

Does ps show that the DFEs are running as root, perhaps?


The DFEs are running with the same wmb userid as the rest of WMB.

We have just upgraded to 6.1.0.8 and still get the same error.
Back to top
View user's profile Send private message
crossland
PostPosted: Tue Aug 17, 2010 1:16 am    Post subject: Reply with quote

Master

Joined: 26 Jun 2001
Posts: 248

mqjeff wrote:
You're pretty much in PMR country here...

Does ps show that the DFEs are running as root, perhaps?


The problem was fixed after a clean installation of AIX, MQ and WMB 6.1.0.8!
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 » BIP8019E after system restore
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.