Precompile web application in cluster

We are running 6.0 sp2 and are trying to determine how to have a web
          application precompile when deployed to a cluster.
          We have seen messages that there is an issue with 6.0 where you can only
          precompile if the web application is in exploded format.
          We have a scenario with 1 admin server servicing a cluster with 2 servers in
          the cluster. The web application is being deployed to the cluster.
          If we set the precompile option, the managed servers fail to deploy the
          application because of an error with precompiling.
          This seems to make sense since when the application is deployed, it is
          deployed as a war file.
          Does anyone have any advice as to how to deploy an application to a cluster
          and take advantage of precompiling?
          Is there any documentation that addresses this?
          

Eric Gordon wrote in message <3b39278e$[email protected]>...
          >We are running 6.0 sp2 and are trying to determine how to have a web
          >application precompile when deployed to a cluster.
          >We have seen messages that there is an issue with 6.0 where you can only
          >precompile if the web application is in exploded format.
          This is precompiling at build time. You have to hardcode the name of the
          server into the path of the precompiled files.
          >We have a scenario with 1 admin server servicing a cluster with 2 servers
          in
          >the cluster. The web application is being deployed to the cluster.
          >If we set the precompile option, the managed servers fail to deploy the
          >application because of an error with precompiling.
          I assume you are you use the precompile option in the web.xml? If so the
          problem may be that not every .jsp file can compile on its own. I have this
          problem and am solving it by changing the extension of include files from
          .jsp to .inc. Otherwise you get these fragment .jsp files that won't
          precompile because they are never going to be used stand alone.
          The only other reason I can see which could affect your ability to
          precompile on the managed servers is if you depend on startWebLogic
          settings, like extra classpath that prevents precompiling.
          Its too bad the weblogic server doesn't give detailed output when
          precompiling a war file.
          

Similar Messages

  • Error reading Web application occurs when starting one server in the cluster

    Hi All,
              I have configured two cluster servers in the win 2000. Admin server also win
              2000. One cluster server joins the cluster while other gives following error
              and starts. But it seems that it does not join to the cluster view because
              prevoius server only serves the requests. I have attached the log also.
              <> <101062> <[HTTP synergyserver] Error reading Web application
              "D:\bea\wlserver6.0\.\config\bd2kadmindomain\applications\.wl_temp_do_not_de
              lete_synergyserver\wl_local_comp12863.war">
              java.net.UnknownHostException: java.sun.com
              at java.net.InetAddress.getAllByName0(InetAddress.java:571)
              at java.net.InetAddress.getAllByName0(InetAddress.java:540)
              at java.net.InetAddress.getAllByName(InetAddress.java:533)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:159)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:221)
              at weblogic.net.http.HttpClient.<init>(HttpClient.java:85)
              at
              weblogic.net.http.HttpURLConnection.getHttpClient(HttpURLConnection.java:109
              at
              weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:30
              1)
              at java.net.URL.openStream(URL.java:798)
              at
              weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultRead
              erFactory.java:149)
              at
              weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
              Entity(DefaultEntityHandler.java:775)
              at
              weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
              Subset(DefaultEntityHandler.java:570)
              at
              weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner
              .java:1131)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocum
              entScanner.java:2177)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScan
              ner.java:2133)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatc
              h(XMLDocumentScanner.java:882)
              at
              weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
              nner.java:380)
              at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
              at
              weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
              va:123)
              at
              weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:1
              78)
              at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:446)
              at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:404)
              at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
              at weblogic.j2ee.Application.addComponent(Application.java:133)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:327)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:143)
              at
              weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
              76)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy40.addWebDeployment(Unknown Source)
              at
              weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
              t(WebServerMBean_CachingStub.java:1012)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:313)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:277)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:232)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:192)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy0.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2299)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:240)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:122)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:562)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
              48)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:285)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
              at $Proxy9.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:435)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1033)
              at weblogic.management.Admin.finish(Admin.java:493)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
              at weblogic.Server.main(Server.java:35)
              Each cluster servers domain names are different i.e. not "mydomain". The
              file its complaining is in the specified directory and it has proper
              priviledges.
              If anyone has an idea please respond.
              Thanks
              Nalika
              [synergyserver.log]
              

    You're getting that probably because the WL instance was not shut down properly.
    If that's the case, you'll need to remove an ldap lock file (with a .lok extension) in the directory of ldap files (under the server dir) .

  • Deploying Java Web Application (WAR-File) into a cluster environment

    Hi,
    we have a web application which has to read from and write to the file system.
    Since a short time we have a cluster environment (2 parallel servers) and since thisa time we have the problem, that files are worked double in the cluster. The application is working on both servers now and so we have this problem.
    Does anybody know how we have to deploy the application correctly in a cluster environment or do we have to change anything in our source code of the application?
    I didn't find any documentation about this.
    At the moment we have deployed the application on one of the two servers only, but I think there must be a better way to solve this problem.
    Thanks for your replies.
    Regards
    Thorsten

    Hi,
    I think first you need to wrap it into an EAR file, then you can deploy it.
    As far as I know standalone deployment of WAR is deprecated as of 640.
    similar threads:
    How to deploy .war on NWDI
    Deploying an existing WAR file into the Portal
    Hopefully this tutorial also gives some idea:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
    Regards,
    Ervin

  • Precompilation of JSPs for default web application

    Hello,
    Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
    However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
    However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
    Is there any way to precompile JSPs for my default web applications?
    Sincerely,
    Sergei Batiuk.

    Hello,
    Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
    However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
    However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
    Is there any way to precompile JSPs for my default web applications?
    Sincerely,
    Sergei Batiuk.

  • Just updated to 3.6.8. Now can't navigate reliably. Frequently get this error message: "Server Error in '/' Application. Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that configuration specifies th

    Just updated to 3.6.8. Now can't navigate reliably. Frequently get this error message: "Server Error in '/' Application. Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster." Pending fix of this glitch, is there a way to go back to previous version of Firefox that worked perfectly well?
    == URL of affected sites ==
    http://www.americanleather.com/ComfortSleeper/Madison.aspx?page=2

    Hi JH,
    According to your description, my understanding is that you got an error when you deleted  columns in SharePoint 2010.
    Please add the following string in <system.web> section of your web.config file :
    <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Never" />
    Note: before changing web.config, please make a backup for the file.
    Here are some similar posts for you to take a look at:
    http://forums.asp.net/p/1355367/2778642.aspx
    http://forums.asp.net/t/1166634.aspx
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Problem with Configuring Tomcat for running jsp web applications..Plz HELP

    I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
    to connect to the database. I have placed my project folder called
    tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
    a collection of html pages,jsp pages and images of my project. Also I created a
    WEB-INF folderand in that I have lib folder which contains catalina-root.jar
    , classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
    file which looks like this
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!--
    Copyright 2004 The Apache Software Foundation
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
    -->
    <web-app>
    <resource-ref>
    <description>Oracle Datasource example</description>
    <res-ref-name>jdbc/gdn</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    My Server.xml file in Tomcat\conf folder is as follows
    <!-- Example Server Configuration File -->
    <!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other -->
    <!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances. The Server
    listens for a shutdown command on the indicated port.
    Note: A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <Server port="8005" shutdown="SHUTDOWN">
    <!-- Comment these entries out to disable JMX MBeans support used for the
    administration web application -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
    <!-- Global JNDI resources -->
    <GlobalNamingResources>
    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <!-- Editable user database that can also be used by
    UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
    type="org.apache.catalina.UserDatabase"
    description="User database that can be updated and saved"
    factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
    pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/gdn" auth="Container"
    type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
    url="jdbc:odbc:gdn"
    username="system" password="tiger" maxActive="20" maxIdle="10"
    maxWait="-1"/>
    </GlobalNamingResources>
    <!-- A "Service" is a collection of one or more "Connectors" that share
    a single "Container" (and therefore the web applications visible
    within that Container). Normally, that Container is an "Engine",
    but this is not required.
    Note: A "Service" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <!-- Define the Tomcat Stand-Alone Service -->
    <Service name="Catalina">
    <!-- A "Connector" represents an endpoint by which requests are received
    and responses are returned. Each Connector passes requests on to the
    associated "Container" (normally an Engine) for processing.
    By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
    You can also enable an SSL HTTP/1.1 Connector on port 8443 by
    following the instructions below and uncommenting the second Connector
    entry. SSL support requires the following steps (see the SSL Config
    HOWTO in the Tomcat 5 documentation bundle for more detailed
    instructions):
    * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
    later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
    * Execute:
    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
    $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
    with a password value of "changeit" for both the certificate and
    the keystore itself.
    By default, DNS lookups are enabled when a web application calls
    request.getRemoteHost(). This can have an adverse impact on
    performance, so you can disable it by setting the
    "enableLookups" attribute to "false". When DNS lookups are disabled,
    request.getRemoteHost() will return the String version of the
    IP address of the remote client.
    -->
    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector
    port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" redirectPort="8443" acceptCount="100"
    connectionTimeout="20000" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to 0 -->
         <!-- Note : To use gzip compression you could set the following properties :
                   compression="on"
                   compressionMinSize="2048"
                   noCompressionUserAgents="gozilla, traviata"
                   compressableMimeType="text/html,text/xml"
         -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" disableUploadTimeout="true"
    acceptCount="100" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
    enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" acceptCount="100" connectionTimeout="20000"
    proxyPort="80" disableUploadTimeout="true" />
    -->
    <!-- An Engine represents the entry point (within Catalina) that processes
    every request. The Engine implementation for Tomcat stand alone
    analyzes the HTTP headers included with the request, and passes them
    on to the appropriate Host (virtual host). -->
    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">
    <!-- The request dumper valve dumps useful debugging information about
    the request headers and cookies that were received, and the response
    headers and cookies that were sent, for all requests received by
    this instance of Tomcat. If you care only about requests to a
    particular virtual host, or a particular application, nest this
    element inside the corresponding <Host> or <Context> entry instead.
    For a similar mechanism that is portable to all Servlet 2.4
    containers, check out the "RequestDumperFilter" Filter in the
    example application (the source for this filter may be found in
    "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
    Request dumping is disabled by default. Uncomment the following
    element to enable it. -->
    <!--
    <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
    -->
    <!-- Because this Realm is here, an instance will be shared globally -->
    <!-- This Realm uses the UserDatabase configured in the global JNDI
    resources under the key "UserDatabase". Any edits
    that are performed against this UserDatabase are immediately
    available for use by the Realm. -->
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
    resourceName="UserDatabase"/>
    <!-- Comment out the old realm but leave here for now in case we
    need to go back quickly -->
    <!--
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    -->
    <!-- Replace the above Realm with one of the following to get a Realm
    stored in a database and accessed via JDBC -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="org.gjt.mm.mysql.Driver"
    connectionURL="jdbc:mysql://localhost/authority"
    connectionName="test" connectionPassword="test"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="oracle.jdbc.driver.OracleDriver"
    connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
    connectionName="scott" connectionPassword="tiger"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="sun.jdbc.odbc.JdbcOdbcDriver"
    connectionURL="jdbc:odbc:CATALINA"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!-- Define the default virtual host
    Note: XML Schema validation will not work with Xerces 2.2.
    -->
    <Host name="localhost" appBase="webapps"
    unpackWARs="true" autoDeploy="true"
    xmlValidation="false" xmlNamespaceAware="false">
    <!-- Defines a cluster for this node,
    By defining this element, means that every manager will be changed.
    So when running a cluster, only make sure that you have webapps in there
    that need to be clustered and remove the other ones.
    A cluster has the following parameters:
    className = the fully qualified name of the cluster class
    name = a descriptive name for your cluster, can be anything
    mcastAddr = the multicast address, has to be the same for all the nodes
    mcastPort = the multicast port, has to be the same for all the nodes
    mcastBindAddr = bind the multicast socket to a specific address
    mcastTTL = the multicast TTL if you want to limit your broadcast
    mcastSoTimeout = the multicast readtimeout
    mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
    mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
    tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
    tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
    in case of multiple ethernet cards.
    auto means that address becomes
    InetAddress.getLocalHost().getHostAddress()
    tcpListenPort = the tcp listen port
    tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
    has a wakup bug in java.nio. Set to 0 for no timeout
    printToScreen = true means that managers will also print to std.out
    expireSessionsOnShutdown = true means that
    useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
    false means to replicate the session after each request.
    false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
    <%
    HashMap map = (HashMap)session.getAttribute("map");
    map.put("key","value");
    %>
    replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
    * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
    * Synchronous means that the thread that executes the request, is also the
    thread the replicates the data to the other nodes, and will not return until all
    nodes have received the information.
    * Asynchronous means that there is a specific 'sender' thread for each cluster node,
    so the request thread will queue the replication request into a "smart" queue,
    and then return to the client.
    The "smart" queue is a queue where when a session is added to the queue, and the same session
    already exists in the queue from a previous request, that session will be replaced
    in the queue instead of replicating two requests. This almost never happens, unless there is a
    large network delay.
    -->
    <!--
    When configuring for clustering, you also add in a valve to catch all the requests
    coming in, at the end of the request, the session may or may not be replicated.
    A session is replicated if and only if all the conditions are met:
    1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
    2. a session exists (has been created)
    3. the request is not trapped by the "filter" attribute
    The filter attribute is to filter out requests that could not modify the session,
    hence we don't replicate the session after the end of this request.
    The filter is negative, ie, anything you put in the filter, you mean to filter out,
    ie, no replication will be done on requests that match one of the filters.
    The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
    filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
    ending with .gif and .js are intercepted.
    The deployer element can be used to deploy apps cluster wide.
    Currently the deployment only deploys/undeploys to working members in the cluster
    so no WARs are copied upons startup of a broken node.
    The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
    When a new war file is added the war gets deployed to the local instance,
    and then deployed to the other instances in the cluster.
    When a war file is deleted from the watchDir the war is undeployed locally
    and cluster wide
    -->
    <!--
    <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
    managerClassName="org.apache.catalina.cluster.session.DeltaManager"
    expireSessionsOnShutdown="false"
    useDirtyFlag="true"
    notifyListenersOnReplication="true">
    <Membership
    className="org.apache.catalina.cluster.mcast.McastService"
    mcastAddr="228.0.0.4"
    mcastPort="45564"
    mcastFrequency="500"
    mcastDropTime="3000"/>
    <Receiver
    className="org.apache.catalina.cluster.tcp.ReplicationListener"
    tcpListenAddress="auto"
    tcpListenPort="4001"
    tcpSelectorTimeout="100"
    tcpThreadCount="6"/>
    <Sender
    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
    replicationMode="pooled"
    ackTimeout="15000"/>
    <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
    filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
    <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
    tempDir="/tmp/war-temp/"
    deployDir="/tmp/war-deploy/"
    watchDir="/tmp/war-listen/"
    watchEnabled="false"/>
    </Cluster>
    -->
    <!-- Normally, users must authenticate themselves to each web app
    individually. Uncomment the following entry if you would like
    a user to be authenticated the first time they encounter a
    resource protected by a security constraint, and then have that
    user identity maintained across all web applications contained
    in this virtual host. -->
    <!--
    <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.AccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    This access log implementation is optimized for maximum performance,
    but is hardcoded to support only the "common" and "combined" patterns.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
    </Host>
    </Engine>
    </Service>
    </Server>
    I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
    My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
    in a browser. Here I accept a username and password from the user and then do the validation in
    a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
    accordingly. However when I enter the username and password and click Go in the homepage, nothing is
    displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
    WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
    WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
    IS IT POSSIBLE?WHY WILL THIS HAPPEN?
    I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
    Is there any other thing that I need to set in classpath? Should I have my project as a
    WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

    I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
    to connect to the database. I have placed my project folder called
    tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
    a collection of html pages,jsp pages and images of my project. Also I created a
    WEB-INF folderand in that I have lib folder which contains catalina-root.jar
    , classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
    file which looks like this
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!--
    Copyright 2004 The Apache Software Foundation
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
    -->
    <web-app>
    <resource-ref>
    <description>Oracle Datasource example</description>
    <res-ref-name>jdbc/gdn</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    My Server.xml file in Tomcat\conf folder is as follows
    <!-- Example Server Configuration File -->
    <!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other -->
    <!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances. The Server
    listens for a shutdown command on the indicated port.
    Note: A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <Server port="8005" shutdown="SHUTDOWN">
    <!-- Comment these entries out to disable JMX MBeans support used for the
    administration web application -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
    <!-- Global JNDI resources -->
    <GlobalNamingResources>
    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <!-- Editable user database that can also be used by
    UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
    type="org.apache.catalina.UserDatabase"
    description="User database that can be updated and saved"
    factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
    pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/gdn" auth="Container"
    type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
    url="jdbc:odbc:gdn"
    username="system" password="tiger" maxActive="20" maxIdle="10"
    maxWait="-1"/>
    </GlobalNamingResources>
    <!-- A "Service" is a collection of one or more "Connectors" that share
    a single "Container" (and therefore the web applications visible
    within that Container). Normally, that Container is an "Engine",
    but this is not required.
    Note: A "Service" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <!-- Define the Tomcat Stand-Alone Service -->
    <Service name="Catalina">
    <!-- A "Connector" represents an endpoint by which requests are received
    and responses are returned. Each Connector passes requests on to the
    associated "Container" (normally an Engine) for processing.
    By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
    You can also enable an SSL HTTP/1.1 Connector on port 8443 by
    following the instructions below and uncommenting the second Connector
    entry. SSL support requires the following steps (see the SSL Config
    HOWTO in the Tomcat 5 documentation bundle for more detailed
    instructions):
    * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
    later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
    * Execute:
    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
    $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
    with a password value of "changeit" for both the certificate and
    the keystore itself.
    By default, DNS lookups are enabled when a web application calls
    request.getRemoteHost(). This can have an adverse impact on
    performance, so you can disable it by setting the
    "enableLookups" attribute to "false". When DNS lookups are disabled,
    request.getRemoteHost() will return the String version of the
    IP address of the remote client.
    -->
    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector
    port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" redirectPort="8443" acceptCount="100"
    connectionTimeout="20000" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to 0 -->
         <!-- Note : To use gzip compression you could set the following properties :
                   compression="on"
                   compressionMinSize="2048"
                   noCompressionUserAgents="gozilla, traviata"
                   compressableMimeType="text/html,text/xml"
         -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" disableUploadTimeout="true"
    acceptCount="100" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
    enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" acceptCount="100" connectionTimeout="20000"
    proxyPort="80" disableUploadTimeout="true" />
    -->
    <!-- An Engine represents the entry point (within Catalina) that processes
    every request. The Engine implementation for Tomcat stand alone
    analyzes the HTTP headers included with the request, and passes them
    on to the appropriate Host (virtual host). -->
    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">
    <!-- The request dumper valve dumps useful debugging information about
    the request headers and cookies that were received, and the response
    headers and cookies that were sent, for all requests received by
    this instance of Tomcat. If you care only about requests to a
    particular virtual host, or a particular application, nest this
    element inside the corresponding <Host> or <Context> entry instead.
    For a similar mechanism that is portable to all Servlet 2.4
    containers, check out the "RequestDumperFilter" Filter in the
    example application (the source for this filter may be found in
    "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
    Request dumping is disabled by default. Uncomment the following
    element to enable it. -->
    <!--
    <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
    -->
    <!-- Because this Realm is here, an instance will be shared globally -->
    <!-- This Realm uses the UserDatabase configured in the global JNDI
    resources under the key "UserDatabase". Any edits
    that are performed against this UserDatabase are immediately
    available for use by the Realm. -->
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
    resourceName="UserDatabase"/>
    <!-- Comment out the old realm but leave here for now in case we
    need to go back quickly -->
    <!--
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    -->
    <!-- Replace the above Realm with one of the following to get a Realm
    stored in a database and accessed via JDBC -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="org.gjt.mm.mysql.Driver"
    connectionURL="jdbc:mysql://localhost/authority"
    connectionName="test" connectionPassword="test"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="oracle.jdbc.driver.OracleDriver"
    connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
    connectionName="scott" connectionPassword="tiger"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm"
    driverName="sun.jdbc.odbc.JdbcOdbcDriver"
    connectionURL="jdbc:odbc:CATALINA"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!-- Define the default virtual host
    Note: XML Schema validation will not work with Xerces 2.2.
    -->
    <Host name="localhost" appBase="webapps"
    unpackWARs="true" autoDeploy="true"
    xmlValidation="false" xmlNamespaceAware="false">
    <!-- Defines a cluster for this node,
    By defining this element, means that every manager will be changed.
    So when running a cluster, only make sure that you have webapps in there
    that need to be clustered and remove the other ones.
    A cluster has the following parameters:
    className = the fully qualified name of the cluster class
    name = a descriptive name for your cluster, can be anything
    mcastAddr = the multicast address, has to be the same for all the nodes
    mcastPort = the multicast port, has to be the same for all the nodes
    mcastBindAddr = bind the multicast socket to a specific address
    mcastTTL = the multicast TTL if you want to limit your broadcast
    mcastSoTimeout = the multicast readtimeout
    mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
    mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
    tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
    tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
    in case of multiple ethernet cards.
    auto means that address becomes
    InetAddress.getLocalHost().getHostAddress()
    tcpListenPort = the tcp listen port
    tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
    has a wakup bug in java.nio. Set to 0 for no timeout
    printToScreen = true means that managers will also print to std.out
    expireSessionsOnShutdown = true means that
    useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
    false means to replicate the session after each request.
    false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
    <%
    HashMap map = (HashMap)session.getAttribute("map");
    map.put("key","value");
    %>
    replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
    * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
    * Synchronous means that the thread that executes the request, is also the
    thread the replicates the data to the other nodes, and will not return until all
    nodes have received the information.
    * Asynchronous means that there is a specific 'sender' thread for each cluster node,
    so the request thread will queue the replication request into a "smart" queue,
    and then return to the client.
    The "smart" queue is a queue where when a session is added to the queue, and the same session
    already exists in the queue from a previous request, that session will be replaced
    in the queue instead of replicating two requests. This almost never happens, unless there is a
    large network delay.
    -->
    <!--
    When configuring for clustering, you also add in a valve to catch all the requests
    coming in, at the end of the request, the session may or may not be replicated.
    A session is replicated if and only if all the conditions are met:
    1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
    2. a session exists (has been created)
    3. the request is not trapped by the "filter" attribute
    The filter attribute is to filter out requests that could not modify the session,
    hence we don't replicate the session after the end of this request.
    The filter is negative, ie, anything you put in the filter, you mean to filter out,
    ie, no replication will be done on requests that match one of the filters.
    The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
    filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
    ending with .gif and .js are intercepted.
    The deployer element can be used to deploy apps cluster wide.
    Currently the deployment only deploys/undeploys to working members in the cluster
    so no WARs are copied upons startup of a broken node.
    The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
    When a new war file is added the war gets deployed to the local instance,
    and then deployed to the other instances in the cluster.
    When a war file is deleted from the watchDir the war is undeployed locally
    and cluster wide
    -->
    <!--
    <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
    managerClassName="org.apache.catalina.cluster.session.DeltaManager"
    expireSessionsOnShutdown="false"
    useDirtyFlag="true"
    notifyListenersOnReplication="true">
    <Membership
    className="org.apache.catalina.cluster.mcast.McastService"
    mcastAddr="228.0.0.4"
    mcastPort="45564"
    mcastFrequency="500"
    mcastDropTime="3000"/>
    <Receiver
    className="org.apache.catalina.cluster.tcp.ReplicationListener"
    tcpListenAddress="auto"
    tcpListenPort="4001"
    tcpSelectorTimeout="100"
    tcpThreadCount="6"/>
    <Sender
    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
    replicationMode="pooled"
    ackTimeout="15000"/>
    <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
    filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
    <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
    tempDir="/tmp/war-temp/"
    deployDir="/tmp/war-deploy/"
    watchDir="/tmp/war-listen/"
    watchEnabled="false"/>
    </Cluster>
    -->
    <!-- Normally, users must authenticate themselves to each web app
    individually. Uncomment the following entry if you would like
    a user to be authenticated the first time they encounter a
    resource protected by a security constraint, and then have that
    user identity maintained across all web applications contained
    in this virtual host. -->
    <!--
    <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.AccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    This access log implementation is optimized for maximum performance,
    but is hardcoded to support only the "common" and "combined" patterns.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
    </Host>
    </Engine>
    </Service>
    </Server>
    I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
    My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
    in a browser. Here I accept a username and password from the user and then do the validation in
    a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
    accordingly. However when I enter the username and password and click Go in the homepage, nothing is
    displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
    WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
    WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
    IS IT POSSIBLE?WHY WILL THIS HAPPEN?
    I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
    Is there any other thing that I need to set in classpath? Should I have my project as a
    WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

  • Error when creating Web Application

    We have a 2 server farm connecting to a SQL cluster.  Servers 1 and 2 are web Front Ends.  When I want create in central admin a new web app  I get the following error.  It actually creates the content DB and I can see new web app in
    central admin but in IIS folder of this web site is empty - no files, no any folders inside.  
    I'll be grateful
    for the help.
    02/03/2014 10:27:37.38     w3wp.exe (0x0CFC)                           0x1E18    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Request
    (GET:http://tstwfe1:8000/systemsettings.aspx))    
    02/03/2014 10:27:37.38     w3wp.exe (0x0CFC)                           0x1E18    SharePoint Foundation       
         Logging Correlation Data          xmnv    Medium      Name=Request (GET:http://tstwfe1:8000/systemsettings.aspx)    12fc5e18-5b16-43a9-8863-e508d74e7b04
    02/03/2014 10:27:37.38     w3wp.exe (0x0CFC)                           0x1E18    SharePoint Foundation       
         Logging Correlation Data          xmnv    Medium      Site=/    12fc5e18-5b16-43a9-8863-e508d74e7b04
    02/03/2014 10:27:37.38     w3wp.exe (0x0CFC)                           0x1E18    SharePoint Foundation       
         Monitoring                        b4ly    High        Leaving Monitored Scope
    (PostResolveRequestCacheHandler). Execution Time=8.4318    12fc5e18-5b16-43a9-8863-e508d74e7b04
    02/03/2014 10:27:37.42     w3wp.exe (0x0CFC)                           0x1E18    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Request
    (GET:http://tstwfe1:8000/systemsettings.aspx)). Execution Time=28.2169    12fc5e18-5b16-43a9-8863-e508d74e7b04
    02/03/2014 10:27:38.17     OWSTIMER.EXE (0x05F8)                       0x245C    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job SchedulingApproval)    55797bac-6375-4f51-8dca-a20ff1374183
    02/03/2014 10:27:38.17     OWSTIMER.EXE (0x05F8)                       0x245C    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    SchedulingApproval). Execution Time=4.3691    55797bac-6375-4f51-8dca-a20ff1374183
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job UpdateHiddenListJobDefinition)    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohp    High        Enumerating
    all sites in SPWebApplication Name=SP - xxxT - Edit.    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohq    Medium      Site Enumeration Stack:   
    at Microsoft.SharePoint.Administration.SPSiteCollection.get_Item(Int32 index)     at Microsoft.SharePoint.Taxonomy.UpdateHiddenListJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
    jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)      90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server           
         Taxonomy                          hy93    Medium      Skipping check for the
    metadata hub timer job because no metadata proxies are active    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server           
         Taxonomy                          fuc1    Medium      Hidden list full sync
    timer job is being created and associated with the web application SP - xxxT - Edit.    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server           
         Taxonomy                          fuc3    Medium      Hidden list full sync
    timer job was not created and associated with the web application SP - xxxT - Edit.  jobDefinition was already set.    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohp    High        Enumerating
    all sites in SPWebApplication Name=SP - xxxT - Edit.    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohq    Medium      Site Enumeration Stack:   
    at Microsoft.SharePoint.Administration.SPSiteCollection.get_Count()     at Microsoft.SharePoint.Taxonomy.UpdateHiddenListJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
    jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)      90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohp    High        Enumerating
    all sites in SPWebApplication Name=SP - xxxT - Edit.    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Database                          4ohq    Medium      Site Enumeration Stack:   
    at Microsoft.SharePoint.Administration.SPSiteCollection.get_Item(Int32 index)     at Microsoft.SharePoint.Taxonomy.UpdateHiddenListJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
    jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)      90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:40.16     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    UpdateHiddenListJobDefinition). Execution Time=8.8473    90c4a860-31eb-4c79-8074-f1b5dfcc9434
    02/03/2014 10:27:41.16     OWSTIMER.EXE (0x05F8)                       0x198C    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job Health Statistics Updating)    ce9fe0e0-860a-4405-bffa-91bfcac0028f
    02/03/2014 10:27:41.16     OWSTIMER.EXE (0x05F8)                       0x198C    SharePoint Foundation       
         Topology                          8xqz    Medium      Updating SPPersistedObject
    SearchServiceApplicationMonitoring Name=Monitoring_7F19A5D194F942e6A9856FCFD6EE6F63. Version: 3978663 Ensure: False, HashCode: 60815176, Id: 1a82c0b8-4208-4199-9689-7f82fd256b00, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()    
    at Microsoft.Office.Server.Search.Monitoring.TraceDiagnosticsProvider.UpdateServiceApplicationHealthStats()     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService,
    Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)      ce9fe0e0-860a-4405-bffa-91bfcac0028f
    02/03/2014 10:27:41.20     OWSTIMER.EXE (0x05F8)                       0x198C    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    Health Statistics Updating). Execution Time=25.0976    ce9fe0e0-860a-4405-bffa-91bfcac0028f
    02/03/2014 10:27:43.46     w3wp.exe (0x0CFC)                           0x168C    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Request
    (GET:http://tstwfe1:8000/_admin/SelectCrossFirewallAccessZone.aspx))    
    02/03/2014 10:27:43.46     w3wp.exe (0x0CFC)                           0x168C    SharePoint Foundation       
         Logging Correlation Data          xmnv    Medium      Name=Request (GET:http://tstwfe1:8000/_admin/SelectCrossFirewallAccessZone.aspx)    746d4c9b-761b-431e-90cc-0557bc3826d4
    02/03/2014 10:27:48.16     OWSTIMER.EXE (0x05F8)                       0x18EC    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job SchedulingApproval)    9855194f-cb44-486f-b282-a578f72a938f
    02/03/2014 10:27:48.16     OWSTIMER.EXE (0x05F8)                       0x18EC    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    SchedulingApproval). Execution Time=3.6232    9855194f-cb44-486f-b282-a578f72a938f
    02/03/2014 10:27:50.16     OWSTIMER.EXE (0x05F8)                       0x0928    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job Search Health Monitoring - Trace Events)    6755d54d-03bd-42ed-8bd6-d0fa097e7daf
    02/03/2014 10:27:50.16     OWSTIMER.EXE (0x05F8)                       0x0928    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    Search Health Monitoring - Trace Events). Execution Time=6.6128    6755d54d-03bd-42ed-8bd6-d0fa097e7daf
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            fe8b    Medium       -  - Unable to activate worker process proxy object within the worker process: ipc://29ffade5-9a06-4ec5-b96b-f3b69c7a6952:7000  
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            fe8c    Medium       -  - Error activating the worker process manager instance within the worker process. - Inner Exception: System.InvalidOperationException:
    Unable to activate worker process proxy object within the worker process: ipc://29ffade5-9a06-4ec5-b96b-f3b69c7a6952:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()    
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            ei0t    Medium       - Process creation/initialization threw an exception. Stopping this process. "ipc://ca3d652e-8f80-4789-b527-65b8376a1da8:7000"  
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            i0o2    Monitorable     - Stopping shim process. Shim process name: "SPUCWorkerProcess" Shim PID: "0x29E8" Shim service
    url: "ipc://ca3d652e-8f80-4789-b527-65b8376a1da8:7000"    
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            i0o3    Monitorable     - Stopping proxy process. Proxy process name: "SPUCWorkerProcessProxy" Proxy PID: "0x236C" Proxy
    service url: "ipc://29ffade5-9a06-4ec5-b96b-f3b69c7a6952:7000"    
    02/03/2014 10:27:53.94     SPUCHostService.exe (0x09EC)                0x0ACC    SharePoint Foundation           
     Sandboxed Code Service            fe87    Medium       -  - Error activating the worker process manager instance within the worker process. - Starting worker process
    threw - Inner Exception: System.InvalidOperationException: Unable to activate worker process proxy object within the worker process: ipc://29ffade5-9a06-4ec5-b96b-f3b69c7a6952:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()  
    02/03/2014 10:27:54.93     w3wp.exe (0x0CFC)                           0x168C    SharePoint Foundation       
         Logging Correlation Data          xmnv    Medium      Site=/    746d4c9b-761b-431e-90cc-0557bc3826d4
    02/03/2014 10:27:55.08     w3wp.exe (0x0CFC)                           0x168C    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Request
    (GET:http://tstwfe1:8000/_admin/SelectCrossFirewallAccessZone.aspx)). Execution Time=11622.9457    746d4c9b-761b-431e-90cc-0557bc3826d4
    02/03/2014 10:27:57.18     OWSTIMER.EXE (0x05F8)                       0x1B24    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job SchedulingApproval)    824bd8e1-df0a-432b-9f18-5824b5c10e6d
    02/03/2014 10:27:57.18     OWSTIMER.EXE (0x05F8)                       0x1B24    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    SchedulingApproval). Execution Time=7.0564    824bd8e1-df0a-432b-9f18-5824b5c10e6d
    02/03/2014 10:28:00.17     OWSTIMER.EXE (0x05F8)                       0x245C    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job job-immediate-alerts)    9a92f513-e5bc-4475-91e3-a9c178554748
    02/03/2014 10:28:00.21     OWSTIMER.EXE (0x05F8)                       0x245C    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    job-immediate-alerts). Execution Time=16.4731    9a92f513-e5bc-4475-91e3-a9c178554748
    02/03/2014 10:28:00.35     SPUCHostService.exe (0x09EC)                0x0CB8    SharePoint Foundation           
     Sandboxed Code Service            f2yg    Medium       - CreateSandBoxedProcessWorker() is called    
    02/03/2014 10:28:00.38     SPUCHostService.exe (0x09EC)                0x0CB8    SharePoint Foundation           
     Sandboxed Code Service            b10e    Medium       - Created desktop: Service-0x0-86b8876$\Microsoft Office Isolated Environment     
    02/03/2014 10:28:00.67     SPUCWorkerProcess.exe (0x26B4)              0x1D98    SharePoint Foundation             Unified
    Logging Service           b8fx    High        ULS Init Completed (SPUCWorkerProcess.exe, onetnative.dll)    
    02/03/2014 10:28:05.72     SPUCWorkerProcess.exe (0x26B4)              0x26BC    SharePoint Foundation             Unified
    Logging Service           7a8a    Medium      LogWMIData: ConnectServer failed: 0x80041003    
    02/03/2014 10:28:06.17     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job job-application-server-admin-service)    2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:06.17     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    dkd5    High        synchronizing search service instance  
     2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:06.17     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    eff0    High        synchronizing search data access service instance  
     2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:07.36     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    dl2i    Medium      Search application 'Search Service Application': Provision
    start addresses in default content source.    2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:07.36     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    fa0w    Medium      Search application name is 'Search Service Application'.  
     2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:07.36     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    fa0x    Medium      Fetching UserProfileApplicationCollection...  
     2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:07.36     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Server Search    
         Administration                    fa0y    Medium      Fetching UserProfileApplication...    2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:07.39     OWSTIMER.EXE (0x05F8)                       0x1808    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    job-application-server-admin-service). Execution Time=1227.1104    2bdc150f-c10c-4fdc-9630-76f5fe204fb4
    02/03/2014 10:28:10.17     OWSTIMER.EXE (0x05F8)                       0x198C    SharePoint Foundation       
         Monitoring                        nasq    Medium      Entering monitored scope (Timer
    Job SchedulingUnpublish)    77ac5e41-7215-4783-b3ca-e9ff8aec57fd
    02/03/2014 10:28:10.19     OWSTIMER.EXE (0x05F8)                       0x198C    SharePoint Foundation       
         Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job
    SchedulingUnpublish). Execution Time=4.763    77ac5e41-7215-4783-b3ca-e9ff8aec57fd
     

    Hi Iron34,
    Looks like the SharePoint Foundation Sandboxed Code Service is having an issue.  You could see if the SharePoint 2010 User Code Host Service is enabled via services.msc, and then either disable it, or go to Manage Services on Server under system settings
    and turn off Microsoft SharePoint Foundation Sandboxed Code Service, if you're not concerned with containing user solutions, and then give the deployment another run.
    if the issue persists, adjust >
    http://www.sharepointpapa.com/blog/_layouts/15/start.aspx#/Lists/Posts/Post.aspx?ID=20
    Cheers,
    Stacy
    Stacy Anothersharepointblog.blogspot.com

  • Web application deployment takes too long?

    Hi All,
    We have a wls 10.3.5 clustering environment with one admin server and two managered servers separately. When we try to deploy a sizable web application, it takes about 1 hour to finish. It seems that it takes too long to finish the deployment. Here is the output from one of two managerd server system log. Could anyone tell me it is normal or not? If not, how can I improve this?
    Thanks in advance,
    John
    +####<Feb 29, 2012 12:11:03 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535463373> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 12:11:05 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9baa7a67b5727417:26f76f6c:135ca05cff2:-8000-00000000000000b0> <1330535465664> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
    +####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442300> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>+
    +####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>+
    +####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>+
    +####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>+
    +####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 0 records in 0 ms.>+
    +####<Feb 29, 2012 1:10:23 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1330539023098> <BEA-003107> <Lost 2 unicast message(s).>+
    +####<Feb 29, 2012 1:10:36 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539036105> <BEA-000111> <Adding Pinellas1tMS2 with ID -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 to cluster: Pinellas1tCluster1 view.>+
    +####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084375> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
    +####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084507> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
    Edited by: john wang on Feb 29, 2012 10:36 AM
    Edited by: john wang on Feb 29, 2012 10:37 AM
    Edited by: john wang on Feb 29, 2012 10:38 AM

    Hi John,
    There may be some circumstances like when there are many files in the WEB-INF folder and JPS don't use TLD.
    I don't think a 1hour deployment is normal, it should be much more faster.
    Since you are using 10.3.5, I suggesto you to install the corresponding patch:
    1. Download patch 10118941p10118941_1035_Generic.zip
    2. Uncompress the file p10118941_1035_Generic.zip
    3. Copy the required files (patch-catalog_XXXXX.xml, CIRF.jar ) to the Patch Download Directory (typically, this folder is <WEBLOGIC_HOME>/utils/bsu/cache_dir).
    4. Rename the file patch-catalog_XXXXX.xml into patch-catalog.xml .
    5. Start Smart Update from <WEBLOGIC_HOME>/utils/bsu/bsu.sh .
    6. Select "Work Offline" mode.
    7. Go to File->Preferences, and select "Patch Download Directory".
    8. Click "Manage Patches" on the right panel.
    9. You will see the patch in the panel below (Downloaded Patches)
    10. Click "Apply button" of the downloaded patch to apply it to the target installation and follow the instructions on the screen.
    11. Add "-Dweblogic.jsp.ignoreTLDsProcessingInWebApp=true" to the Java options to ignore additional findTLDs cost.
    12. Restart servers.
    Hope this helps.
    Thanks,
    Cris

  • Remove Web Application Proxy from ADFS 3.0

    We have two Web Application Proxies deployed with ADFS 3.0, however we'd like to remove one. We uninstalled the role from the server, however on the other Web Application Proxy it still shows the uninstalled server under Clustered Servers on the Remote
    Management mmc. How can I get this completely removed from ADFS?

    Hi,
    According to your description, are these two web application proxy servers clustered?
    By “on the other Web Application Proxy it still shows the uninstalled server under Clustered Servers”, do you mean that the uninstalled proxy server still shows as a node of cluster?
    If that’s the case, then it is normal, because uninstalling web application proxy role doesn’t remove its role as a node of cluster.
    More information for you:
    How to Evict a Node from a Windows Server 2008 Failover Cluster
    http://technet.microsoft.com/en-us/library/bb676524(v=EXCHG.80).aspx
    Best Regards,
    Amy Wang

  • Web-application deployment problem (404 - File not found)

    Hello
    Does anyone have had the same problems like me on deploying java web-applications on iPlanet WS 6.0?
    I started with the HelloWorld.war example that came with the server and went through the manual but no luck so far. Heres what I did:
    0. Checked that webapps are enabled in the servler.xml file
    1. Created a directory /opt/webapps and /opt/webapps/hello with sufficient permissions
    2. Copied the HelloWorld.war example to /opt/webapps
    3. Deployed the excample on my test-server using the webinterface.
    Heres the content of the web-apps.xml file of my testserver after step 3:
    [DTD here]
    <vs>
    <jsp-servlet enable="true">
    <init-param>
    <param-name>use-precompiled</param-name>
    <param-value>true</param-value>
    </init-param>
    </jsp-servlet>
    <web-app uri="/hello" dir="/opt/webapps/hello" enable="true"/>
    </vs>
    All files have been extracted to /opt/webapps/hello properly. The server has been restarted.
    When I finally point my browser to http://server/hello or hello/index.jsp I get only a 404 - File not found message by the server. The context path seems to be totaly ignored.
    Heres the error log of the server
    [17/Feb/2003:16:17:38] info (12040): successful server startup
    [17/Feb/2003:16:17:38] info (12040): iPlanet-WebServer-Enterprise/6.0SP2 B11/13/2001 00:49
    [17/Feb/2003:16:17:39] info (12041): Installing a new configuration
    [17/Feb/2003:16:17:39] info (12041): [LS ls1] http://XXX.XXX.XXX.XX, port 1080 ready to accept requests
    [17/Feb/2003:16:17:39] info (12041): A new configuration was successfully installed
    [17/Feb/2003:16:17:40] info (12041): Using the Solaris VM v1.2.2 from Sun Microsystems Inc.
    [17/Feb/2003:16:17:40] info (12041): Java VM classpath: /www/ns-home6sp2/plugins/servlets/examples/legacy/beans.10/SDKBeans10.jar:/opt/jdk1.2.2/lib/tools.jar:/www/ns-home6sp2/bin/https/jar/NSServletLayer.jar:/www/ns-home6sp2/bin/https/jar/NSJavaUtil.jar:/www/ns-home6sp2/bin/https/jar/NSJavaMiscUtil.jar:/www/ns-home6sp2/bin/https/jar/servlet.jar:/www/ns-home6sp2/bin/https/jar/servlet-2.3-filters-api.jar:/www/ns-home6sp2/bin/https/jar/jsp092.jar:/www/ns-home6sp2/bin/https/jar/jaxp.jar:/www/ns-home6sp2/bin/https/jar/crimson.jar:/www/ns-home6sp2/bin/https/jar/xalan.jar:/www/ns-home6sp2/bin/https/jar/jspengine.jar:
    [17/Feb/2003:16:17:40] info (12041): Loading IWSSessionManager by default.
    [17/Feb/2003:16:17:40] info (12041): IWSSessionManager: Maximum number of sessions is 1000
    [17/Feb/2003:16:17:40] info (12041): Adding web application (/hello) at (/opt/webapps/hello)
    [17/Feb/2003:16:17:40] info (12041): Loading IWSSessionManager by default.
    [17/Feb/2003:16:17:40] info (12041): IWSSessionManager: Maximum number of sessions is 1000
    [17/Feb/2003:16:17:40] info (12041): vs(https-duke)servlet 'snoop' class = 'SnoopServlet' loaded in context = '/hello'
    [17/Feb/2003:16:17:40] info (12041): snoop: init
    [17/Feb/2003:16:17:40] info (12041): Successfully initialized web application environment (web-apps.xml) for virtual server (https-duke)

    i had similar problem due to the incorrect jdk path...
    try http://..../hello/snoop, if this works, it seems that the jsp file cannot be compiled automatically and jdk path needs to be checked...

  • Problem While Deploying Java Web Application(Struts,Hiber) on NetWeaver 7.3

    Hi
    Fortunately i had a requirement to deploy my project JAVA (Struts, Hiber, DOJO)web application build as war file using Eclipse 3.4 on SAP Net Weaver 7.3
    Its showing in the Deployed Components List of NetWeaver ...
    When i tried to open the home page i found an exception ...
    The following is the log file content ... Hope its something related to hibernate ...
    >deploy s:\usr\sap\trans\EPS\in\LMSDemo.war on_deploy_error=stop
    Converting s:\usr\sap\trans\EPS\in\LMSDemo.war to sda
    s:\usr\sap\trans\EPS\in\LMSDemo.war has been successfully converted to sda
    Deploy settings:
    life_cycle=bulk
    on_deploy_error=stop
    on_prerequisite_error=stop
    version_rule=lower
    workflow=normal
    If there is an offline deployment, Telnet connection to host may be lost, but th
    e result can be seen using get_result command
    Processing deployment operation, wait...
    ===== PROGRESS START =====
    Deploying JavaEE_LMSDemo (sda) ...
    Deployment of JavaEE_LMSDemo (sda) finished.
    ===== PROGRESS END =====
    ===== DEPLOY RESULT =====
    sdu id: JavaEE_LMSDemo
    sdu file path: [S:\usr\sap\N73\J10\j2ee\cluster\server0\temp\tcbldeploy_contro
    ller\archives\31\263890545832850\SDA\LMSDemo.war]
    version status: NEW
    deployment status: Warning
    description: [
    1. Warning exception has been returned while the [] was starting. Warnings:[
    Warning occurred on server 102466650 during startApp of JavaEE/LMSDemo : com.sap
    .ASJ.web.000607 (Failed in component: JavaEE/LMSDemo, ) Initialization of servle
    t action failed. Check init() method of servlet. Error is: [javax.servlet.Unav
    ailableException: org/slf4j/LoggerFactory]
    ===== END DEPLOY RESULT =====
    ===== Summary - Deploy Result - Start =====
    Type | Status : Count
    > SCA(s)
    > SDA(s)
    - Warning : [1]
    Type | Status : Id
    > SCA(s)
    > SDA(s)
    - Warning : JavaEE_LMSDemo,
    ===== Summary - Deploy Result - End =====
    >
    Does anyone knows this ..

    In your deploy message it says that it can't initialize your servlet because it is missing a java class from the logging framework that is used by hibernate. It might also be possible that that logging framework ([SL4J|http://www.slf4j.org/]) is configured to use a logger that is not available in your Netweaver 7.3 installation. Maybe check the documentation of sl4j for details. There is also a [document|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/bf0d57db-0c01-0010-6fa3-83503981eed4] about Hibernate on Netweaver but that was back when Hibernate did not use sl4j. Probably you just need to add the sl4j library to your libs.

  • Problem with CRM 2011 web front end cluster

    Hi.
    We have a CRM 2011 (RU17) environment with a SQL DB server and 2 web front end CRM server in a cluster.
    Since few days (about 10) it seems that one of the 2 nodes is not working, and since yesterday many users report access problems when calling the application by cluster name - as usual since we deployed CRM 1 year ago.
    I tried myself, and I can run the application by cluster name without problems. If it try the separate notes addresses, one of them works, the other doesn't.
    I checked the 2 web front end servers, and are (or seem) both properly configured, with all patches installed.
    Following the information I got from Event viewer. Any suggestion welcomed!
    Many thanks and Best regards
    On the 'faulty' server I have different errors at event viewer level:
    Faulting application name: Microsoft.Crm.Sandbox.HostService.exe, version: 5.0.9690.4150, time stamp: 0x53559982
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
    Exception code: 0xe0434352
    Fault offset: 0x000000000000940d
    Faulting process id: 0x6f8
    Faulting application start time: 0x01cf8f93aa9a7ff8
    Faulting application path: C:\PROGRA~1\MICROS~4\Server\bin\Microsoft.Crm.Sandbox.HostService.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: f5019a68-fb86-11e3-9f21-005056853970
    Application: Microsoft.Crm.Sandbox.HostService.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Runtime.InteropServices.COMException
    Stack:
       at Microsoft.Crm.Sandbox.HostService.InitializeThreadProc(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    The Sandbox Host service has encountered an unexpected error and has stopped.
     Source: Microsoft.Crm.Sandbox.HostService.exe (1784)
     Error: System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.
       at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.get_AdsObject()
       at System.DirectoryServices.PropertyValueCollection.PopulateList()
       at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
       at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
       at Microsoft.Crm.SecurityUtils.GetSidFromAD(Guid objectGuid)
       at Microsoft.Crm.Sandbox.SandboxHost.SetPrivilegeUserGroupId(Guid privilegeUserGroupId)
       at Microsoft.Crm.Sandbox.HostService.InitializeThreadProc(Object stateInfo)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    On the 'running' server event viewer I only have one error, related to mail router:
    #23379 - Could not verify the version of Microsoft Dynamics CRM at http://alkcg106.d30.intra:5555/AkzoNobelIndustrialCoatings. There was no endpoint listening at http://alkcg106:5555/AkzoNobelIndustrialCoatings/XRMServices/2011/Organization.svc that could
    accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

    Apologize for not having indicated here the resolotion I got thanks to MS support...
    We enabled the trace and we got
    a http error page stating maxQueryStringLength was insufficient. We changed the maxQueryStringLength and QueryString values in the CRM web.config value to 10240.
    We also noticed an error related to the DC being unavailable. We checked in the CRM registry hive and see in the non-working server you had a PreferredDc key pointing to “AMDNAD”. On pinging
    AMDNAD we see it is not reachable. We removed the PreferredDc key and after iisreset we can navigate to crm.

  • Displaying a photo obtained from SAP R/3  in a Web Application Module

    Hi,
    I am currently developing a Web Application Module (through NWDS) which displays details of employees (name, last name, picture, etc...) obtained from a RFC function module called remotely through SAP JCA connector.
    I could obtain the picture passed through the RFC module, but now I need to displayed in a JSP page. I first start to look for a service which allows me to upload the picture to an application server cache as I have already done with
    IWDCachedWebResource
    in Web Dynpro development, but could not find anything alike. Then I tried to upload the picture to a relatively referenciable (Web Application) path, that I can use as a source for the IMG HTML tag, but I am just able to save the picture at the root directory of the application server (/usr/sap/SID/JC00/j2ee/cluster/server0) and this path can not (and must not) be referenced through my application JSP.
    Please any help or workaround will be gladly welcome
    Best regards,
    Jonathan

    Ravi,
    We have tried the same from SOAP UI client also and it is not working,
    same result as PI. But I repeat the Service is working from DOTNET applications.
    If it is not working in SOAP UI then it will not work in PI also. I suggest you to re-import the WSDL in you .net application and check.
    Regards,
    Ramesh

  • Some users hitting error page when trying to access Web Applications...why?

    Hi,
    I have a SharePoint 2010 setup with 4 WFE, 4 APP Servers and 1 DB Server.
    After reading up a while back which services should be running on which server layer I remove the Web Application Service from APP Server (using Central Admin). The service is currently in error state on that machine. I had also removed a WFE Server which
    was not required and ensured all WFE had Web Application Service running as Microsoft Specified. I have checked each WFE and they have all same Web Applications in IIS. I have accessed a specific Web Application (that a user said they couldn't access) on 2
    of the 3 WFE servers when remoted into them, but one prompts me for login details. I have looked at the NLB on each WFE Server and saw that 2 out of three servers had all three servers in cluster. One that didn't was not same server as had problems accessing
    Web Application. I have removed a Server from Cluster and added it back as I saw Priorities were 1,2,4 (3 must have been initial removed server) and added it back again so Priorities were 1,2,3.
    Can anyone explain what may have happened in this scenario? It seems I think to be hitting this server with the problem accessing the Web Application. It seems to time out. How do I resolve this? DO I need to resync?
    Thanks.
    John.    

    Hi John,
    For your issue, it can be caused by that you remove  and  re-add a WFE from the NLB cluster. As  the Priority was changed, you need to disconnect and reconnect your SharePoint using SharePoint Products Configuration Wizard.
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Eric Tao
    TechNet Community Support

Maybe you are looking for