Forum Stats

  • 3,816,042 Users
  • 2,259,133 Discussions
  • 7,893,368 Comments

Discussions

Error in Database adapter Toplink session

daimien
daimien Member Posts: 19
edited Apr 7, 2017 3:39AM in SOA Suite Discusssions

Hi all,

Recently in our SOA application, in development environment, we have been getting faults when invoking database adapters, and we haven't made any changes to them or any datasource/dbadapter.

<part  name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert'   failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore.   Caused by Exception [EclipseLink-0] (Eclipse Persistence Services - 2.3.1.qualifier): org.eclipse.persistence.exceptions.IntegrityException Descriptor   Exceptions: ---------------------------------------------------------   Runtime Exceptions: ---------------------------------------------------------   Exception [EclipseLink-25016] (Eclipse Persistence Services - 2.3.1.qualifier): org.eclipse.persistence.exceptions.XMLMarshalException Exception   Description: A namespace for the prefix toplink:read-whole-document was not found in the namespace resolver. .   You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.   This exception is considered not retriable, likely due to a modelling mistake. ".   The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part  name="detail"><detail> Descriptor Exceptions: --------------------------------------------------------- Runtime Exceptions: --------------------------------------------------------- Exception [EclipseLink-25016] (Eclipse Persistence Services - 2.3.1.qualifier): org.eclipse.persistence.exceptions.XMLMarshalException Exception Description: A namespace for the prefix toplink:read-whole-document was not found in the namespace resolver. </detail></part>

We have tried restarting servers, redeploying the dbadapter but this keeps happening.

Our configuration is:

soa suite 11g (11.1.1.7)

JDeveloper 11g

Oracle Database XE 11g

Regards,

Danilo

Tagged:

Answers

  • Martien van den Akker
    Martien van den Akker Member Posts: 2,776 Bronze Crown
    edited Apr 5, 2017 5:57AM

    Hi Daimien,

    Since the description said: 'Description: A namespace for the prefix toplink:read-whole-document was not found in the namespace resolver.', it seems that there did something change. It might be helpfull to trackdown when it started to happen and if there were some developments in that time frame.

    But I'd start with checking the datasources, if those are ok (can connect, etc.) and then the db configurations of the outbound connection pools of the DB Adapter under Deployments in Weblogic.


    Since you state that you use Oracle Dabase XE 11g, may I conclude this is a development environment?

    Regards,
    Martien

  • daimien
    daimien Member Posts: 19
    edited Apr 5, 2017 5:34PM

    Hi Martien,

    Yes this is a development environment and we have checked the datasources and other configurations. We deleted and developed the adapters that were causing the faults and the fault isn't happening, but this doesn't seem a viable solution if it comes to happen again.

    Regards,

    Danilo

  • Martien van den Akker
    Martien van den Akker Member Posts: 2,776 Bronze Crown
    edited Apr 7, 2017 3:39AM

    Hi Danilo,

    This is indeed no solution, of course. But it is actually a good way to solve a problem like this: stripping out until the problem disappears and then from then on building up again. Actually, to do it properly you should do the stripping step by step with in between checks. So you can track down at which strip-step the problem dissappears. At that point you know that you removed the cause and thereby identified the cause.


    But good news you're up and running again. Now build it out again. Good luck.

    Regards,
    Martien

This discussion has been closed.