|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Two Issues with Mb 6.1.0.4 in AIX Environment |
« View previous topic :: View next topic » |
Author |
Message
|
sankritya |
Posted: Tue Jul 06, 2010 8:50 am Post subject: Two Issues with Mb 6.1.0.4 in AIX Environment |
|
|
Centurion
Joined: 14 Feb 2008 Posts: 100
|
Hi All,
I am facing two issues in the deployment of Flows in the Broker installed in the AIX Environment. I am using JCN in the flow
1. If around 10 flows including 10 jar files are deployed in the EG and I try to deploy a new flow Broker returns error
BIP4502E: An unexpected error occurred during the deployment of a Java resource.
An error occurred during the deployment of a Java resource. This may have left the broker in an inconsistent state.
Ensure there is sufficient disk space available on the machine running the broker runtime. Stop the broker, delete all files in '/var/mqsi/components/BrokerName/EGUUID/config/JAR', restart the broker and perform a full redeploy.
2. When I am deleting the Jar files from the EG most of the times it is getting deleted. But sometimes the old jar files remains in the directory '/var/mqsi/components/BrokerName/EGUUID/config/JAR'. It is not deleted even when the Broker is restarted. It creates a problem for flow can execute the class files placed in the old jar if the pakage name for the classes are same. I generally use toolkit to delete the Jar Files. Old Jar files are not visible in the Broker administration view of the toolkit. |
|
Back to top |
|
 |
Gaya3 |
Posted: Tue Jul 06, 2010 10:56 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
whats the broker version, it looks like a bug. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 06, 2010 11:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
If the broker version is really 6.1.0.4 as stated in the subject, then you should try updating to 6.1.0.7 and see if that helps.
You should also look at the stderr file for the broker runtime, as for this particular error that file may contain more specific information about why the jar failed to deploy. |
|
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
|
|
|
|