This section contains a list of commonly occurring problems by category and some troubleshooting tips for each item.
This list is not an all-inclusive list of problems. These steps are not guaranteed to solve your problems. If you attempted these steps and the problem persists, capture the WebSphere® Application Server logs, traces, and Data Transformation logs and contact your IBM® representative for further assistance.
The installation of WebSphere Premises Server on Linux® fails. The installation fails if the installation script was not run from a shell window. Try running the installation script again, making sure to run the command from a shell window.
During the installation of WebSphere Premises Server on Windows® 2003, the installation might not be able to find the WebSphere Application Server installation directory. See the topic about starting the installation in the Microsoft® Windows Server TechCenter.
change /user install
If you are installing on a Windows operating system, and you see exceptions in IBM_RFID_HOME\logs\install.log file similar to the following, then there is a path character limitation on the operating system:
com.ibm.websphere.management.exception.ConfigServiceException com.ibm.ws.sm.workspace.WorkSpaceException java.io.IOException: java.io.IOException: The URI length is greater than the Windows limit of 259 characters.
To resolve this issue, use a shorter profile name when you install WebSphere Premises Server, or use a shorter WebSphere Application Server installation path.
If you have installed WebSphere Premises Server silently, and you see a message similar to the following example, you can safely ignore it.
2008-01-28 16:56:49, , exception: java.lang.NullPointerException java.lang.NullPointerException at com.ibm.jsdt.rxa.RxaRemoteAccessSelector.populateRxaCredentials(RxaRemoteAccessSelector.java:184) at com.ibm.jsdt.main.InstallDriver.pushIia(InstallDriver.java:88) at com.ibm.jsdt.main.AbstractInstallDriver.runInstalls(AbstractInstallDriver.java:179) at com.ibm.jsdt.main.AbstractInstallDriver.installGroup(AbstractInstallDriver.java:108) at com.ibm.jsdt.task.InstallTask.execute(InstallTask.java:448) at com.ibm.jsdt.task.JsdtTask.launch(JsdtTask.java:151) at com.ibm.jsdt.task.TaskManager.launchTheseTasks(TaskManager.java:205) at com.ibm.jsdt.factory.task.TaskWorker.launchTasks(TaskWorker.java:86) at com.ibm.jsdt.factory.task.TaskWorker.doWork(TaskWorker.java:72) at com.ibm.jsdt.factory.base.Factory.startWorkers(Factory.java:224) at com.ibm.jsdt.factory.task.TaskFactory.generate(TaskFactory.java:59) at com.ibm.jsdt.factory.base.Builder.parseURI(Builder.java:192) at com.ibm.jsdt.task.TaskManager.createTasks(TaskManager.java:138) at com.ibm.jsdt.main.MainManager.createTasks(MainManager.java:856) at com.ibm.jsdt.main.MainManager.<init>(MainManager.java:328) at com.ibm.jsdt.main.MainManager.main(MainManager.java:447)
If you use the installation wizard to install DB2® for Linux, UNIX®, and Windows, you could see an "Microsoft Visual C++ ..." window that appears as a blue or gray bar on the server desktop. You can ignore this window. Restarting the DB2 server will remove this window.
Perform the following actions to try and resolve the problem:
Use the following actions to try and resolve the problem:
If the connection between the tag reader and the edge controller is interrupted due to power failure or network outage, the edge controller might not immediately connect to the tag reader. If the edge controller does not reconnect to the tag reader within the specified reconnection time out, use the following two steps.
If you are unable to configure the device adapter with WebSphere Premises Server, update the core bundle list copy it to the bundle repository.
Check to see if the maximum queue depth has been reached. See Checking the depth of WebSphere MQ queues.
If you are using a Linux operating system and you have uninstalled WebSphere Premises Server, but the WebSphere MQ queue managers, IBM.RFID.QM and IBM.DC.QM, have not been deleted, you need to check your group membership and delete the queue managers manually.
AMQ7077: You are not authorized to perform the requested operation.
This error message indicates that the terminal session root user running the uninstallation program has not inherited the mqm group; therefore, the MQ commands in the uninstallation program, endmgm and dltmqm do not work. The terminal session root user must be a member of the mqm group to delete the queue managers.
To find out if this is the cause of the problem, use the id -a command to see if the current terminal session root user is a member of the mqm group and make any necessary changes.
Then, use the following commands to stop and delete the queue managers:
/opt/mqm/bin/endmqm -i IBM.RFID.QM /opt/mqm/bin/dltmqm IBM.RFID.QM /opt/mqm/bin/endmqm -i IBM.DC.QM /opt/mqm/bin/dltmqm IBM.DC.QM
See J2CA0294W: Deprecated usage of direct JNDI lookup of resource for details.
If you use the default encryption method on SUSE LINUX 9.3, the WebSphere Premises Server Administrative Console may accept passwords that are eight characters or shorter in length.
To resolve this issue, change the password encryption from DES to MD5:
If you have installed WebSphere Premises Server remotely, you may see an error about the WAS_HOME environment variable not being applicable when you try to run the dts.bat file, even though it appears that the environment variable has been set correctly.
This problem can occur if you have logged into the target server before starting the remote installation of WebSphere Premises Server.
To resolve this issue, log out of the target server you used for your remote deployment (the server where you installed WebSphere Premises Server). Then log back in to the server and try running the dts.bat file again.
The WebSphere Application Server SystemOut.log file shows informational log messages for ALE that are incorrectly labeled as error messages. These messages are not error messages.
java.lang.NullPointerException at org.eclipse.osgi.framework.internal.core.BundleHost.getLoaderProxy(BundleHost.java:534) at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:526) at org.eclipse.osgi.framework.internal.core.ExportedPackageImpl.getImportingBundles (ExportedPackageImpl.java:56) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleDependencyManager.register ImportedPackageDependency(BundleDependencyManager.java:470) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleDependencyManager.register ImportedPackageDependencies(BundleDependencyManager.java:445) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleDependencyManager.handleBundle Installed(BundleDependencyManager.java:293) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleDependencyManager.populateDependency Tracker(BundleDependencyManager.java:360) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleDependencyManager.handleManager Started(BundleDependencyManager.java:324) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleManager.startup (BundleManager.java:366) at org.eclipse.soda.sat.core.internal.framework.bundle.Activator.startupBundleDependencyManager (Activator.java:310) at org.eclipse.soda.sat.core.internal.framework.bundle.Activator.addExportedBundleDependencyService (Activator.java:93) at org.eclipse.soda.sat.core.internal.framework.bundle.Activator.activate (Activator.java:85 at org.eclipse.soda.sat.core.framework.BaseBundleActivator$1.activate (BaseBundleActivator.java:280 at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.activate (BundleActivationManager.java:150) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.performActivation (BundleActivationManager.java:1262) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.access$0 (BundleActivationManager.java:1248) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager$1.acquired (BundleActivationManager.java:391) at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.serviceAcquired (ImportServiceRecordContainer.java:470) at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.access$0 (ImportServiceRecordContainer.java:458) at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$4.serviceAcquired (ImportServiceRecordContainer.java:282) at org.eclipse.soda.sat.core.internal.record.ImportServiceRecord.acquire (ImportServiceRecord.java:115) at org.eclipse.soda.sat.core.internal.record.ImportServiceRecord.acquire (ImportServiceRecord.java:124) at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$1.execute (ImportServiceRecordContainer.java:58) at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForService (ServiceRecordContainer.java:353) at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach (ServiceRecordContainer.java:321) at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.acquire (ImportServiceRecordContainer.java:237) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportedServices (BundleActivationManager.java:125) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.startSync (BundleActivationManager.java:1663) at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.start (BundleActivationManager.java:1632) at org.eclipse.soda.sat.core.framework.BaseBundleActivator.start (BaseBundleActivator.java:1073) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run (BundleContextImpl.java:991) at java.security.AccessController.doPrivileged(AccessController.java:220) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator (BundleContextImpl.java:985) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start (BundleContextImpl.java:966) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:317) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start (AbstractBundle.java:256) at com.ibm.rfid.bundle.loader.BundleLoader.startBundles(Unknown Source) at com.ibm.rfid.bundle.loader.BundleLoader.loadBundles(Unknown Source) at com.ibm.rfid.bundle.loader.Activator.doStart(Unknown Source) at com.ibm.rfid.bundle.loader.Activator$2.run(Unknown Source) at java.lang.Thread.run(Thread.java:719) Exception when starting bundle: org.eclipse.soda.sat.core org.osgi.framework.BundleException: Exception in org.eclipse.soda.sat.core.internal.framework.bundle.Activator.start() of bundle org.eclipse.soda.sat.core.
To prevent this problem from occurring, set the following property to false in the config.ini file on your system: -Dorg.eclipse.soda.sat.core.bds.status=false.
Setting this property disables the SAT BundleDependencyManager and prevents SAT from collecting dependency data. The SAT BundleDependencyManager is used by tooling for development and debugging. Disabling it does not impact normal production systems.
If you need the SAT BundleDependencyManager for debugging or development, you can turn this option on again. If this problem reoccurs, restart the system since the problem only occurs approximately one out of 50 times OSGi starts.
If you see this error, it may appear similar to the following example:
[11/19/07 11:15:08:703 CST] 0000001d ApplicationMg A WSVR0200I: Starting application: IBM_Premises_Server_BIRT [11/19/07 11:15:08:703 CST] 0000001d ApplicationMg A WSVR0204I: Application: IBM_Premises_Server_BIRT Application build level: Unknown [11/19/07 11:15:08:921 CST] 0000001d ExtensionRegi E CWXRS0004E: Failed to resolve plug-in [11/19/07 11:15:08:937 CST] 0000001d ExtensionRegi E CWXRS0004E: Failed to resolve plug-in [11/19/07 11:15:08:953 CST] 0000001d ExtensionRegi E CWXRS0004E: Failed to resolve plug-in [11/19/07 11:15:08:968 CST] 0000001d ExtensionRegi E CWXRS0004E: Failed to resolve plug-in [11/19/07 11:15:09:187 CST] 0000001d WebGroup A SRVE0169I: Loading Web Module: Eclipse BIRT Report Viewer. [11/19/07 11:15:11:625 CST] 00000027 SampledbPlugi I Sampledb plugin starts up. Current startCount=0 [11/19/07 11:15:11:625 CST] 00000027 SampledbPlugi I Creating Sampledb database at location C:\WINDOWS\TEMP\/BIRTSampleDB_1195442111625_15d815d8 [11/19/07 11:15:13:109 CST] 0000001d VirtualHost I SRVE0250I: Web Module Eclipse BIRT Report Viewer has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443]. [11/19/07 11:15:13:109 CST] 0000001d ApplicationMg A WSVR0221I: Application started: IBM_Premises_Server_BIRT
You can safely ignore these messages. They are from Business Intelligence and Reporting Tools (BIRT), which WebSphere Premises Server uses for reports.
The maximum number of tags that can be printed in a single print request varies and is dependent on a number of factors, including the label design, the amount of data per tag, your server size, and your network. If you submit a print job and the job fails, check for an error similar to the following in your WebSphere Application Server SystemOut.log file that indicates that you have too many tags in your print job:
[10/25/07 14:14:06:750 CST] 0000002f ExceptionUtil E CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "getPrintTemplateDetails". Exception data: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction rolled back; nested exception is: javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout at com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(TransactionControlImpl.java:1403) at com.ibm.ejs.csi.TransactionControlImpl.preInvoke(TransactionControlImpl.java:295) at com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContainer.java:3402) at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2874) at com.ibm.rfid.admin.model.ejb.session.EJSRemoteStatelessPrinterAdmin_84bad528.getPrintTemplateDetails (EJSRemoteStatelessPrinterAdmin_84bad528.java:425) at com.ibm.rfid.admin.model.ejb.session._PrinterAdmin_Stub.getPrintTemplateDetails( _PrinterAdmin_Stub.java:1245) at com.ibm.rfid.premises.supplychain.data.GenericPrintProfile.getTemplateName (GenericPrintProfile.java:274) at com.ibm.rfid.premises.supplychain.data.GenericPrintProfile.createGenericXML (GenericPrintProfile.java:236) at com.ibm.rfid.premises.supplychain.data.GenericPrintProfile.print (GenericPrintProfile.java:80) at com.ibm.rfid.premises.supplychain.data.PrintRequestHandler.handleRequest (PrintRequestHandler.java:135) at com.ibm.rfid.premises.supplychain.task.command.ejb.PrintRFIDTagCommandTaskBean.onMessage (PrintRFIDTagCommandTaskBean.java:118) at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:302) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:271) at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:240) at com.ibm.mq.jms.MQSession.run(MQSession.java:1592) at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:970) at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:891) at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:656) at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:623) at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:96) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:132) at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:481) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469) Caused by: javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout at com.ibm.ws.Transaction.JTA.TranManagerImpl.completeTxTimeout(TranManagerImpl.java:576) at com.ibm.ws.Transaction.JTA.TranManagerSet.completeTxTimeout(TranManagerSet.java:625) at com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(TransactionControlImpl.java:1395) ...
If you find this error, reduce the number of tags in your print job and submit the job again. If it still fails, continue reducing your tag count until the print job succeeds.
[6/13/08 9:30:31:125 EDT] 0000001d jdbc E Error while registering Oracle JDBC Diagnosability MBean. javax.management.MalformedObjectNameException: Invalid character ' ' in value part of property at javax.management.ObjectName.construct(ObjectName.java:544) at javax.management.ObjectName.<init>(ObjectName.java:1312) at oracle.jdbc.driver.OracleDriver.registerMBeans(OracleDriver.java:303) at oracle.jdbc.driver.OracleDriver$1.run(OracleDriver.java:213) at java.security.AccessController.doPrivileged(AccessController.java:197) at oracle.jdbc.driver.OracleDriver.<clinit>(OracleDriver.java:209) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at oracle.jdbc.pool.OracleDataSource.<clinit>(OracleDataSource.java:94) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) at java.lang.J9VMInternals.initialize(J9VMInternals.java:159) at java.lang.J9VMInternals.initialize(J9VMInternals.java:159) at java.lang.J9VMInternals.initialize(J9VMInternals.java:159) at java.lang.Class.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1328) at com.ibm.ws.rsadapter.DSConfigurationHelper.createDataSource(DSConfigurationHelper.java:1078) at com.ibm.ws.rsadapter.spi.WSRdbDataSource$6.run(WSRdbDataSource.java:1975) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.rsadapter.spi.WSRdbDataSource.createNewDataSource(WSRdbDataSource.java:1971) at com.ibm.ws.rsadapter.spi.WSRdbDataSource.<init>(WSRdbDataSource.java:902) at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.setDataSourceProperties(WSManagedConnectionFactoryImpl.java:1947) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.ejs.j2c.J2CUtilityClass.createMCFEntry(J2CUtilityClass.java:389) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandPM(ConnectionFactoryBuilderServerImpl.java:551) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObjectInstance(ConnectionFactoryBuilderServerImpl.java:922) at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:618) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:705) at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:2093) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1947) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221) at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:149) at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:144) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896) at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191) at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:406) at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280) at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:384) at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:204) at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:144) at javax.naming.InitialContext.lookup(InitialContext.java:363) at com.ibm.ejs.container.BeanMetaData.doConnectionHandlePerformanceSettings(BeanMetaData.java:4719) at com.ibm.ws.runtime.component.EJBContainerImpl.processBean(EJBContainerImpl.java:1852) at com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:2860) at com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:3720) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
InternalOracl I DSRA8206I: JDBC driver version : 11.1.0.6.0-Production
The patched ojdbc.jar file can be downloaded from Oracle:http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_111060.html.
[8/7/08 12:50:23:531 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:531 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding IBMRFIDQM as jms/ibm.rfid.qm [8/7/08 12:50:23:546 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:546 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding EDGE.IN.QUEUE as jms/edge.in.q [8/7/08 12:50:23:546 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:562 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding EDGE.OUT.QUEUE as jms/edge.out.q [8/7/08 12:50:23:562 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:562 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding CONTROL.IN.QUEUE as jms/control.in.q [8/7/08 12:50:23:578 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:578 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding CONTROL.OUT.QUEUE as jms/control.out.q [8/7/08 12:50:23:578 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:593 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding TASK.QUEUE as jms/task.q [8/7/08 12:50:23:593 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:593 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding MANAGEMENT.QUEUE as jms/management.q [8/7/08 12:50:23:609 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:609 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding PERSISTENCE.QUEUE as jms/persistence.q [8/7/08 12:50:23:609 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:625 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding DEAD.MESSAGE.QUEUE as jms/dead.message.q [8/7/08 12:50:23:625 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:625 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding TAGMONITOR.OUT.QUEUE as jms/tagmonitor.out.q [8/7/08 12:50:23:640 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:640 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding ALE.TAG.INPUT.Q as jms/ale.tag.input.q [8/7/08 12:50:23:640 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:656 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding EDGE.PRINT.IN.Q as jms/edge.print.in.q [8/7/08 12:50:23:656 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:656 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding EDGE.OUTBYTES.Q as jms/edge.outbytes.q [8/7/08 12:50:23:671 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:671 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding ALE.REPORT.Q as jms/ale.report.q [8/7/08 12:50:23:671 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:687 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding IBMDCQM as jms/ibm.dc.qm [8/7/08 12:50:23:687 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:687 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding DC.IN.QUEUE as jms/dc.in.q [8/7/08 12:50:23:703 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:703 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding DC.OUT.QUEUE as jms/dc.out.q [8/7/08 12:50:23:703 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:718 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding ENTERPRISE.IN.QUEUE as jms/enterprise.in.q [8/7/08 12:50:23:718 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:718 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding ENTERPRISE.OUT.QUEUE as jms/enterprise.out.q [8/7/08 12:50:23:734 CST] 0000000a JMSResourceRe E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. [8/7/08 12:50:23:734 CST] 0000000a ResourceMgrIm I WSVR0049I: Binding KIMONO.RESPONSE.Q as jms/kimono.response.q
To resolve these errors, restart the central server and the cluster.
You may see the following exception in the WebSphere Application Server SystemOut.log files when you migrate from WebSphere Premises Server 6.1 to version 6.1.0.1:
[8/30/08 15:40:24:984 CST] 00000041 SchedulerDaem E SCHD0104E: The Scheduler poll daemon AMITSCHEDULER (sched/Amit) failed to load tasks from the database due to an exception: com.ibm.websphere.scheduler.SchedulerNotAvailableException: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-204;42704;DB2ADMIN.SCHEDTASK at com.ibm.ws.scheduler.TaskStoreImpl.findTasksBeforeNotComplete(TaskStoreImpl.java:1161) at com.ibm.ws.scheduler.SchedulerDaemonImpl.poll(SchedulerDaemonImpl.java:653) at com.ibm.ws.scheduler.SchedulerDaemonImpl.run(SchedulerDaemonImpl.java:451) at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:761) at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:218) at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:158) at java.lang.Thread.run(Thread.java:810) Caused by: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-204;42704;DB2ADMIN.SCHEDTASK at com.ibm.db2.jcc.c.kh.c(kh.java:1660) at com.ibm.db2.jcc.c.kh.a(kh.java:1224) at com.ibm.db2.jcc.b.db.n(db.java:737) at com.ibm.db2.jcc.b.db.i(db.java:257) at com.ibm.db2.jcc.b.db.c(db.java:53) at com.ibm.db2.jcc.b.t.c(t.java:46) at com.ibm.db2.jcc.b.sb.g(sb.java:154) at com.ibm.db2.jcc.c.kh.o(kh.java:1219) at com.ibm.db2.jcc.c.lh.d(lh.java:2436) at com.ibm.db2.jcc.c.lh.S(lh.java:432) at com.ibm.db2.jcc.c.lh.executeQuery(lh.java:415) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuery(WSJdbcPreparedStatement.java:878) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:559) at com.ibm.ws.scheduler.TaskStoreImpl.executeQueryWithRetry(TaskStoreImpl.java:1729) at com.ibm.ws.scheduler.TaskStoreImpl$ExecuteQueryPriviledged.run(TaskStoreImpl.java:1616) at java.security.AccessController.doPrivileged(AccessController.java:246) at com.ibm.ws.scheduler.TaskStoreImpl.executePrivilegedQueryWithRetry(TaskStoreImpl.java:1785) at com.ibm.ws.scheduler.TaskStoreImpl.findTasksBeforeNotComplete(TaskStoreImpl.java:1154) ... 6 more
This error occurs during the uninstallation of WebSphere Premises Server 6.1 when you are migrating and can be safely ignored.