Servlet Example

Sir,
Based on bug 7313163; the documentation example http://youngcow.net/doc/oracle10g/appdev.102/b14259/xdb23jv1.htm#i1045379 is for a non-existing feature.
Thread Re: javax.naming.* classes don't work inside the database to load XMLDB doc talks about this.
Mark Drake said: "demo that shows how to write some JNDI wrappers over JDBC to get some (not all) of the JNDI methods working", I need this example plz.
Islam.

Please download the latest version of the XFiles demo from the XML DB page on OTN.

Similar Messages

Am getting the following error while running the servlet example

Hi,
am getting the following error while running the servlet example
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.NullPointerException
     edu.dao.StudentDao.insertStudent(StudentDao.java:18)
     edu.servlet.StudentServlet.doGet(StudentServlet.java:25)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.20 logs.
Thanks
//sreekanth

Hi,
the following code i have written in StudentDao
package edu.dao;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import org.apache.commons.dbutils.DbUtils;
import edu.model.Student;
import edu.util.DBUtil;
public class StudentDao {
     public void insertStudent(Student student) {
          String stuQuery = "INSERT INTO STUDENT VALUES(?,?)";
          Connection connection = DBUtil.getConnection();
          PreparedStatement preparedStatement = null;
          try {
               preparedStatement = connection.prepareStatement(stuQuery);
               preparedStatement.setString(1,student.getStudentNo());
               preparedStatement.setString(2, student.getStudentName());
               preparedStatement.executeUpdate();
          } catch(SQLException e){
               System.out.println("..Sql exception......");
          }finally {
               DbUtils.closeQuietly(connection,preparedStatement,null);
}

J2EE tutorial (June 17 '04) servlet example compilation error

This is a copy of my previous post on the same topic, but this one has a more self-desriptive subject line. Apologies for duplication.
I am trying the first servlet example in the J2EE tutorial, June 17, 2004, pgs 443 - 448. I have completed all the steps as described. However, the URL results in the following error. I would like to point out that I am using the URL http://localhost:8081/bookstore1/bookstore (instead of port 8080 because the admin console suggests that port 8081 is an available http port):
Assistance would be appreciated.
HTTP Status 404 - /bookstore1/bookstore
type Status report
message /bookstore1/bookstore
description The requested resource (/bookstore1/bookstore) is not available.
Sun-Java-System/Application-Server-PE-8.0
I looked at the logviewer and there are 3 severe errors in the log:
1. Application Server
Log Entry Detail
Details
Timestamp: Aug 6, 2004 14:36:28.375
Log Level: SEVERE
Logger: javax.enterprise.system.container.web
Name-Value Pairs:
_ThreadID=12;
Record Number: 754
Message ID: WebModule[bookstore1]Exception sending context initialized event to listener instance of class listeners.ContextListener java.lang.NoClassDefFoundError
Complete Message
exception/OrderException
at listeners.ContextListener.contextInitialized(Unknown Source)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3679)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4140)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:873)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:171)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:193)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:855)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:947)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:729)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:147)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:224)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:488)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:475)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:302)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:107)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3880)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:680)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.phasing.DeploymentService.multicastEvent(DeploymentService.java:341)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:284)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:115)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:92)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:69)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:768)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:583)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:200)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
at java.lang.Thread.run(Thread.java:534)
2. Application Server
Log Entry Detail
Details
Timestamp: Aug 6, 2004 14:36:28.375
Log Level: SEVERE
Logger: tomcat.server./bookstore1.Context
Name-Value Pairs:
_ThreadID=12;
Record Number: 755
Message ID:
Complete Message
Error listenerStart
3. Application Server
Log Entry Detail
Details
Timestamp: Aug 6, 2004 14:36:28.375
Log Level: SEVERE
Logger: tomcat.server./bookstore1.Context
Name-Value Pairs:
_ThreadID=12;
Record Number: 756
Message ID:
Complete Message
Context startup failed due to previous errors

I had the same problem. It was caused by not including \j2eetutorial14\examples\web\bookstore\dist\bookstore.jar in the bookstore1.war. You may need to build the bookstore.jar file first if you haven�t already.

SIMPLEST servlet example please

Hi,
I was wondering if someone could post a java servlet example that accepts a string array (let's say we pass "A" and "B") and returns back a string array (let's say "1" and "2") without having to use a doGet or doPost. This would simply be passed as a value as one normally might, using a procedure or function.
Help on this is greatly appreciated. I am using this to access DB information, and already have the rest of the code finished, however I must implement this as a servlet.
Thanks...

Hello lafnjack,
A servlet is a kind of plugin-class that is connected to a HTTP-server to handle HTTP requests by interpreting the request itself and generating the response.
Therefore, a servlet is called through methods that are in parallel to the HTTP requests GET, POST and in some cases the other variants. Having said this, it should be obvious that a servlet has no more options for functioning than implementing doGet/doPost etc functions.
Silvio Bierman

Compiled Tomcat Servlet Example & got JAR, not WAR?

Is there a basic reference on how to create a simple servlet with NetBeans 4.1 and deploy it to Tomcat?
When I created the project I chose Samples->Web->Tomcat Servlet Example, and yet it does not create a WAR file on compilation.
And of course once I'm past that I have to figure out how to edit the XML file, I gather.
I need a reference that will hold me by the hand and walk me through it once to kick start me.
After that I think I can make it without having to ask such newbie questions.

Hi,
not sure to what extent you are clear in build.xml file (done thru ant).
what i can tell you is, ant creates any archive file (be it .jar, .war, .ear) with the tasks named "jar" (<jar jarfile="yourfilename.jar"..>), "war" and "ear". But both war and ear are the extensions of the jar only.
You can achieve creation of any archive file with the jar task itself.
you need to take care of the following...
(1) you can /should edit the extension of the files at every stage.. first .jar and then .war and then .ear (if necessary) => basic flow
(2) at every step, you have to have a file inclusion inside the corresponding archive file..
say for example, for a .jar file you should include all the compiled .class files, and ejb-jar.xml (incase you use ejbs) and other built-in jar files....
In case of .war files (web archive) you should include the web.xml file, any static files (html, jsp etc), any tld files - it goes with your application's nature and requirement.....
fyi, i m including a sample build.xml file which i use for a webapplication, so it deals with war...
<?xml version="1.0" encoding="UTF-8"?>
<project name="ServletsReqDispFwd" default="deploy">
     <property name="top" value="."/>
     <property name="webinf" value="${top}/WEB-INF"/>
     <property name="lib" value="${webinf}/lib"></property>
     <property name="classes" value="WEB-INF/classes"/>
     <property name="jboss.dir" value="D:\jboss-3.2.2RC3\server\default\deploy"></property>
     <property name="tomcat.dir" value="D:\jakarta-tomcat-4.1.27\webapps"></property>
     <property name="warfile" value="ServletsReqDispFwd.war"></property>
     <property name="src" value="${top}/src"/>
     <property name="web.xml" value="WEB-INF/web.xml"/>
     <target name="package">
          <javac srcdir="${src}" destdir="${classes}"
                 listfiles="true" debug="true" verbose="true"
                      classpath="${lib}/*.jar"/>
          <war warfile="${warfile}" webxml="${web.xml}">
               <webinf dir="${top}">
                    <include name="**/*web*.xml"/>
                    <include name="**/*application*.xml"/>
                    <exclude name="src/**/*.xml"/>
               </webinf>
               <lib dir="${lib}">
                    <include name="*.jar"/>
               </lib>
               <fileset dir="." includes="**/*.html"/>
               <classes dir="${classes}" includes="**/*.class"></classes>
          </war>
     </target>
     <target name="deploy" depends="clean,package">
          <copy file="${warfile}" todir="${tomcat.dir}" overwrite="true"></copy>
     </target>
     <target name="clean">
          <delete dir="${classes}">
               <filename name="*.class"/>
          </delete>
          <delete>
               <fileset dir="${top}" includes="${warfile}"/>
          </delete>
          <delete>
               <fileset dir="${tomcat.dir}" includes="${warfile}"/>
          </delete>
     </target>
</project>hope this contribues to a certain extent to help you edit the buildfile (xml file as you go) to meet your requirement.....

Trouble compiling servlet example

Hi All, I am trying out an example for servlets and I ran into trouble compiling the the file called "FormProcessingServlet.java" in tutorial located here: http://developer.java.sun.com/developer/onlineTraining/Servlets/Fundamentals/magercises/FormPostingAndProcessing/index.html
The exact problem happens in this line:
isStructure = context.getResourceAsStream(paramStructureFile[0]);
The error says:
FormProcessingServlet.java:127: cannot resolve symbol
symbol : method getResourceAsStream (java.lang.String)
location: interface javax.servlet.ServletContext
isStructure = context.getResourceAsStream(paramStructureFile[0]);
anyone else ran into this problem? How do I fix this? Thanks.

"cannot resolve symbol" means that the JVM can't find a particular class.
Adjust your systems classpath variable to include all the jar files that you use, I also add "." to include files in the current directory I'm working from.

JWSDP Tutorial - Servlet Example

I am trying to run the bookstore example in the Servlet section of the JWSDP on Red Hat 7.3.I am also getting confused over ANT and the Tomcat Manager.
I need to build the bookstore example and the instructions read: (for those who know the tutorial)
1. In a terminal window, go to /docs/tutorial/examples/web/bookstore1
2. Run ant build - The build target will spawn any necessary compilations and copy files to the docs/tutorial/examples/web/bookstore1/build directory.
3. Make sure Tomcat is started.
4. Run ant install - The install target notifies Tomcat that the new context is available.
5. Start the Pointbase database server and populate the database if you have not done so already
6. Open the bookstore URL http://localhost:8080/bookstore1/enter
On the command line I can run ANT BUILD fine, but ANT INSTALL fails. (It also fails in Tomcat Manager...but not sure whether I can use this instead of ANT INSTALL?)
I know this is sketchy but does anyone have any idea?
Regards
Scott

Hi Scott,
Thank you any way.
Last time, I met it and carried the tutorial on by compiling and copying manually. Then, I came back to set the ant.jar into path&classpath, and it worked.(ant build)
Today, I'm trying on "hello1" example, but can't get though.
Maybe it's still classpath and path issue, as I can't compile two servlet classes by javac from command line, but from Forte, it passed.
Cheers!
Zhan

XML-RPC with Servlet Example

Hi,
I was wondering if someone could point me to a good, simple example of using XML-RPC with a servlet. I have tried Apache's site where they write: "A full example servlet is included in the package" but I've downloaded it twice from two different mirrors and it is not there. Neither is the entire "examples" directory listed in the README. Hence, my request here. Thanks for any help you can provide.

Push...

Simple Servlet Example - Using Tuxedo JOLT

Hi
I am trying to run the sample Tuxedo provided application which uses Servlets. I had configured JSL & JSH properly and had booted the Tuxedo Service and they are all running properly.
I have WebLogic Server installed and had created the JoltSessionPool with name "samplejoltpool" and had also defined the StartupClass & ShutdonClass. While defining the JoltSessionPool i had given min services as 5 and max services as 10 becasue I used the following definition for JSL in UBBCONFIG.
CLOPT="-A -- -n //172.20.34.17:7777 -m5 -M10 -x5"
No as per the guide they are asking me to Restart WebLogic Server when I did so. I got an error I went into WebLogic Log and found out the following in the Log. It states
CRITICAL [06:52:35] (JDKLog4jAdapter.java:log:80) - Failed to invoke startup class "TuxedoStartupClass", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
The Entire Trace from the Log file is:
NOTICE [06:52:34] (JDKLog4jAdapter.java:log:80) - The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.
INFO [06:52:34] (JDKLog4jAdapter.java:log:80) - Initialized the Diagnostic Accessor Service.
INFO [06:52:34] (JDKLog4jAdapter.java:log:80) - Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)
CRITICAL [06:52:35] (JDKLog4jAdapter.java:log:80) - Failed to invoke startup class "TuxedoStartupClass", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=demojoltpool,Type=JoltConnectionPool : Cannot create 5 connections
     at bea.jolt.pool.servlet.weblogic.impl.PoolManagerStartUpJMX.startup(PoolManagerStartUpJMX.java:216)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:615)
     at bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(PoolManagerStartUp.java:38)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:615)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
     at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppActivation(ClassDeploymentManager.java:158)
     at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Can someone help me out to overcome this error. The JooltSessionPool entry properties are as below.
Name : demojoltpool
Min Pool Size : 5
Max Pool Size : 10
Recv Timeout : 30
Prim Addr : //172.20.34.17:7777
With Regards
Venkat
Tata Consultancy Services
India

The problem was with JVM total memroy available when I try to create 5 Session Pools the JVM memeory goes to 97% that is the main reason why it is failling. I restarted all the processes in the server now it seems to be working fine without any issues.

ServerException deploying bookstore servlet example

I am trying to run the examples in the tutorial addendum (1.4 beta). I am using JSDK 1.4.1 and J2EE 1.4 on Windows XP.
I have run ant build and ant package-bookstore in the bookstore directory.
I then ran ant build in the bookstore1 directory and ran ant package. Everything built successfully. Then I started the J2EE server by typing j2ee at the command prompt and ran ant deploy. I got the following output:
C:\j2sdkee1.4\doc\tutorial\examples\web\bookstore1>j2ee
Redirecting application output to C:\j2sdkee1.4\logs\launcher.server.log
C:\j2sdkee1.4\doc\tutorial\examples\web\bookstore1>ant deploy
Buildfile: build.xml
set-deploytool:
deploy:
[exec] Could not connect to localhost
[exec] com.sun.enterprise.tools.deployment.main.ServerException: Could not
connect to localhost
[exec] at com.sun.enterprise.tools.deployment.main.ServerManager.getJar
Installer(ServerManager.java:587)
[exec] at com.sun.enterprise.tools.deployment.main.Main.deployModule(Ma
in.java:538)
[exec] at com.sun.enterprise.tools.deployment.main.Main.internalMain(Ma
in.java:205)
[exec] at com.sun.enterprise.tools.deployment.main.Main.main(Main.java:
114)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] Sender object Deploytool (Main) : Could not connect to localhost
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
[exec] Error occurred: com.sun.enterprise.tools.deployment.main.ServerExcep
tion: Could not connect to localhost
[exec] com.sun.enterprise.tools.deployment.main.ServerException: Could not
connect to localhost
[exec] at com.sun.enterprise.tools.deployment.main.ServerManager.getJar
Installer(ServerManager.java:587)
[exec] at com.sun.enterprise.tools.deployment.main.Main.deployModule(Ma
in.java:538)
[exec] at com.sun.enterprise.tools.deployment.main.Main.internalMain(Ma
in.java:205)
[exec] at com.sun.enterprise.tools.deployment.main.Main.main(Main.java:
114)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
[exec] Result: 1
BUILD SUCCESSFUL
Total time: 8 seconds
C:\j2sdkee1.4\doc\tutorial\examples\web\bookstore1>
I'd really appreciate any help on this...
Thanks,
Francois

you donnot complete to start the j2ee.
type the following:
j2ee
then wait for several minutes

Where to place HTMl files in tomcat while executing Servlets examples ?

Hi,
I'm learning servelets (HttpServlets). in that input is given through html files.now i dont know where to place that html file in apache tomcat server
This is my Directry Structure
Java's ---- C:\Program Files\Java\jdk1.5.0\bin
Tomcat's--C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class ThreeParams extends HttpServlet
public void doGet(HttpServletRequest request,HttpServletResponse response)throws ServletException, IOException
response.setContentType("text/html");
PrintWriter out = response.getWriter();
String title = "Reading Three Request Parameters";
String docType ="<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 " +"Transitional//EN\">\n";
out.println(docType +"<HTML>\n" +"<HEAD><TITLE>" + title + "</TITLE></HEAD>\n" +"<BODY BGCOLOR=\"#FDF5E6\">\n" +"<H1 ALIGN=\"CENTER\">" + title + "</H1>\n" +"<UL>\n" +" <LI><B>param1</B>: "+ request.getParameter("param1") + "\n" +" <LI><B>param2</B>: "+ request.getParameter("param2") + "\n" +" <LI><B>param3</B>: "+ request.getParameter("param3") + "\n" +"</UL>\n" +"</BODY></HTML>");
}HTML code ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Collecting Three Parameters</TITLE></HEAD>
<BODY BGCOLOR="#FDF5E6">
<H1 ALIGN="CENTER">Collecting Three Parameters</H1>
<FORM ACTION="ACTION="C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\root\WEB-INF\classes.ThreeParams">
First Parameter: <INPUT TYPE="TEXT" NAME="param1"><BR>
Second Parameter: <INPUT TYPE="TEXT" NAME="param2"><BR>
Third Parameter: <INPUT TYPE="TEXT" NAME="param3"><BR>
<CENTER><INPUT TYPE="SUBMIT"></CENTER>
</FORM>
</BODY></HTML>
{code}
servlet code is compiling without any errors, now where should i place the class file and html file in tomcat to execute this program..

webapps\yourapplicationname\WEB-INF\

Error while running a Servlet program in Eclipse IDE

Hi,
I have tried running the following program in the Eclipse Editor. It doesnt compile. I have installed the Tomcat plugin too.
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
public class HTTPGetServlet extends HttpServlet {
     public void doGet(HttpServletRequest request,
               HttpServletResponse response)
     throws ServletException, IOException
          PrintWriter output;
          response.setContentTe("text/html");
          output=response.getWriter();
          StringBufer buf=new StringBuffer();
          buf.append("<HTML><HEAD><TITLE>\n");
          buf.append("A simple servlet example\n");
          buf.append("</TITLE></HEAD><BODY>");
          buf.append("<H1>Welcome to the world</H1>\n");
          buf.append("</BODY></HTML>");
          out.println(buf.toString());
          output.close();
On a closer look i realized that the IDE is showing as error any import statements i type in. Can anyone help me get over this problem? Thanks a lot in advance.
bye
V

You need to add the JAR containing the servlet API in the external JARs for the project.
Regards,
Carol.

Error 404 -- Not Found, when a Servlet is invoked from browser

Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
          even the simplest servlet.
          I painstakenly went through all the steps that are listed in the WebLogic
          Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
          have missed a step somewhere.
          I have modified the weblogic.properties file as per all the instrustions,
          but the server simply won't recognize any servlets, not even the SqlServlet
          that came with the server as an example.
          It would require more than 1 exchange of posts to resolve it for me, and I
          am wondering if one of you is willing to work with me on this until I have
          managed to configure the server to make a servlet work on it.
          The server does function as a Web server as I can run the index.html
          document by entering the URL: http://localhost:7001/index.html
          I am pasting the contents of weblogic.properties file below to get the
          person who is willing to help me started.
          The machine I have is a Pentium III with Windows 2000 Professional on it.
          It's a home machine and the WebLogic server is the freely downloadable
          version. I am using it to prepare for a potential contract work.
          I have managed to modify setEnv.cmd file and have managed to compile the
          SqlServlet.java, which is an example servlet. Neither this particular
          servlet nor a HelloWorld type of very basic servlet I have written are
          recognized by the server.
          As you can see from my weblogic.properties file (pasted at the end of this
          post), the SqlServlet has been registered. I have also uncommented the lines
          to allow for the following type of URL:
          http://localhost:7001/servlet/myServlet
          Thanks!
          Anjum Jaleel
          CONTENTS OF MY weblogic.properties file
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic XML demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JSP properties
          # WebLogic JHTML properties
          # WebLogic RMI over IIOP properties
          # User-written and demo servlet registrations
          # CORE PROPERTIES
          # You should set these before you start the WebLogic Server the first time.
          # If you need more instructions on individual properties in this
          # section, check the same section in the Optional Properties, where
          # we've left the long explanations. Or, better yet, go to our
          # website and read all about properties, at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # CORE SYSTEM PROPERTIES
          # TCP/IP port number at which the WebLogic Server listens for connections
          weblogic.system.listenPort=7001
          # CORE SECURITY-RELATED PROPERTIES
          # Read important information about security at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # REQUIRED: The system password MUST be set in order to start the
          # WebLogic Server. This password is case-sensitive, at least 8 characters.
          # The username for the privileged user is ALWAYS "system".
          # This username and password also includes httpd access (see
          # HTTPD properties below).
          weblogic.password.system=lovkako1
          # RECOMMEND Set to 'everyone' if HTTPD is enabled
          weblogic.allow.execute.weblogic.servlet=everyone
          # Set individual ACLs to restrict access to HTTP-related resources,
          # such as the Administration servlets.
          # To make your own servlets generally available, follow this
          # pattern (provide a weblogic.allow.execute) for your packages and
          # set ACLs as appropriate.
          # CORE SECURITY-RELATED PROPERTIES FOR SSL
          # Read important information about SSL at:
          # http://www.weblogic.com/docs51/classdocs/API_secure.html
          # Enable SSL
          # (default if property not defined is false)
          weblogic.security.ssl.enable=true
          # SSL listen port
          weblogic.system.SSLListenPort=7002
          # Servlets for SSL
          # Authentication servlet for creating tokens for applets
          weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
          ervlet
          # Limits number of unclaimed stored tokens
          weblogic.security.certificateCacheSize=3
          # Capture CA root of client servlet
          weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
          # Certificates for SSL
          # Name of acceptable CA roots
          # For client authentication change value to a valid .pem file
          #weblogic.security.clientRootCA=SecureServerCA.pem
          # Server certificates for SSL
          weblogic.security.certificate.server=democert.pem
          weblogic.security.key.server=demokey.pem
          weblogic.security.certificate.authority=ca.pem
          # registration for certificate generator servlet
          weblogic.httpd.register.Certificate=utils.certificate
          weblogic.allow.execute.weblogic.servlet.Certificate=system
          # CORE HTTPD ADMINISTRATIVE PROPERTIES
          # True permits the HTTPD to run (default)
          # Uncomment this property to disable HTTPD
          weblogic.httpd.enable=true
          # If authentication is required, add username/password for each user
          # who will be included in an ACL, as in this commented-out example:
          #weblogic.password.peter=#8gjsL4*
          # OPTIONAL PROPERTIES
          # These properties affect the behavior of the WebLogic Server.
          # You only need to set these properties if you want
          # to change the default setting, which is the property shown.
          # ADMINISTRATOR PROPERTIES
          # Administrator properties are optional information properties,
          # particularly useful for clusters.
          #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
          94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # SYSTEM PROPERTIES
          # System properties in this section are set to system defaults
          # Performance pack. The shared library must be accessible from your
          # PATH (NT) or from your shared library path (UNIX; the name of the
          # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          weblogic.system.nativeIO.enable=true
          # Outputs logging information to the console as well as to the log file
          weblogic.system.enableConsole=true
          # Sets the directory or URL for the WebLogic Admin help pages
          # The help pages are shipped in the "docs/adminhelp" directory, in the
          # default document root in public_html
          weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
          p/
          # If you prefer to access the most recent help pages, you can do so online
          # by commenting out the previous property and uncommenting this one:
          #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
          # Properties for tuning the server's performance
          # Number of WebLogic Server execute threads.
          weblogic.system.executeThreadCount=15
          # Other optional system properties
          # Limits size of weblogic.log (in K) and versions old log
          weblogic.system.maxLogFileSize=1024
          # Adjust minimum length of password
          weblogic.system.minPasswordLen=8
          # UNIX only: If running on port 80 on UNIX, enable the setUID program
          #weblogic.system.enableSetUID=false
          # UNIX only: Unprivileged user to setUID to after starting up
          # WebLogic Server on port 80
          #weblogic.system.nonPrivUser=nobody
          # CLUSTER-SPECIFIC PROPERTIES
          # Cluster-specific properties in this section are set to system defaults.
          # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
          # in the per-cluster properties file ONLY.
          # Time-to-live (number of hops) for the cluster's multicast messages
          # (default 1, range 1-255).
          #weblogic.cluster.multicastTTL=1
          # Sets the load-balancing algorithm to be used between
          # replicated services if none is specified. If not specified,
          # round-robin is used.
          #weblogic.cluster.defaultLoadAlgorithm=round-robin
          # SERVER-SPECIFIC CLUSTER PROPERTIES
          # Cluster-related properties in this section are set to system defaults.
          # CLUSTER USERS: Note that these server-specific cluster-related properties
          # should be set in the per-server properties file ONLY.
          # Sets the weight of the individual server for the weight-based
          load-balancing.
          # Range is 0 - 100.
          # Larger numbers increase the amount of traffic routed to this server.
          #weblogic.system.weight=100
          # SYSTEM STARTUP FILES - Examples
          # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
          # objects should be registered in the per-server properties file.
          # All other startup classes should be registered in the per-cluster
          # properties file.
          # For more info on writing and using startup file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a startup class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.startupClass.[virtual_name]=[full_pathname]
          # Add arguments for the startup class
          #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/StartupQuery.java
          #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
          #weblogic.system.startupArgs.doquery=\
          # query=select * from emp,\
          # db=jdbc:weblogic:pool:demoPool
          # SYSTEM SHUTDOWN FILES - Examples
          # For more info on writing and using shutdown file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a shutdown class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
          # Add arguments for the shutdown class
          #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/ShutdownTest.java
          #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
          #weblogic.system.shutdownArgs.ShutdownTest=\
          # outfile=c:/temp/shutdown.log
          # SECURITY-RELATED PROPERTIES FOR WORKSPACES
          # For backward compatibility, the following entries disable Access
          # Control on Workspaces
          weblogic.allow.read.weblogic.workspace=everyone
          weblogic.allow.write.weblogic.workspace=everyone
          # JOLT FOR WEBLOGIC PROPERTIES
          # These properties configure a BEA Jolt connection pool for use with
          # the simpapp and bankapp examples, and register a servlet for use with
          # with the simpapp example. The default server address provided here
          # points to a public TUXEDO server that is hosted by BEA for use with
          # this example.
          # Servlet registration for simpapp example:
          #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
          t
          # Pool creation and cleanup
          # note this example is set up to work with the public
          # demo TUXEDO server available from BEA's website:
          #weblogic.system.startupClass.demojoltpoolStart=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
          #weblogic.system.startupArgs.demojoltpoolStart=\
          # poolname=demojoltpool,\
          # appaddrlist=//beademo1.beasys.com:8000,\
          # failoverlist=//beademo1.beasys.com:8000,\
          # minpoolsize=1,\
          # maxpoolsize=3
          #weblogic.system.shutdownClass.demojoltpoolStop=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
          #weblogic.system.shutdownArgs.demojoltpoolStop=\
          # poolname=demojoltpool
          # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
          # The registrations enable a BEA IIOP connection pool and
          # register servlets for use with the simpapp and university examples.
          # Configure for your environment and uncomment to use.
          # Uncommenting these properties requires WebLogic Enterprise Connectivity
          # and an operating WebLogic Enterprise Server.
          # Servlet registration for simpapp servlet example
          #weblogic.httpd.register.SimpappServlet=\
          # examples.wlec.servlets.simpapp.SimpappServlet
          #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
          # Servlet registration for simpapp EJB example
          # (You'll need to add the wlec_ejb_simpapp.jar to the
          # weblogic.ejb.deploy property in this file.)
          #weblogic.httpd.register.ejbSimpappServlet=\
          # examples.wlec.ejb.simpapp.ejbSimpappServlet
          #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
          # Pool creation and cleanup for the simpapp example
          #weblogic.CORBA.connectionPool.simplepool=\
          # appaddrlist=//wlehost:2468,\
          # failoverlist=//wlehost:2468,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # domainname=simpapp
          # Servlet registration for university Servlet example:
          #weblogic.httpd.register.UniversityServlet=\
          # examples.wlec.servlets.university.UniversityServlet
          #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
          # Pool creation and cleanup for the University example:
          #weblogic.CORBA.connectionPool.Univpool=\
          # appaddrlist=//wlehost:2498,\
          # failoverlist=//wlehost:2498,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # apppassword=wlepassword,\
          # domainname=university
          # WEBLOGIC FILE PROPERTIES
          # Maps a volume name to a path, for client file read/write
          #weblogic.io.fileSystem.[volumeName]=[fullPathName]
          # WEBLOGIC JMS DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL JMS deployment should be done in the
          # per-cluster properties file ONLY.
          # You set up a JDBC connection pool if you want persistent messages
          # (including durable subscriptions). To use JMS and EJBs in the same
          # transaction, both must use the same JDBC connection pool. Uncomment
          # the following property to use the default JDBC connection pool
          # 'demo', which is defined in the Demo connection pool section of this file.
          #weblogic.jms.connectionPool=demoPool
          # The JMS Webshare example demonstrates how the ClientID for a
          # durable subscriber is configured in the connection factory:
          #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
          #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
          #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
          #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
          # The JMS trader example shows how to use JMS with an EJB. In addition
          # to uncommenting the following properties, you must also set up and
          # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
          # ejb_basic_statelessSession.jar to try out this JMS example:
          #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
          #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
          #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
          #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
          # Registers the underlying servlet
          #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
          # These properties are used with the ServerReceive JMS example,
          # which demonstrates how to establish a JMS message consumer
          # in a startup class:
          #weblogic.system.startupClass.serverReceive=\
          # examples.jms.startup.ServerReceive
          #weblogic.system.startupArgs.serverReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          # These properties are used with the PoolReceive JMS example,
          # which demonstrates how to establish a pool of JMS message consumers
          # in a startup class:
          #weblogic.system.startupClass.poolReceive=\
          # examples.jms.startup.PoolReceive
          #weblogic.system.startupArgs.poolReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
          # WEBLOGIC RMI DEMO PROPERTIES
          # CLUSTER USERS: Note that pinned RMI objects should be registered
          # in the per-server properties file ONLY. All other RMI startup
          # classes should be registered in the per-cluster properties file.
          # Remote classes registered at startup after the pattern:
          #weblogic.system.startupClass.[virtualName]=[fullPackageName]
          # These examples can be compiled to see RMI in action. Uncomment to use:
          #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
          #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
          # WEBLOGIC EJB DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL EJB deployment should be done in the
          # per-cluster properties file ONLY.
          # See WebLogic Demo Connection Pool below for a connection pool
          # to use with these examples.
          # Deploys EJBeans. Uncomment the appropriate lines below and
          # modify DBMS-related info and paths to match your particular installation:
          #weblogic.ejb.deploy=\
          # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
          # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
          # g:/weblogic/myserver/ejb_subclass.jar, \
          # g:/weblogic/myserver/jolt_ejb_bankapp.jar
          # Servlet used by the EJB basic beanManaged example
          # Uncomment to use:
          #weblogic.httpd.register.beanManaged=\
          # examples.ejb.basic.beanManaged.Servlet
          # Add a list of users (set the password with
          weblogic.password.[username]=XXX)
          # to set an ACL for this servlet:
          #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
          #weblogic.password.user1=user1Password
          #weblogic.password.user2=user2Password
          # WEBLOGIC XML DEMO PROPERTIES
          # These properties are required to run the XML examples.
          # Uncomment to use.
          # CLUSTER USERS: Note that ALL servlets should be set up
          # in the per-cluster properties file ONLY.
          #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
          # BizTalk example properties
          #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
          #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
          #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
          dapter
          #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
          # WEBLOGIC ZAC DEMO PROPERTIES
          # These registrations enable the ZAC Publish Wizard.
          weblogic.zac.enable=true
          # Set the publish root for a WebLogic Server. Edit and
          # uncomment to use.
          #weblogic.zac.publishRoot=g:/weblogic/zac
          # Set an ACL for each package you publish. The [name] is
          # the "Package name" you assign in the ZAC Publish Wizard.
          # Publish a package, edit this property, and uncomment to use.
          #weblogic.allow.read.weblogic.zac.[name]=[user list]
          #weblogic.allow.write.weblogic.zac.[name]=system
          # HTTPD ADMINISTRATIVE PROPERTIES
          # Enables logging of HTTPD info in common log format and
          # sets the log file name (default is "access.log" in "myserver")
          weblogic.httpd.enableLogFile=true
          weblogic.httpd.logFileName=access.log
          # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
          weblogic.httpd.enableEvents=false
          # Enables HTTP sessions
          weblogic.httpd.session.enable=true
          # Sets an optional cookie name. The default name is "WebLogicSession".
          # Prior to version 4.0, the default was "TengahSession". To make
          # this backward compatible with cookies generated from previous
          # installations, you should set this property to "TengahSession".
          # Uncomment this line and set this to any string of your choice,
          # or comment out this property to use the default.
          #weblogic.httpd.session.cookie.name=WebLogicSession
          # MIME types
          weblogic.httpd.mimeType.text/html=html,htm
          weblogic.httpd.mimeType.image/gif=gif
          weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
          weblogic.httpd.mimeType.application/pdf=pdf
          weblogic.httpd.mimeType.application/zip=zip
          weblogic.httpd.mimeType.application/x-java-vm=class
          weblogic.httpd.mimeType.application/x-java-archive=jar
          weblogic.httpd.mimeType.application/x-java-serialized-object=ser
          weblogic.httpd.mimeType.application/octet-stream=exe
          weblogic.httpd.mimeType.text/vnd.wap.wml=wml
          weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
          weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
          weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
          weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
          # In seconds, the keep-alive for HTTP and HTTPS requests
          weblogic.httpd.http.keepAliveSecs=60
          weblogic.httpd.https.keepAliveSecs=120
          # WEBLOGIC JDBC DRIVER PROPERTIES
          # Enables JDBC driver logging and sets the file name for the log
          # The weblogic.jdbc.logFile is placed in the per-server
          # directory (default is "myserver")
          weblogic.jdbc.enableLogFile=false
          weblogic.jdbc.logFileName=jdbc.log
          # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
          # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
          # in the per-cluster properties file ONLY.
          # For creating JDBC connection pools. This example shows a connection
          # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
          # to use 4 JDBC connections (with a potential for up to 10 connections,
          # incremented by two at a time, with a delay of 1 second between each
          # attempt to connect to the database), to an Oracle database server called
          # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
          # connections are dropped from the pool until only 4 connections remain
          open.
          # Every 10 minutes, any unused connections in the pool are tested and
          # refreshed if they are not viable.
          #weblogic.jdbc.connectionPool.oraclePool=\
          # url=jdbc:weblogic:oracle,\
          # driver=weblogic.jdbc.oci.Driver,\
          # loginDelaySecs=1,\
          # initialCapacity=4,\
          # maxCapacity=10,\
          # capacityIncrement=2,\
          # allowShrinking=true,\
          # shrinkPeriodMins=15,\
          # refreshMinutes=10,\
          # testTable=dual,\
          # props=user=SCOTT;password=tiger;server=DEMO
          # Get more details on each argument for this property in the
          # Administrators Guide on setting properties at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # Set up ACLs for this connection pool with the following:
          #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

Problem Resolved!
          I found out that I had 'http' instead of 'httpd' in the statement where I
          registered my servlet, SqlServlet.
          Now, I am having difficulty with hot deployment. The server is returning
          error 404.

Javax.servlet does not exit

hello all,
i m new and have recently started using java, servlets, jsp with netbeans and Tomcat.
There are some servlet examples in Tomcat5.5\webapps\servlets-examples\WEB-INF\classes\...
Using the //localhost:8080/....... , i can easily get these servlets working in the browser.
When i opened one of the java file say: HelloWorldExample.java in Netbeans, there area lot of red circles with exclamation mark in it.
it says: "package javax.servlet does not exist"
in this line: import javax.servlet.*;
i am surprised why such errors are there and with such errors also the program runs...i want to get rid of such red circles and the error it is showing.
I have jdk1.6.0_10 , jre1.6.0_05 , Netbeans IDE 6.0.1 , Tomcat 5.5 installed in my Windows Vista OS
i have set my classpath as
.;C:\root\jakarta-tomcat-5.5.9\common\lib\servlet-api.jar;C:\root\jakarta-tomcat-5.5.9\common\lib\jsp-api.jar;
JAVA_HOME : C:\Program Files\Java\jdk1.6.0_10
any help is appreciated....
Thank you.
Edited by: kuchu on Jun 26, 2009 12:00 PM

The servlet API is included in the application server implementation which you're going to use (in this case Tomcat). You need to associate the application server with the Netbeans project. Check the project properties.
I cannot tell the detailed steps how to do it in Netbeans as I already uninstalled it after 5 minutes of trying some years ago, but in Eclipse you can select and add the application server during the 'create dynamic web project' wizard. It is smart enough to include the appserver's libraries in the project's build path. From what I heard and read about Netbeans is that it is also able to do so.

How to place a servlet file in Tomcat 5.0?

Hi,
i'm using Apache Tomcat 5.0 as myweb server.i don't know how to set the class path and where to place my servlet and html files,and how to run my servlet file.if anybody knows plz give me a detailed description abt this topic.

Look at the directory structure of your Tomcat installation directory. You will see a webapps directory under that. The Tomcat installation comes with samples ready to run. Look at those and create a similar directory structure under webapps for your application. I don't think you need to worry about classpath. Tomcat should be taking care of all that if you create the proper directory structure.
You run your servlet by specifying a url like:
localhost:8080/servlets-examples/from a browser. This assumes that your installation is using port 8080 which I think is the norm for Tomcat. Here "servlets-examples" is the name of the directory you created. Actually Tomcat 5.0 comes with a "servlets-examples" application. This would be a good directory to look at. You could also run their examples to get a feel for it.
If you are new to servlets, you'll probably have to get a book that explains how things need to be set up. You'll need to create a web.xml for your application. If you look at the servlets-examples directory under webapps, you'll see that it has a WEB-INF directory under it and that directory contains a file called web.xml as well as a sub-directory called classes. This structure is standard accross all application servers because it corresponds to the war (wars are specialized types of jars for web apps) file standard.

Servlet Example

Similar Messages

Maybe you are looking for