| Author |
Message
|
| rmah |
 Posted: Tue Mar 04, 2008 2:05 pm Post subject: Configuration manager damaged |
 |
|
Centurion
Joined: 04 May 2007
Posts: 142
|
Hi all,
I'm getting this error I've never seen before when trying to communicate with the config mgr via command line:
-bash-3.00$ mqsilistaclentry mqconfig_01
Skipped Compiling {java/util/Hashtable}{rehash}
Skipped Compiling {java/util/Hashtable}{rehash}
BIP1047E: The operation could not be completed by the Configuration Manager.
The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: 'hasBeenUpdatedByConfigManager timed out'
Ensure that the Configuration Manager is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.
BIP8071I: Successful command completion.
Same errror when I increase the timeout period via -w flag. The Toolkit gives me this error:
BIP1162S: Unprocessable registration request received by the Configuration Manager.
A request was received by the Configuration Manager to register for updates to the resource */ConfigManagerProxy/ , but an exception was thrown while processing this request (com.ibm.broker.config.ConfigManagerLoggedException: handleSQLException).
Restart the connection to the Configuration Manager and retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request and contact your IBM support center.
Any thoughts?
THanks!!!!
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 04, 2008 2:07 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Restart the ConfigMgr...
It seems that "the internal ConfigMgr data repository" (we do not use the word 'derby') may be unavailable for some reason.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Mar 04, 2008 2:08 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| jefflowrey wrote: |
Restart the ConfigMgr...
It seems that "the internal ConfigMgr data repository" (we do not use the word 'derby') may be unavailable for some reason. |
I've bounced the configuration manager many times with no avail.
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 04, 2008 2:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is the ConfigMgr responding to a Toolkit?
Is the ConfigMgr throwing errors in the system log?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Mar 04, 2008 2:28 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| jefflowrey wrote: |
Is the ConfigMgr responding to a Toolkit?
Is the ConfigMgr throwing errors in the system log? |
Config manager not responding to connection request from Toolkit.
There are no errors in /var/log/messages. No new FDC's in /var/mqm/errors. AMQERR01.LOG shows no information to help either...
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 04, 2008 3:24 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So configmgr is running on unix, and is logging in /var/log/messages that a) it has successfully started, b) that it's ready to receive communications?
Is ConfigMgr using the same qmgr as Broker?
Has anything changed with filesystems or networks or etc. since the last time it worked?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqexplorer |
| Posted: Tue Mar 04, 2008 3:29 pm Post subject: |
|
|
Novice
Joined: 02 Aug 2007
Posts: 17
|
| jefflowrey wrote: |
So configmgr is running on unix, and is logging in /var/log/messages that a) it has successfully started, b) that it's ready to receive communications?
|
Correct
| Quote: |
Is ConfigMgr using the same qmgr as Broker?
|
No, it has its own qmanager.
| Quote: |
Has anything changed with filesystems or networks or etc. since the last time it worked? |
Dont believe so...one of the testers might have changed something but he claims not to have. I enabled the trace and have sent the trace files to ibm. |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Mar 04, 2008 4:35 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| jefflowrey wrote: |
So configmgr is running on unix, and is logging in /var/log/messages that a) it has successfully started, b) that it's ready to receive communications?
Is ConfigMgr using the same qmgr as Broker?
Has anything changed with filesystems or networks or etc. since the last time it worked? |
A tester started the config manager as the wrong user, thus causing the db.lck file to be owned by the wrong user.
We've changed the ownership and it works! 
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 04, 2008 4:37 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| rmah wrote: |
| A tester started the config manager as the wrong user, thus causing the db.lck file to be owned by the wrong user. |
Bad tester. No cookie for them!
| rmah wrote: |
| We've changed the ownership and it works! |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
