WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Troubleshooting tips

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.

Installation issues

Installation fails on Linux

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.

Installer cannot find WebSphere Application Server installation directory

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.

To resolve this problem, complete the following steps:
  1. Exit the installation.
  2. Open a command prompt and run the following command:
    change /user install
  3. Restart the WebSphere Premises Server installation.

URI length exceptions in the install.log file

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.

Error in the IRU_DeploymentWizard.log file after silent installation

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)

A "Microsoft Visual C++ ..." window appears after installing DB2

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.

Communication and connectivity issues

The back-end system does not receive messages

Perform the following actions to try and resolve the problem:

  • Check that WebSphere MQ is running. Start WebSphere MQ if it is not running.
  • Use the MQ Explorer to view the IBM.DC.QM queue manager and check that the depth of the ENTERPRISE.OUT queue is zero.
  • Check that WebSphere Application Server is running. Using a Web browser, go to: http://premises_server_ip:9060/ibm/console and log in with any user name. Start WebSphere Application Server if it is not running. Start any stopped listeners, and restart WebSphere Application Server if they cannot be started.
  • On the WebSphere Application Server administrative console, go to Servers > Application Servers > server1 > Messaging > Messaging Listener service > Listener Ports. Check that all listeners are running. A listener is running if it has a green arrow next to it.
  • Check that the Data Transformation service is running. Check the runtime log:
    • Windows C:\Program Files\IBM\RFID\logs\DTSRuntime.log
    • Linux /opt/IBM/RFID/logs/DTSruntime.log
    Stop and start the Data Transformation service if the log shows errors or exceptions.

The edge controller cannot connect to WebSphere Premises Server

Use the following actions to try and resolve the problem:

  • Check that WebSphere Application Server is running. Use the Windows Services panel. If WebSphere Application Server is down, start it.
  • Check that the Data Transformation service is running. Use the Windows Services panel to locate IBM WebSphere Premises Server DT Service. If the service is down, start it.
  • Try to access the configuration from a browser at: http://premises_server_ip:9080/ibmrfidadmin/premises.sl?action=getconfig&edge=EdgeID. If you cannot "ping" WebSphere Premises Server from the edge controller, check cables and hardware connections.
  • Check the network connection between the edge controller and WebSphere Premises Server. Try to Telnet into the edge controller and "ping" WebSphere Premises Server. If you cannot Telnet into the edge controller, make sure that the edge controller is running.

Connection between the tag reader and edge controller is interrupted

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.

  1. Switch the power off and back on again on the tag reader. In many cases, turning the power off and on solves the problem.
  2. Restart the edge controller.

The edge controller is unable to obtain configuration from WebSphere Premises Server

  • Try to access the configuration from a browser at: http://premises_server_ip:9080/ibmrfidadmin/premises.sl?action=getconfig&edge=EdgeID
  • Once the connection from the edge controller to WebSphere Premises Server is fixed, you do not need to perform any additional steps. You do not need to restart the edge controller. It automatically tries to restart approximately every two minutes to obtain the configuration from the premises server.
  • Verify that the network topology is correct. If it is not, fix the network topology and restart the edge controller.
  • Verify that the correct EDGEID, PREMISES_IP, and PORT_NUMBER were delivered from DMS UpdateParameters.xml job. If they were not, reissue the DMS UpdateParameters.xml job.

The edge controller is unable to communicate with the tag reader

  • Check the Data Transformation log.
  • Check the tag reader. If you cannot Telnet to the tag reader using the reader port, it might already be controlled by another edge controller. Ensure that no other edge controller is configured to use that tag reader and no other machine has a Telnet session open to that tag reader through the reader port.
  • Check the network connection between the edge controller and the tag reader. Try to Telnet into the edge controller and "ping" the tag reader. If you cannot "ping" the reader, check the cables and hardware connections.
  • If the problem persists, restart the tag reader.
  • If the problem persists, capture the Data Transformation log and contact your IBM representative for additional assistance.

Unable to start the device agent on WebSphere Premises Server

If you are unable to configure the device adapter with WebSphere Premises Server, update the core bundle list copy it to the bundle repository.

To resolve this problem, copy the following bundle loader files to the bundlelists directory in the bundle repository (for example, C:\Program Files\IBM HTTP Server\htdocs\en_US\bundles\bundlelists):
  • The dc_core4dts.txt file is for running Data Capture and Delivery bundles inside the Data Transformation service on WebSphere Premises Server.
  • The dc_core.txt file is for running Data Capture and Delivery bundles that are remote to the Data Transformation service (on the remote Data Capture and Delivery controller, which is running in an Equinox environment).
To install the bundles on the local machine or on the remote Data Capture and Delivery controller:
  1. Copy the device agent bundles to the bundle repository.
  2. Edit the bundle loader file (dc_core4dts.txt or dc_core.txt) and add the bundle name to it (for example, START bundle.jar) and update host_name with the correct host name or IP address.
  3. Update the config.ini file that is located in the configuration folder (for RFID Data Transformation Service, the file is located under IBM_RFID_HOME/dts/configuration) with the correct bundle file name: com.ibm.rfid.bundle.list.url=http://host_name:port/bundleadmin/GetBundle?name=http://host_name/bundles/bundlelists/bundle_loader_file
  4. Reset the bundle list on the local Data Transformation service by running the resetDTS script, which is located in the IBM_RFID_HOME/dts directory. On the remote Data Capture and Delivery controller, reset the bundle list to the default settings.
  5. Restart the Data Transformation service or the remote Data Capture and Delivery controller.
  6. Start the bundle loader bundle (com.ibm.rfid.bundle.loader_version.jar).

Queue issues

Queues filled to maximum depth in the queue managers

Check to see if the maximum queue depth has been reached. See Checking the depth of WebSphere MQ queues.

If you have reached the maximum queue depth, perform the following workaround steps:
  1. Stop WebSphere Application Server.
  2. Stop the Data Transformation on all edge controllers.
  3. Extend the maximum queue depth for all queues that are saturated.
    Note: The default queue depth is 5,000.
  4. Restart WebSphere Application Server.
  5. Restart the Data Transformation on the WebSphere Premises Server.
  6. Monitor the affected queue depths until they fall to zero.
  7. Restart the Data Transformation on all edge controllers.

Queue managers are not removed after uninstallation of WebSphere Premises Server

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.

If you have this problem, you should see an MQ error message in the uninstall.log file that states:
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

Other issues

WebSphere Premises Server does not work after stopping and restarting

  • Check that WebSphere MQ is running. If not, start WebSphere MQ from the Services panel.
  • Check that DB2 for Linux, UNIX, and Windows (DB2) or Oracle is running. If not, start DB2 or Oracle from the Services panel.
  • Check that WebSphere Application Server is running. If not, start WebSphere Application Server from the Services panel.
  • Check that the Data Transformation is running. If not, start IBM WebSphere Premises Server DT Service from the Services panel.

WebSphere Premises Server does not work in general

  • Check the WebSphere Application Server server1 logs in the WAS_PROFILE_HOME\logs\server1 directory. Check the SystemOut.log and the SystemErr.log files. Send the log files to the IBM support team.
  • Check that trace is enabled. Enable trace and send the trace.log file to the IBM support team.

Usage of direct JNDI lookup of resources has been deprecated

See J2CA0294W: Deprecated usage of direct JNDI lookup of resource for details.

WebSphere Premises Server Administrative Console password on Linux can be shorter than required

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:

  1. Navigate to YAST > Security and Users > Edit and Create Users.
  2. Select Password Encryption in the Expert options menu.
  3. Change the value from DES to MD5.

The WAS_HOME environment variable is not applied in a remote deployment

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.

Exceptions and errors

Incorrectly labeled ALE information messages in the WebSphere Application Server logs

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.

A NullPointerException occurs when OSGi starts

An org.eclipse.osgi.framework.internal.core.BundleHost.getLoaderProxy error, such as the following, might occur when starting OSGi. This error will not affect the operation of the system.
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.

"Failed to resolve plug-in" error in the WebSphere Application Server SystemOut.log file

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.

Print job fails with a rollback exception

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.

Oracle 11g exceptions in SystemOut.log file

If you use Oracle 11g, you may see the following exceptions in the WebSphere Application Server SystemOut.log file during WebSphere Premises Server startup:
[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)
If you see the following string in the SystemOut.log file, you need to download the patched ojdbc.jar file:
InternalOracl I DSRA8206I: JDBC driver version : 11.1.0.6.0-Production
Note: If there is a plus sign (+) at the end of the string, you are already running the patched file.

The patched ojdbc.jar file can be downloaded from Oracle:http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_111060.html.

JMSResource exceptions in the SystemOut.log files on the central server and node servers

You may see the following exceptions in the WebSphere Application Server SystemOut.log files on the central server and on the cluster node servers after running the high availability installer:
[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.

Scheduler exception in the SystemOut.log file when migrating

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.

Shared library exception in SystemOut.log files on cluster members

You may see the following exception in the cluster member SystemOut.log files when running a high availability topology:

[8/12/08 9:08:00:765 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\Rfid.jar.
[8/12/08 9:08:00:781 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\xsdbeans.jar.
[8/12/08 9:08:00:781 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_premises_api_client.jar.
[8/12/08 9:08:00:796 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_premises_api_ejbClient.jar.
[8/12/08 9:08:00:796 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_premises_api_ws.jar.
[8/12/08 9:08:00:812 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_premises_util.jar.
[8/12/08 9:08:00:812 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\com.ibm.rfid.epcg.tds.jar.
[8/12/08 9:08:00:828 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\org.apache.regexp.jar.
[8/12/08 9:08:00:828 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library PremisesClientAPI contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_common_utils.jar.
[8/12/08 9:08:00:843 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\Amit3.0Common.jar.
[8/12/08 9:08:00:843 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\com.ibm.rfid.epcg.tds.jar.
[8/12/08 9:08:00:843 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\org.apache.regexp.jar.
[8/12/08 9:08:00:859 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmse_common_util.jar.
[8/12/08 9:08:00:859 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmse_taskagent_runtime.jar.
[8/12/08 9:08:00:875 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmse_event_model_uuid.jar.
[8/12/08 9:08:00:875 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmse_event_model_converter.jar.
[8/12/08 9:08:00:890 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmse_event_model.jar.
[8/12/08 9:08:00:890 EDT] 0000000a ModuleManifes E   UTLS0002E: 
The shared library TaskAgentRuntime contains a classpath entry which does 
not resolve to a valid jar file, the library jar file is expected to be found at 
C:\Program Files\IBM\RFID\premises\api\lib\ibmrfid_common_utils.jar.

This error can be safely ignored; however, to remove these messages from the file, copy all JAR files from the central server IBM_RFID_HOME\premises\api\lib to the same director structure. The shared libraries PremisesClientAPI and TaskAgentRuntime are intended to customize applications using WebSphere Premises Server.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.