Deploying J2E CA 1.0 Resource Adapter on 11g

I am currently only supplying an ra.xml file since I have not been able to get the same RAR file that worked with WLS 8 to install correctly on 11g with my weblogic-ra.xml. I receive the following error even though I do not supply a weblogic-ra.xml file as the error message states. Are 1.0 resource adapters supported? I have included a copy of the ra.xml at the bottom of message.
Any ideas?
Eric
<Nov 24, 2010 2:37:04 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1290634624475' for task '0'. Err
or is: 'weblogic.application.ModuleException: A <jndi-name> is specified for the
resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> el
ement is specified in ra.xml'
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149004> <Failures were d
etected while initiating deploy task for application 'BullHooXG8Line'.>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149078> <Stack trace for
message 149004
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Error> <Console> <BEA-240003> <Console encountere
d the following error weblogic.application.ModuleException: A <jndi-name> is spe
cified for the resource adapter bean in weblogic-ra.xml, however no <resourceada
pter-class> element is specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo
duleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.d
td'>
<connector>
<display-name>HooXG8 Line NoTxn Adapter</display-name>
<vendor-name>Bull</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>GCOS</eis-type>
<version>2.1</version>
<resourceadapter>
<managedconnectionfactory-class>com.bull.HooX.GcosManagedConnectionFactoryImpl</managedconnectionfactory-class
>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.bull.HooX.GcosConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.bull.HooX.GcosConnectionImpl</connection-impl-class>
<transaction-support>NoTransaction</transaction-support>
<config-property>
<description>IP name or address</description>
<config-property-name>ipAddress</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>DSA node name</description>
<config-property-name>dsaNode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Mailbox name</description>
<config-property-name>mailbox</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Protocol to use(EGATE, LINE, NONE)</description>
<config-property-name>protocol</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>LINE</config-property-value>
</config-property>

There should be a weblogic-ra.xml file in your deployment plan somewhere. The structure of the deployment plan is as follows:
somewhere/Plan.xml
somewhere/plan/META-INF/weblogic-ra.xml
The resource adapter does not support you specifying a <jndi-name> for the resource adapter. You can however specify <jndi-name> for the connection instances you create after deploying the adapter. If you have a <jndi-name> for the recource adapter, simply delete it from weblogic-ra.xml (also delete empty element such as <jndi-name></jndi-name> or <jndi-name /> ). Then update the adapter from the Deployments page in Admin console.
Here is my weblogic-ra.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-connector xmlns="http://xmlns.oracle.com/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-connector http://xmlns.oracle.com/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
<native-libdir>C:\dev\wls_domains\domain1\lib</native-libdir>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<security></security>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params></pool-params>
<logging></logging>
</default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<default-connection-properties>
<pool-params></pool-params>
<logging>
<logging-enabled>false</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>false</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>500</file-size-limit>
<rotate-log-on-startup>true</rotate-log-on-startup>
<log-file-rotation-dir></log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
</default-connection-properties>
<connection-instance>
<jndi-name>hoox</jndi-name>
<connection-properties>
<pool-params></pool-params>
<logging>
<log-filename>C:\dev\wls_domains\domain1\servers\AdminServer\logs\hoox.log</log-filename>
<logging-enabled>true</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>10000</file-size-limit>
<rotate-log-on-startup>false</rotate-log-on-startup>
<log-file-rotation-dir>C:\dev\wls_domains\domain1\servers\AdminServer\logs</log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
<properties>
<property>
<name>mailbox</name>
<value>XXXXXXXXXXXXXX</value>
</property>
<property>
<name>dsaNode</name>
<value>XXXXXXXXXXXXX</value>
</property>
<property>
<name>ipAddress</name>
<value>XXXXXXXXXXXXXXX</value>
</property>
<property>
<name>options</name>
<value>-TL FULL -MCMDSIZE 5</value>
</property>
<property>
<name>protocol</name>
<value>EGATE</value>
</property>
<property>
<name>serviceMapPath</name>
<value>C:\dev\wls_domains\domain1\lib\vdirmap.xml</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>

Similar Messages

NoClassDefFoundError error when deploying a resource adapter rar file

Hi,
Iam trying to deploy a resource adapter(RA) rar file which uses orabpel.jar.
1. When i dont package the orabpel.jar along with the adapter, i get the following error during deployment
[Apr 19, 2007 8:05:00 PM] Connector Module Deployer for BRMAdapter STARTS.
[Apr 19, 2007 8:05:00 PM] Copy the archive to E:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\BRMAdapter\BRMAdapter.rar
[Apr 19, 2007 8:05:00 PM] Unpacking BRMAdapter.rar
[Apr 19, 2007 8:05:00 PM] Done unpacking BRMAdapter.rar
[Apr 19, 2007 8:05:00 PM] Starting up resource adapter
[Apr 19, 2007 8:05:00 PM] Exception: NoClassDefFoundError: oracle/tip/adapter/api/exception/PCRetriableResourceException
[Apr 19, 2007 8:05:00 PM] Operation failed with error: oracle/tip/adapter/api/exception/PCRetriableResourceException
2. If i package the orabpel.jar file along with the RA, i get ClassCastException.
3. I tried including the imported-shared-libraries section in the packaged oc4j-ra.xml, but this gets overwritten as part of the deployment.
4. I removed the above class which gave NoClassDefFoundError and then tried deploying and got the following error
[Apr 19, 2007 7:49:07 PM] Connector Module Deployer for BRMAdapter STARTS.
[Apr 19, 2007 7:49:07 PM] Copy the archive to E:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\BRMAdapter\BRMAdapter.rar
[Apr 19, 2007 7:49:07 PM] Unpacking BRMAdapter.rar
[Apr 19, 2007 7:49:07 PM] Done unpacking BRMAdapter.rar
[Apr 19, 2007 7:49:07 PM] Starting up resource adapter
[Apr 19, 2007 7:49:07 PM] Exception: NoClassDefFoundError: Missing class: oracle.tip.adapter.api.OracleConnectionFactory Dependent class: oracle.tip.adapter.brm.BRMConnectionFactory Loader: BRMAdapter:0.0.0 Code-Source: /E:/product/10.1.3.1/OracleAS_1/j2ee/home/connectors/BRMAdapter/BRMAdapter/BRMAdapter.jar Configuration: in E:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\BRMAdapter\BRMAdapter The missing class is available from the following locations: 1. Code-Source: /E:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar (from in /E:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml) This code-source is available in loader oracle.bpel.common:10.1.3.
[Apr 19, 2007 7:49:07 PM] Operation failed with error: Missing class: oracle.tip.adapter.api.OracleConnectionFactory Dependent class: oracle.tip.adapter.brm.BRMConnectionFactory Loader: BRMAdapter:0.0.0 Code-Source: /E:/product/10.1.3.1/OracleAS_1/j2ee/home/connectors/BRMAdapter/BRMAdapter/BRMAdapter.jar Configuration: in E:\product\10.1.3.1\OracleAS_1\j2ee\home\connectors\BRMAdapter\BRMAdapter The missing class is available from the following locations: 1. Code-Source: /E:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar (from in /E:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml) This code-source is available in loader oracle.bpel.common:10.1.3.
Here is the oc4j-ra.xml i package:
<?xml version="1.0"?>
<oc4j-connector-factories xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.oracle.com/technology/oracleas/schema/oc4j-connector-factories-10_0.xsd"
schema-major-version="10" schema-minor-version="0">
<imported-shared-libraries>
<import-shared-library name="oracle.bpel.common"></import-shared-library>
</imported-shared-libraries>
<connector-factory location="eis/BRM" connector-name="OracleBRMAdapter">
<config-property name="ConnectionString" value="ip blrhpdv3 12006"></config-property>
<config-property name="DBNumber" value="1"></config-property>
<connection-pooling use="none"/>
<security-config use="none"/>
<connectionfactory-interface>
javax.resource.cci.ConnectionFactory
</connectionfactory-interface>
</connector-factory>
</oc4j-connector-factories>
Currently i package orabpel.jar file along with the RA rar file, deploy, later go and modify the oc4j-ra.xml from application-deployments/... to include the imported-shared-libraries, remove the orabpel.jar from the connectors/BRMAdapter directory, restart the AS and it works
Iam using Oracle AS 10.1.3 as part of the SOA Suite.
Any help would be appreciated.

Found a soln, add the codesource to the j2ee instance application.xml
eg adding the following
<imported-shared-libraries>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
solves the problem. Make sure the shared libraries are installed and is added to the instance server.xml
This is described in "Oracle® Containers for J2EE Developer’s Guide 10g (10.1.3.1.0)"
But not sure if the end customers need to be told to edit the configuration file manually.

BPEL & Resource adapter deployment in 10.1.2

Hi,
I have deployed a JCA resource adapter in a 10.1.2 server and it seems that it doesn't get deployed right or, at least, when I test it with a BPEL process, doesn’t work.
I have tested the adapter and the BPEL process in 10.1.3 and works fine, but it doesn't work in 10.1.2. I need to work in 10.1.2 because I'm using the B2B integration suite and this is only available in 10.1.2.
This is what I have done to deploy the adapter:
i. I created the file oc4j-ra.xml in C:\OraHome_1OAS\j2ee\OC4J_BPEL\application-deployments\default\EbMS Adapter
ii. I copied the adapter rar file in C:\OraHome_1OAS\j2ee\OC4J_BPEL\connectors\EbMS Adapter
iii. I update C:\OraHome_1OAS\j2ee\OC4J_BPEL\config\oc4j-connectors.xml
Then, when I try to deploy a BPEL process to test the adapter, I get this error in the log (C:\OraHome_1OAS\integration\orabpel\domains\default\logs\domain.log):
<2007-06-20 09:18:31,984> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Looking up Resource Adapter JNDI location 'eis/ebmsra'
<2007-06-20 09:18:31,984> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JNDI lookup of 'eis/ebmsra' failed due to: eis/ebmsra not found
<2007-06-20 09:18:31,984> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Looking up Resource Adapter JNDI location 'eis/ebmsra'
<2007-06-20 09:18:31,984> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JNDI lookup of 'eis/ebmsra' failed due to: eis/ebmsra not found
<2007-06-20 09:18:32,078> <DEBUG> <default.collaxa.cube.engine.deployment> <DeploymentHelper::deployProcess> failed because
java.lang.Exception: Problem 1: [EBMSOutgoing.wsdl]: Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/ebmsra'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/ebmsra. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server
     at oracle.tip.adapter.fw.validation.WSDLDeploymentValidation.performDeploymentWsdlValidation(WSDLDeploymentValidation.java:144)
     at com.collaxa.cube.engine.deployment.DeploymentHelper.performPreDeploymentActions(DeploymentHelper.java:578)
     at com.collaxa.cube.engine.deployment.DeploymentHelper.deployProcess(DeploymentHelper.java:350)
     at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deployProcess(BPELDomainManagerBean.java:412)
     at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.deployProcess(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2300)
     at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:303)
     at deployProcess.jspService(_deployProcess.java:136)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
<2007-06-20 09:18:32,078> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "domain manager": Error deploying BPEL archive.
An error occurred while attempting to deploy the BPEL archive file "bpel_EBMSOutgoingSample_v2007_06_19__39432.jar"; the exception reported is: Problem 1: [EBMSOutgoing.wsdl]: Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/ebmsra'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/ebmsra. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server
ORABPEL-05207
Error deploying BPEL archive.
An error occurred while attempting to deploy the BPEL archive file "bpel_EBMSOutgoingSample_v2007_06_19__39432.jar"; the exception reported is: Problem 1: [EBMSOutgoing.wsdl]: Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/ebmsra'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/ebmsra. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server
     at com.collaxa.cube.engine.deployment.DeploymentHelper.deployProcess(DeploymentHelper.java:363)
     at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deployProcess(BPELDomainManagerBean.java:412)
     at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.deployProcess(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2300)
     at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:303)
     at deployProcess.jspService(_deployProcess.java:136)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
<2007-06-20 09:19:18,515> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::insert> Received no-op message
<2007-06-20 09:19:18,515> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::adjustThreadPool> Allocating 1 thread(s); pending threads: 1, active threads: 0, total: 5
<2007-06-20 09:19:18,515> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::getConnection> Fetched a queue connection from pool java:comp/env/jms/collaxa/BPELWorkerQueueFactory, available connections=24, total connections=25
<2007-06-20 09:19:18,515> <DEBUG> <default.collaxa.cube.engine.dispatch> <DispatcherBean::send> Sent message to queue
<2007-06-20 09:19:18,515> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::releaseConnection> Released queue connection to pool java:comp/env/jms/collaxa/BPELWorkerQueueFactory, available connections=25, total connections=25
As I see that I have deployed the connector in C:\OraHome_1OAS\j2ee\OC4J_BPEL, but the BPEL process is been deployed in C:\OraHome_1OAS\integration\orabpel, I try to deploy the connector in C:\OraHome_1OAS\integration\orabpel\system\appserver\oc4j\j2ee\home. I copied the "connectors" and "application-deployments" directories into C:\OraHome_1OAS\integration\orabpel\system\appserver\oc4j\j2ee\home (because didn't exist) and updated the C:\OraHome_1OAS\integration\orabpel\system\appserver\oc4j\j2ee\home\config\oc4j-connectors.xml, but I still get the same error.
Anybody can help me?
Thanks,
Miguel

Hi miquel,
I'm working in 10.1.3.1 environmen and wanna develop a custom JCA adapter. Can you show me some hits/reference for JCA adapter in 10.1.3.1?
Steven

JCA Resource Adapter Deployment in OAS 10.1.2

Hi,
I have installed the Oracle Application Server 10g Release 2 (10.1.2) (j2ee & web cache) and I want to know how I can deploy a JCA Resource Adapter. Until now I have work with Oracle Application Server 10g Release 3 (10.1.3.1.0) and this version has a section in the administration web (applications->Standalone Resource Adapters) where I can deploy the RA.
But now, I have to deploy a Resource adapter in OAS 10.1.2 and I don't know how to do it. Any help?
Thanks,
Miquel

Is there any error or warning message in WLS server log related to your adapter? WLS may ignore some properties if found non-fundamental error.

ClassCastException by using deployed resource adapter

Dear community team,
I try to create an connection for my web application (war file) running on SAP Web Application Server to access an enterprise information system (Apache JackRabbit) by using JCA and deployed resource adapter. The resource adapter "jackrabbit-jca-1.3.3.rar " is provided Apache Jackrabbit.
http://jackrabbit.apache.org/downloads.cgi
I changed some deployment descriptor configuration and deployed it successfully by using Deployment Tools. With the Visual Administrator I also could check the JNDI object and finded an entry in connector container.
The JNDI lookup worked fine and it returned a object type "JCARepositoryHandle" (I could analyse its type and attributes in debugging modus).If I tried to cast the object "JCARepositoryHandle", I got an ClassCastException.
Do you have any adoption why I only saw the returned object "JCARepositoryHandle" in debugging modus but it wasnt possible cast and to use it.
If you need any more information, please let me know.
Thanks for your support.
PS: Please have also a look in the attached source an configuration files:
Java servlet class
===================================================================
Connection connection = null;
      Context initctx = null;
         try {
          //get the initial JNDI context
          Hashtable env = null;
          initctx = new InitialContext();
         // perform JNDI lookup to get the connection factory
         JCARepositoryHandle rep = (JCARepositoryHandle)initctx.lookup("deployedAdapters/jcr/Repository/shareable/jcr/Repository");
connector-j2ee-engine.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector-j2ee-engine SYSTEM 'connector-j2ee-engine.dtd'>
<connector-j2ee-engine>
     <jndi-name>jcr/Repository</jndi-name>
     <pool-params>
          <max-connections-number>10</max-connections-number>
          <max-time-to-wait-connection>120</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>900</connection-lifetime>
               <run-cleanup-thread>300</run-cleanup-thread>
          </expiration-control>
     </pool-params>
</connector-j2ee-engine>
ra.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE connector PUBLIC
        '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN'
        'http://java.sun.com/dtd/connector_1_0.dtd'>
    <connector>
      <display-name>Jackrabbit JCR Adapter</display-name>
      <vendor-name>Apache.org</vendor-name>
      <spec-version>1.0</spec-version>
      <eis-type>JCR Adapter</eis-type>
      <version>1.6</version>
      <license>
        <description>Not required</description>
        <license-required>false</license-required>
      </license>
      <resourceadapter>
        <managedconnectionfactory-class>org.apache.jackrabbit.jca.JCAManagedConnectionFactory</managedconnectionfactory-class>
        <connectionfactory-interface>javax.jcr.Repository</connectionfactory-interface>
        <connectionfactory-impl-class>org.apache.jackrabbit.jca.JCARepositoryHandle</connectionfactory-impl-class>
        <connection-interface>javax.jcr.Session</connection-interface>
        <connection-impl-class>org.apache.jackrabbit.jca.JCASessionHandle</connection-impl-class>
        <transaction-support>XATransaction</transaction-support>
        <config-property>
          <config-property-name>HomeDir</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>C:/temp/repository</config-property-value>
        </config-property>
        <config-property>
          <config-property-name>ConfigFile</config-property-name>
          <config-property-type>java.lang.String</config-property-type>
          <config-property-value>C:/temp/repository/repository.xml</config-property-value>
        </config-property>
        <reauthentication-support>false</reauthentication-support>
      </resourceadapter>
    </connector>

The reason for the ClassCastException was the class loader issue.

Deploying a custom JCA 1.5 resource adapter...

I am developing a custom resource adapter that will be deployed in OC4J 10.1.3.0.0. When starting OC4J, I receive the following error:
Unable to find connection definition in ra.xml for connectionfactory interface specified in connection-factory element: bmv.ipc.ra.IpcConnectionFactory.
Does anyone have experience deploying custom resource adapters? Also, does anyone know the earliest version of OC4J that supports JCA 1.5?
Thank you,
Jason
Here is my oc4j-ra.xml file:
<oc4j-connector-factories xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.oracle.com/technology/oracleas/schema/oc4j-connector-factories-10_0.xsd" schema-major-version="10" schema-minor-version="0" >
<connector-factory location="eis/bmvIpcRa" connector-name="bmvIpcRa">
<security-config use="none">
</security-config>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
</connector-factory>
</oc4j-connector-factories>
And a snippet of my ra.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<connector xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
version="1.5">
<display-name>IpcResourceAdapter</display-name>
<vendor-name>...</vendor-name>
<eis-type>...</eis-type>
<resourceadapter-version>1.0</resourceadapter-version>
<license>
<license-required>false</license-required>
</license>
<resourceadapter>
<resourceadapter-class>
bmv.ipc.ra.IpcResourceAdapter
</resourceadapter-class>
<outbound-resourceadapter>
<connection-definition>
<managedconnectionfactory-class>
bmv.ipc.ra.IpcManagedConnectionFactory
</managedconnectionfactory-class>
<config-property>
<config-property-name>Path</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>/tmp/outbound</config-property-value>
</config-property>
<connectionfactory-interface>
javax.resource.cci.ConnectionFactory
</connectionfactory-interface>
<connectionfactory-impl-class>
bmv.ipc.ra.IpcConnectionFactory
</connectionfactory-impl-class>
<connection-interface>
javax.resource.cci.Connection
</connection-interface>
<connection-impl-class>
bmv.ipc.ra.IpcConnection
</connection-impl-class>
</connection-definition>
<transaction-support>NoTransaction</transaction-support>
<reauthentication-support>false</reauthentication-support>
</outbound-resourceadapter>

Nevermind, it appears that OC4J was using an incorrect oc4j-ra.xml that was stored in <OC4J_HOME>\j2ee\home\application-deployments\default\<my_rar_file_folder_name>\oc4j.xml
when I deployed my initial testing.

Deploying a resource adapter

Hello,
i have developed and successfully deployed a resource adapter. But as i went on developing i encountered some strange behaviour.
In the DeployTool that i used to deploy the adapter i have build the archives again and deployed the EAR to the WAS 640 successfully. But if i ran my Test coding against it, my changes have not be set online.
So i deleted the DeployProject and created a new one, that i deployed to the was640 and now my changes are online.
I have searched for a refresh button to load updated resources, but i could not find any. Did i miss anything in the DeployTool? Besides the DeployTool also comes up with some error messages like IOException, FileNotFound from a generated file *.mf!
Is it possible to deploy a resource adapter from within the NetWeaver Studio? Or anything else, that is more stabil?
Best regards
Christian

Hi Christian,
Currently there's no straight-forward way to add a resource adapter (RAR) into an application project (EAR) in the NW Developer Studio. But you can build the JAR of the connector Java project, build the EAR for the application project (it can contain also the JAR of your EJB module project), then rename the connector JAR to RAR and add it manually to the EAR file, and modify the application.xml as you already did
<module>
<connector>raresourceDB.rar</connector>
</module>
(You don't have to use the alternative DD option.)
Then you can use any of the tools mentioned above to deploy the EAR. The simplest (and most reliable) way is via the J2EE telnet console, but you can also use the Admin Tool or the SDM GUI.
Hope it helps,
Vladimir

Deploying resource adapter

          Getting an error, trying to deploy a resource adapter.
          Here's the log and exception below.
          Log
          preparing application TestRA on testServer
          Exception caught for task Activate application TestRA on testServer: Prepare failed.
          Task Id = 10
          Module, myRA, reported error: java.lang.NullPointerException
          failed application TestRA on testServer
          Exception
          weblogic.management.ApplicationException: Prepare failed. Task Id = 10
          Module Name: myRA, Error: java.lang.NullPointerException
               at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:638)
               at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:552)
               at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
               at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
               at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)


          "Madhav Inamti" <[email protected]> wrote:
          >
          >Getting an error, trying to deploy a resource adapter.
          >
          >Here's the log and exception below.
          >
          >Log
          >---
          >
          >preparing application TestRA on testServer
          >Exception caught for task Activate application TestRA on testServer:
          >Prepare failed.
          >Task Id = 10
          >Module, myRA, reported error: java.lang.NullPointerException
          >failed application TestRA on testServer
          >
          >Exception
          >---------
          >
          >weblogic.management.ApplicationException: Prepare failed. Task Id = 10
          >{
          >Module Name: myRA, Error: java.lang.NullPointerException
          >}
          >     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:638)
          >     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:552)
          >     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
          >     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
          >     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
          >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          >
          It may caused by your jca code, for example, write to a log writer before the
          log writer is set by WLS.

Resource Adapter Deployment Error (Resolved)

This Problem Has Been Resolved.
I'm trying to develop an application using Inbound resource adapters on Weblogic 9.2.1 .
I have the resource adapter and the MDB packaged separately. The MDB appears to deploy successfully, but the resource adapter does not.
I get the following exception
javax.naming.NamingException [Root exception is java.rmi.RemoteException: javax.naming.InitialContext; nested exception is:
     java.io.NotSerializableException: javax.naming.InitialContext]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:97)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:421)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:297)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:389)
     at weblogic.connector.deploy.JNDIHandler.bindRA(JNDIHandler.java:575)
     at weblogic.connector.common.RAInstanceManager.putRAintoJNDITree(RAInstanceManager.java:1361)
     at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:432)
     A similar issues was referenced in this message :
     http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4330872
     It appears that the exception means the InitialContext is not serializable.
     This is my start(BootstrapContext) method in my resource adapter. If I DO NOT call new InitialContext(), or setMDBOnMessageMethod(), the exception does not occur.
public void start(BootstrapContext ctx)
     this.ctx = ctx;
     System.out.println("entering AddScanResourceAdapterImpl start");
     logger.info("entering AddScanResourceAdapterImpl start");
     try
     this.JNDIContext = new InitialContext(); // This causes the exception.
     this.wm = this.ctx.getWorkManager(); // Calling this does not cause and exception.
     setMDBOnMessageMethod(); // This also appears to cause the same exception.
     catch (Exception e)
          System.out.println("AddScanRA start : Exception thrown: " + e);
     // TODO: Log problem.
     logger.info("exiting AddScanResourceAdapterImpl start");
private void setMDBOnMessageMethod()
try
Class socketListenerClass = com.fedex.ground.tms.mtms.server.addscan.connector.ra.AddScanSocketHandler.class;
Class[] paramTypes      = { java.net.Socket.class };
this.onMessageMethod      = socketListenerClass.getMethod("onMessage", paramTypes);
catch (NoSuchMethodException ex)
ex.printStackTrace();
Thanks for your any help,
John
Edited by johnbrod20 at 04/17/2007 6:48 AM

Hi John,
One of my customer is facing the same error .
Can you please share the resolution of this problem

WebLogic Server 10.0 MP1: Error in resource adapter deployment

When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
An error occurred during activation of changes, please see the log for details.
weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
java.util.logging.LoggingPermission.(java.lang.String)
The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
permission javax.management.MBeanTrustPermission "register";
permission java.util.logging.LoggingPermission "control";
When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
For me this seems to be a bug in WebLogic 10.0MP1.
Best,
Manfred

Re: Installation error: Weblogic Server 10.0 MP2

Resource Adapter deployment on cluster

Hi,
I have a weblogic cluster with 2 nodes and a load balancer. Recently I have deployed a database adapter to connect to a sql server database which is used by a service (OSB proxy service). The deployed was performed with both nodes running and I connected to the admin console using the LB IP. The deployed was done with successful and I have restarted both nodes. The cluster is configured with a stage mode in order to copy files from admin server.
When I call this service, it goes ok when node1 is used but not ok when node2 is used. It gives an JCA error accessing the sql server database. To solve this issue I had to copy the deployment plan file from node1 to node2 and reploy de dbadapter resource with node1 down in order to update the node2. I was expecting that these files were updated on both nodes whenever I deploy a resource adapter on admin console.
What am I doing wrong? Or what config should I check/update on admin console in order to avoid this manual task?
Thanks,
Regards,
António Amado

Use the shared location for deployment plans.
Please see the link : Managing the Topology for an Enterprise Deployment - 11g Release 1 (11.1.1)

Deployment of standalone Resource Adapter

I've deployed a standalone resource adapter on my application server. I
have a web application that accesses it. I have a client.jar in the libs
directory of the web application which contains the class for
SquareInteractionSpecImpl which is needed by the web app. I can get the
web app to build with the jar in the classpath. When I deploy it though
I get
ResourceException caught: javax.resource.ResourceException: Bad
Interaction Spec
The InteractionSpec is the exact same as the one in the jar file of the
rar for the resource adapter. Why is this happening?
Regards
Ivan Kelly

My RA runs correctly after deployment, I can see my RA in the JNDI tree.
I just did some more tests.
I use the following way to look up:
InitialContext ctx = new InitialContext();
ConnectionFactory cf = (ConnectionFactory) ctx.lookup("MyConnectionFactory");
If I look up it in an EJB, I can get the object.
But when I look up in a servlet, no object can be found.
The servlet is in a war embeded in the ear.

Anyone tried to deploy IBM's Java resource adapter for IMS on WLS6.1sp2?

          Has anyone had success or attempted to deploy the IMS Connector
          for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          use this to connect WebLogic to IMS via IMS Connect 1.2?
          Thanks
          Sam


          "Sam Naylor" <[email protected]> wrote:
          >
          >Has anyone had success or attempted to deploy the IMS Connector
          >for Java (IBM's resource adapter) on WLS6.1sp2? I would like to
          >use this to connect WebLogic to IMS via IMS Connect 1.2?
          >
          >Thanks
          >Sam
          Sam,
          I was wondering if you were able to use the IMN Connector RAR file. I was able
          to deploy but that was teh extent of my effort.
          Appreciate you insight!

Installing a J2EE compliant resource adapter

Hi,
          Do I need to install weblogic application Intergrator to install a
          resource adapter.
          Means, I have 2 files, one is rar and another is war which together forms
          the resource adapter
          that I want to deploy in weblogic. To deploy this do I need to install WLAI,
          or just installing weblogic will work ?
          If I can deploy it without installing WLAI, then how do I do that ?
          Thanks
          Amit Chauhan


Thanks a lot Mitch.
          Amit Chauhan
          eTouch System
          510-795-4800 ext 113
          Mitch Upton <[email protected]> wrote in message
          news:[email protected]...
          >
          > If you intend to use the value-added features that you get when writing an
          > adapter with the WLI ADK, then yes, you need to run in WLI. You can still
          use
          > your adapter in plain WLS 6.0 with Connector Beta or WLS 6.1 betas and
          beyond.
          > However, without WLI you cannot use Application Views, events, or
          asynchronous
          > invocation of services. You will need to use your adapters CCI (or other)
          client
          > interface directly. Bear in mind that you can use CCI only from within the
          > server VM (not from a client VM). To use the adapter remotely you must
          either
          > use an ApplicationView, or a customer EJB/web app that wraps your adapter.
          >
          > Mitch
          >
          > Amit wrote:
          >
          > > Hi,
          > > Do I need to install weblogic application Intergrator to install a
          > > resource adapter.
          > > Means, I have 2 files, one is rar and another is war which together
          forms
          > > the resource adapter
          > > that I want to deploy in weblogic. To deploy this do I need to install
          WLAI,
          > > or just installing weblogic will work ?
          > > If I can deploy it without installing WLAI, then how do I do that ?
          > >
          > > Thanks
          > > Amit Chauhan
          >
          > --
          > Mitch Upton
          > Architect - Application Integration
          > BEA Systems
          > Denver, 5th Floor
          > [email protected]
          > (720)528-6087
          >
          >

JCA Resource adapter deployment in Weblogic server

Hi,
I have deployed a resource adapter successfully in Weblogic server and works fine.My resource adapter has weblogic-ra.xml and ra.xml available under meta-inf folder.I have provided some properties in weblogic-ra.xml and ra.xml but unable to see the same properties when i open the resource adapter settings page in the the weblogic administration console
I want to change resource adapter properties from weblogic adminstration console but dont see the properties which i used during deployment.
Can someone help with identifying the issue or if i have to do something different.
Appreciate any help.
Thanks
S

Not sure what might be causing this behavior. Property values in ra/weblogic-ra.xml should be displayed on the console (http://machine:port/console). I think I have experienced similar issue only to realize that console only displays 10 properties and other properties are displayed after pressing Next link on the page.
How many proprieties you have? What are getting displayed and what properties are not getting displayed?
Manoj

Deploying J2E CA 1.0 Resource Adapter on 11g

Similar Messages

Maybe you are looking for