X

Recent Posts

JCA Binding Component is unable to create an outbound JCA (CCI) connection

Issue :You may get these errors while working with JCA Adapters, in my case its FTP Adapters in SOA 11.1.1.4.02011-10-07T17:49:27.593+05:30] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-11] [userId: ] [ecid: a556e7f5f253ac28:-59a8abc8:132ddb6e0a7:-8000-000000000001510c,0:1:100000057] [APP: soa-infra] failed to handle message[[com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}parts: {{summary=Exception occured when binding was invoked.Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: JCA Binding Component connection issue.JCA Binding Component is unable to create an outbound JCA (CCI) connection.DataReconciliationSFTP:FTP_WR_OUT [ Put_ptt::Put(opaque) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/Ftp/FtpAdapter from JNDI and get a new Connection Handle.Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections.". The invoked JCA adapter raised a resource exception.Please examine the above error message carefully to determine a resolution.,detail=[Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/Ftp/FtpAdapter from JNDI and get a new Connection Handle.,code=null}]][2011-10-07T17:49:27.593+05:30] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-11] [userId: ] [ecid: a556e7f5f253ac28:-59a8abc8:132ddb6e0a7:-8000-000000000001510c,0:1:100000057] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[Message handle error.error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.failure to handle a fault thrown from a scope, by any blocks in the scope chain.This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.A top-level fault handler should be added to the flow to handle faults not caught from within the flow.This error contained an exception thrown by the message handler.Check the exception trace in the log (with logging level set to debug mode). ORABPEL-05002Message handle error.error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.failure to handle a fault thrown from a scope, by any blocks in the scope chain.This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.A top-level fault handler should be added to the flow to handle faults not caught from within the flow.This error contained an exception thrown by the message handler.Check the exception trace in the log (with logging level set to debug mode).at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:207)at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)at java.lang.Thread.run(Thread.java:619)Solution :I logged into the /console - > ftp adapter - > opened the jndi where I use and has issues - > increase the max value under configuration to 700 - > saved. FTP Adapter started working fine

Issue : You may get these errors while working with JCA Adapters, in my case its FTP Adapters in SOA 11.1.1.4.02011-10-07T17:49:27.593+05:30] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch]...

MDS-01329 ; MDS-01370 ; unable to load MDS configuration document

You get the following exceptions when deploying a composite in JDEV 11.1.1.4 on SOA 11.1.1.4 :Error(9,56): Parse of component type files failed, check the adf-config.xml file : "oracle.fabric.common.FabricException: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document MDS-01329: unable to load element "persistence-config"MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_1" is invalid. MDS-00503: The metadata path "C:\JDeveloper11\Middleware\jdeveloper\integration" does not contain any valid directories.: MDS-01330: unable to load MDS configuration document MDS-01329: unable to load element "persistence-config"MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_1" is invalid. MDS-00503: The metadata path "C:\JDeveloper11\Middleware\jdeveloper\integration" does not contain any valid directories.: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document MDS-01329: unable to load element "persistence-config"MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_1" is invalid. MDS-00503: The metadata path "C:\JDeveloper11\Middleware\jdeveloper\integration" does not contain any valid directories.: MDS-01330: unable to load MDS configuration document MDS-01329: unable to load element "persistence-config"MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_1" is invalid. MDS-00503: The metadata path "C:\JDeveloper11\Middleware\jdeveloper\integration" does not contain any valid directories."Fix :Open the /.adf/META-INF/adf-config.xmland ensure you have right entries for :

You get the following exceptions when deploying a composite in JDEV 11.1.1.4 on SOA 11.1.1.4 :Error(9,56): Parse of component type files failed, check the adf-config.xml file :...

Unable to set the activation state to true for the application 'FtpAdapter'

You get an issue in SOA 11g while the server is started :####<Apr 7, 2011 12:30:36 PM IST> <Warning> <Connector> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159636869> <BEA-190104> <While configuring an object of type: oracle.tip.adapter.ftp.FTPManagedConnectionFactory of Resource Adapter FtpAdapter.rar, the following errors/omissions were found:Unable to invoke the setter method for the key : useSftpUnable to invoke the setter method for the key : enableCipherSuitsUnable to invoke the setter method for the key : passwordUnable to invoke the setter method for the key : preferredCipherSuite> ####<Apr 7, 2011 12:30:36 PM IST> <Info> <Common> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159636915> <BEA-000625> <The application has disabled periodic testing of free resources in pool "eis/Ftp/FtpAdapter".> ####<Apr 7, 2011 12:31:14 PM IST> <Error> <Deployer> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159674606> <BEA-149231> <Unable to set the activation state to true for the application 'FtpAdapter'.java.lang.NoClassDefFoundError: oracle/tip/adapter/file/FileLoggerat oracle.tip.adapter.ftp.FTPManagedConnectionFactory.createConnectionFactory(FTPManagedConnectionFactory.java:154)at weblogic.connector.security.layer.AdapterLayer.createConnectionFactory(AdapterLayer.java:787)at weblogic.connector.outbound.ConnectionPool.getConnectionFactory(ConnectionPool.java:2013)Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/file/FileLoggerat oracle.tip.adapter.ftp.FTPManagedConnectionFactory.createConnectionFactory(FTPManagedConnectionFactory.java:154)at weblogic.connector.security.layer.AdapterLayer.createConnectionFactory(AdapterLayer.java:787)at weblogic.connector.outbound.ConnectionPool.getConnectionFactory(ConnectionPool.java:2013)####<Apr 7, 2011 12:31:14 PM IST> <Info> <Deployer> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159674612> <BEA-149059> <Module FtpAdapter.rar of application FtpAdapter is transitioning from STATE_PREPARED to STATE_NEW on server AdminServer.> ####<Apr 7, 2011 12:31:14 PM IST> <Info> <Deployer> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159674640> <BEA-149061> <Module FtpAdapter.rar of application FtpAdapter failed to transition from STATE_PREPARED to STATE_NEW on server AdminServer.> ####<Apr 7, 2011 12:31:14 PM IST> <Error> <Deployer> <inhysu01> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Iwikhf_8TsO8mjGNtn1DbM3f000002> <1302159674653> <BEA-149250> <Unable to unprepare application 'FtpAdapter'.weblogic.application.ModuleException: Error occurred while trying to rollback the module: weblogic.connector.exception.RAException: There are 1 nested errors:There are 1 nested errors:ObjectLifeCycleException: weblogic.common.resourcepool.ObjectLifeCycleException: Attempted to shutdown the pool eis/Ftp/FtpAdapter when it is currently not in SUSPENDED state (Running)at weblogic.common.resourcepool.ResourcePoolImpl.shutdown(ResourcePoolImpl.java:299)at weblogic.connector.outbound.ConnectionPool.shutdown(ConnectionPool.java:355)at weblogic.connector.outbound.RAOutboundManager.internalShutdownPool(RAOutboundManager.java:346)Solution :Put the FileAdapter.rar file in the $domain_home/lib and restart the server.

You get an issue in SOA 11g while the server is started :####<Apr 7, 2011 12:30:36 PM IST> <Warning> <Connector> <inhysu01> <AdminServer><[ACTIVE] ExecuteThread: '1' for...

Unable to start SOA Domain in SOA 11g due to weblogic.security.SecurityInitializationException: Authentication for user weblogic denied

You notice the following exceptions while starting a SOA Server domain :<Apr 9, 2011 11:21:54 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING><Apr 9, 2011 11:21:54 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool><Apr 9, 2011 11:21:55 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file C:\SOA1114\user_projects\domailog is opened. All server side log events will be written to this file.><Apr 9, 2011 11:22:57 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.><Apr 9, 2011 11:22:58 AM IST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied><Apr 9, 2011 11:22:58 AM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.securication for user weblogic deniedweblogic.security.SecurityInitializationException: Authentication for user weblogic denied        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceM        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDel        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)        at weblogic.security.SecurityService.start(SecurityService.java:141)        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)        Truncated. see log file for complete stacktraceCaused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogielegateException: [Security:090295]caught unexpected exception        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)        Truncated. see log file for complete stacktrace><Apr 9, 2011 11:22:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED><Apr 9, 2011 11:22:58 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut its<Apr 9, 2011 11:22:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>Solution :Remove the bot.properties file and ldap folder from the domain local folders and start the domain from cmd prompt.

You notice the following exceptions while starting a SOA Server domain : <Apr 9, 2011 11:21:54 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING><Apr 9, 2011 11:21:54 AM...