Deploying ear file in Sun app server

[#|2004-10-15T12:46:20.781+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=11;|
javax.management.InstanceAlreadyExistsException: com.sun.appserv:j2eeType=ResourceAdapter,name=StartUpConnector.rar,ResourceAdapterModule=StartUpConnector.rar,J2EEApplication=null,J2EEServer=server,category=runtime
     at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:460)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1418)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:944)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:345)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:505)
     at com.sun.enterprise.admin.meta.MBeanRegistry.instantiateMBean(MBeanRegistry.java:528)
     at com.sun.enterprise.management.util.J2EEManagementObjectManager.instantiateAndRegisterRuntimeMBean(J2EEManagementObjectManager.java:787)
     at com.sun.enterprise.management.util.J2EEManagementObjectManager.createRARMBean(J2EEManagementObjectManager.java:2317)
     at com.sun.enterprise.server.ApplicationLoader.createLeafMBean(ApplicationLoader.java:222)
     at com.sun.enterprise.server.AbstractLoader.loadRars(AbstractLoader.java:660)
     at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:122)
     at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:205)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:156)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:480)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:448)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:432)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:299)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:107)
     at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3880)
     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.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
     at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
     at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:680)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.phasing.DeploymentService.multicastEvent(DeploymentService.java:341)
     at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:284)
     at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:115)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
     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.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:105)
     at com.sun.enterprise.tools.admingui.util.MBeanUtil.invoke(MBeanUtil.java:35)
     at com.sun.enterprise.tools.admingui.handlers.DeploymentHandler.deploy(DeploymentHandler.java:98)
     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.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.invokeHandler(DescriptorViewHelper.java:785)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.dispatchEvent(DescriptorViewHelper.java:731)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewHelper.execute(DescriptorViewHelper.java:250)
     at com.sun.enterprise.tools.guiframework.view.DescriptorViewBeanBase.execute(DescriptorViewBeanBase.java:187)
     at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
     at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:822)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:760)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:780)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:590)
     at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:951)
     at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:622)
     at com.sun.enterprise.tools.guiframework.view.BaseServlet.processRequest(BaseServlet.java:186)
     at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:480)
     at com.sun.enterprise.tools.admingui.AdminGUIServlet.doPost(AdminGUIServlet.java:65)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:768)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil|#]
[#|2004-10-15T12:46:20.796+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=11;|.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:536)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:305)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
|#]

Did you do a asadmin list-components or the equivalent from the gui? It looks like your rar is already deployed based on the stacktrace

Similar Messages

  • Deploying an ear file in Sun Web Server

    I have an ear file that we use to deploy to weblogic. Is it possible to deploy an ear file to Sun WEb Server 6.0? Instead of deploying the war files one-by-one?
    If yes, what are the steps?
    Thanks.
    Beth

    No, Sun ONE Web Server does not support ear files; ear files are typically the domain of J2EE application servers.

  • Deploying a WAR file to Sun App Server 8.1 PE

    So I thought that if I downloaded Sun App Server PE 8.1 and put it on my soon-to-be production machine, it should be pretty easy right?
    Nope. So I have JSC update 6 (which includes Sun Application Server 8.0) (God how I wish there was a catchy name like Tomcat or something)
    And I have a machine running a good copy, installed and everything, of Sun Application Server 8.1 Platform Edition (another catchy name) up on the production target.
    I create a WAR file in JSC, scp it up.
    Then try to deploy it - so I get bit by the no DB connection thing.
    Ok, but when I copy each of my connection's attributes (the driver (which I did copy up to the lib directory) is MySQL's Connector/J)
    I copy the username, password, URL and DriverClass attributes to the connection pool.
    I still get a
    "Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.sun.sql.datasource.DriverAdapter"
    when I try to Ping the ConnectionPool
    I have javax.sql.DataSource as the resource type... (same as 8.0 uses)
    what JAR file is DriverAdapter in? anyone know?
    cheers,
    Kris

    Okay. mysql folks - this works......
    here's what happened, on the production server, different from the dev machine....
    mysql 4.1.9
    sun application server platform edition PE 8.1
    connector/j - latest
    and on the dev machine: JSC Update 6 and the app works fine on the dev machine.
    first, there is a JAR file in ~whatever/Create/SunAppServer/lib/ named
    driveradaptor.jar
    and it it comtains
    com.sun.sql.datasource.DriverAdapter
    which 8.1 ain't got
    and should be copied up to
    /installdir/SunAppServer/domains/domain1/lib/ext/driveradapter.jar
    (domain1 is your app svr domain that runs your app.)
    your Connector/J JAR needs to go here too. I used:
    mysql-connector-java-3.2.0-alpha-bin.jar
    downloaded from mysql.com.
    and then there is the whole thing about Added Properties in the Connection Pool page inside the 8.1 Admin Console (which is nice work guys). Gawd, I added a bunch of properties and am, frankly, not sure which ones actually work (for the Ping, for the initial connection creation and the eventual successful connection all seem to use different combinations...)
    and I found this in the domain's domain.xml once all the admin console page filling was done - but you'll need to add each one as a Property in the connection pool:
    <jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.sun.sql.datasource.DriverAdapter" fail-all-connections="false" [blah...]
    <property name="Username" value="root"/>
    <property name="Password" value="secret"/>
    <property name="ValidationQuery" value="SELECT 1"/>
    <property name="DriverClassName" value="com.mysql.jdbc.Driver"/>
    <property name="LoginTimeout" value="0"/>
    <property name="Url" value="jdbc:mysql://localhost/databasename?autoReconnect=true"/>
    <property name="User" value="root"/>
    <property name="password" value="secret"/>
    <property name="PasswordCredential" value="secret"/>
    </jdbc-connection-pool>
    (and you see how User and Username and username are all the same thing? well, different parts of 8.1 seem to use different attributes...)
    Just keep Adding Properties in the connection pool until you get them all....
    Oh and, the two key class references for the pool are:
    datasource class: com.sun.sql.datasource.DriverAdapter
    resource type: javax.sql.ConnectionPoolDataSource
    Finally: in the /installdir/SunAppServer/domains/domain1/applications/j2ee-modules/YourAppName/WEB-INF/
    your 'sun-web.xml' (don't delete it, like some have advocated, I think that wrong) needs to look like:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd">
    <sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
    <context-root>/yourcontext</context-root>
    <resource-ref>
    <res-ref-name>jdbc/Yourname</res-ref-name>
    <jndi-name>jdbc/Yourname</jndi-name>
    <default-resource-principal>
    <name>root</name>
    <password>secret</password>
    </default-resource-principal>
    </resource-ref>
    </sun-web-app>
    and I think that's all of it. the only Bug I would I would say is that the sun-web.xml should have the right res-ref-name, but then I think the Creator Team knows this and will fix it sometime soon.
    cheers,
    and Roger Federer lost in the Aussie Open. (I think he lost tomorrow too, that whole time zone thing being so damn Einsteinian...)
    -Kristofer

  • Ruleset webservice: error during deployment EAR file on the java server

    Hi,
    I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
    During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
    <h5>
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
         Name:DeclaratieCheckRulesetEAR
         Vendor:sap.com
         Location:localhost
         Version:2008.03.12.12.02.09
         Deploy status:Warning
         Version:NEW
         Description:
              1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
              2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
               -> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
    server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 36 more
    Result
    Status:Warning
    </h5>
    Development Infrastructure:
    - development configuration: local development
    - development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
    Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
    - Created a ruleset (including two rules and one decision table) (development configuration: saptest)
    - Build and deploy the ruleset on the java server...
    - Created a dummy web module (development configuration: local development)
    - Added 3 dependencies (references) to the dummy web module:
    - References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
    - References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
    - References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
    - Dummy web module -> sync used DC's
    - Build dummy web module
    After that I started the Web Service Generation Tool and created the EAR file....
    1) NWDS -> window -> show view -> others -> deploy view -> deploy view
    2) Added the EAR file to External Deployable Archives
    3) deployed the file to the java server... then the warning occurs...
    How can I resolve this error?
    <h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
    And...
    <h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
    Can somebody help me with this problem?
    Kind regards,
    Martin Gerritsen

    Hello Martin Gerritsen,
    This is Arti from the PM team.
    It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
    You need to access the JavaEE Applications running on your AS. To do this -
    1. Open the nwa portal
    2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
    3. Search for the brms related applications available on the server.
    In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
    I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
    Regards,
    Arti

  • Deploying ear file to Web AS server

    Hi,
    I am trying to deploy the ear file from Netweaver Developer Studio using "Administrator " user. After Successfull deployment I logon to Enterprise portal server, immediatelty asked passwd expired & change password.I have changed that!
    Then I logged into Visual admin with changed password...
    But i was able to logon to SDM Remote GUI without changing SDM passwd
    once again i deployed same application after password changes and it is giving
    <b>deployment abort exception</b>
    Dec 13, 2006 1:10:17 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [021]Deployment aborted
    Settings
    SDM host : stcecommdv2
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/KALADH1.NAG/LOCALS~1/Temp/temp28154simpleEAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/KALADH1.NAG/LOCALS~1/Temp/temp28154simpleEAR.ear
    Aborted: development component 'simpleEAR'/'sap.com'/'localhost'/'2006.12.13.08.20.50':
    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: [stcecommdv2] with user name: [Administrator]                     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: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted
    Later I have changed SDM password..then also displays same Deployment Abort Exception
    How to do local deployment using "remotegui"
    Please help me!!!!
    Thanks
    Kaladhar

    Hi Kaladhar,
         See this thread same problem but solved:
    Re: An Deploy Problem about Credentials.
    Regards, Suresh KB

  • Urgent :- Unable to deploy EAR file in Oracle application server

    Hello folks,
    I am trying to deploy an application containing jsps and servlets
    packaged into EAR using ant. However when am trying to do so by using
    the Deploy EAR option in the Enterprise manager, it throws the
    following error -
    "Invalid J2EE application file specified - Jar file:
    /var/tmp/jar47241.tmp is missing its standard xml descriptor located at
    META-INF/ejb-jar.xml"
    I suspect that something could be wrong with regards to the way the ear
    file has been created.
    Please if someone could pin point the problem and help me understand
    the the above error message , it will be of great help to me and I d
    really appreciate this.
    Many Thanks,
    Ramn.

    Hello,
    I try to deploy an ear file (contains jar and war files) in Oracle Application server in linux, but the time is so long. The same file I deploy in a OAS in windows and the deploy time was 2 minutes, but in linux I leave the hole night and the session close and the deploy in unable.
    I don't know if I need configure an especial option in the OAS in Linux, how I can load my ear file.
    The OAS in windows was installed with oc4j options only, but the OAS in linux was full installation
    Please help me....
    Thanks.

  • Error message when deploying war file to sun web server 6.1

    i've been trying to deploy an application developed locally in tomcat to a local install of sun web server 6.1, and can't seem to get it to work. the error message i am getting now is:
    [05/Dec/2008:12:44:08] config ( 1640): for host xxx.xxx.xxx.xx trying to GET /cart/index.jsp, handle-processed reports: HTTP2205: The request method is not applicable to the requested resource.
    but that is the only error showing up. i've found some other forum topics involving memory issues (not the case here) and mime.type issues (not the case here), but nothing where this is the only error message showing up.
    any ideas? anyone?

    I deployed the application using a WAR file I created and the Server Manager.
    I've been able to get a JSP running in the $INSTALL_DIR/docs directory (database connectivity, result set printing, session data storing) but not outside of there.
    I switched to "finest" error reporting, but that isn't really helping much either.
    I even deployed one of the sample WAR files that came with the installation (webapps-simple.war), and it failed too, the error message I got was:
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, ntrans-j2ee reports: mapped uri "/jsp/num/numguess.jsp" in context "/simple" to resource "jsp"
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: context = StandardEngine[null].StandardHost[https-arlll3n4244.arcds.com].StandardContext[simple]
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: contextPath = /simple
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: wrapper = null
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: servletPath =
    [09/Dec/2008:10:35:51] fine ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: pathInfo = null
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: Authenticator[simple]: Security checking request GET /simple/jsp/num/numguess.jsp
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: Authenticator[simple]: Checking constraint 'SecurityConstraint[Protected Area]' against GET /jsp/num/numguess.jsp --> false
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: Authenticator[simple]: No applicable constraint located
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: Authenticator[simple]: Not subject to any constraint
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Mapping contextPath='/simple' with requestURI='/simple/jsp/num/numguess.jsp' and relativeURI='/jsp/num/numguess.jsp'
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Decoded relativeURI='/jsp/num/numguess.jsp'
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Trying exact match
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Trying prefix match
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Trying extension match
    [09/Dec/2008:10:35:51] finer ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WebModule[simple]: Mapped to servlet 'jsp' with servlet path '/jsp/num/numguess.jsp' and path info 'null' and update=true
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): JspEngine --> /jsp/num/numguess.jsp
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): ServletPath: /jsp/num/numguess.jsp
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): PathInfo: null
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): RealPath: C:\Sun\WebServer6.1\https-ARLLL3N4244.arcds.com\webapps\https-ARLLL3N4244.arcds.com\simple\jsp\num\numguess.jsp
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): RequestURI: /simple/jsp/num/numguess.jsp
    [09/Dec/2008:10:35:51] info ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: WEB2798: [cart/] ServletContext.log(): QueryString: null
    [09/Dec/2008:10:35:51] failure ( 5384): for host 192.168.112.96 trying to GET /simple/jsp/num/numguess.jsp, service-j2ee reports: StandardWrapperValve[jsp]: WEB2792: Servlet.service() for servlet jsp threw exception
    java.lang.IllegalArgumentException: WEB3446: setAttribute: Non-serializable attribute
         at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1280)
         at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
         at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
         at org.apache.jasper.runtime.PageContextImpl.setAttribute(PageContextImpl.java:271)
         at jsps.jsp._num._numguess_jsp._jspService(_numguess_jsp.java:81)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
         at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:688)
         at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:460)
         at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:376)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
         at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
         at com.iplanet.ias.web.WebContainer.service(WebContainer.java:579)

  • Geting error when deploy ear file on Oracle Application Server

    Hi,
    i m trying to deploy EAR on Oracle Application Server but i m getting ther Error
    Operation failed with error: Missing class: oracle.adf.controller.v2.lifecycle.PagePhaseListener Dependent class:
    any body know that what is this error
    plz help me
    Harish

    What version of JDeveloper are you using? And what version is your app server?

  • Error while deploying .EAR file Error 500 Internal server error

    While trying to run an application on NWCE i got this error.
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.UnsupportedClassVersionError: Bad version number in .class file
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:654)
        at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:198)
        at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:306)
        at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256)
        ... 60 more

    The error has been resolved by changing the compiler version for JAVA from 6.0 to 5.0 as I was using JDK5.0.

  • Opensso.war deployment fails in Sun App server 8.2 windows vissta business

    I tried deploying opensso.war in Sun App server 8.2 on windows vista business machine. Am getting following error.
    Deploying application in domain failed; C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied) ; requested operation cannot be completed C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied)
    Am I missing something

    This is windows permission to the folder issue

  • Problem while deploying the ear file in sap itc server

    error loading archive
    manifest attributes are missing while deploying ear file in sap itc server
    attribute key location is missing
    attribute key vendor is missing

    error loading archive
    manifest attributes are missing while deploying ear file in sap itc server
    attribute key location is missing
    attribute key vendor is missing

  • Can JSC support Sun App Server 9?

    Does anyone know if JSC can support sun app server 9?
    Last I heard was that 8.2 is the max version.
    Along the same line, is there any word of another update to JSC
    that will work with app server 9 and jdk 6???

    Hi!
    Actually You can deploy your application to Sun App Server 9.0, but probably not all features will work. But now You can download NetBeans 5.5 and Visual Web Pack for it (it's a next step of Creator's evolution) and this IDE supports GlassFish (opensourced Sun App Server 9.0).
    Thanks,
    Roman.

  • Deploy .war or .ear file to sun java web server 7.0 update 4

    Hi
    This could be a very daft question, but still I would like to get a clarification.
    My clients are a financial organisation, and for security and various other reasons they accept only .ear files. But this time the development and deployment would be done on Sun Java Web Server 7.0 update 4 . Now since its a web server I don't think I can deploy an .ear file.
    But sure I would like to get an answer from the experts here, is it possible to deploy and .ear file to Sun Java Web Server 7.0 before I can go back to my clients.
    Please help me here as I'm in a real big confusion here. Your help would be highly valuable to me.
    Thanks
    Jagdish

    Hi
    Thanks for the reply and I appreciate your help. Well I tried deploying an .ear file directly and web server 7 complains that it doesn't have a .war extension, understandably so.
    And then ripping apart the .ear file and deploying the .war file does work, as is expected of a web server.
    Well, about my customer is a bank and they have a very tight security policy, and why they need an .ear file is beyond my understanding. Well as far as this issue is concerned, I need a strong point so that I can get back to them that we need to comply to the third party software.
    But I didn't wan't to get back to them saying we can only provide a .war file and then later find out an .ear file could have done the job. And being seen as the technical experts we can't afford to make any mistake.
    Thanks
    Jagdish

  • Got this error after deploying ear file into OC4J server.

    Hello Frnsz,
    Can any one help to resolve the following error :)
    Got this error after deploying ear file into OC4J server.
    2008-06-04 14:57:58.551 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/pager-taglib.tld
    2008-06-04 14:57:58.566 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:57:58.566 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-bean.tld
    2008-06-04 14:57:58.598 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:57:58.598 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-html.tld
    2008-06-04 14:57:58.629 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:57:58.629 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-logic.tld
    2008-06-04 14:57:58.660 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:57:58.660 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-nested.tld
    2008-06-04 14:57:58.691 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:57:58.691 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-tiles.tld
    2008-06-04 14:57:58.723 NOTIFICATION Binding web application(s) to site default-web-site ends...
    2008-06-04 14:57:58.723 NOTIFICATION Application Deployer for MyEarProject COMPLETES. Operation time: 3422 msecs
    2008-06-04 14:58:04.895 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.910 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.926 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.942 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.957 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
    2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
    2008-06-04 14:58:05.020 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.jsp.parse.JspParseException: /WEB-INF/jsp/login.jsp: Line # 2, <%@ taglib uri="/WEB-INF/tld/struts-html.tld" prefix="html"%>
    Error: java.lang.ClassNotFoundException: org.apache.struts.taglib.html.MessagesTei
    Cheers,
    Cap

    Cross posted in correct forum
    [http://forum.java.sun.com/thread.jspa?threadID=5302192]

  • Deployed webservices is not compatible on sun app server 9

    I build my webservices in automated form provided by excelent wizards of jdev.
    I was not changed any name, and let all default descriptors generated to after I try to run it, and it run perfectly on oc4j, who is compatible with j2ee specification....
    But when I deploy it on Sun App Server 9(stable), the follow error is throwed
    "Invalid url pattern" like my screenshot: http://img115.imageshack.us/img115/4673/errojf1.gif
    I have tried to replace this url, but without sucess to run my web services. Someone with more experience can help me?
    I need to run it on SunAppServer.
    Thanks all

    You probably need to add the Sun specific deployment descriptor files to your WAR.
    JDeveloper doesn't have a utility to do that automatically for Sun.

Maybe you are looking for