My Oracle Support Banner

Data source was not created in weblogic after successful Installation of ASAP (Doc ID 1467366.1)

Last updated on NOVEMBER 20, 2023

Applies to:

Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.

Symptoms

After installing ASAP successfully (according to the installer),  the data source was not created in weblogic and the following error messages appeared in the nohup.out file :

Nohup.out:



Jun 4, 2012 6:21:44 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
Jun 4, 2012 6:21:44 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'

java.lang.IllegalArgumentException: Commit request id 1338824495867 does not match outstanding request id -1
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:308)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     Truncated. see log file for complete stacktrace
>

java.lang.IllegalArgumentException: Commit request id 1338824495867 does not match outstanding request id -1
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:308)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     Truncated. see log file for complete stacktrace
>

java.lang.IllegalArgumentException: Commit request id 1338824495867 does not match outstanding request id -1
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:308)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     Truncated. see log file for complete stacktrace
>

java.lang.IllegalArgumentException: Commit request id 1338824495867 does not match outstanding request id -1
     at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:308)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     Truncated. see log file for complete stacktrace
>

java.lang.IllegalArgumentException: Commit request id 1338824495867 does not match outstanding request id -1

-------

>
weblogic.store.PersistentStoreException: The JDBC store VQFL.JMSJDBCStore has no data source
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:81)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
     Truncated. see log file for complete stacktrace
>
weblogic.management.DeploymentException:
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)


-----


 ThreadDump for vqflserver<
"Timer-2" waiting for lock java.util.TaskQueue@fe07b8 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)

"Thread-12" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:468)
java.net.ServerSocket.accept(ServerSocket.java:436)
com.mslv.asap.activation.srp.JsrpInitializerBean$ListenSarmEvents.run(JsrpInitializerBean.java:214)

-------

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.