IBM E02HRLL-G Administration Guide - Page 189
Rendering of tab headings on displays with resolution greater than 1024
![]() |
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 189 highlights
duplicate document delivery during the processing of large volumes of documents, include the following attributes in the Websphere variables of each router instance: 1. bcg.dm.checkFileLatency=true 2. bcg.dm.latencyWaitTime=3000 Rendering of tab headings on displays with resolution greater than 1024 On displays that have the resolution width set to a value greater than 1024 pixels, the Community Console might misdraw the tab headings on screens such as the Document Details view. You can ignore this behavior. Documents not processed when using Oracle 9i Release 2 About this task If you are using Oracle 9i Release 2, you might find that documents are not processed and the BCGMAS messaging engine logs contain the following error: J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource datasources/bcgMASDS The exception received is com.ibm.websphere.ce.cm.StaleConnectionException: No more data to read from socket: java.sql.SQLException: No more data to read from socket To resolve this issue, install the Oracle 10g version of the JDBC driver. This driver alleviates known incompatibilities between Oracle 9i and the WebSphere Application Server Messaging Engine. For more details, see the IBM Technote for this issue. To find the IBM Technote: 1. Go to http://www.ibm.com/support/us/. 2. Type number 1239781 in the search box. 3. Select Oracle 9i Thin driver running in cognizance with Service Integration Bus and Scheduler Service can result in J2C Connection Pool Exhaustion from the search results list. You can download the Oracle 10g JDBC driver from the Oracle website at:http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html Document processing when the database goes down If the database goes down while WebSphere Partner Gateway is processing the documents, then the documents will get stuck in the 'inprocess' state and the messages will be moved to datalogerrorQ. When the database is up, you must run the batch file reprocessDbLoggingErrors.bat (present under WPG_HOME/bin) in order to move the messages back from the datalogerrorQ and continue processing the documents. Chapter 17. Troubleshooting 183
![](/manual_guide/products/ibm-e02hrllg-administration-guide-f948001/189.png)