GlassFish Server Logs Shows "SEVERE: RAR6030 : Failed To Remove The MCF" for JPA Application

(Doc ID 1446295.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version: 3.1.1 and later   [Release: 3.1 and later ]
Information in this document applies to any platform.

Symptoms

On Oracle GlassFish Server 3.1.1 and 3.1.2, The following error "RAR6030 : Failed to remove the MCF" is seen in the GlassFish server logs.
[#|2012-03-19T10:31:02.296+0900|SEVERE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=361;_ThreadName=Thread-2;|RAR6030 : Failed to remove the MCF : sample|#]

This happens on an JPA/Eclipselink application with the following persistence.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="businessPU" transaction-type="JTA">
<jta-data-source>jdbc/sample</jta-data-source>
....
</persistence-unit>

When more detail logging is enabled on the following logger "javax.enterprise.resource.resourceadapter" to FINE , some of the following extra information is seen:
[#|2012-03-19T10:31:49.394+0900|FINE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors|_ThreadID=361;_ThreadName=Thread-2;ClassName=com.sun.enterprise.connectors.ConnectorRegistry;MethodName=isMCFCreated;|isMCFCreated sample - false|#]

[#|2012-03-19T10:31:49.394+0900|FINE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors|_ThreadID=368;_ThreadName=Thread-2;ClassName=com.sun.enterprise.connectors.ConnectorRegistry;MethodName=removeManagedConnectionFactory;|Failed to remove the MCF from connector registry.|#]

[#|2012-03-19T10:31:49.394+0900|SEVERE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=368;_ThreadName=Thread-2;|RAR6030 : Failed to remove the MCF : sample|#]

[#|2012-03-19T10:31:49.394+0900|FINE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=361;_ThreadName=Thread-2;ClassName=com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl;MethodName=obtainManagedConnectionFactory;|RAR6017 : Failed to get connection pool object sample via JNDI lookup : {1}|#]

[#|2012-03-19T10:31:49.394+0900|FINE|oracle-glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service|_ThreadID=368;_ThreadName=Thread-2;ClassName=com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl;MethodName=unloadAndKillPool;|
com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Wrong parameters for pool creation : sample
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.unloadAndKillPool(ConnectorConnectionPoolAdminServiceImpl.java:1387)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:625)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1607)
at com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRuntime.java:585)
at com.sun.enterprise.connectors.service.ConnectorResourceAdminServiceImpl$MyDataSource.getConnection(ConnectorResourceAdminServiceImpl.java:279)
at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:123)
at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:330)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:293)
........
........
........
Caused by: javax.naming.NamingException: Lookup failed for '__SYSTEM/pools/sample' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming} [Root exception is javax.naming.NameNotFoundException: sample not found]
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.sun.appserv.connectors.internal.api.ResourceNamingService.lookup(ResourceNamingService.java:221)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:871)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1004)
... 445 more
Caused by: javax.naming.NameNotFoundException: sample not found
at com.sun.enterprise.naming.impl.TransientContext.doLookup....


Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms