JCA-deployment in Weblogic8.1

We deployed the kodo.rar in Weblogic 8.1
When executing the JNDI-lookup to retrieve the PersistenceManagerFactory
we get the following exception:
java.lang.IllegalStateException: No reference found for "-1104443365".
at
kodo.ee.JDOObjectFactory.getObjectInstance(JDOObjectFactory.java:44)
at
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:257)
at
weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:357)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
1104443365 is the hash code of the connector in the jndi-tree.
An idea what causes this?

Mallezie-
I've never seen that error before. What version of Kodo are you using?
Do you see this with any other resource adapters?
What is the exact API call you are using?
Also, if you manually create and bind a Kodo PersistenceManagerFactory
instance into Weblogic's JNDI and then look it up again, do you still
see the same error?
In article <d1euin$csg$[email protected]>, Mallezie Frank wrote:
>
We deployed the kodo.rar in Weblogic 8.1
When executing the JNDI-lookup to retrieve the PersistenceManagerFactory
we get the following exception:
java.lang.IllegalStateException: No reference found for "-1104443365".
at
kodo.ee.JDOObjectFactory.getObjectInstance(JDOObjectFactory.java:44)
at
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:257)
at
weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:357)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
1104443365 is the hash code of the connector in the jndi-tree.
An idea what causes this?
Marc Prud'hommeaux
SolarMetric Inc.

Similar Messages

  • Need help: JCA deployment unsuccessful using dcmctl

    I am using the command line tool dcmctl with the deployApplication option to deploy a standalone JCA resource adapter. I am having some problems with lookup of this JCA from EJB.
    I execute the command:
    dcmctl deployApplication –f my_jca.rar –a my_jca
    The output I get:
    Application: my_jca
    Component Name: home
    Component Type: OC4J
    Instance: myinstance.mycompany.com
    At the end of it, I see the logfiles and it seems like the jca deployment went thru ok. But, when I use my ejb, I keep getting the message that my_jca not found (com.evermind.server.rmi.OrionRemoteException).
    Under what JNDI tree is this jndi name my_jca to be found? How do we lookup for this? How do I know what went wrong in my lookup. The same jca works well with all other appservers.
    Here is the ra.xml I have. DO I need to provide a vendor specific descriptor? OC4J deploys one automatically so I didn't supply one:
    <?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 id="Connector_ID">
          <display-name>my_jca</display-name>
          <description>My JCA</description>
          <vendor-name>my company</vendor-name>
          <spec-version>1.0</spec-version>
          <eis-type>DCOM Applications</eis-type>
          <version>1.0</version>
          <license>
             <license-required>false</license-required>
          </license>
          <resourceadapter id="J2CResourceAdapter_ID">
             <managedconnectionfactory-class>com.intrinsyc.jca.JintManagedConnectionFactory</managedconnectionfactory-class>
             <connectionfactory-interface>com.intrinsyc.jca.ConnectionFactory</connectionfactory-interface>
             <connectionfactory-impl-class>com.intrinsyc.jca.JintConnectionFactory</connectionfactory-impl-class>
             <connection-interface>com.intrinsyc.jca.Connection</connection-interface>
             <connection-impl-class>com.intrinsyc.jca.JintConnection</connection-impl-class>
             <transaction-support>NoTransaction</transaction-support>
             <authentication-mechanism id="AuthenticationMechanism_1067225162993">
                <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
                <credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
             </authentication-mechanism>
             <reauthentication-support>false</reauthentication-support>
             <security-permission id="SecurityPermission_1067117771153">
                <description>testing with all</description>
                <security-permission-spec>grant { permission java.security.AllPermission; };</security-permission-spec>
             </security-permission>
          </resourceadapter>
       </connector>

    I am using the command line tool dcmctl with the deployApplication option to deploy a standalone JCA resource adapter. I am having some problems with lookup of this JCA from EJB.
    I execute the command:
    dcmctl deployApplication –f my_jca.rar –a my_jca
    The output I get:
    Application: my_jca
    Component Name: home
    Component Type: OC4J
    Instance: myinstance.mycompany.com
    At the end of it, I see the logfiles and it seems like the jca deployment went thru ok. But, when I use my ejb, I keep getting the message that my_jca not found (com.evermind.server.rmi.OrionRemoteException).
    Under what JNDI tree is this jndi name my_jca to be found? How do we lookup for this? How do I know what went wrong in my lookup. The same jca works well with all other appservers.
    Here is the ra.xml I have. DO I need to provide a vendor specific descriptor? OC4J deploys one automatically so I didn't supply one:
    <?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 id="Connector_ID">
          <display-name>my_jca</display-name>
          <description>My JCA</description>
          <vendor-name>my company</vendor-name>
          <spec-version>1.0</spec-version>
          <eis-type>DCOM Applications</eis-type>
          <version>1.0</version>
          <license>
             <license-required>false</license-required>
          </license>
          <resourceadapter id="J2CResourceAdapter_ID">
             <managedconnectionfactory-class>com.intrinsyc.jca.JintManagedConnectionFactory</managedconnectionfactory-class>
             <connectionfactory-interface>com.intrinsyc.jca.ConnectionFactory</connectionfactory-interface>
             <connectionfactory-impl-class>com.intrinsyc.jca.JintConnectionFactory</connectionfactory-impl-class>
             <connection-interface>com.intrinsyc.jca.Connection</connection-interface>
             <connection-impl-class>com.intrinsyc.jca.JintConnection</connection-impl-class>
             <transaction-support>NoTransaction</transaction-support>
             <authentication-mechanism id="AuthenticationMechanism_1067225162993">
                <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
                <credential-interface>javax.resource.spi.security.PasswordCredential</credential-interface>
             </authentication-mechanism>
             <reauthentication-support>false</reauthentication-support>
             <security-permission id="SecurityPermission_1067117771153">
                <description>testing with all</description>
                <security-permission-spec>grant { permission java.security.AllPermission; };</security-permission-spec>
             </security-permission>
          </resourceadapter>
       </connector>

  • Deployment in Weblogic8.1 Falied due to EJB-QL

    Hi,
    While depolying the application on Weblogic 8.1 Sp2, am getting WARNING(S) from EJB QL Compiler.
    for instance :
    [EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
    Query:
    EJB Name: EOTransactionBean
    Method Name: findByEoNum
    Parameter Types: (java.lang.String)
    SELECT o FROM EOTransactionBean o WHERE =>> eoNum <<= = ?1
    EJB QL compilation encountered error: [EJB:013080]
    Problem, the path expression/Identifier 'eoNum' starts with an identifier: 'eoNum'. The identifier 'eoNum', which can be either a range variable identifier or a collection member identifier, is required to be declared in the FROM clause of its query or in the FROM clause of a parent query. 'eoNum' is not defined in the FROM clause of either its query or in any parent query.
    Action, rewrite the query paying attention to the usage of 'eoNum'.
    ==========================================================
    How can I overcome this? Is there a workaround for this? I read that there is a temporary patch available for this. If so please help. Thanks.
    Regards,
    David

    you can try with this query
    select object(o) from EOTransancationBean As o where o.eoNum >= or <= ?1

  • Getting runtime error when i am deploying my ear file in weblogic8.1

    I deployed my ear file into weblogic server, the below error i got in console of weblogic server. please tell where i need to setup class path. I am using eclipse as IDE and running the project in eclipse.
    How can i set classpath in weblogic server ? Give me step by step please.
    <May 25, 2006 8:13:45 PM GMT+05:30> <Error> <HTTP> <BEA-101017> <[ServletContext(id=19766836,name=MarketFusionCom.war,context-path=)] Root cause of ServletException.
    weblogic.servlet.jsp.CompilationException: Compilation of C:\bea\user_projects\domains\mydomain\marketfusioncom\jsp_servlet\__index.java failed.java.io.IOException: CreateProcess: javac -classpath "C:\bea\user_projects\domains\mydomain\MarketFusionServer\.wlnotdelete\extract\MarketFusionServer_MarketFusionCom_MarketFusionCom.war\MarketFusionCom.war;C:\bea\user_projects\domains\mydomain\MarketFusionServer\.wlnotdelete\MarketFusionCom\MarketFusionCom.jar;marketfusioncom;C:\Program Files\Java\j2re1.4.2_01\lib\rt.jar;C:\Program Files\Java\j2re1.4.2_01\lib\i18n.jar;C:\Program Files\Java\j2re1.4.2_01\lib\sunrsasign.jar;C:\Program Files\Java\j2re1.4.2_01\lib\jsse.jar;C:\Program Files\Java\j2re1.4.2_01\lib\jce.jar;C:\Program Files\Java\j2re1.4.2_01\lib\charsets.jar;C:\Program Files\Java\j2re1.4.2_01\classes;C:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\weblogic81\server\lib\wlcipher.jar;C:\bea\weblogic81\server\lib\jsafeFIPS.jar;C:\bea\weblogic81\server\lib\webservices.jar;C:\bea\weblogic81\server\lib\xmlx.jar;C:\bea\weblogic81\server\lib\ojdbc14.jar;C:\bea\weblogic81\server\lib\jconn2.jar;C:\bea\weblogic81\server\lib\jConnect.jar;C:\bea\weblogic81\server\lib\EccpressoAsn1.ja?
    at java.lang.Win32Process.create(Native Method)
    at java.lang.Win32Process.<init>(Unknown Source)
    at java.lang.Runtime.execInternal(Native Method)
    at java.lang.Runtime.exec(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at weblogic.utils.Executable.exec(Executable.java:227)
    at weblogic.utils.Executable.exec(Executable.java:156)
    at weblogic.utils.Executable.exec(Executable.java:142)
    at weblogic.utils.compiler.CompilerInvoker.execCompiler(CompilerInvoker.java:249)
    at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:428)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:321)
    at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:451)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:196)
    at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:598)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:406)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:478)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
    at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:196)
    at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:598)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:406)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: java.io.IOException: Compiler failed executable.exec
    at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:321)
    at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:451)
    ... 12 more
    >

    Hi i got this same problem and i solved this
    weblogic8 containing ejbcompiler supports only the jdk1.4 versioning class files
    so plz compile u r java file with jdk1.4 version and deploy in weblogic8 . u r problem will be solved
    Regards
    Srinivasa Rao.Teki
    Software Engineer
    ITON Technologies
    Tanuku, W.G.Dt, A.P,India
    GSM: 9885504303 (+91)

  • Deployment validation failing to load DTDs for Struts

    I created a fresh webapp that includes the Struts 1.2.2 binaries and got some errors when deploying on WebLogic8.1sp3. My guess is that I need to configure some proxy setting in weblogic.
    Sep 7, 2004 4:07:14 PM org.apache.struts.tiles.TilesPlugin initDefinitionsFactoryINFO: Tiles definition factory loaded for module ''.
    Sep 7, 2004 4:07:14 PM org.apache.struts.validator.ValidatorPlugIn initResources
    INFO: Loading validation rules file from '/WEB-INF/validator-rules.xml'
    Sep 7, 2004 4:07:14 PM org.apache.struts.validator.ValidatorPlugIn initResources
    INFO: Loading validation rules file from '/WEB-INF/validation.xml'
    <Sep 7, 2004 4:07:14 PM CDT> <Warning> <Net> <BEA-000905> <Could not open connection with host: jakarta.apache.org and port: 80.>
    Sep 7, 2004 4:07:14 PM org.apache.struts.validator.ValidatorPlugIn init
    SEVERE: Tried all: '1' addresses, but could not connect over HTTP to server: 'jakarta.apache.org', port: '80'
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'jakarta.apache.org', port: '80'
    at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
    at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
    I copied the referenced .DTDs locally and after adding the full path to the local copies, things worked fine. Unfortunately this is just a big hack. I would like to know either:
    1. how to package the things so that a local copy of the DTDs that I include in a .ear file can be found, or
    2. how to configure proxy settings in weblogic so I can validate against remote DTDs.
    Any ideas?

    the exception seems to suggest that you cant connect to the outside world. Can you check if you can connect to the mentioned remote server from your deployment machine ?
    anand

  • J2EE Deployment Exception

    Hi
    We are trying to deploy the a XI JCA adapter code into PI7.0 server. The SDM logs showed the following warning during deployment. Can anyone advise on the possible reason for this warning
    May 28, 2008 4:16:19 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 28, 2008 4:16:22 PM  Info: Begin of log messages of the target system:
    08/05/28 16:16:19 -  ***********************************************************
    08/05/28 16:16:20 -  Start updating EAR file...
    08/05/28 16:16:20 -  start-up mode is lazy
    08/05/28 16:16:20 -  EAR file updated successfully for 63ms.
    08/05/28 16:16:20 -  Start deploying ...
    08/05/28 16:16:21 -  EAR file uploaded to server for 216ms.
    08/05/28 16:16:21 -  Successfully deployed. Deployment took 501ms.
    08/05/28 16:16:21 -    Application : sap.com/com.sap.aii.af.edi.adapter.ra
    08/05/28 16:16:21 -   
    08/05/28 16:16:21 -    com.sap.aii.af.edi.adapter.ra  - LOGGING CONFIGURATION
    08/05/28 16:16:21 -    edi_ra  - CONNECTOR
    08/05/28 16:16:21 -  ***********************************************************
    May 28, 2008 4:16:22 PM  Info: End of log messages of the target system.
    May 28, 2008 4:16:22 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 28, 2008 4:16:22 PM  Warning:
    Finished with warnings: development component 'com.sap.aii.af.edi.adapter.ra'/'sap.com'/'SAP AG'/'7.0010.20080227062718.0000'/'0':
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException:
    Error occurred while starting application sap.com/com.sap.aii.af.edi.adapter.ra and wait.
    Reason: Clusterwide exception: server ID 5497750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException:
    Exception while preparing start of application sap.com/com.sap.aii.af.edi.adapter.ra.
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:233)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoClassDefFoundError: com.sun.enterprise.repository.ResourceAdapter
         at java.lang.Class.getDeclaredMethodsImpl(Native Method)
         at java.lang.Class.getDeclaredMethods(Class.java:885)
         at java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1737)
         at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:97)
         at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:252)
         at java.security.AccessController.doPrivileged(AccessController.java:187)
         at java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:249)
         at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:690)
         at java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:622)
         at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1196)
         at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1131)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1332)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1083)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1423)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1395)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1338)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1083)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:309)
         at com.sap.engine.services.jndi.persistent.RemoteSerializator.toByteArray(RemoteSerializator.java:48)
         at com.sap.engine.services.jndi.implclient.ClientContext.serializeObject(ClientContext.java:3332)
         at com.sap.engine.services.jndi.implclient.ClientContext.serializeDirObject(ClientContext.java:3224)
         at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:778)
         at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:715)
         at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:924)
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.bind(DeployAdmin.java:1549)
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.bindMCF(DeployAdmin.java:2209)
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.registerConnector(DeployAdmin.java:1886)
         at com.sap.engine.services.connector.jca.deploy.ContainerImpl.prepareStart(ContainerImpl.java:1144)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Thanks in advance...

    Caused by: java.lang.NoClassDefFoundError: com.sun.enterprise.repository.ResourceAdapter
    This dependency needs to be resolved .
    I think you have not deployed the library containing this dependency.

  • Error in ear deployment weblogic9.2

    Hi..
    When i try to deploy an ear in weblogic9.2 im repeatedly getting these 2 error messages -
    1)Unable to access the selected application
    2)No name parameter specified
    the steps i followed are
    i selected the install option in deployments menu and i selected the ear file and clicked on next.
    i get these error messages here.
    i dont get any error message when deploying in weblogic8.1.
    kindly help me out in this
    Arun

    Yes i have used :
    import com.sap.aii.af.mp.module.Module;
    import com.sap.aii.af.mp.module.ModuleContext;
    import com.sap.aii.af.mp.module.ModuleData;
    import com.sap.aii.af.mp.module.ModuleException;
    also in the build Build path; i have the "aii_af_mp.jar". Though in EAR i have removed all added jar file except the one jar file which is not provided by SAP. As mentioned in Adapter module dev guide.
    Do you think adding that jar file could solve the issue.
    Thanks
    Ankur

  • JSF compatibility with Weblogic8.1

    Hi,
    I've a question regarding JSF compatibility with Weblogic 8.1.
    I'm developing web application using JSF and Rich Faces.I'm using rich faces 3.2 and JSF 1.2. And i'm calling services which is written using JDK1.4 and deployed on weblogic8 .
    So I'm worried whether I can deploy my JSF web application on Weblogic 8.1 or not ? I don't know which version of Servlet API JSF uses,I believe if it uses 2.3 then
    it might be compatible with Weblogic8.1
    Please let me know any info about this ?
    Thanks,
    Anand

    So can I use Servlet 2.3 with JSF 1.2 at Facelets. Will it work ?
    As I've google some of the sites and it seems Weblogic 8.1 supports JEE 1.3 technologies and JEE1.3 is fully compliant with the Servlet 2.3 specification only.
    So I'm not sure if my application which has presentation layer developed using JSF/facelet could be deployed on weblogic 8.1 or not?

  • Fail to test JCA proxy

              Hi,
              We are developing JCA to work with WebLogic 8.1.0.0.
              The JCA deployed successfully, but at the server console the following message
              displayed:
              <Jul 23, 2003 2:44:29 PM IDT> <Warning> <Connector> <BEA-190083> <Proxy test failed.
              WLS will not use connection proxies for resource adapter "eis/GigaSpacesCF".>
              When having a session bean using this JCA we see the JCA commit method is not
              called when the session bean method ended.
              This JCA works fine with other J2EE vendors.
              Questions:
              Does WebLogic 8.1 support JCA 1.1 spec?
              What could be the reason for the above problem?
              Would WL 8.1.1.0 might fix this problem?
              Any help would be appreciated.
              Thanks,
              Shay
              Please respond also to: [email protected]
              

              Same thing happened here. And I noticed that if implement CCI and the getConnection
              method of ManagedConnection class returns an CCI Connection object, there won't
              be such proxy warning. I didn't find any information about this proxy thing in
              JCA specification.
              But what I want is return a real CCI connection instead of a proxy object. Is
              it possible?
              

  • Deploy rar fail with ClassNotFoundException

    Hi,
    I try to deploy a resource adapter rar file into WAS using deploytools. In this rar, I have ra.xml/connector-j2ee-engine.xml and jars. I load this as module and deploy. It failed and error message is:
    Reason: Cannot load class "com.iona.jca.core.resourceadapter.CorbaManagedConnectionFactoryImpl".
    some top stacktrace is
         at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1195)
         at com.sap.engine.services.connector.jca.deploy.ContainerImpl.deploy(ContainerImpl.java:414)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
    My class is in the jar, and I can successful deploy into other app servers(JBoss, Weblogic, Webshere..)
    I follow the steps as JRA connection (JRA ConnectionSpecImpl). The only different is it use      
    <loader-name>library:com.sap.mw.jco</loader-name>
    in xml file. My question:
    1. Do I need add my jars into library as reference? If yes, how to do it? I notice there are connector:default in log, but it seems not work?
    2. How to get more log when I deploy? I use Visual Admin tools to change log configure Categories/System/Server and  Location/com.sap.engine.services.deploy lever to ALL. But I can't get more log than before.
    All comment will welcome!
    Thanks
    Jeff

    The exception trace shows that lookup of JNDI resource jdbc/cis failed.
    If you haven't defined a JDBC resource, you will need to do so. For information on how to do that, please see the following blog.
    http://blogs.sun.com/roller/page/theaquarium?anchor=configuring_an_oracle_database_for

  • Deploying weblogic 8.1 app onto another app server

    Is it possible to deploy a weblogic8.1 app onto a different app server such as Tomcat. If so where do I go for documentation on how to do it and what app server do you recommend I use?
    Stephen

    I have same interest in this too. I have looked around for some information, but I have no answer yet about deploying weblogic 8.1 on other server other than weblogic server.
    But, there are some information about deploying weblogic 5.x, 6.x, and some part of 7.x in jboss server. You can check these urls:
    http://wiki.jboss.org/wiki/Wiki.jsp?page=FoeDeployerService
    http://wiki.jboss.org/wiki/Wiki.jsp?page=PortingFromWeblogic
    And for anybody who has had any clue, idea, or any information about deploying weblogic 8.1 (and above) outside weblogic server, please kindly share your knowledge.
    Regards,
    Muhyi

  • Error when Upgrading BI_UDI SP-9  to BI_UDI SP-20 from SDM

    Hi Experts.
    can any one solve my problem its urgent.
    I am trying to upgrade BI_UDI SP-9  to  BI_UDI SP-20,but it is giving me the error.
    The below is the entire log of the Error.
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    <!NAME[D:\usr\sap\BW3\DVEBMGS00\SDM\program\log\sdmlog20070730.log]/>
    <!PATTERN[sdmlog20070730.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Jul 30, 2007 2:34:23 PM  Info:
    Jul 30, 2007 2:34:24 PM  Info: ============================================
    Jul 30, 2007 2:34:24 PM  Info: =   Starting to execute command 'server'   =
    Jul 30, 2007 2:34:24 PM  Info: ============================================
    Jul 30, 2007 2:34:24 PM  Info: Starting SDM - Software Deployment Manager...
    Jul 30, 2007 2:34:25 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4020.00.0000.20070308110902.0000
    Jul 30, 2007 2:34:27 PM  Info: SDM operation mode successfully set to: Integrated
    Jul 30, 2007 2:34:28 PM  Info: JStartupFramework is requesting to start the SDM Server.
    Jul 30, 2007 2:34:28 PM  Info: Start the SDM Server integrated in the JStartupFramework.
    Jul 30, 2007 2:34:28 PM  Info: Initializing Network Manager (50017)
    Jul 30, 2007 2:34:28 PM  Info: Starting SDM Server listening on port 50018
    Jul 30, 2007 2:34:28 PM  Info: SDM started successfully.
    Jul 31, 2007 9:11:50 AM  Info: Opened client connection to HostName (IP address HostName/192.158.3.36, remote port 4072)
    Jul 31, 2007 9:11:50 AM  Info: Request for Logon as admin accepted
    Jul 31, 2007 9:12:26 AM  Info: Loading archive 'E:\sap-download\downloads\javasp20\BIUDI20_0-20000143.SCA'
    Jul 31, 2007 9:12:34 AM  Info: Actions per selected component:
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.monitoring'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.monitoring'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1' updates currently deployed software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.9.0.20041025073430''/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.sys'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.sys'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'bi/mmr/browser_ea'/'sap.com'/'MAIN_BIMMRVAL_D'/'1183786'/'1' will not update currently deployed development component 'bi/mmr/browser_ea'/'sap.com'/'MAIN_BIMMRVAL_D'/'1183786'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkxmla'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkxmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'350.1183777.000'/'1' will not update currently deployed development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'350.1183777.000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.olap'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.olap'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.sync'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.sync'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checksapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checksapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.jdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.jdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.ds'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.ds'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: Initial deployment: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla.proxy.ws'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will be deployed.
    Jul 31, 2007 9:12:34 AM  Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.fields'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.fields'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkjdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkjdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkodbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkodbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.sapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.sapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
    Jul 31, 2007 9:12:34 AM  Info: No action: Selected development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.1183781.000'/'1' will not update currently deployed development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.1183781.000'/'0'.
    Jul 31, 2007 9:12:43 AM  Info: Saved current Engine state.
    Jul 31, 2007 9:12:44 AM  Info: Starting: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
    Jul 31, 2007 9:12:44 AM  Info: SDA to be deployed: D:\usr\sap\BW3\DVEBMGS00\SDM\root\origin\sap.com\com.sap.ip.bi.sdk.dac.connector.xmla\SAP AG\1\350.20070308111013.0000\bi_sdk_xmla.rar
    Jul 31, 2007 9:12:44 AM  Info: Software type of SDA: single-module
    Jul 31, 2007 9:12:45 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Module) *****
    Jul 31, 2007 9:18:24 AM  Info: Begin of log messages of the target system:
    07/07/31 09:14:05 -  ***********************************************************
    07/07/31 09:14:05 -  Start updating archive file...
    07/07/31 09:14:06 -  Archive file updated successfully for 47ms.
    07/07/31 09:14:06 -  Start updating...
    07/07/31 09:14:21 -  Archive file uploaded to server for 94ms.
    07/07/31 09:18:24 -  ERROR: Not updated. Deploy Service returned ERROR:
    java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.xmla..
    Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:789)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    at com.sap.engine.services.connector.exceptions.BaseDeploymentException.writeReplace(BaseDeploymentException.java:46)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:145)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:314)
    ... 8 more
    For detailed information see the log file of the Deploy Service.
    07/07/31 09:18:24 -  ***********************************************************
    Jul 31, 2007 9:18:24 AM  Info: End of log messages of the target system.
    Jul 31, 2007 9:18:24 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Module) *****
    Jul 31, 2007 9:18:25 AM  Error: Aborted: development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1', grouped by software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1':
    Caught exception during module deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.xmla..
    Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
    at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:774)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
    at java.lang.Class.getMethod(Class.java:986)
    at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
    ... 18 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 31, 2007 9:18:25 AM  Info: Starting to save the repository
    Jul 31, 2007 9:18:25 AM  Info: Finished saving the repository
    Jul 31, 2007 9:18:26 AM  Info: Starting: Update: Selected software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1' updates currently deployed software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.9.0.20041025073430''/'0'.
    Jul 31, 2007 9:18:26 AM  Error: Aborted: software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1':
    Failed deployment of SDAs:
    development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Jul 31, 2007 9:18:26 AM  Info: Starting to save the repository
    Jul 31, 2007 9:18:26 AM  Info: Finished saving the repository
    Jul 31, 2007 9:18:27 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Thanks in Advance
    regards
    Ken

    I have just solved this problem. The symptom is the "No server is running"
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
    The cause for my case is that the server contains more than one NIC. P4 can't bind to correct NIC.
    The solution is to follow SAP Notes 609603 to configure the "bindHost" property of p4 services using config tool.

  • Installing AIA FP 2.4 on SOA Suite 10.1.3.4 with Weblogic 9.2 failed

    Hi,
    While Installing AIA FP 2.4 on Weblogic 9.2 using FPWLInstall.xml,
    I got the following Error..
    BUILD FAILED
    D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLInstall.xml:218: The following error occurred while executing this line:
    D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLInstall.xml:226: The following error occurred while executing this line:
    D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLDeployment.xml:17: The following error occurred while executing this line:
    D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLDeployment.xml:29: The following error occurred while executing this line:
    D:\AIA_HOME\Infrastructure\install\wlscripts\FPWLErrorHandlingInstall.xml:140: The following error occurred while executing this line:
    D:\AIA_HOME\Infrastructure\ErrorHandling\AIAReadJMSNotificationProcess\build.xml:209: A problem occured while connecting to server "localhost" using port "9700": bpel_aiareadjmsnotificationprocess_1.0.jar failed to deploy. Exception message is:  Could not initialize activation agent.
    An error occured while initializing an activation agent for process "AIAReadJMSNotificationProcess", revision "1.0".
    Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).
    oracle.tip.adapter.fw.agent.jca.JCAActivationAgent: ORABPEL-12517
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter  was unable to activate the endpoint :{} due to the following reason: ORABPEL-12561
    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/Jms/AIA_ERROR_JMS'*
    The reason for this is most likely that either
    *1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic J2EE Application server or*
    *2) the JNDI location setting in the WebLogic JCA deployment descriptor has not been set to eis/Jms/AIA_ERROR_JMS. In the last case you might have to add a new 'connector-factory' entry (connection) to the deployment descriptor.*
    Please correct this and then restart the BPEL/WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    Please help.

    pls see http://bit.ly/ozJqoz , in case you have missed some steps.

  • Kodo 4.1.2 in Weblogic 10 Problem

    I was told by BEA that Kodo/openJPA is included in Weblogic 10. However, now I have Weblogic 10 but I could not located much Kodo classes from Weblogic libraries. I searched all the JARs under BEA_HOME\wlserver_10.0\server\lib.
    I also tried to migrate Kodo/JPA application from Weblogic 9.2 to Weblogic 10. My application depends on Kodo JCA deployment in managed environment. The application and Kodo JCA deployed fine into Weblogic 10. But when I test any application, the test failed when I tried to create EntityMaanger from EntityManagerFactory:
    Caused by: <4|false|0.9.7> org.apache.openjpa.persistence.ArgumentException: config-error
         at weblogic.kodo.event.ClusterRemoteCommitProvider.endConfiguration(ClusterRemoteCommitProvider.java:112)
         at org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurations.java:447)
         at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiate(RemoteCommitProviderValue.java:122)
         at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiateProvider(RemoteCommitProviderValue.java:103)
         at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiateProvider(RemoteCommitProviderValue.java:95)
         at org.apache.openjpa.conf.OpenJPAConfigurationImpl.newRemoteCommitProviderInstance(OpenJPAConfigurationImpl.java:708)
         at org.apache.openjpa.event.RemoteCommitEventManager.(RemoteCommitEventManager.java:56)
         at org.apache.openjpa.conf.OpenJPAConfigurationImpl.getRemoteCommitEventManager(OpenJPAConfigurationImpl.java:720)
         at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:177)
         at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:139)
         at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:187)
         at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:140)
         at kodo.persistence.jdbc.JPAConnectionFactory.createEntityManager(JPAConnectionFactory.java:144)
         at kodo.persistence.jdbc.JPAConnectionFactory.createEntityManager(JPAConnectionFactory.java:23)
         at com.psi.vida.ejb.JPASessionBean.list(JPASessionBean.java:165)
         at com.psi.vida.ejb.JPASessionEJB_lvtqkz_EOImpl.list(JPASessionEJB_lvtqkz_EOImpl.java:134)
         at com.psi.vida.ejb.JPASessionEJB_lvtqkz_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
         ... 17 more
    Caused by: java.lang.Exception: <0|true|0.9.7> org.apache.openjpa.persistence.PersistenceException: no-trasport
         at org.apache.openjpa.util.Exceptions.replaceNestedThrowables(Exceptions.java:230)
         at org.apache.openjpa.persistence.ArgumentException.writeObject(ArgumentException.java:104)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:890)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1333)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
         at weblogic.rmi.extensions.server.CBVOutputStream.writeObject(CBVOutputStream.java:84)
         at weblogic.rmi.internal.ServerRequest.unmarshalThrowable(ServerRequest.java:349)
         at weblogic.rmi.internal.ServerRequest.getThrowable(ServerRequest.java:62)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:203)
         ... 17 more

    I was told by BEA that Kodo/openJPA is included in
    Weblogic 10. However, now I have Weblogic 10 but I
    could not located much Kodo classes from Weblogic
    libraries. I searched all the JARs under
    BEA_HOME\wlserver_10.0\server\lib. They're in the (new) modules directory. weblogic.jar refers to stuff in the modules directory via its manifest classpath.
    I also tried to migrate Kodo/JPA application from
    Weblogic 9.2 to Weblogic 10. My application depends
    on Kodo JCA deployment in managed environment. The
    application and Kodo JCA deployed fine into Weblogic
    10. But when I test any application, the test failed
    when I tried to create EntityMaanger from
    EntityManagerFactory:Interesting. I do not know what the status of Kodo JCA testing is in WebLogic 10, but it sounds like something is a bit wonky.
    Basically, in a WLS environment, the default remote commit provider is automatically set to the new weblogic.kodo.event.ClusterRemoteCommitProvider, which uses the WLS clustering protocol to communicate cache notifications. The error that you're seeing indicates that cluster services are not available in the execution context. You can probably get around this by explicitly setting the 'kodo.RemoteCommitProvider' option to 'sjvm' (if you're not running in a cluster), or to whatever you had it set to in the past. (I'm guessing that it was unset in the past, as otherwise, the configuration should be picking up that instead of the new default.)
    However, personally, I much prefer the new persistence.xml configuration file format, compared to JCA configuration. (You can trivially use the persistence.xml format with Kodo JDO, even though it's a JPA-specified feature.) You might want to look into moving away from JCA and to the persistence.xml style instead.
    If you do this, you'll end up putting a META-INF/persistence.xml file in your EAR (and possibly a META-INF/persistence-configuration.xml file, if you want to use the strongly-typed Kodo XML configuration format), and replacing your JNDI lookups with java:comp/env/persistence/<persistence-unit-name>. (I think that's the right location. I might be mistaken, though.)
    Also, I can't guarantee that WebLogic 10 really handles JCA configuration all that well; some bits of that exception make it look like maybe some resources are not available in the classloader, which is surprising. So, it's possible that there is some sort of more fundamental JCA problem here (and not just a problem with the new remote commit provider).
    -Patrick

  • Data Adapter is not configuring properly.....

    I have created a BPEL process and added a DB adapter for polling a particular table.
    and after this created a datasource with jndi name "eis/DB/DAMS" and Next in Weblogic server console --> Deployments --> DBAdapter --> Configurations --> Outbound Pool Connections --> create a new outbound pool connection with the name "dbadapterjndi".
    Now update the "xADataSourceName" property of this connection pool with the JNDI name of the datasource created in the first step.
    first thing is this is not updating in the server, its giving the message successfully saved and then update the deployment, i did after that also I am getting the following error.
    ==> CubeEngine deploy processDBAdapter/ProcessDBAdapterBPEL took 78 msecs
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/proces
    sDBAdapter!1.0*soa_b79fa747-e7fe-4e12-8a0a-0fec5d5e319c
    INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation SOA Keystore location: C:/
    Oracle/MIDDLE~1/USER_P~1/domains/URA_DO~1/config/fmwconfig/default-keystore.jks
    INFO: SSLSocketFactoryManagerImpl.getKeystorePassword Obtained null or empty key
    store password
    INFO: SSLSocketFactoryManagerImpl.getKeyPassword Obtained null or empty key pass
    word
    INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Could not obtain keystore
    location or password
    <Mar 24, 2011 6:11:55 PM SGT> <Warning> <oracle.soa.adapter> <BEA-000000> <JCABi
    nding=> processDBAdapter JNDI lookup of 'eis/DB/DAMS' failed due to: weblogic.j
    dbc.common.internal.RmiDataSource cannot be cast to javax.resource.cci.Connectio
    nFactory>
    <Mar 24, 2011 6:11:55 PM SGT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABind
    ing=> processDBAdapter Error while performing endpoint Activation: BINDING.JCA-
    12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    >
    <Mar 24, 2011 6:11:55 PM SGT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABind
    ing=> processDBAdapter
    BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    at oracle.integration.platform.blocks.adapter.fw.AdapterBindingException
    .createJndiLookupException(AdapterBindingException.java:92)
    at oracle.integration.platform.blocks.adapter.fw.jca.spi.ResourceAdapter
    Locator.findResourceAdapter(ResourceAdapterLocator.java:140)
    at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkIm
    pl.endpointActivation(AdapterFrameworkImpl.java:332)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.performEndpointActivation(JCAEndpointActivation.java:621)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:604)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.performActivation(JCAEndpointActivation.java:371)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisio
    nRegistry.java:585)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.
    java:440)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisio
    nRegistry.java:405)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionR
    egistry.java:330)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisi
    onRegistry.java:136)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:98)
    at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevi
    sionChanged(AdapterService.java:311)
    at oracle.integration.platform.kernel.WLSFabricKernelInitializer$2.proce
    ssDefaultInSeries(WLSFabricKernelInitializer.java:464)
    at oracle.integration.platform.kernel.WLSFabricKernelInitializer$2.run(W
    LSFabricKernelInitializer.java:391)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    oracle.fabric.common.FabricDeploymentException: [JCABinding] [processDBAdapter.D
    BAdapter/1.0]Unable to complete initialization due to: Endpoint Activation Error
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter was unable to activate the endpoint :{} due to the followi
    ng reason: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter was unable to activate the endpoint :{} due to the followi
    ng reason: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    {rootCauses=[]}
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:68)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisio
    nRegistry.java:610)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.
    java:440)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisio
    nRegistry.java:405)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionR
    egistry.java:330)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisi
    onRegistry.java:136)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:98)
    at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevi
    sionChanged(AdapterService.java:311)
    at oracle.integration.platform.kernel.WLSFabricKernelInitializer$2.proce
    ssDefaultInSeries(WLSFabricKernelInitializer.java:464)
    at oracle.integration.platform.kernel.WLSFabricKernelInitializer$2.run(W
    LSFabricKernelInitializer.java:391)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: BINDING.JCA-12517
    Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter was unable to activate the endpoint :{} due to the followi
    ng reason: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkIm
    pl.endpointActivation(AdapterFrameworkImpl.java:511)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.performEndpointActivation(JCAEndpointActivation.java:621)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:604)
    at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpoi
    ntActivation.performActivation(JCAEndpointActivation.java:371)
    at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterService
    RevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisio
    nRegistry.java:585)
    ... 11 more
    Caused by: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    at oracle.integration.platform.blocks.adapter.fw.AdapterBindingException
    .createJndiLookupException(AdapterBindingException.java:92)
    at oracle.integration.platform.blocks.adapter.fw.jca.spi.ResourceAdapter
    Locator.findResourceAdapter(ResourceAdapterLocator.java:140)
    at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkIm
    pl.endpointActivation(AdapterFrameworkImpl.java:332)
    ... 15 more
    <Mar 24, 2011 6:11:56 PM SGT> <Error> <oracle.integration.platform> <SOA-20020>
    <Deployment of composite "processDBAdapter" failed: [JCABinding] [processDBAdapt
    er.DBAdapter/1.0]Unable to complete initialization due to: Endpoint Activation E
    rror.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter was unable to activate the endpoint :{} due to the followi
    ng reason: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter was unable to activate the endpoint :{} due to the followi
    ng reason: BINDING.JCA-12561
    JCA Resource Adapter location error (WebLogic).
    Unable to locate the JCA Resource Adapter via .jca binding file element <connect
    ion-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in
    the <connection-factory/> element: location='eis/DB/DAMS'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the Web
    Logic J2EE Application server or
    2) the JNDI <jndi-name> setting in the WebLogic JCA deployment descriptor has n
    ot been set to eis/DB/DAMS. In the last case you might have to add a new 'connec
    tor-factory' entry (connection) to the deployment descriptor.
    Please correct this and then restart the WebLogic Application Server
    Please correct the reported issue and redeploy the BPEL process.
    .>
    INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation SOA Keystore location: C:/
    Oracle/MIDDLE~1/USER_P~1/domains/URA_DO~1/config/fmwconfig/default-keystore.jks
    INFO: SSLSocketFactoryManagerImpl.getKeystorePassword Obtained null or empty key
    store password
    INFO: SSLSocketFactoryManagerImpl.getKeyPassword Obtained null or empty key pass
    word
    INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Could not obtain keystore
    location or password
    ==> CubeEngine deploy SchedulerProject/SchedulerBPELProcess took 172 msecs
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/Schedu
    lerProject!1.0*soa_07eeda8d-196a-4174-81ee-05589086d5f2
    INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation SOA Keystore location: C:/
    Oracle/MIDDLE~1/USER_P~1/domains/URA_DO~1/config/fmwconfig/default-keystore.jks
    INFO: SSLSocketFactoryManagerImpl.getKeystorePassword Obtained null or empty key
    store password
    INFO: SSLSocketFactoryManagerImpl.getKeyPassword Obtained null or empty key pass
    word
    INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Could not obtain keystore
    location or password
    ==> CubeEngine deploy Registrationupload/RegistrationUploadBPELProcess took 531
    msecs
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/Regist
    rationupload!3.0*soa_7a4793e2-dab1-4d3f-b4a9-f6050dfda617
    INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation SOA Keystore location: C:/
    Oracle/MIDDLE~1/USER_P~1/domains/URA_DO~1/config/fmwconfig/default-keystore.jks
    INFO: SSLSocketFactoryManagerImpl.getKeystorePassword Obtained null or empty key
    store password
    INFO: SSLSocketFactoryManagerImpl.getKeyPassword Obtained null or empty key pass
    word
    INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Could not obtain keystore
    location or password
    ==> CubeEngine deploy Registrationupload/RegistrationUploadBPELProcess took 282
    msecs
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/Regist
    rationupload!1.0*soa_562b243b-bf72-41d6-8fc3-76777af5c1e9
    looking up version 11.1.1.3.0
    SchemaVersion actual dbVersion=11.1.1.3.0, expected dbVersion=11.1.1.3.0
    INFO: FabricProviderServlet.stateChanged SOA Platform is running and accepting r
    equests
    please suggest and if my steps are wrong, then please guide me too.\
    thks

    Me too. I'm trying to setup an FTP Listener. As soon as I edit the Deployment Descriptor (with the FTP Server settings) and save it to a new DD file I get the same message.
    Something isn't linking up. I do note that there is not an explicit setting for <jndi-name> in the DD, except within the Variable Declarations. Does anyone know where that should be included? I don't see it in any other DDs (that work), but they're not setup for Listening either...

Maybe you are looking for