J2ee Application Deployed,error connecting to 9i db

Hi,
I am working on a Oracle 10g 9.0.4 AS and a Oracle 9i db, both of which I have just installed on red Hat Linux 2.1 Advanced Server.
I have deployed a j2ee ear file in an OC4J container. The deployment works fine as I get the login page correctly. But it fails to go further than that and gives an error "contact system administrator".The Http Server logs show the following error messages :
[Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0015: recv() returns 0. There
has no message available to be received and oc4j has gracefully (orderly) closed the connection.
[Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0054: Failed to call network
routine to receive an ajp13 message from oc4j.
[Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0033: Failed to receive an
ajp13 message from oc4j.
[Fri Mar 25 13:07:22 2005] [warn] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0078: Network connection errors
happened to host: midtier.mastek.com and port: 3303 while receiving the first response from oc4j. This request is recoverable.
I have configured a user in the database with the reqd schema and also a datasource pointing to it and whose jndi name I have specified in the application.
Also, I get an error saying in the OC4J container :
05/03/25 13:02:28 log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources).
05/03/25 13:02:28 log4j:WARN Please initialize the log4j system properly.
indicating that mebbe the logging hasnt been successfully installed and that's mebbe why I am not getting proper error messages.
I am thinking that there maybe some error in the connection to the 9i database, but cant figure out what.
PLEASE,PLEASE HELLLLPPPPP!!!!

Also got these in logs
emias.log
com.evermind.server.http.HttpIOException: Broken pipe ---> Enterprise Manager
em-application.log
Broken pipe sometimes followed with : java.io.FileNotFoundException: Could not find ias/.uix
and                    : java.io.FileNotFoundException: Could not find ias/clusters/.uix
OHS errors :
[warn] [client 127.0.0.1] MOD_OC4J_0078: Network connection errors happened to host: midtier.mastek.com and port: 3303 while receiving
the first response from oc4j. This request is recoverable.
March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] (32)Broken pipe: MOD_OC4J_0087: Got an unexpected error while calling send() to send a message to oc4j
and the error code is 32.
March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] MOD_OC4J_0053: Failed to call network routine to send out an ajp13 buffer message to oc4j.
March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] MOD_OC4J_0032: Failed to send out an ajp13 message to oc4j.
March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0015: recv() returns 0. There has no message available to be received and oc4j has gracefully (orderly)
closed the connection.
March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0054: Failed to call network routine to receive an ajp13 message from oc4j.
March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0033: Failed to receive an ajp13 message from oc4j.

Similar Messages

  • J2ee application deployment error

    Hi All,
             I have created a J2ee application. I have created a EJB module project in which i have created a session bean. Also I have created a Web module project, i am referring the above created EJB in this web module. Both these projects are added to one enterprise application.While deploying this ear file to j2ee engine I am getting following error.
    Aborted: development component 'TestEAR'/'sap.com'/'localhost'/'2007.06.28.10.34.29'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/TestEAR.. Reason: Exception during generation of components of application sap.com/TestEAR in container EJBContainer.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/TestEAR in container EJBContainer.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Please can anybody tell me what is going wrong?
    I am using NW 2004s.
    Cheers
    jayant

    I have the same problem. I retart the SDM.and del the app in VA,It is OK now.

  • J2EE application deploy error

    Hi!
    thank you for see my question.
    when I deploy EJB Model to Oracle 10 AS, the server notice exception like this
    "java.rmi.RemoteException
    deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns. deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns".
    and I deploied a JSF Application to Oracle 10g AS, but the Faces Servlets cann't be used.
    please help me, thank you so much.

    What specific versions are you using? It sounds like you are deploying a J2EE 1.4 based application (from JDev 10.1.3) to OC4J/OracleAS 10.1.2. That version of the server implements J2EE 1.3 which used DTDs and not XML schema. Thus when you are throwing some schema at it, it's not able to handle it.
    Using OC4J/OracleAS 10.1.3 should solver this problem.
    -steve-

  • Using Web Dynpro WDUrlGenerator from within J2EE Application deployed on NW

    I have two applications deployed on a NetWeaver Application Server 2004s.
    1. A Web Dynpro application.
    2. A J2EE Application
    What I want to do is to be able to build a url to the Web Dynpro application from within the J2EE application. Obviously the problem is using Web Dynpro classes within the J2EE application.
    So I edited the Java Build Path of the J2EE application to include the werbdynproservices.jar file and exception.jar files by extending ECLIPSE_HOME variable in the libraries section. I also checked them in Order and Export. I verified the built .war file and it does contain the two .jar files.
    This was sufficient to get my project build and deployed, however the servlet in my J2EE application shows NoClassDefFoundException when I run it. My guess is there's more I need to do to get the WDUrlGenerator to run in my J2EE class.
    Is this possible or is there a better way? I am trying to avoid the client having to modify a web.xml for each depployment.
    Thanks in Advance.

    This looks like what I want, but I am unable to test it.
    I found the application-j2ee-engine.xml file under the <project-root>/gen_wdp folder. I then attempted to open it with the SAP EARDD editor. It opens with the Source tab selected. If I try to click the General tab I get an error saying:
    "The source page has errors. Other pages cannot be used until these erros are corrected."
    I see nothing wrong with the XML document. It's source is here:
    <?xml version="1.0" encoding="UTF-8"?>
    <application-j2ee-engine>
        <provider-name>local</provider-name> 
        <modules-additional>
        <module>
          <entry-name>EVENTS_WorkflowNotification.wda</entry-name>
          <container-type>webdynpro</container-type>
        </module>
      </modules-additional>
    </application-j2ee-engine>
    When I deploy the application, everything works fine. I was going to edit the XML document by hand, but of course there is no DTD listed so I don't know what's supposed to go in there without the Editor doing it for me.
    Getting closer. Thanks so much.

  • EJB Application Deployment Error

    Hi,
    I am trying to deploy an J2EE application ear, which contains both EJB modules and a WEB module, on NW 2004's SP10.  Here is the error message that is written out to the defaultTrace file in the server logs directory:
    #1.5#00137262AE6E006500000035000012CC000438363739A6D9#1187705412772#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application champtech.com/COINejb.#2#deploy#champtech.com/COINejb#
    #1.5#00137262AE6E006500000036000012CC000438363739B7D8#1187705412788#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application champtech.com/COINejb.
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
         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.deploy(DeployServiceImpl.java:552)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
         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 com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application champtech.com/COINejb.
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
         ... 33 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         ... 35 more
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         ... 36 more
    #1.5#00137262AE6E006500000038000012CC00043836373AA34F#1187705412835#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Plain###
    Operation deploy over application champtech.com/COINejb finished with errors on server 9460450. For more detailed information see traces of Deploy Service.#
    #1.5#00137262AE6E00650000003B000012CC00043836373ACAFD#1187705412850#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java#deploy_5047##Cannot deploy application champtech.com/COINejb.#1#champtech.com/COINejb#
    #1.5#00137262AE6E00650000003C000012CC00043836373ACCCB#1187705412850#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application champtech.com/COINejb.
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         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.deploy(DeployServiceImpl.java:552)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
         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 com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         ... 35 more
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         ... 36 more
    #1.5#00137262AE6E00650000003E000012CC00043836373ADBB9#1187705412850#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Warning#1#/System/Server#Java###Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 551 |  src: 2 target-node: 9460450 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=9460450,SAP_J2EECluster="" deploy [Ljava.lang.Object;@67beb7 [Ljava.lang.String;@11a0ebf ]
    [EXCEPTION]
    #1#javax.management.MBeanException: Exception invoking method deploy
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.rmi.RemoteException: Cannot deploy application champtech.com/COINejb..
    Reason: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
         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 com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         ... 24 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         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.deploy(DeployServiceImpl.java:552)
         ... 30 more
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         ... 36 more
    caused by -
    java.rmi.RemoteException: Cannot deploy application champtech.com/COINejb..
    Reason: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
         at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
         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 com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         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.deploy(DeployServiceImpl.java:552)
         ... 30 more
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
         at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         ... 36 more
    It seems that from the exception message that there is an issue loading or locating the EJB local home interface, however I am not exactly sure what is going as I can't find any additional information on this issue in the NW logs.  I have a previous ear that will deploy.  This earlier ear file only contains EJB remote interfaces.  In the newer ear I have implemented and added the EJB local interface and believe that I have the correct configurations, since the NW IDE doesn't show any errors and is able to generate the EJB archieves and the deployment EAR.
    Any assistance or help would be greatly appreciated as I have hit a wall on this.
    Thanks

    Here is one of my EJB modules ejb-jar.xml configuration files:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
                             "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
        <description>EJB JAR description</description>
        <display-name>EJB JAR</display-name>
        <enterprise-beans>
            <session>
                <ejb-name>AlertFacadeBean</ejb-name>
                <home>com.champtech.coin.alerts.session.remote.RemoteAlertFacadeHome</home>
                <remote>com.champtech.coin.alerts.session.remote.RemoteAlertFacade</remote>
                <local-home>com.champtech.coin.alerts.session.local.LocalAlertFacadeHome</local-home>
                <local>com.champtech.coin.alerts.session.local.LocalAlertFacade</local>
                <ejb-class>com.champtech.coin.alerts.session.AlertFacadeBean</ejb-class>
                <session-type>Stateful</session-type>
                <transaction-type>Container</transaction-type>
            </session>
            <entity>
                <ejb-name>AlertBean</ejb-name>
                <home>com.champtech.coin.alerts.entity.remote.RemoteAlertHome</home>
                <remote>com.champtech.coin.alerts.entity.remote.RemoteAlert</remote>
                <local-home>com.champtech.coin.alerts.entity.local.LocalAlertHome</local-home>
                <local>com.champtech.coin.alerts.entity.local.LocalAlert</local>
                <ejb-class>com.champtech.coin.alerts.entity.AlertBean</ejb-class>
                <persistence-type>Bean</persistence-type>
                <prim-key-class>java.lang.Long</prim-key-class>
                <reentrant>False</reentrant>
            </entity>
            <entity>
                <ejb-name>AlertInstanceBean</ejb-name>
                <home>com.champtech.coin.alerts.entity.remote.RemoteAlertInstanceHome</home>
                <remote>com.champtech.coin.alerts.entity.remote.RemoteAlertInstance</remote>
                <local-home>com.champtech.coin.alerts.entity.local.LocalAlertInstanceHome</local-home>
                <local>com.champtech.coin.alerts.entity.local.LocalAlertInstance</local>
                <ejb-class>com.champtech.coin.alerts.entity.AlertInstanceBean</ejb-class>
                <persistence-type>Bean</persistence-type>
                <prim-key-class>java.lang.Long</prim-key-class>
                <reentrant>False</reentrant>
            </entity>
            <entity>
                <ejb-name>AlertLogBean</ejb-name>
                <home>com.champtech.coin.alerts.entity.remote.RemoteAlertLogHome</home>
                <remote>com.champtech.coin.alerts.entity.remote.RemoteAlertLog</remote>
                <local-home>com.champtech.coin.alerts.entity.local.LocalAlertLogHome</local-home>
                <local>com.champtech.coin.alerts.entity.local.LocalAlertLog</local>
                <ejb-class>com.champtech.coin.alerts.entity.AlertLogBean</ejb-class>
                <persistence-type>Bean</persistence-type>
                <prim-key-class>java.lang.Long</prim-key-class>
                <reentrant>False</reentrant>
            </entity>
            <entity>
                <ejb-name>SubscriptionBean</ejb-name>
                <home>com.champtech.coin.alerts.entity.remote.RemoteSubscriptionHome</home>
                <remote>com.champtech.coin.alerts.entity.remote.RemoteSubscription</remote>
                <local-home>com.champtech.coin.alerts.entity.local.LocalSubscriptionHome</local-home>
                <local>com.champtech.coin.alerts.entity.local.LocalSubscription</local>
                <ejb-class>com.champtech.coin.alerts.entity.SubscriptionBean</ejb-class>
                <persistence-type>Bean</persistence-type>
                <prim-key-class>java.lang.Object</prim-key-class>
                <reentrant>False</reentrant>
            </entity>
        </enterprise-beans>
    </ejb-jar>

  • ADF application Deployment error:

    Hi
    I am trying to deploy a working version of our ADF application on to SQA 10.1.3.4 using Jdeveloper 10.1.3.3
    the connection for application server is connected successfully with setting: opmn port:6003, host: hofo3sop02ab.domain.com the type of server using oracle oc4j soa instance.
    the deployment failed:
    Operation failed with error:
    Cannot create temp directory: The system cannot find the path specified
    Deployment failed
    when I tried to deploy the AppName.ear file manually on to oc4j instance on the server, it stuck in uploading..
    I have been searching for the cause and solution, but no luck so far. Can anyone help?
    thanks a lot in advance.
    Edited by: Lang on May 20, 2011 2:34 AM

    Depending on the kind of app you try to deploy you can't just delete these entries. They needed by the framework.
    You need to make they libraries available on the server you try deploy to. That they are present is not enough.
    Timo

  • J2EE Engine Deployment Error

    I have written the betting pool applicaton for Soccer world Cup (/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-i)
    now i would like to deploy to j2ee Engine((/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-ii), Deploy and test the Services)
    but i receive follow error:
    01.06.2006 14:57:28 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [029]Deployment aborted
    Settings
    SDM host : uxept01
    SDM port : 50118
    URL to deploy : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Result
    => deployment aborted : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Aborted: development component 'wc/metadata'/'sap.com'/'local'/'20060601143708':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/wc_metadata.ear. Reason: None of the available containers recognized the components of application sap.com/wc~metadata; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anybody help me please
    Thanks
    Julia
    Message was edited by: Julia Fichtel
    Message was edited by: Julia Fichtel

    I also had this error and was solved with just uninstalling everything and reinstalling it again.
    I followed the following steps proposed in other forum:
    Regards,
    María Margarita Monteverde
    Hello Andre,
    It seems that you'd already an NWDS installation on your machine that wasn't de-installed completely. Before you install an new NWDS you must be sure that the following steps have been checked:
    1) Having completely run the de-installation routine of the NWDS
    2) It’s recommended to delete the directories “c:program filessapide” and “c:program filessapjdt” to be sure that there won’t stay any ‘old’ files.
    3) Furthermore you should delete the folder ‘workspace’ (including all files and subfolders) in the path ‘c:documents and settingsDocumentsSAP’ (where d012345 is your username). Or move this folder somewhere in the file system, afterwards you may re-import the 'old' projects.
    4) It's recommended to delete all .dtr/.dtc/.metadata directories in your personal folder (e.g. C:Documents and Settingsd0abcde).
    Please stop the IDE before you do all these steps.
    Regards,
    Jan
    Message was edited by:
            Maria Margarita Monteverde

  • Creating worker threads in J2EE application deployed in OAS...

    Will OAS allow for the creation of worker threads in a J2EE application? I can create a worker thread in my J2EE application that is deployed in OC4J Standalone, I need to verify if the same capabilities exist in OAS.
    Thank you,
    Jason

    Hi Ritushree,
    Yor approach is not correct. You need to do a JNDI lookup for the service.
    Refer
    http://help.sap.com/saphelp_nw04/helpdata/en/42/9ddd0cbb211d72e10000000a1553f6/frameset.htm
    Thanks
    Prashant

  • OA Framework application deployment error

    Dear all,
    i am facing an error in OA Framwork application deployment step.
    when i use this command for importing OA Pages in server then one error is prompted:
    "Unable to initialize threads: cannot find class java/lang/Thread"
    my import command was like:
    import C:\p4573517_11i_current\jdevhome\jdev\oracle\apps\ak\cacheoffice\webui\DetailsPG.xml -username apps -password 12345 -rootdir C:\p4573517_11i_current\jdevhome\jdev\myprojects\ -dbconnection "(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 101.210.180.44)(PORT = 1536))) (CONNECT_DATA = (SERVICE_NAME = DEV)))"
    Please suggest
    Edited by: Mofizur on Jun 7, 2011 2:56 PM

    Dear Gyan,
    that problem has been solved as u suggested.
    now i am getting a error:
    <Line 3, Column 45>: XML-0112: (Fatal Error) Error opening external DTD 'jbo_03_
    01.dtd'.
    Warning: Could not find the customization level value for document "/oracle/apps
    /ak/poplist/server/DepartmentPL".
    Error opening external DTD 'jbo_03_01.dtd'.
    Importing /oracle/apps/ak/poplist/server/DepartmentPL
    Error:
    Error opening external DTD 'jbo_03_01.dtd'.
    Import failed."
    Please suggest

  • Application Deployment Error 0x87D00324

    Hello All--
    I have a deployment setup for Java 7 Update 45.  I have two deployment types (x86 and x64). Each deployment type has a Windows Installer detection method set. I created a required deployment to 13+ test machines. Only two show this as 'Installed',
    the rest show 'Past Due - Will be retried' with error code 0x87D00324.  When I check AppEnforce.log, it shows a successful installation, but the next lines show 'Application not Detected'. All the machines are 32-bit.
    Any thoughts/help would be much appreciated.
    Thanks,
    Matt

    Hi,
    I found a similar threads for your reference.
    SCCM 2012 Deploy --- Error = The software change returned error code 0x87D00324
    http://social.technet.microsoft.com/Forums/en-US/99b13d65-3305-46c7-b5a0-96513408520b/sccm-2012-deploy-error-the-software-change-returned-error-code-0x87d003242016410844?forum=configmanagerapps
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • J2EE applications deploying

    Hi all.
    I'd like to know what differences there are when I deploy a J2EE application as an application instead of deploying it as stand-alone modules, other than classes being loaded by the same class loader. I am specially interested in differences at a JNDI level, if there are differences at all.
    Thanks in advance.

    My pleasure.
    From the nature of your original question, it sounds to me that you have a good grip on the J2EE, so, if what I am about to point out is something that you already know, then by all means please ignore it...
    The J2EE defines several packaging methodolgies: EJB (.jar), web application ([b/.war[/b]) and enterprise application (.ear). Each packaging paradigm is an archive, specifically, a Java archive. The J2EE specifies the specific layout of each archive as well as the specific XML deployment descriptors which are needed. EJB's can be contained within a web application and a web application can be contained with an enterprise application. Additionally, the J2EE also specifies a client application which can be packaged into an enterprise application - again, the client application is an archive, with the XML descriptors specified by the J2EE. If I remember right, the J2EE also specifies other modules, such as plain Java classes that are to be used by the enterprise application.
    From a logical namespace perspective, clients of these components see one view - they need not concern themselves with any differences in terms of acquiring references to components in the container via the JNDI. However, it should be noted that the J2EE, for EJB's, specifies not only home and remotes, but local home and remotes. Just as the "normal" home interface is bound to the JNDI, so is the local home interface; both of these must be not be bound to the same node in the JNDI namespace.
    Hope this helps.

  • Suite application deployment error

    Hi,
    I have installed webcenter on my laptop but I can't able to access space http://localhost:8888/webcenter, When I saw the applications deployment status from console then I saw almost 14 applications are in failed state and when I tried to start them individually from weblogic console then some applications giving null pointer exceptionn or some noclass found exception ? Does anybody have idea on this? below is the list of applications are in failed state.
    applications target
    DMS Application(11.1.1.1.0) WLS_Portlet
    DMS Application(11.1.1.1.0) WLS_Services
    DMS Application(11.1.1.1.0) WLS_Spaces
    owc_discussions(11.1.1.2.0) WLS_Services
    owc_wiki(11.1.1.2.0) WLS_Services
    portalTools(11.1.1.2.0) WLS_Portlet
    webcenter WLS_Spaces
    webcenter-help(11.1.1.2.0) WLS_Spaces
    wsil-wls WLS_Portlet
    wsil-wls WLS_Services
    wsil-wls WLS_Spaces
    wsm-pm WLS_Portlet
    wsm-pm WLS_Spaces
    wsrp-tools(11.1.1.2.0)

    Hey can u post ur solution ?

  • Webdynpro application deployment error

    Hi,
    When i tried to deploy a webdynpro application into portal6 it gives me the following error message. When asked for the SDM password i gave the sdm password, which is the same i use to login to SDM thru RemoteGUI.bat.
    Oct 3, 2005 1:47:09 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [004]Deployment aborted
    Settings
    SDM host : portal6
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/GOPINA1/LOCALS~1/Temp/temp10205TutWD_KMBrowser_Init.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/GOPINA1/LOCALS~1/Temp/temp10205TutWD_KMBrowser_Init.ear
    Aborted: development component 'TutWD_KMBrowser_Init'/'local'/'LOKAL'/'0.2005.10.03.13.47.07':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [portal6] with user name: [J2EE_ADMIN]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: User not authorized.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted.
    Can anyone help me in this regard.
    thanx.
    Gopi

    Hi Gopi,
    Check what roles assigned to user J2EE_ADMIN at http://<server>:<port>/useradmin
    Also check password for J2EE_ADMIN should be same at both side, in Useradmin and in config tool.
    Regards,
    Bhavik

  • JSP Application Deployment Error : BIB-16632

    I have successfully developed , Tested in the development environment and deployed a BI Beans JSP application . But when I try to access the same JSP through the Web Context root , I am getting the following error
    Error
    javax.servlet.jsp.JspException: BIB-18007 A MetadataManager exception has occurred.
    BIB-10100 Cannot connect to the database. (Reason: See error BIB-16632)
    BIB-16632 Cannot connect to the database because the JDBC driver version is incompatible with the database version of the OLAP option.
         at oracle.dss.addins.jspTags.PresentationTag.doStartTag(PresentationTag.java:194)
         at simpleJSP.jspService(_simpleJSP.java:68)
         [SRC:/simpleJSP.jsp:6]
         at com.orionserver[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:349)
         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[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    The BI_CHECKCONFIG output is as under
    BI Beans Diagnostics(v1.0.2.0) 8/17/04
    =========================================================
    JDEV_ORACLE_HOME .......................... = c:\jdev904
    JAVA_HOME ................................. = C:\j2sdk1.4.2_01
    JDeveloper version ........................ = 9.0.4.0.1419
    BI Beans release description .............. = BI Beans 9.0.4 Production Release
    BI Beans component number ................. = 9.0.4.23.0
    BI Beans internal version ................. = 2.7.5.32
    Connect to database ....................... = Successful
    JDBC driver version ....................... = 9.2.0.4.0
    JDBC JAR file location .................... = C:\jdev904\jdev\lib\patches
    Database version .......................... = 9.2.0.4.0
    OLAP Catalog version ...................... = 9.2.0.4.0
    OLAP AW Engine version .................... = 9.2.0.4.0
    OLAP API Server version ................... = 9.2.0.4.0
    BI Beans Catalog version .................. = N/A; not installed in BIBDEMO
    OLAP API JAR file version ................. = 9.2
    OLAP API JAR file location ................ = c:\jdev904\jdev\lib\ext
    Load OLAP API metadata .................... = Successful
    Number of metadata folders ................ = 2
    Number of metadata measures ............... = 12
    Number of metadata dimensions ............. = 8
    Metadata output location .................. = C:\jdev904\bibeans\bi_checkconfig\bi_metadata.txt
    Can anybody please help ?

    Your middle tier has the incorrect JDBC libraries installed. The documentation on the BI Beans section of OTN explains how to deploy a BI Beans app and how to include the correct JDBC files with the deployment:
    Setting up a separate OC4J instance in Oracle9i Application Server on Windows for BI Beans Deployment
    Setting up a separate OC4J instance in Oracle9i Application Server on Unix for BI Beans Deployment
    Deploying Applications to BEA WebLogic Server
    For example in the Windows documentation, the following steps are required:
    Log into the machine where you created the oc4j_bibeans instance. You must log in as the user who installed Oracle Application Server.
    Create a new directory named jdbc under new_oc4j_instance. This is the name you specified in the -Djava.ext.dirs option in step 2.
    Copy the JDBC driver files (classes12.jar, classes12dms.jar, and nls_charset12.jar) to this new directory. The correct source for these files differs, depending one which type of JDBC driver you are using.
    If you are using the Oracle JDBC Thin (Pure Java) driver, then copy the files from the $ORACLE_HOME\bibeans\jdbc\lib_92 directory in the BI Beans installation. Do not use the files that are installed with JDeveloper.
    If you are using the Oracle JDBC Thick (OCI) driver, then copy the files from the Oracle9i client or server installation. When you use the thick driver, the version of the JDBC driver files must match the version of the database client. The files are located in the $ORACLE_HOME\jdbc\lib directory, where $ORACLE_HOME is the Oracle Home for the database.
    Return to Oracle Enterprise Manager and click Application Server Instance.
    Select the oc4j_bibeans instance from the list and click Start. You are now ready to deploy your Oracle BI Beans 10g (9.0.4) application.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • Application Deployment Error - SOA Suite 10.1.3.1

    Hi Gurus,
    I have deployed an application on Oracle SOA suite 10.1.3.1 on AIX 6.1, all went well until I tried to access it from a browser, I got errors and was unable to launch the application. I then decided to look at the relevant logs, I got a network adapter related error. I have defined the connection pools and data sources properly and tested them successfully. I am however getting the following error:
    <2014-07-16 11:55:12,873> <ERROR> <oracle.bpel.services> <::> Io exception: The Network Adapter could not establish the connection
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:287)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:430)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
        at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:116)
        at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:75)
        at oracle.oc4j.sql.DataSourceConnectionPoolDataSource.getPooledConnection(DataSourceConnectionPoolDataSource.java:57)
        at oracle.oc4j.sql.xa.EmulatedXADataSource.getXAConnection(EmulatedXADataSource.java:92)
        at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createXAConnection(ManagedConnectionFactoryImpl.java:211)
        at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:170)
        at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(ApplicationConnectionManager.java:1461)
        at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(ConnectionPoolImpl.java:329)
        at oracle.j2ee.connector.ConnectionPoolImpl.access$900(ConnectionPoolImpl.java:100)
        at oracle.j2ee.connector.ConnectionPoolImpl$FixedWaitPoolingScheme.getManagedConnection(ConnectionPoolImpl.java:1518)
        at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:792)
        at oracle.oc4j.sql.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:45)
        at com.evermind.server.connector.ApplicationConnectionManager.getConnectionFromPool(ApplicationConnectionManager.java:1700)
        at com.evermind.server.connector.ApplicationConnectionManager.acquireConnectionContext(ApplicationConnectionManager.java:1640
        at com.evermind.server.connector.ApplicationConnectionManager.allocateConnection(ApplicationConnectionManager.java:1580)
        at oracle.j2ee.connector.OracleConnectionManager.unprivileged_allocateConnection(OracleConnectionManager.java:265)
        at oracle.j2ee.connector.OracleConnectionManager.allocateConnection(OracleConnectionManager.java:214)
        at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:272)
        at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:200)
        at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
        at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
        at oracle.bpel.services.notification.repos.NotificationPersistencyDriver.getConnection(NotificationPersistencyDriver.java:170
        at oracle.bpel.services.notification.repos.NotificationPersistencyDriver.getTransactionService(NotificationPersistencyDriver.java
        :196)
        at oracle.bpel.services.notification.repos.NotificationPersistencyDriver.getInstance(NotificationPersistencyDriver.java:224)
        at oracle.bpel.services.notification.repos.Transaction.start(Transaction.java:57)
        at oracle.bpel.services.notification.NotificationUtil.getNotifications(NotificationUtil.java:265)
        at oracle.bpel.services.notification.queue.sender.Publisher.retryFailedNotification(Publisher.java:387)
        at oracle.bpel.services.notification.ejb.impl.NotificationBean.retryFailedNotification(NotificationBean.java:344)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
        at java.security.AccessController.doPrivileged(AccessController.java:279)
        at javax.security.auth.Subject.doAs(Subject.java:573)
        at com.evermind.server.ThreadState.runAs(ThreadState.java:707)
        at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
        at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
        at NotificationServiceBean_RemoteProxy_68d4144.retryFailedNotification(Unknown Source)
        at oracle.bpel.services.notification.queue.sender.QuartzPublisher.execute(QuartzPublisher.java:93)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
    Any help towards resolving this issue would be greatly appreciated.

    Hi,
    Firstly I see that you are not on a certified version.
    To use AIX  6.1 the minimum version of OAS should be 10.1.3.3 +
    There would be issues that you could face even due to unsupported configuration.
    Thanks,
    Sharmela

Maybe you are looking for