Troubleshooting FAQ

The following sections provide answers to frequently asked questions about problems that you might encounter as you develop and deploy WebLogic Integration solutions:

Questions are categorized according to typical user experiences. Each section describes one or more problems and includes a detailed description of the problem, one or more suggested remedies, and cross-references to additional helpful information, such as product documentation.

Installation and Preparation

This section answers the following questions:

What should I do if bulk loading of repository data fails?

Problem

In certain circumstances when working with B2B integration, such as before you run a WebLogic Integration sample, you are required to bulk load data into the WebLogic Integration repository. If error messages are displayed after you try to bulk load data into the repository, the bulk loading process has not run successfully.

Solution

Check the error message to determine the reason for the error. Then correct the error and perform the bulk loading operation again. Because bulk loading is not transactional, we suggest that you completely clean your database before bulk loading the data again.

Possible errors during bulk loading include:

How can I determine the version of WebLogic Integration that I am using?

Problem

You do not know how to determine the installed version of WebLogic Integration.

Solution

Look in the registry.xml file in the BEA Home directory that contains the WebLogic Integration installation. The registry.xml file contains an XML segment similar to the following:

<bea-product-information>
    <host home="c:\bea" name="hostname" number="1">
        <product format="1.0" name="WebLogic Platform">
            <release BeaProgramGroup="BEA WebLogic Platform 7.0" BuiltInServicePackLevel="0" InstallDir="c:\bea\weblogic700" InstallTime="Jun 6, 2002 4:57:18 PM" JavaHome="c:\bea\jdk131_03" JavaVersion="1.3.1_03" PatchLevel="1" ServicePackLevel="0" Status="installed" level="7.0">
                <component name="WebLogic Server" version="7.0.0.1">
                    <component name="Server"/>
                    <component name="Server Examples"/>
                </component>
                <component name="WebLogic Integration" version="7.0.0.0">
                    <component name="Integration Server"/>
                    <component name="Integration Examples"/>
                </component>
            </release>
        </product>
    </host>
</bea-product-information>

Look at the release element (text starting with <release . . . ). This element indicates the number of the release and service pack of WebLogic Integration that is currently installed.

I have just changed the IP address of my system. Why do I see lots of transaction errors in the log file?

Problem

An IP address change causes large numbers of transaction log errors.

Solution

Remove the old transaction log files. For further information, see "Troubleshooting Transactions" in Programming WebLogic JTA at the following URL:

Migration

This section answers the following questions:

How can I move my design-time data for WebLogic Integration to another database?

Problem

You might want or need to move the design-time data for WebLogic Integration to another database. Such migration may become necessary, for example, because you are installing a new release of WebLogic Integration, or because you are changing database types.

Solution

Why do my workflows fail to work when I import a package into the WebLogic Integration Studio?

Problem

Sometimes, after a previously exported package is imported into the WebLogic Integration Studio, the imported workflows are not instantiated properly, or you encounter run-time errors.

Solution

Consider the following possible solutions:

Using the Samples

This section answers the following question:

I installed a sample from BEA dev2dev Online and it does not seem to work with my WebLogic Integration installation. How can I fix this?

Problem

Although all the samples packaged with the product are compatible with your WebLogic Integration installation, not all samples available from BEA dev2dev Online are updated for the current release. Some samples are not forwardly compatible.

Solution

Read the documentation for the downloaded sample to verify that all the components of your environment (platform, release of WebLogic Integration, and version of WebLogic Server) are supported for the sample.

Starting the Server

This section answers the following questions:

Why do I get ConnectExceptions when starting the server?

Problem

You encounter the following exception message when the server is started:

              a routed: 'Protocol: 't3'' connection
to:'0S:172.16.3.18:[7001,-1,-1,-1,-1,-1,-1]' on port: '7001'
java.rmi.ConnectException: No available router to destination
. . .

Solution

If this problem occurs on a production server, make sure you archive the transaction log files before deleting them, as they contain information about transactions that were in process when the server failed.

Why do I get a Table or View Does Not Exist error when starting the server? I am using an Oracle database.

Problem

You encounter the following error message when a server, running over an Oracle database, is started:

####<Aug 30, 2001 12:40:52 PM GMT-08:00> <Alert> <JMS> <fushigi.beasys.com> 
<myserver> <main> <system> <> <040052> <JMSServer "WLA
I_JMSServer", store failed to open, java.io.IOException: JMS JDBC store, 
connection pool = <wliPool>, prefix = <null>: JMS JDBC I/
O failure
java.sql.SQLException: ORA-00942: table or view does not exist

         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
         at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:542)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1311)
         at 
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:595)
         at 
oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1600)
         at 
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1758)
         at 
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java 
:1805)
         at 
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:410)
         at weblogic.jdbc.pool.Statement.executeQuery(Statement.java:48)
         at   

Solutions

This error occurs when JMS finds two tables with the same name, one of which belongs to a different user or schema. Assign each JMSJDBCStore table a unique name. Change the JMSJDBCStore line in your config.xml file to a line similar to the following example:

<JMSJDBCStore ConnectionPool="wliPool" Name="wliPool" 
PrefixName="someuniqname" />

Designing Applications

This section answers the following questions:

Why do I encounter an error message when I create an XML document in the WebLogic Integration Studio XML editor?

Problem

When you create a legitimate XML document in the WebLogic Integration Studio XML editor, the instance editor may display the following message:

Solution

Problem

When you import a legitimate XML document into the WebLogic Integration Studio XML editor, the instance editor may display an error message, prompting you to convert the document to a valid template document.

Solution

Click Yes and convert the document into a template document.

How do I start a public workflow that starts a B2B conversation?

Problem

You want to start a workflow that initiates a B2B conversation.

Solution

To start a workflow that initiates a B2B conversation, use the Start Public Workflow action from another workflow. An API is also available to start a public workflow from within a Java application. Note that Start Public Workflow provides input parameters to determine a collaboration agreement, which determines a conversation. The conversation, in turn, contains the workflow template name.

Problem

I am using a Start Public Workflow action and the workflow does not start.

Solution

Common errors:

What should I do if I cannot see an entity (such as a trading partner) in the navigation tree?

Problem

You cannot find entities that you expect to see listed in the navigation tree of the WebLogic Integration B2B Console.

Solution

Complete the following steps:

What should I do if I cannot see the details of business protocol definitions?

Problem

You cannot see the details of business protocol definitions in the navigation tree of the WebLogic Integration B2B Console.

Solution

Complete the following steps:

What does it mean if I see a SQL Exception while trying to remove an element from the WebLogic Integration repository?

Problem

You encounter a similar SQL exception while removing an element from the repository:

Exception:ERROR: In SQLHelper.execute(), a SQL Exception was caught while
executing a SQL Statement: SQL Exception: DELETE on table 'PARTY_IDENTIFIER'
caused a violation of foreign key constraint
'15b58164-00e8-4d2f-8ace-00ac100b2400' for key (27).  The statement has been
rolled back.
com.bea.b2b.management.ManagementException: ERROR: In SQLHelper.execute(), a SQL
Exception was caught while executing a SQL Statement: SQL Exception: DELETE on
table 'PARTY_IDENTIFIER' caused a violation of foreign key constraint
'15b58164-00e8-4d2f-8ace-00ac100b2400' for key (27).  The statement has been
rolled back.
. . . <remainder of stack trace not shown> . . .

Solution

Running Applications

This section answers the following questions:

How can I can find, in the Worklist, the name of the workflow template needed to start the workflow?

Problem

You create a workflow template in the WebLogic Integration Studio and then use the Worklist user interface to start the workflow. However, you cannot find the workflow template in the Worklist when you want to start the workflow.

Solutions

Perform one or more of the following steps:

Additional Information

How can I debug and trace my workflow execution?

Problem

You are having difficulty determining why a workflow is not operating correctly.

Solution

Tracing the execution of a workflow can help determine the cause of problems and indicate a solution. There are several ways to debug or trace the execution of a workflow instance:

Additional Information

Starting a workflow throws an exception. Why is no instance created?

Problem

A workflow encounters an exception, but no workflow instance exists to indicate that the workflow was instantiated.

Solution

Workflow instances are created and persisted in the database only after a workflow reaches a quiescent state or done node. If a workflow encounters an exception before it reaches a quiescent state or done node, the workflow instance is rolled back. To solve this problem, force a quiescent state by inserting an action, such as No Operation or Assign Task to User, that causes the workflow instance to wait.

Additional Information

What should I do if the WebLogic Integration process engine does not process some messages or events in the JMS queue?

Problem

It appears that the events or messages posted to the JMS queue are not processed by the WebLogic Integration process engine.

Solution

Try any of the following solutions:

What should I do if I get a "resource unavailable" or "Transaction has timed out when making request to XAResource 'WebLogic.jdbc.jts.Connection'" exception?

Problem

You encounter one of the following exceptions:

Solution

These errors can indicate that more connections are required by your application than you have allocated in the connection pool. An error might occur due to pool exhaustion in the WebLogic Integration repository pool or in the application integration connection factory pool for an ApplicationView.

To determine which pool is being exhausted, check the exception stack trace. If you see a class with a name such as xxxConnectionFactory.getConnection() in the stack trace, you can conclude that a connection factory pool is depleted. The exception message often points to the depleted pool. If you do not see such a class in the stack trace, you can conclude that the JDBC connection pool is depleted.

For either type of pool, estimate the number of expected maximum concurrently active users, multiply that number by two, and use the resulting number as the value of Max Capacity in the pool. For JDBC connection pools, modify the JDBCConnectionPool element of your config.xml file. For connection factory pools for application views, use the Application View Console to edit the connection parameters section of the application view and set the Max Capacity value.

If setting Max Capacity for connection factories does not solve the problem, increase the maximum capacity in the adapter deployment unit. To do this, locate the adapter's RAR file (the location is indicated in your server's config.xml file within the application element for your adapter) and edit its weblogic-ra.xml deployment descriptor, which is located within the META-INF directory of the archive.

Note: To edit the weblogic-ra.xml file, extract the archive, edit the file, and jar the archive. Increase the max-capacity element of the pool-params element in the weblogic-ra.xml file.

If you are using Oracle, check your database block size. If the block size is 2K, rebuild your database with an 8K block size.

You can also adjust the ThreadPoolSize and JDBC connection pool size to proper levels so that each transaction does not need to wait a long time to get a free database connection. In most cases, you should set the JDBC connection pool size to be twice as big as the ThreadPoolSize, but the appropriate size depends on the needs of your application.

What should I do if I encounter event generation problems while using application integration?

Problem

You define an application view containing event definitions and deploy it, but you cannot receive any events when using the event-test facility in the WebLogic Integration Application View Console.

Solution

This problem might be due to any of the following reasons:

What should I do if my application integration asynchronous service responses are lost while I am using business process management?

Problem

In the WebLogic Integration Studio, you define a workflow in which application integration functionality is used to invoke services asynchronously. Within the workflow you define a task node, to invoke a service, and an event node, to receive the response from a service. At run time, however, the response event is not received.

Solution

This problem can occur when no significant amount of logic is designed between the task node and the event node for an asynchronous response. In this case, you might encounter a race condition in the WebLogic Integration process engine that causes it to miss events. It is difficult to determine whether the response is received by the BPM event queue. Use the WebLogic Server Administration Console to monitor the BPM event queue and to determine whether the message count has increased as a result of running the workflow containing the task that invokes the asynchronous service. To solve this problem, add a No Operation in a task that is placed between the task node and the event node for the asynchronous service. The addition of the No Operation introduces a slight delay in the processing of the workflow instance.

Why doesn't the B2B engine accept messages from remote trading partners?

Problem

You cannot establish communications with one or more of the B2B delivery channels (URLs). A common cause for this problem is that the HTTP/HTTPS subsystem has not been properly configured for B2B.

Solution

To debug this problem, try the following steps:

If you completed all the steps in this solution, and you are still experiencing communication problems, it is unlikely that the HTTP/HTTPS communication channel is the source of your problem. Check the following in the WebLogic Integration repository:

General Run-Time Issues

This section answers the following questions:

How can I solve out of memory errors?

Problem

You encounter out of memory errors in Java applications when the demand for memory allocation in the program exceeds the free space in the JVM heap. You must terminate the Java process that is currently running and restart the application. Although out of memory errors cannot be eliminated completely, the following solutions can reduce the occurrence of this error.

Solution

Increase the amount of free space in the JVM and reduce demand. Specifically, you can implement the following steps:

Where are WebLogic Integration log messages saved?

Problem

You do not know how to find WebLogic Integration log messages.

Solutions

Use the following instructions to locate WebLogic Integration log messages:

My server will not shut down properly.

Problem

After running the stopWeblogic command, you get the following error message:

<Oct 12, 2001 6:24:00 PM PDT> <Critical> <WebLogicServer> <Failed to invoke shutdown class "WLCShutdown",java.lang.IllegalArgumentException>

Solutions

This problem, a known bug with WebLogic Server, occurs when you stop and restart the B2B engine without concurrently stopping and restarting WebLogic Server. When this bug appears, the B2B engine has already been shut down properly, but WebLogic Server may hang. For more information, see the BEA WebLogic Server documentation.