Skip to Content

XI JDBC Connectivity Problems

Hi All,

We are using the J2EE Engine of our XI box for connectivity to an external DB for BI UD Connect.

We keep getting on an intermittent basis the following error message :-

BIRuntimeException: Null is not a supported value for Connection Property: url

But the URL property is not blank and works fine but if we resave the configuration when we get this message it works again without us doing anything!!!

Is there something we can do or should do to stop this?

SAP_ABA 640 0020 SAPKA64020 Cross-Application Component

SAP_BASIS 640 0020 SAPKB64020 SAP Basis Component

PI_BASIS 2006_1_640 0001 SAPKIPYL01 Basis Plug-In (PI_BASIS) 2006_1_640

ST-PI 2005_1_640 0007 SAPKITLQH7 SAP Solution Tools Plug-In

SAP_BW 350 0020 SAPKW35020 Business Information Warehouse

Any help appreciated.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    Mar 04, 2008 at 01:05 PM

    You are missing the jar file "jaxrpc-api.jar". Include the jar in the project build path.

    Hope it helps

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 04, 2008 at 01:11 PM
    Add comment
    10|10000 characters needed characters exceeded

  • Mar 10, 2008 at 08:46 AM

    Thanks for the replies.

    We got this from SAP :-

    The reported error can be raised when a UDI connection is required to

    read data and it can not be established. Let me try to explain how does

    it work and what we can do to fix this.

    When BW asks UD Connect to get data from the source system, UDC opens a

    connection on demand. At this moment, there are 2 scenarios possible:

    1) there is no open unused connection in the pool - new connection

    created and registered with the connection pool;

    2) there is an open unused connection in the poll - it is reused.

    There is no "automatic reconnect", but you can configure the J2EE Engine to cleanup the invalid connections like those which are raising the

    exceptions. This happens when some sort of error occured with the


    Using the Visual Administrator, go to the Connector Container service.

    Select your JDBC connector instance (e.g.: SDK_JDBC) under Then go to the "Managed Connection

    Factory" tab and to "Connection Definition". Check the "Expiration"

    option. Set both the "Connection Lifetime" and "Cleanup Thread" to 20.

    This will cleanup any lingering invalid connections.

    The conection lifetime is measured in seconds. So, in our case, after

    lost the connection, in 20 seconds the unused connection is closed. It

    is pre-condition to open a new connection.

    As you have said that saving again the settings in the connector

    container re-activates the connection, I hope these tips can solve the

    issue for you.

    Looks like this has resolved our issue.

    Thanks again.


    Add comment
    10|10000 characters needed characters exceeded