为什么我每次修改servlet都要重新启动weblogic?

为什么我每次修改servlet都要重新启动weblogic?
我用的是weblogic6.1,sp2,操作系统是win2000.
修改了几个可能的地方,可是没有生效:
1. startWebLogic.cmd:
     set STARTMODE=false
2. web.xml:
<servlet-mapping>
<servlet-name>loginA</servlet-name>
<url-pattern>/servlet/loginCheckA</url-pattern>
<load-on-startup>0</load-on-startup>
</servlet-mapping>
3. weblogic.xml:
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>0</param-value>
</jsp-param>
请各位大侠指点,不胜感激!

可是,在另一台机器上,每次修改servlet不需要重启weblogic就可以马
上反映出来,而那台机器的设置是:
1 在WLS管理控制台中,在该web app的Files页中,把<Reload Period>设
为1
2 the servlet classes are in the classpath of the PC
好像与两位说的相矛盾.
thx any way!

Similar Messages

  • Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

    Hi!
    We need to implement authentication using our own methods, and the authentication
    information is provided to the web service implementation in a basic authentication
    header. The problem is, that the servlet
    weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
    in
    wls 7.0.sp2, always attempts to perform authentication, if the header is present.
    Is there any way to circumvent this, because we want to implement authentication
    on our own?
    I already know two workarounds:
    The best would of course be to implement a custom security realm for our own
    authentication system. This is not an option, implementing an own security
    realm is overkill for this specific web service.
    The other way would be to route the requests by way of a custom servlet, which
    would
    remove the basic authentication header, and put the authentication info in custom
    headers, such as x-auth: <user:password>, or smthng similar, and after successful
    authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
    But still, I'd like to know if there is any way to tell bea's servlet to ignore
    the basic
    authentication header?
    Oh yeah, by the way, this is URGENT, as always. (really!! ;)
    Toni Nykanen

    Currently there is no option to turn off security check.
    I think you can use a servlet filter mapped to the URL
    of your service, instead of a proxy servlet?
    Regards,
    -manoj
    http://manojc.com
    "Toni Nykanen" <[email protected]> wrote in message
    news:3ef1577b$[email protected]..
    >
    Hi!
    We need to implement authentication using our own methods, and theauthentication
    information is provided to the web service implementation in a basicauthentication
    header. The problem is, that the servlet
    weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
    in
    wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
    Is there any way to circumvent this, because we want to implementauthentication
    on our own?
    I already know two workarounds:
    The best would of course be to implement a custom security realm for ourown
    authentication system. This is not an option, implementing an own security
    realm is overkill for this specific web service.
    The other way would be to route the requests by way of a custom servlet,which
    would
    remove the basic authentication header, and put the authentication info incustom
    headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
    authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
    >
    But still, I'd like to know if there is any way to tell bea's servlet toignore
    the basic
    authentication header?
    Oh yeah, by the way, this is URGENT, as always. (really!! ;)
    Toni Nykanen

  • The servlet weblogic.servlet.AsyncInitServlet init method failed

    I installed WLS 9.2.2 recently with my app being on 8.1.5 for a long time.
    I chose to create a new domain instead of upgrading my existing one.
    I use the eclipse 3.2.2 with the WL plugin.
    When I start the server and login to the console not using eclipse it works fine.
    Trying to start the server and login to the console gives a internal server error.
    Any idea what could be wrong? I bolded the parts where I have looked into.
    Here is the console output:
    <Nov 19, 2008 3:13:02 PM CST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\bea92\weblogic92\platform\lib\p13n\p13n-schemas.jar;C:\bea92\weblogic92\platform\lib\p13n\p13n_common.jar;*C:\bea92\weblogic92\platform\lib\p13n\p13n_system.jar*;C:\bea92\weblogic92\platform\lib\wlp\netuix_common.jar;C:\bea92\weblogic92\platform\lib\wlp\netuix_schemas.jar;C:\bea92\weblogic92\platform\lib\wlp\netuix_system.jar;C:\bea92\weblogic92\platform\lib\wlp\wsrp-common.jar>
    <Nov 19, 2008 3:13:03 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_10-b03 from Sun Microsystems Inc.>
    <Nov 19, 2008 3:13:05 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP2 Mon Jun 25 01:32:01 EDT 2007 952826 >
    <Nov 19, 2008 3:13:10 PM CST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : C:\bea92\license.bea>
    <Nov 19, 2008 3:13:10 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 19, 2008 3:13:10 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Nov 19, 2008 3:13:11 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea92\user_projects\domains\domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <Nov 19, 2008 3:13:15 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Nov 19, 2008 3:13:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Nov 19, 2008 3:13:22 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 19, 2008 3:13:30 PM CST> <Error> <HTTP> <BEA-101359> <The servlet weblogic.servlet.AsyncInitServlet init method failed while it was run in the background. The exception was: java.lang.NoClassDefFoundError: com/bea/p13n/management/ApplicationFilePoller$Handler.
    java.lang.NoClassDefFoundError: com/bea/p13n/management/ApplicationFilePoller$Handler
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
         at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
         Truncated. see log file for complete stacktrace
    >
    <Nov 19, 2008 3:13:37 PM CST> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
    <Nov 19, 2008 3:13:37 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Nov 19, 2008 3:13:37 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Nov 19, 2008 3:13:39 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7005 for protocols iiop, t3, ldap, http.>
    <Nov 19, 2008 3:13:39 PM CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "domain" running in Development Mode>
    <Nov 19, 2008 3:13:40 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Nov 19, 2008 3:13:40 PM CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Nov 19, 2008 3:22:04 PM CST> <Error> <HTTP> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@d6c6a0 - appName: 'consoleapp', name: 'console', context-path: '/console'] Servlet failed with Exception
    java.lang.NullPointerException
         at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         Truncated. see log file for complete stacktrace
    Edited by: user5384782 on Nov 19, 2008 1:42 PM
    Edited by: user5384782 on Nov 19, 2008 3:59 PM

    Thanks for your replies adrian and david.
    The only thing I see different is that eclipse has different arguments when calling the jvm at the top.
    startWebLogic.cmd:
    C:\bea92\JDK150~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000
    -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=C:\b
    ea92\WEBLOG~1 -Dwls.home=C:\bea92\WEBLOG~1\server -Dwli.home=C:\bea92\WEBLOG~1\i
    ntegration -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testC
    onsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea92\patch_weblogic922
    \profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.s
    ecurity.policy=C:\bea92\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    eclipse:
    -hotspot -Xms32m -Xmx200m -Dweblogic.ProductionModeEnabled=
    Eclipse may be calling the cmd I dont know.
    I will try upgrading my eclipse like adrian said, but in the meantime I appreciate any further advice/tips.

  • Error loading servlet: weblogic.servlet.FileServlet with v. 4.0.3

    Servlets have been working for months. Suddenly, I'm getting
              this error (see below) as soon as I try to hit a servlet.
              The startup process looks normal. I've re-installed WL v 4.0.3
              several time, gotten the license in place, so on and so forth,
              but cannot get around this problem. "weblogic.properties" file
              still reads:
              weblogic.httpd.register.file=weblogic.servlet.FileServlet
              All my servlets and EJBs have been registered, and db connection and
              pool made, as usual. As I said above, everything looks normal until
              I try to hit a servlet.
              [... startup output tidied up a bit ...]
              Thu Jan 27 14:46:05 MST 2000:<I> <ListenThread> Listening on port: 80
              Thu Jan 27 14:46:06 MST 2000:<I> <SSLListenThread> Listening on port: 7002
              Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> Error loading servlet: weblogic.servlet.FileServlet
              Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> java.lang.IncompatibleClassChangeError: class
              weblogic.utils.classloaders.ClasspathClassFinder does not implement interface weblogic.utils.classloaders.ClassFinder
              at weblogic.utils.classloaders.GenericClassloader.findLocalClass(GenericClassloader.java:196)
              at weblogic.utils.classloaders.GenericClassloader.reallyLoadClass(Compiled Code)
              at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$Slave.loadClass(RecursiveReloadOnModifyClassLoader.java:221
              at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:66)
              at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.findLocalClass(RecursiveReloadOnModifyClassLoader.java:96)
              at weblogic.utils.classloaders.GenericClassloader.reallyLoadClass(Compiled Code)
              at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:82)
              at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:66)
              at weblogic.servlet.internal.ServletContextImpl.loadClass(ServletContextImpl.java:440)
              at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:121)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:85)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:67)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:203)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:505)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
              at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> Servlet failed with ServletException ...
              ... and so on with multiple cascading failures.
              Does anyone have any idea as to what could cause this?
              Thanks.
              Paul Furbacher
              [email protected]
              

    Did you register your servlets after reinstalling. FileServlet is only for handling html pages. It has no role in loading servlets.
              "Paul Furbacher [TeamB]" wrote:
              > Servlets have been working for months. Suddenly, I'm getting
              > this error (see below) as soon as I try to hit a servlet.
              > The startup process looks normal. I've re-installed WL v 4.0.3
              > several time, gotten the license in place, so on and so forth,
              > but cannot get around this problem. "weblogic.properties" file
              > still reads:
              >
              > weblogic.httpd.register.file=weblogic.servlet.FileServlet
              >
              > All my servlets and EJBs have been registered, and db connection and
              > pool made, as usual. As I said above, everything looks normal until
              > I try to hit a servlet.
              >
              > ****
              >
              > [... startup output tidied up a bit ...]
              > Thu Jan 27 14:46:05 MST 2000:<I> <ListenThread> Listening on port: 80
              > Thu Jan 27 14:46:06 MST 2000:<I> <SSLListenThread> Listening on port: 7002
              > Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> Error loading servlet: weblogic.servlet.FileServlet
              > Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> java.lang.IncompatibleClassChangeError: class
              > weblogic.utils.classloaders.ClasspathClassFinder does not implement interface weblogic.utils.classloaders.ClassFinder
              > at weblogic.utils.classloaders.GenericClassloader.findLocalClass(GenericClassloader.java:196)
              > at weblogic.utils.classloaders.GenericClassloader.reallyLoadClass(Compiled Code)
              > at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$Slave.loadClass(RecursiveReloadOnModifyClassLoader.java:221
              > at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:66)
              > at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.findLocalClass(RecursiveReloadOnModifyClassLoader.java:96)
              > at weblogic.utils.classloaders.GenericClassloader.reallyLoadClass(Compiled Code)
              > at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:82)
              > at weblogic.utils.classloaders.GenericClassloader.loadClass(GenericClassloader.java:66)
              > at weblogic.servlet.internal.ServletContextImpl.loadClass(ServletContextImpl.java:440)
              > at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:121)
              > at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:85)
              > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:67)
              > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:203)
              > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:505)
              > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
              > at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              >
              > Thu Jan 27 14:47:32 MST 2000:<E> <ServletContext-Servlets> Servlet failed with ServletException ...
              >
              > ... and so on with multiple cascading failures.
              >
              > ****
              >
              > Does anyone have any idea as to what could cause this?
              >
              > Thanks.
              >
              > Paul Furbacher
              > [email protected]
              

  • Restricting access to a particular servlet in Weblogic

    Thanx in advance for reading and replying to this query.
    I have an application running under a domain.
    This application has two servlets.
    I want that whenever a user hits one servlet, weblogic's authentication window should pop up.
    I know this could be achieved by making entry for <security-constraint >.
    But how?
    Please advise.
    Regards,
    Vikas

    in your web.xml where /MyServletURL is the url that you mapped your servlet to:
      <security-constraint>
        <web-resource-collection>
          <web-resource-name>Weblog3</web-resource-name>
          <description>
            Test of web application security
          </description>
          <url-pattern>/MyServletURL</url-pattern>
          <http-method>GET</http-method>
          <http-method>POST</http-method>
        </web-resource-collection>
        <auth-constraint>
          <description>
            These are the roles who have access
          </description>
            <role-name>
              webappRole1
            </role-name>
        </auth-constraint>
        <user-data-constraint>
          <description>
            This is how the user data must be transmitted
          </description>
          <transport-guarantee>NONE</transport-guarantee>
        </user-data-constraint>
      </security-constraint>
      <login-config>
        <auth-method>BASIC</auth-method>
      </login-config>
      <security-role>
        <description>
          An administrator
        </description>
        <role-name>
          webappRole1
        </role-name>
      </security-role>Then in the weblogic.xml file where cust is a group that you have created in Weblogic using the console. You can then assign users to the group so that they can access the servlet:
    <weblogic-web-app>
       <security-role-assignment>
          <role-name>webappRole1</role-name>
          <principal-name>cust</principal-name>
       </security-role-assignment>
    </weblogic-web-app>

  • About weblogic proxy call weblogic cluster's servlet error

              I use weblogic server 5.1, configruation tow weblogic cluster server and a weblogic
              web server, through weblogic web server received browser's http request only,
              weblogic cluster server do with jsp and servlet, now html&jsp is ok but servlet
              can not do with, if through weblogic cluster server do with jsp and servlet direct,
              it's ok.
              this is my weblogic.properties section:
              weblogic.httpd.register.*.html=\
              weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.*.html=\
              defaultServers=132.147.35.221:7001|132.147.35.222:7001
              weblogic.httpd.register.*.jsp=\
              weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.*.jsp=\
              defaultServers=132.147.35.221:7001|132.147.35.222:7001
              weblogic.httpd.register.*.servlet=\
              weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.*.servlet=\
              defaultServers=132.147.35.221:7001|132.147.35.222:7001
              these are weblogic server as proxy webserver errors:
              &#26143;&#26399;&#19968; &#20843;&#26376; 20 17:42:38 GMT+08:00 2001:<I> <ServletContext-General>
              helloWorld: init
              &#26143;&#26399;&#19968; &#20843;&#26376; 20 17:42:38 GMT+08:00 2001:<E> <ServletContext-General>
              Servlet failed with Exception
              java.lang.NullPointerException
              at weblogic.servlet.internal.HttpClusterServlet.init(HttpClusterServlet.java:99)
              at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:499)
              at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java,
              Compiled Code)
              at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:442)
              at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:922)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:886)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
              tell me a right configuration please ,thanks.
              

    ############### Cluster Proxy Configuration ########################
              weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.cluster=defaultServers=132.147.35.221:7001|132.147.3
              5.222:7001
              weblogic.httpd.defaultServlet=cluster
              weblogic.allow.execute.weblogic.clustler=everyone
              "chris" <[email protected]> wrote in message
              news:[email protected]...
              >
              > I use weblogic server 5.1, configruation tow weblogic cluster server and
              a weblogic
              > web server, through weblogic web server received browser's http request
              only,
              > weblogic cluster server do with jsp and servlet, now html&jsp is ok but
              servlet
              > can not do with, if through weblogic cluster server do with jsp and
              servlet direct,
              > it's ok.
              >
              > this is my weblogic.properties section:
              > -----------------------------------------------------------------
              > weblogic.httpd.register.*.html=\
              > weblogic.servlet.internal.HttpClusterServlet
              > weblogic.httpd.initArgs.*.html=\
              > defaultServers=132.147.35.221:7001|132.147.35.222:7001
              > weblogic.httpd.register.*.jsp=\
              > weblogic.servlet.internal.HttpClusterServlet
              > weblogic.httpd.initArgs.*.jsp=\
              > defaultServers=132.147.35.221:7001|132.147.35.222:7001
              > weblogic.httpd.register.*.servlet=\
              > weblogic.servlet.internal.HttpClusterServlet
              > weblogic.httpd.initArgs.*.servlet=\
              > defaultServers=132.147.35.221:7001|132.147.35.222:7001
              > -----------------------------------------------------------------
              >
              >
              >
              > these are weblogic server as proxy webserver errors:
              > -----------------------------------------------------------------
              > &#26143;&#26399;&#19968; &#20843;&#26376; 20 17:42:38 GMT+08:00 2001:<I>
              <ServletContext-General>
              > helloWorld: init
              > &#26143;&#26399;&#19968; &#20843;&#26376; 20 17:42:38 GMT+08:00 2001:<E>
              <ServletContext-General>
              > Servlet failed with Exception
              > java.lang.NullPointerException
              > at
              weblogic.servlet.internal.HttpClusterServlet.init(HttpClusterServlet.java:99
              > at
              weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
              :499)
              > at
              weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
              va,
              > Compiled Code)
              > at
              weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              a:442)
              > at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:20
              0)
              > at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :115)
              > at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:922)
              > at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:886)
              > at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.java:269)
              > at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
              > at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              > -----------------------------------------------------------------
              >
              > tell me a right configuration please ,thanks.
              

  • Weblogic startup servlet loading

    Hi
    I am encountering problems in loading a Servlet on Weblogic
    server startup.
    The steps to be followed to load a servlet on webLogic
    Server startup are as follows
    Register the following in the Weblogic properties
    file.
    1.register the servlet
    weblogic.httpd.register.MyServlet=\
    examples.servlets.myservletclass
    2.weblogic.system.startupClass.StartMyServlet=\
    weblogic.servlet.utils.ServletStartup
    3.weblogic.system.startupArgs.StartMyServlet=\
    servlet=MyServlet
    where MyServlet is the synonym used for registering the
    servlet in the file and myservletclass is the Actual
    name of the servlet.
    I have followed the steps accordingly but the server
    is failing to load my servlet on startup.
    Any suggestions,solutions for the above problem
    will be most welcome.
    Thanx
    Tapan.

    Hi
    I am encountering problems in loading a Servlet on Weblogic
    server startup.
    The steps to be followed to load a servlet on webLogic
    Server startup are as follows
    Register the following in the Weblogic properties
    file.
    1.register the servlet
    weblogic.httpd.register.MyServlet=\
    examples.servlets.myservletclass
    2.weblogic.system.startupClass.StartMyServlet=\
    weblogic.servlet.utils.ServletStartup
    3.weblogic.system.startupArgs.StartMyServlet=\
    servlet=MyServlet
    where MyServlet is the synonym used for registering the
    servlet in the file and myservletclass is the Actual
    name of the servlet.
    I have followed the steps accordingly but the server
    is failing to load my servlet on startup.
    Any suggestions,solutions for the above problem
    will be most welcome.
    Thanx
    Tapan.

  • Weblogic startup servlet load

              Hi,
              I am encountering problems in running a Servlet on Weblogic
              server startup.
              The steps to be followed to execute a servlet on webLogic
              Server startup are as follows
              Register the following in the Weblogic properties
              file.
              1.register the servlet
              weblogic.httpd.register.MyServlet=\
              examples.servlets.myservletclass
              2.weblogic.system.startupClass.StartMyServlet=\
              weblogic.servlet.utils.ServletStartup
              3.weblogic.system.startupArgs.StartMyServlet=\
              servlet=MyServlet
              where MyServlet is the synonym used for registering the
              servlet in the file and myservletclass is the Actual
              name of the servlet.
              I have followed the steps accordingly but the server
              is failing to execute my servlet on startup.
              Any suggestions,solutions for the above problem
              will be most welcome.
              Thanx
              Tapan.
              

    HOw did you specified the load-on-startup? and what error you get
              upon startup/deployment time?
              Kumar
              Giulia Esposito wrote:
              > I try to load my servlet on startup of Bea WebLogic Server 6.1 (SP 3) cluster.
              > This load failed.
              >
              > Can you help me?
              >
              > Tank's!
              >
              

  • Weblogic Proxy Servlet

              I'm creating a servlet filter that filters the content of resources that are proxied
              by the Weblogic Proxy servlet (weblogic.servlet.proxy.HttpProxyServlet)
              The filtering of the content is working but getting the filtering of incoming
              and outgoing headers is a problem.
              I get ClasscastExceptions if I try to implement my own request wrapper in WL 7
              SP2 (incoming headers). And filtering headers in the response wrapper (outgoing
              headers) causes a IndexOutOfBoundsException. This is caused by a call to response.setHeader
              in the wrapper.
              Has someone managed to get header filtering to work?
              java.lang.IndexOutOfBoundsException
              at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
              at java.io.DataInputStream.read(DataInputStream.java:108)
              at weblogic.servlet.proxy.GenericProxyServlet.sendResponse(GenericProxyServlet.java:595)
              

    This looks like a bug in the ProxyServlet. I would report this to support.
              Sam
              Sven Andersson wrote:
              > I'm creating a servlet filter that filters the content of resources that are proxied
              > by the Weblogic Proxy servlet (weblogic.servlet.proxy.HttpProxyServlet)
              >
              > The filtering of the content is working but getting the filtering of incoming
              > and outgoing headers is a problem.
              >
              > I get ClasscastExceptions if I try to implement my own request wrapper in WL 7
              > SP2 (incoming headers). And filtering headers in the response wrapper (outgoing
              > headers) causes a IndexOutOfBoundsException. This is caused by a call to response.setHeader
              > in the wrapper.
              >
              > Has someone managed to get header filtering to work?
              >
              > java.lang.IndexOutOfBoundsException
              > at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
              > at java.io.DataInputStream.read(DataInputStream.java:108)
              > at weblogic.servlet.proxy.GenericProxyServlet.sendResponse(GenericProxyServlet.java:595)
              

  • JoltConnectionPool can not start in weblogic server

    Hi
    I am trying to run the sample Tuxedo provided application which uses Servlets or Ejb.
    Now the Tuxedo Server has been configured and running properly.
    I have WebLogic Server installed and had created the JoltSessionPool with name "MAJoltConnectionPool" and had also defined the StartupClass & ShutdonClass.
    While defining the JoltSessionPool i had given min services as 1 and max services as 5 and others as default,
    and the JoltSessionPool's target is a weblogic managed server which named ct2.
    Then i tryed to start the ct2 server on command line such as:
    startManagedWebLogic.cmd ct2 http://localhost:7001
    I got an error in starting "MAJoltConnectionPool" but the server ct2 is starting normally.
    Anyone who can help me to find out the reason? Thanks a lot.
    The Command Line window shown following in the Log:
    Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
    com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool :
    Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
    The Entire Trace from the Log file is:
    ####<Mar 16, 2011 11:58:35 AM CST> <Notice> <Log Management> <HXU49> <ct2> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915024> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Mar 16, 2011 11:58:35 AM CST> <Info> <Diagnostics> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915070> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Mar 16, 2011 11:58:35 AM CST> <Info> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915078> <BEA-000256> <Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)>
    ####<Mar 16, 2011 11:58:35 AM CST> <Critical> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915239> <BEA-000286> <Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
    com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
    java.lang.Exception: Errors in starting the following connection pools :
    com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
         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:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         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:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
         at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
         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:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >
    ####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915288> <BEA-000365> <Server state changed to ADMIN>
    ####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915313> <BEA-000365> <Server state changed to RESUMING>
    ####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916769> <BEA-000365> <Server state changed to RUNNING>
    ####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916770> <BEA-000360> <Server started in RUNNING mode>
    With Regards
    Han

    Hi
    To resolve this problem , you have 2 solutions:
    - modify the config.xml file to add in the tag <security-configuration> the following line :
    <clear-text-credential-access-enabled>true</clear-text-credential-access-enabled>
    or
    - check the checkbox "Clear Text Credential Access Enabled" in the settings for the domain / security / general / advanced
    restart the weblogic server to activate this change if necessary (Normaly, no restarts are necessary with weblogic server v10.3.5.0)
    Hope this reponse help you (if it's not too late ;-) )
    Laurent.

  • 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.
              

  • Problem deploying EAR to weblogic server

    Hi everyone
    I am using Jdeveloper 11.1.1.4 and have deployed an ADF Fusion app to weblogic 10.3.4.
    I manage to deploy it but when I go to start it I get the following exception
    [HTTP:101216]Servlet: "weblogic.wsee.jaxws.client.async.AsyncTransportProvider" failed to preload on startup in Web application: "Objekti-ViewController-context-root". javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:36) at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55) at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82) at com.sun.xml.ws.server.InvokerTube.setEndpoint(InvokerTube.java:85) at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:48) at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:153) at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:67) at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:37) at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:34) ... 51 more Caused by: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:308) at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:54) at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:42) at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:35) ... 52 more
    I have looked on the forum and can't seem to find anything.
    Any help you offer is greatly appreciated

    I could not find those files anywhere but maybe I was looking in the wrong place. I go to application properties and then deployment and then the profile I created but I searched everywhere and nowhere do those 2 jar files even appear, not even an unchecked checkbox or something
    So maybe I was in the wrong place but I checked the project properties as well....
    I will look through it again and the web inf file but just dont know where those jars could be...
    Maybe it is the Web inf file, because I know you can include that although Im pretty sure I excluded it on both the project and application deployment properties...

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # 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=12345678
    # 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=false
    # 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*
    # 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=/weblogic/myserver/public_html/docs51/adminhelp/
    # 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:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/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=d:/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=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • Problem deploying a WAR file in Weblogic 10

    I get an error trying to deploy a WAR file on WebLogic 10 on two of my co-workers computers. On my computer it works fine and on our development server running on SUSE 10 it is also fine. We are using Struts 2, Hibernate 3 and Spring 2.5. The exception says that weblogic.wsee.async.AsyncResponseBean failed to preload because weblogic.wsee.async.jaxws.OnAsyncDelivery could not be found. We are not knowingly trying to use these classes. We do not have web services. The full text of the error we get when trying to deploy is:
    <Aug 20, 2008 3:01:45 PM CDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application '_appsdir_pilotVacation_war'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.async.AsyncResponseBean" failed to preload on startup in Web application: "pilotVacation.war".
    class: weblogic.wsee.async.jaxws.OnAsyncDelivery could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:950)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    Truncated. see log file for complete stacktrace
    class: weblogic.wsee.async.jaxws.OnAsyncDelivery could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >

    Hey,
    From what I understand, your configuration is obviously different from your co-workers' config.
    So you've got two choices : either you make their environments work like yours, or you make the application to work anywhere !
    In order to do so, I would advise you to use a comparison tool, such as BeyondCompare (excellent) and compare your domain configurations (config directories)
    Or as James suggested it, you go hunt for unnecessary libraries in your application DD.
    Extra question : have you tried to create a new domain, and activate the Workshop extension ? Try then to deploy your application and tell us what's the result.
    If you created your application in Workshop, mind the facets : if you do not chose the correct set of facets, you'll have lots of extra libs, more annoying than helping.

  • Problems deploying a JAX-WS webservice on Weblogic 10.3

    Hello Experts,
    I have deveoped a SOAP1.2 over HTTP web service using JAX-WS @WebServiceProvider annotation and am trying to deploy it on Weblogic 10.3
    The jwsc task is successful. However, I get the following exception when deploying it on weblogic 10.3:
    ===========================================================================================
    ####<Feb 16, 2010 12:35:18 PM PST> <Info> <Deployer> <....> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518172> <BEA-149060> <Module OIMTrustedRecon of application OIMTrustedReconEar successfully transitioned from STATE_PREPARED to STATE_NEW on server WLS_ManagedServer_1.>
    ####<Feb 16, 2010 12:35:18 PM PST> <Error> <Deployer> <psharma-lap> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518656> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266352473562' for task '10'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.async.AsyncResponseBean" failed to preload on startup in Web application: "OIMTrustedRecon".
    com.sun.xml.ws.model.RuntimeModelerException: The web service defined by the class weblogic.wsee.async.AsyncResponseBean does not contain any valid WebMethods.
         at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:262)
         at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
         at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
         at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
         at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:510)
         at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:182)
         at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:164)
         at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:51)
         at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:53)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ===========================================================================================
    Could you please let know if I have done something wrong or am missing something.
    Please let me know if you need more information to help me.
    Many Thanks,
    Pulkit Sharma

    Hi Pulkit,
    If your WebService is not very complex ...then can you please paste it here ...Or can u describe something about your WebService. Like Which kind of methods are there? And Are u using any Asynchronous feature in it?
    If you are not using any Asynchronous feature in your webservice then u can try disabling it by adding "-Dweblogic.wsee.skip.async.response=true"
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

Maybe you are looking for

  • I need this requirement :create PR+get list of PO+ack of MIGO

    Hi All, Can u tell me the releationship for the flow of PRequistion,POrder,GRecipts. and what are the Standard BAPI/RFC's available. Thanks @Prami Moderator message: please search for available information/documentation. Edited by: Thomas Zloch on Ma

  • Any other realtors having issues with updating their Suprakey on their Android?

    Any other realtors having issues with updating their Suprakey on their Android?

  • New Mobo

    I am currently using a K8T Neo-FIS2R with at with a 3200+.  I am looking into making a new machine and need some help in choosing a new mobo or ordering another of the same.  I want to have at least 1gig of mem and am hoping for a pci-express board (

  • Check next number (activity code)

    Good day experts. This is the issue we are currently importing a SFC into the system or using the supplier barcode for the SFC inside visprise.  We unfortnately use two diferent product types from the same supplier where the two don't really have any

  • Flash Animation Does Not Refresh

    I've created a Captivate demo that has an animated flash segment in the middle of it. This demo was developed for a trade show and was designed to loop so it can run automatically throughout the day. Plays great through the first pass. Problem is, af