Wednesday, November 3, 2010

Unable to start queue manager :An internal WebSphere MQ error has occurred on queue manager

If u r not able to connnect to ur Queue Manager in MQ Explorer, then I have a soln for it or if the queuemanger doesnt start after log in.

Try this out.

In Control Panel --> Administrative Tools --> Component Services --> Console Root --> Component Services --> Computers --> My Computer --> DCOM Config --> IBM MQ Series

Right Click that and select properties. In that u have Identity Tab, in that it there will be a question "Which user account do you want to use to run this application?" In that currently it will be selected as This user. Instead select The launching user and give apply and Ok. Then log off and log in and again retry ur process.

WMB password change Issues

Below is the solution to fix broker password change.

1. Fix DB2 services – The easiest way to do this is switch to services view in Windows and spot the services that are failing to start. Next right click these services and from the context menu select properties. Select the Log On tab and change the password used for these services. Please note that some services use the local system account while others use a selected account and it is these services which use a selected account that fail. (I don’t know why services use a different approach as of now so if you know I would appreciate if you can tell me)
2. Next you need to fix the service password for your configuration manager. For this you need to issue amqsichangeconfigmgr -a . Start your configuration manager by issuing a mqsistart command following this.
3. The last piece you need to fix is your broker instance. For this you need to fix both service password and data source password. Issue a mqsichangebroker -a -p . Start your broker instance by issuing a mqsistart command.

Thursday, June 17, 2010

RAD publishing problem and corba errors

I was deploying an application in rad 7 and was 6.1 server. I received below mentioned error. It took lot of time to figure some changed virtualHostName entry
in ibm-web-bnd.xmi to some random name from default_host. This should always be default_host.

Error:
Publish failed with errors, warnings or both. Please see server logs for more details.
Application Failed to Start. xxxxEAR
CORBA MARSHAL 0x4942f89a No; nested exception is:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Mismatched serialization UIDs : Source (RepId RMI:java.lang.Throwable:F8678B4F4D2EB705:D5C635273977B8CB) = D5C635273977B8CB whereas Target (RepId RMI:com.ibm.ws.webcontainer.exception.WebAppNotLoadedException:2E921E9DEB124A7F:2D33383134313233) = 2D33383134313233 vmcid: IBM minor code: 89A completed: No
CORBA MARSHAL 0x4942f89a No; nested exception is:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Mismatched serialization UIDs : Source (RepId RMI:java.lang.Throwable:F8678B4F4D2EB705:D5C635273977B8CB) = D5C635273977B8CB whereas Target (RepId RMI:com.ibm.ws.webcontainer.exception.WebAppNotLoadedException:2E921E9DEB124A7F:2D33383134313233) = 2D33383134313233 vmcid: IBM minor code: 89A completed: No
Please see server logs for more details.

Wednesday, June 16, 2010

less no of database connections and Multithreading

We have a Multithreaded application that is 10 year old. It worked fine for all those years suddenly it was too slow. The reason was while threads are created database connections are fully used and threads had wait on each other for the resource. The database configurations are defined in application for data source. It had max connections of 3 and min of 1. we changed the maximum connections to 30. it worked like a charm.

The type oracle.jdbc.driver.OracleTypes is not visible

I was working on migrating a project from WAS 5 to WAS 7. I experienced an issue with oracletypes class . The issue was type oracle.jdbc.driver.OracleTypes is not visible .
After doing hours of research looks like the WAS 7 uses oracle 11g driver. In ojdbc14.jar the visibility of OracleTypes is public the visibility of the OracleTypes class in ojdbc6.jar is changed to default so you can use it. We had to change to oracle.jdbc.OracleTypes from oracle.jdbc.driver.OracleTypes to make the application work.

Monday, April 26, 2010

JSF and Error Messages

I was working on JSF and I tried to display an error message. It never worked. The reason is
I was using redirect tag in faces-config.xml. Please dont use the redirect tag (< redirect/>) in faces-config.xml the error messages are request scope. So these messages will be lost when you do a redirect.

ORA-12154: TNS:could not resolve the connect identifier specified and windows 64 bit machines

I Installed oracle 10.2.0.1 on my windows xp 64 bit machine. I was able to log on on to Sql plus.The problem was Toad was not able to connect and websphere message broker too. I received ORA-12154: TNS:could not resolve the connect identifier when i tried to connect from Toad or WMB tool kit. After 2 days of research I found that there is a bug in oracle client on 64 bit machines because on 64 bit machines oracle installs in to program files x86 folder part of apllication . To resolve this issue download patch from oracle but this will require metalink.oracle.com access (the simplest way is to ask the DBA generally they have access to oracle support). I applied oracle 10.20.0.4 patch (patch no: p6810189_10204_Win32) and now it is working fine. Happy coding.