Weblogic 7.0 servlets deployment and clustering

          I am unable to deploy servlet application in WL 7.0 cluster configuration. I am
          using Iplanet NES 4.0 as my web server. I have deployed the weblogic proxy successfully
          in iplanet.
          The servlet application has class files in exploded form and are present under
          bin/applications/DefaultWebApp/WEB-INF/classes folder
          web.xml also exists in the above folder.
          I receive the following exception.
          <Apr 23, 2003 2:26:44 PM EDT> <Error> <socket> <000405> <Uncaught Throwable in
          processSockets
          java.lang.NullPointerException
          java.lang.NullPointerException
          at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:968)
          at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:239)
          at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:121)
          at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:481)
          at weblogic.servlet.internal.ChunkOutput.commit(ChunkOutput.java:259)
          at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:91)
          at weblogic.servlet.internal.ChunkWriter.write(ChunkWriter.java:37)
          at java.io.Writer.write(Writer.java:148)
          at java.io.PrintWriter.write(PrintWriter.java:208)
          Please help.
          

This might be a known bug, please contact support and reference CR100572 to
          see if it is also a bug in WLS7.0
          sree
          "Manju" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am unable to deploy servlet application in WL 7.0 cluster configuration.
          I am
          > using Iplanet NES 4.0 as my web server. I have deployed the weblogic proxy
          successfully
          > in iplanet.
          > The servlet application has class files in exploded form and are present
          under
          > bin/applications/DefaultWebApp/WEB-INF/classes folder
          > web.xml also exists in the above folder.
          > I receive the following exception.
          > <Apr 23, 2003 2:26:44 PM EDT> <Error> <socket> <000405> <Uncaught
          Throwable in
          > processSockets
          > java.lang.NullPointerException
          > java.lang.NullPointerException
          > at
          weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseIm
          pl.java:968)
          > at
          weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputS
          treamImpl.java:239)
          > at
          weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
          mpl.java:121)
          > at
          weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStream
          Impl.java:481)
          > at
          weblogic.servlet.internal.ChunkOutput.commit(ChunkOutput.java:259)
          > at
          weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:9
          1)
          > at
          weblogic.servlet.internal.ChunkWriter.write(ChunkWriter.java:37)
          > at java.io.Writer.write(Writer.java:148)
          > at java.io.PrintWriter.write(PrintWriter.java:208)
          >
          >
          > Please help.
          >
          

Similar Messages

  • EJB & Servlet deployment in Clustered Env.

              Hi,
              I have made a cluster of 3 weblogic servers. I would like to send a request to one
              server (e.g. http://myserver1:7001/TestServlet). The servlet utilizes an EJB which
              is not located and not deployed on myserver1 , but on other 2 servers in the cluster.
              The algorithm is round-robin. It gives me a lot of errors (Impl... classes not found
              etc etc).
              Do I have to deploy everything on all the servers?
              If I do that, the request is not routed to other servers. Since the servlet finds
              the EJB locally, it never goes to the other servers, regardless of the algorithm.
              I have set up the "home-is-clusterable" and all other relevant properties for EJB
              deployment.
              Any ideas??
              Sharad
              

    If the ejb is deployed on the server that is looking for the ejb, then it
              won't go network to use the ejb. That is a "big" WL optimization, and helps
              quite a bit for most apps.
              If you want to segregate the ejb and web functionality, you should probably
              consider running two distinct clusters (in 5.1 parlance).
              I suggest putting web and ejb together though and clustering that. Latency
              is lower. Scalability is not particularly affected. Configuration is much
              simpler.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com
              +1.617.623.5782
              WebLogic Consulting Available
              "Sharad Joshi" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi,
              >
              > I have made a cluster of 3 weblogic servers. I would like to send a
              request to one
              > server (e.g. http://myserver1:7001/TestServlet). The servlet utilizes an
              EJB which
              > is not located and not deployed on myserver1 , but on other 2 servers in
              the cluster.
              > The algorithm is round-robin. It gives me a lot of errors (Impl... classes
              not found
              > etc etc).
              >
              > Do I have to deploy everything on all the servers?
              > If I do that, the request is not routed to other servers. Since the
              servlet finds
              > the EJB locally, it never goes to the other servers, regardless of the
              algorithm.
              > I have set up the "home-is-clusterable" and all other relevant properties
              for EJB
              > deployment.
              >
              > Any ideas??
              >
              > Sharad
              

  • JNDI / EJB deployment and clustering

    I'm aware that replication isn't supported for stateful EJBs. But the
              "serialization of the handle isn't supported" statement has me concerned.
              So I'm looking for a little clarification on this scenario:
              Let's say I've got a stateful session bean, which is accessed from a
              servlet. For performance reasons, you want to find the colocated instance -
              the smart stub should do this, right? To have it colocated in all
              instances, then I need to deploy it into each server of the cluster. This
              essentially bind()/rebind()'s (whichever call the container does during a
              deploy operation) the EJB n times. Does each of those JNDI bind/rebind
              calls "overwrite" the previous one, or does the replicated JNDI tree somehow
              "keep" all the entries?
              What happens if I bind/rebind "non-cluster enabled" objects into the JNDI
              tree in each server to the same name (like a reference data table - doesn't
              really need to be an RMI object, one per server is fine)? Will they get
              "overwritten"? Should I need to take into account the server name when
              binding into the tree, and then also use that for subsequent lookups?
              Thanks for any input!
              --Jason
              

    Guys,
    Thanks for the information.
    The problem was that classpath, some other packages required for the Bean
    were not in the weblogic\classes directory.
    so that was it.
    Thanks
    /selvan
    Murali Krishna Devarakonda wrote in message
    <7qjkr1$7dl$[email protected]>...
    Are you using the HOT DEPLOY feature(startweblogic.bat does it)?
    Then you could go to the WebLogic Console, select the Bean, and Redploy.
    You could also do it from a command line utility "weblogic.deploy".
    If you didn't start the server with the hot deploy, you need to restartyour
    server after any changes.
    You should read the weblogic docs on the Hot Deploy feature. A different
    classloader is used for it. Also, the standard weblogic classpath cannot
    coexist with it.
    Hot Deploy uses: (assuming your weblogic installation is in D:/WebLogic
    D:\WebLogic\classes/boot
    It will throw an exception if you have D:\weblogic\classes or
    D:\WebLogic\lib\weblogicaux.jar in the system classpath. You need to use
    the weblogic.classpath instead.
    Regards,
    Murali Krishna Devarakonda
    Tamilselvan Ramasamy <[email protected]> wrote in message
    news:7qi0ln$kpc$[email protected]..
    Hello,
    I have created bunch of EJB Components and deployed for WLS4.0 using the
    following way. It works fine under WLS4.0
    To compile java code -> javac *.java
    Create SER file -> java weblogic.ejb.utils.DDCreator -d .
    DeploymentDescriptor.txt
    Create JAR file -> jar cmf manifest Bean.jar /directory
    EJBC and deployment -> java weblogic.ejbc -d /targetDirectory Bean.jar
    and also add an entry in the welogic.properties file
    weblogic.ejb.deploy= ...
    When I do the samething in the WLS4.5, it doesn't work, first of all,
    JNDI
    is not finding the home interface. It throws a naming Exception
    please give me an idea hw do I deploy my Beans in the WLS4.5 using the
    command line option. I don't have Visual Cafe to do that automatically.So
    I
    have to do that manually.
    Thanks
    /selvan
    Captura Software Inc
    [email protected]

  • How to access contextRoot in Servlet deployed in an ear in Weblogic 81

    Hi,
    I need to access the contextRoot or webapp name from a startup servlet deployed in WebLogic. I've tried the following;
    getServletContext().getRealPath("/") return null.
    getServletContext().getServerInfo() returns Weblogic 8.1 service pack 3...
    getServletContext().getServletContextName() display the <display-name> value from my web.xml.
    What I want is the <context-root> value in the EARs application.xml.
    I tried the following JNDI lookup and the lookup failed but the error message contained the contextRoot.
    String name = (String) jndiContext.lookup("java:/comp/env/namespace");
    log.info("jndiContextlookup namespace = "+name);
    Any help would be GREATLY appreciated. This should be easy!!
    Shane

    Hi VR
    From Weblogic Admin Console, Deployments, on right side click on the link named with your EAR Application. It opens detailed page with more tabs. Click on the tab named Targets. Here select your WebService module and click on Change Targets button. Uncheck the server where it is targetted (Deployed), click on Yes. And activate the changes.
    Thanks
    Ravi Jegga

  • T3 protocol and clusters

    Hi,
              I'm porting a Java application running against WLS6.0 to use a clustered
              server solution. This means I connect via t3 protocol. Any views on the best
              way to get failover and loadbalancing from this approach, for example is
              there anyway I can get the weblogic proxy functionality of
              HttpClusterServlet without using http protocol?
              Thanks
              Sioux
              

    Your web.xml looks OK to me.
              All you need to do is, create a .war file and copy it into applications
              directory of proxy server.
              Then register this webapp as default webapp. So whenever you hit proxy server ,
              those requests
              will be handled by this default webapp, in turn the requests will be routed to
              one of the clustered servers.
              Hope it helps
              Kumar
              Sioux France wrote:
              > Hi,
              > I understand this solution, can I ask about the possibility of using a
              > proxy?
              > Is it possible if my URL is t3://localhost:7001 and I now want to use a
              > proxy on this server to redirect to the cluster to use HttpClusterServlet
              > rather than a DNS based solution? If so what do I call to get the proxy to
              > redirect me to the cluster?
              > I've set up a servlet for HttpClusterServlet with my cluster members in the
              > parameters. How can I test from a browser that this is proxying correctly?
              > For the t3 protocol is it possible to get redirection to the cluster members
              > using HttpClusterServlet from a command line client, or is this route only
              > available for web-based queries as that is the only way the
              > HttpClusterServlet can intercept the call? i.e. Must I use my own failover
              > implementation in a DNS-based solution as discussed below?
              >
              > Here's the web.xml for my HttpClusterServlet which I've set as my default
              > webserver on the admin server. Any help understanding this appreciated!
              > Sioux
              >
              > <web-app>
              > <servlet>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <servlet-class>
              > weblogic.servlet.internal.HttpClusterServlet
              > </servlet-class>
              >
              > <init-param>
              > <param-name>defaultServers</param-name>
              > <param-value>
              > managedserver1:7003:7004|managedserver2:7003:7004
              > </param-value>
              > </init-param>
              >
              > <init-param>
              > <param-name>DebugConfigInfo</param-name>
              > <param-value>ON</param-value>
              > </init-param>
              >
              > </servlet>
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>/</url-pattern>
              > </servlet-mapping>
              >
              > <!-- This bit is just to show it's deployed, and sure enough, it can't find
              > index.html when I call http://localhost:7001 now -->
              > <servlet-mapping>
              > <servlet-name>HttpClusterServlet</servlet-name>
              > <url-pattern>*.html</url-pattern>
              > </servlet-mapping>
              >
              > </web-app>
              >
              > "Robert Patrick" <[email protected]> wrote in message
              > news:[email protected]...
              > > The connection to the cluster is done via the JNDI lookup. The
              > PROVIDER_URL
              > > should be the "cluster name" which is either a DNS name that is mapped to
              > the
              > > list of IP addresses of the clustered servers or a hardware load-balancer.
              > Once
              > > that connection has been made, you will be looking up EJB Home objects --
              > the
              > > objects downloaded to your client are "smart stubs" that understand
              > clustering.
              > > Multiple invocations on that EJBHome reference will be load-balanced
              > across the
              > > cluster of available servers (meaning that it will handle fail-over).
              > This is
              > > easy to do since the EJBHome object is always stateless. If you use
              > stateless
              > > session beans, you can get the same behavior at the bean instance level.
              > > Stateful session beans can be replicated in-memory across a pair of server
              > > instances (much like the HttpSession replication).
              > >
              > > I suggest that you read our clustering documentation at
              > > http://e-docs.bea.com/wls/docs60/
              > >
              > > Hope this helps,
              > > Robert
              > >
              > > Sioux France wrote:
              > >
              > > > I think my point is missed, I have a lovely running cluster, with
              > clustered
              > > > EJBs, clustered JMS and now I want to call it via the t3 protocol or
              > > > something similar from a Java Application. As I understand this, it
              > means I
              > > > can't use HTTP or a proxy. I order to utilise the failover/loadbalancing
              > of
              > > > the cluster that exists, how should I connect to it from the client, can
              > I
              > > > use DNS, RMI, is there any documentation for running a cluster with Java
              > > > Application clients rather than a web front end?
              > > >
              > > > "Robert Patrick" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > Use clustered EJBs.
              > > > >
              > > > > Sioux France wrote:
              > > > >
              > > > > > Hi,
              > > > > > I'm porting a Java application running against WLS6.0 to use a
              > clustered
              > > > > > server solution. This means I connect via t3 protocol. Any views on
              > the
              > > > best
              > > > > > way to get failover and loadbalancing from this approach, for
              > example is
              > > > > > there anyway I can get the weblogic proxy functionality of
              > > > > > HttpClusterServlet without using http protocol?
              > > > > > Thanks
              > > > > > Sioux
              > > > >
              > >
              

  • Weblogic cluster for 24x7 environment and a front OHS server

    Hi experts,
    We are going to set up a reliable J2EE application server environment by using clustering webgoic servers on TWO nodes, and a front OHS https server in DMZ for load balancing.
    I am new to weblogic cluster and load balance by OHS. I have visited this forum for Fusion MiddleWare clustering etc. Can some experts share some light on this?
    Will our deployment architecture be able to handle the J2EE applications failover? In other word, we can restart one of Weblogic Managed Servers when a new release of J2EE codes are re-deployed without impacting business end users’s usage?
    Problems we want to solve:
    1. All J2EE applications are available for 24x7 even when new J2EE codes are released and deployed on weblogic Managed Servers ANY TIME, side-by-side deployment and restart a managed server if we need to clean the HTTP cache.
    2. The J2EE applications should be accessed by external and internal users with a Single Access Point, like
    https://apps.company1.com/j2ee1
    https://apps.company2.com/j2ee1
    https://apps.company1.com/j2ee2
    https://apps.company2.com/j2ee2
    All J2EE applications (j2ee1, j2ee2, j2ee3 etc) should be deployed on both of weblogic Servers in a cluster, and pointing to a SAME backend database.
    Can some experts share with us the best practices on components and configurations? Thanks.

    Seems your architecture is like Browser => OHS ( DMZ ) => Weblogic => DB OR Browser => HLB( like bigip ) => OHS ( DMZ ) => Weblogic => DB
    Cluster is the solution for load balancing however if you are using OHS for redirection to weblogic then OHS does the load balancing in round robin way. using cluster in this way has a benefit of in case of any one of your managed server is down the OHS will divert connection request to any one of the active managed server ( you have to turn on dynamic list on at OHS ).
    http://weblogicserveradministration.blogspot.com/2010/10/load-balancing-in-weblogic-server.html
    Failover is something different, if in case any of the any managed server goes down then your user you get the application session from another server but new one, means the the tasks not saved by the users on earlier session will lost. for that yo need to use cluster and then need to enable the session replication. another best option is you can use the coherence web if you are using latest versions of weblogic supporting coherence web. with that you not need to worry on user sessions and you can start any of the managed server anytime without worrying about the user sessions.
    http://weblogicserveradministration.blogspot.com/2010/10/manage-http-session-states-session.html
    http://weblogicserveradministration.blogspot.com/2011/05/oracle-coherence-37-coherenceweb.html
    http://weblogicserveradministration.blogspot.com/2010/11/clustering-part-i.html
    another way is, you can use side by side deployment feature in case you don't want shutdown your application completely, with this, old connections and new requests will goes to old application and once new application activated all new requests will come to new application and once all requests on old application will complete that application will retire automatically.
    Regards
    Mukesh Negi
    http://weblogicserveradministration.blogspot.com

  • Auto-Deployment and Restarting Managed Server

    Hi,
    We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
    over a new WAR file into the applications directory. Then he ried to restart the
    managed server. This appeared to hang, so he tried restarting the admin. server,
    which also failed. Looking at the log, it looks like the admin. server is trying
    to deploy apps. from the applications/backup directory.
    After I removed the backup directory and edited config.xml to remove all references
    to this directory, I was able to startup the Admin. server (though there were
    still some errors; see later) and the managed server.
    The servers are actually running in "developemnt" mode and have the Aut-Deploy
    feature enabled, so my theory is that the auto-deployment was conflicting with
    the managed server restart. He shouldn't have had to restart the managed server
    since Auto-Deploy is enabled, right?
    I'm also wondering about these errors I got when I the Admin. server finally started:
    Starting WebLogic Server...
    <May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
    /wlsapp/prod/ivrprod/./config.xml>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "admin" for domain "ivrprod">
    <May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir>
    <May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Running>
    <May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Completed>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
    started for development server.>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir-0>
    <May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
    in RUNNING mode>
    <May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
    InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
    errors:
    /wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
    va:17: package com.nuance.ps.telus does not exist
    <May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
    yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
    (line 7): class 'com.nuance.ps.telus.Shared
    Storage' could not be loaded>
    <May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
    translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
    (line 2): class 'com.nuance.ps.telus.SharedStorage'
    could not be loaded>
    <May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
    failed to complete the deployment task with id 16 for
    the application appsdirbackup_dir.
    weblogic.management.ApplicationException: Prepare failed. Task Id = 16
    Thanks,
    Paul

    The short answer to your question is that auto-deployment and multiple
    servers don't mix.
    If you have a single-server domain and choose to use auto-deployment,
    that'll work fine.
    Once you have separate admin/managed servers, you need to use
    weblogic.Deployer, the wldeploy ant task (8.1), or the console to deploy
    applications.
    -- Rob
    Paul wrote:
    Hi,
    We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
    over a new WAR file into the applications directory. Then he ried to restart the
    managed server. This appeared to hang, so he tried restarting the admin. server,
    which also failed. Looking at the log, it looks like the admin. server is trying
    to deploy apps. from the applications/backup directory.
    After I removed the backup directory and edited config.xml to remove all references
    to this directory, I was able to startup the Admin. server (though there were
    still some errors; see later) and the managed server.
    The servers are actually running in "developemnt" mode and have the Aut-Deploy
    feature enabled, so my theory is that the auto-deployment was conflicting with
    the managed server restart. He shouldn't have had to restart the managed server
    since Auto-Deploy is enabled, right?
    I'm also wondering about these errors I got when I the Admin. server finally started:
    Starting WebLogic Server...
    <May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
    /wlsapp/prod/ivrprod/./config.xml>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "admin" for domain "ivrprod">
    <May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir>
    <May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Running>
    <May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Completed>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
    started for development server.>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir-0>
    <May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
    in RUNNING mode>
    <May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
    InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
    errors:
    /wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
    va:17: package com.nuance.ps.telus does not exist
    <May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
    yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
    (line 7): class 'com.nuance.ps.telus.Shared
    Storage' could not be loaded>
    <May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
    translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
    (line 2): class 'com.nuance.ps.telus.SharedStorage'
    could not be loaded>
    <May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
    failed to complete the deployment task with id 16 for
    the application appsdirbackup_dir.
    weblogic.management.ApplicationException: Prepare failed. Task Id = 16
    Thanks,
    Paul

  • Unable to deploy and run WD Java app through NWDS with a remote J2ee engine

    Hi ,
    We have a clustered server instance configuration in our environment.
    I have already added the message server port and the server details in the remote J2ee engine configuration in NWDS through windows->preferences .
    I found the port no. and the host server name using <servername>:<portname>sap/monitor/systeminfo
    Also, I can see the SDM , dispatcher and the server running/shown in green in the J2ee engine setting.
    But when I was trying to connect deploy and run the application, first it asks for the SDM password and after entering it , it aborts with the following message :
    Sep 18, 2007 8:32:15 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : XXX00
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/check1/LOCALS~1/Temp/temp11565my_pro.ear
    Deployment exception : Server XXX00 did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server XXX00 at port 50018: Connection timed out: connect
    Inner exception was :
    Server XXX00 did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server XXX00 at port 50018: Connection timed out: connect
    Can anyone let me know what can be the reason.
    Best Regards
    Sid

    Hi Siddharth,
    Re-start  SDM process of J2EE engine.Make sure when you are deploying u r project others are not deploying their project.
    SAP Note : <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_jas/~form/handler">701654</a>
    Regards,
    Mithu

  • WebLogic 11g EAR EJB Classpath and class loaders

    All,
    I have been having issues migrating Spring based EJB applications from OC4J to WebLogic 11g (10.3.1). I have been in communication with Oracle who has suggested a work around however I am keen to see if anyone else can suggest a solution.
    The application is dependant on stateless session EJB beans that communicate with a Spring managed service tier to perform the business logic and database access. PitchFork is used to inject the Spring managers into the EJB’s using the spring-ejb-jar.xml configuration file. Note originally I was using the SpringBeanAutowiringInterceptor however I could not get this to work. See WebLogic 11g and Spring beens injected into EJB for details.
    When the application is deployed packaging all the dependant jars within the APP-INF\lib folder I get a verity of errors from the following InvalidClassException, NoSuchMethodError, AbstractMethodError and IllegalArgumentException. I am using Spring 2.5.3 to match the supported WebLogic version. Note within the EAR application.xml the library-directory is set to APP-INF/lib. The issue appears to be Spring, PitchFork, commons-logging and aspectj libraries are being loaded form WebLogic and do not have visibility on jars within the application or have been modified when bundled for WebLogic. An example of this is the PitchFork jar within WebLogic has been changed excluding the spi package resulting in java.lang.ClassNotFoundException: org.springframework.jee.spi.PitchforkUtilsImpl errors.
    Moving the jars to the domain library path does not resolve any of the issues. I have been unable to successfully deploy the application picking up the application jars using the prefer-application-packages configuration.
    Oracle has advised me to deploy the libraries into the WebLogic system classpath by modifying the startWebLogic command to load the libraries into the classpath. I am concerned that modifying the system classpath will result in an unstable WebLogic server as I will be replacing modified jar files packages with WebLogic (such as PitchFork). This will also limit the applications that can be deployed within the server as each application must use the same libraries and versions (as the application ibraries are leing ignored).
    Has anyone else hit this issue and corrected it? Can anyone think of an alternative solution?
    Regards
    Neil

    Hi,
    I am in the process of updating the tracking bug# 331569 with copies of the eclipse EAR/WAR projects and the EAR for these scenarios. Here are some details on how I got past the 2nd CCE on the org.eclipse.persistence.jpa.PersistenceProvider class (not the javax one)
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=331569
    Essentially an SE persistence unit running both JPA 2.0 api and the 2.0 XSD schema work fine. I will next retest the EE case with variations of the 3 types of injection on the SSB or Servlet.
    Update: There are 3 (possibly 4) issues here (all of these may become obsolete when the next WLS version ships)Initially I got the same 2.0 schema error and the ClassCastException on org.eclipse.persistence.jpa.PersistenceProvider
    It turns out that my import of the 2 eclipse projects from my bug # 296271 for WebLogic 10.3.2.0 lost their facets(specifically the dynamic web facet) because I associated them with a different WebLogic 10.3.3.0. - this caused the CCE I was experiencing like Sri.
    Anyways, after creating an EAR/Web project combination from scratch in eclipse associated with the 10.3.3.0 instance - I predeployed/deployed/ran fine - even with the 2.0 schema - in SE bootstrap mode (no EE yet).
    Reproduction Procedure:
    redoing project from scratch as I noticed that the war was not at the root of the ear - it was a jar in the app-inf/lib dir - my imported eclipse project was not referenced correctly as a web module facet- create empty EAR and WAR project with references
    - download and open my EAR and WAR project code from bug # 296271
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=296271
    - do essentially all the steps in the page below (I paraphrase for re-verification)
    http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#DI_1.1:_Alternative_3:_Application_Level_Shared_Library_-InUse
    - copy applicationService, entity and FrontController servlet code into new projects
    - create persistence.xml and MANIFEST.MF manifest in src\META-INF
    - update manifest
    Class-Path: APP-INF/lib/eclipselink.jar
    APP-INF/lib/javax.persistence_2.0.0.v200911041116.jar
    - copy both javax.persistence 2.0 and eclipselink 2.x jars to APP-INF/lib
    - change ordering of WebLogic library modules classpath reference (javax.persistence 1.0) to ear reference (2.0 version)
    - update web.xml with servlet tags
    - update weblogic.xml with new context root
    - make the persistence unit name the same in persistence.xml and ApplicationManagedService
    - update weblogic-application.xml with prefer-application-packages overrides
    <wls:prefer-application-packages>
    <wls:package-name>javax.persistence.*</wls:package-name>
    <wls:package-name>org.eclipse.persistence.*</wls:package-name>
    </wls:prefer-application-packages>
    - enable server redirect logging
    <!-- new for 10.3.3.0 http://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging#Server_Logging -->
    <property name="eclipselink.logging.logger" value="DefaultLogger"/>
    - start WebLogic 10.3.3.0
    - deploy (run on) server from eclipse or export ear to auto deploy directory
    1) JPA 2.0 XSD usage on 10.3.3.0
    - I reproduced this issue with a bad EAR
    - was able to use the 2.0 schema within the WAR-only application managed EAR
    persistence.xml<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
    <!-- persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"-->
    <persistence-unit name="example2" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>localJTA</jta-data-source>
    <class>org.eclipse.persistence.example.business.Cell</class>
    <shared-cache-mode>NONE</shared-cache-mode>
    <properties>
    <property name="eclipselink.target-server" value="WebLogic_10"/>
    <property name="eclipselink.logging.level" value="FINEST"/>
    <property name="eclipselink.target-database" value="Derby"/>
    <!-- new for 10.3.3.0 http://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging#Server_Logging -->
    <property name="eclipselink.logging.logger" value="DefaultLogger"/>
    <!-- property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.ClientDriver"/>
    <property name="javax.persistence.jdbc.url" value="jdbc:derby://127.0.0.1:1527/dataparallel;create=true"/>
    <property name="javax.persistence.jdbc.user" value="APP"/>
    <property name="javax.persistence.jdbc.password" value="APP"/-->
    <!-- turn off DDL generation after the model is stable -->
    <!-- property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
    <property name="eclipselink.ddl-generation.output-mode" value="both"/-->
    </properties>
    </persistence-unit>
    </persistence>
    2) CCE on JPA provider implementation class
    Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit example2: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider
    - I reproduced and fixed this one (was Eclipse project facet issue) - EAR was wrong
    - was able to run JPA 2.0 code fine on an SE PU (predeploy/deploy together)
    - EE injection should not work but I will post an example EAR anyway
    log[EL Example]: enterprise: JPA 2.0 Metamodel: MetamodelImpl@56287508 [ 3 Types: , 1 ManagedTypes: , 1 EntityTypes: , 0 MappedSuperclassTypes: , 0 EmbeddableTypes: ]
    3) CCE on JPA spec interface class
    - I could not reproduce this one
    Re: WebLogic 11g EAR EJB Classpath and class loaders
    Error processing persistence unit PT of module pt: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit PT: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider
    4) CCE on fallback Kodo JPA provider (if an invalid say 2.1 JPA XSD schema is referenced)
    java.lang.ClassCastException: kodo.persistence.PersistenceProviderImpl
    at javax.persistence.Persistence.findAllProviders(Persistence.java:186)
    java.lang.NoSuchMethodError: javax/persistence/EntityManager.getMetamodel()Ljavax/persistence/metamodel/Metamodel;
    - reproduced by using the 1.0 javax.persistence jar (but named as the 2.0 one in APP-INF/lib)
    - fixed by using either the 1.0 or 2.0 JPA XSD schema and using the correct 2.0 spec jar
    thank you
    /michael

  • Deploy and upload

    Through the web management interface, it is possible to upload an ear file from
    my desktop to a server and deploy it. However, it seems that there is no way
    to "update" or redeploy the ear from the web interface, so instead I ftp it up
    to an upload directory, then run the weblogic.deploy tool to redeploy it.
    Question: when running weblogic.deploy, my server puts the ear in a .wlstaging
    directory, but it doesn't actually update the ear in the applications directory.
    no errors are thrown, but the ear in applications clearly is not the same as
    the one in .wlstaging. Any reasons why? I am not redeploying as root, but I
    am part of a group that has read/write permissions on that directory. does it
    need execute as well? is it something else?
    jay

    There isn't currently. Sorry. I noted this hole the other day. The
    command line deployer will do this for you, but it aint an API which is what
    you want.
    I filed an enhancement to do this in a future release. For now you will
    have to implement an upload servlet in the AS and then execute the
    deployment.
    Cheers
    mbg
    "Steven Haines" <[email protected]> wrote in message
    news:3e9dd25a$[email protected]..
    Hi,
    Is there a way through remote accesss of WebLogic JMX MBeans to upload and
    deploy a WAR file to a WebLogic server? Does anyone know if this
    functionality is exposed via any of WebLogic's MBeans? I have the API, but
    there are just too many classes.. I already looked through ServerMBean,
    ServerRuntimeMBean, DeploymentMBean, DeployerRuntimeMBean, and
    DeploymentTaskRuntimeMBean docs as a starting point, but nothing thus far.
    Thanks,
    Steve

  • Tiered Architecture and Clustering

    Hi,
              Was wondering if anyone had problems setting up clustering in a
              tiered environment. What we are looking to do is setup a load balancer
              in front of a weblogic presentation tier (Servlets and JSP) that in
              turn connect to a clustered application tier of EJB's. Just some
              random thoughts:
              1) Does the replica aware stub live in the presentation tier?
              2) Does it make sense to put another load balancer between tier's? Or
              just let the stub handle the load balancing?
              Curious to know if anyone else has setup a similar configuration.
              Regards,
              Rick Mitterer
              

    I have seen several such setups. You do not usually have a dedicated
              hardware load balancer between the JSP/Servlet container and the EJB
              container. The replica-aware stub is where the EJB client is, which is the
              JSP/Servlet container.
              Peace,
              Cameron Purdy
              Tangosol Inc.
              << Tangosol Server: How Weblogic applications are customized >>
              << Download now from http://www.tangosol.com/download.jsp >>
              "Rick Mitterer" <[email protected]> wrote in message
              news:[email protected]..
              > Hi,
              > Was wondering if anyone had problems setting up clustering in a
              > tiered environment. What we are looking to do is setup a load balancer
              > in front of a weblogic presentation tier (Servlets and JSP) that in
              > turn connect to a clustered application tier of EJB's. Just some
              > random thoughts:
              >
              > 1) Does the replica aware stub live in the presentation tier?
              >
              > 2) Does it make sense to put another load balancer between tier's? Or
              > just let the stub handle the load balancing?
              >
              > Curious to know if anyone else has setup a similar configuration.
              >
              > Regards,
              > Rick Mitterer
              

  • Multiple call managers and clusters sharing one application server

    Hi
    I need to program my application such that it can be shared by multiple call managers and clusters. That is, I can only have one application server, and as a result I need to tell my application from which call manager / cluster this "request" is coming from.
    My question is how do we do that? do we have access to some parameters / variables, similar to "#DEVICENAME#", which can be used to pass the call manager identity to the application?
    TIA

    Use multiple instances of your application with different URIs (assuming the instances will not have to talk to each other), then, when configuring the service on each cluster, simply reference the specific URI of the application instance for that cluster. eg: Using Tomcat to host the PhoneMessenger application for Cluster1 and Cluster2, Deploy the same application twice: PhoneMessengerForCluster1 and PhoneMessengerForCluster2. The service URL on Cluster1 might be: http://app_server/PhoneMessengerForCluster1/servlet/PhoneMessenger , and for Cluster2 it could be http://app_server/PhoneMessengerForCluster2/servlet/PhoneMessenger

  • Weblogic Portal: Error While Deploying: VALIDATION PROBLEMS WERE FOUND

    Hello friends
    I am getting following error while deploying EAR on server.
    “Module named 'MyEAR' failed to deploy. See Error Log view for more detail.”
    Steps I followed:
    1: Created one portal domain successfully and was able to start the serve after thatr.
    2: Created one Portal EAR Project and added it on server.
    Now when I am restarting the server, getting following error/log
    **“weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND**
    **problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>”**
    Exception stack Trace:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
    at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
    at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
    at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
    at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    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)
    Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:178)
    as it is ‘brand new ‘ – IDE generated application, weblogic-application.xml is untouched.
    Thanks & Regards

    I have seen this problem also. To be clear, this occurs straight out of the box. In other words - launch eclipse, create a new workspace, create a new portal EAR project with the wizard, and then try to deploy it without touching anything. In fact, try changing the portal's facets to anything, plain EAR, 11g default, Portal EAR - it doesn't matter. It will not deploy. Either you get this error or you get deployment errors complaining about missing library references in the weblogic-application.xml. Then - you have to do surgery just to get an 'out of the box' portal to run. Very frustrating.

  • 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

  • How to deploy and run  EJB in eclipse without XDoclet

    Hi Friends
    I am new in j2ee.In my academic project i want to do some ejb programming.
    For that purpose i want to write some ejb's.I have written all required class for ejb,created ejb-jar.xml file manually,weblogic .xml file manually. I am using weblogic8 as an server for deployment.
    I know deployment with xdoclet but i want to know hoe to deploy ejb without xdoclet.
    If u have saple code or useful link regarding this please send it as soon as possible.
    Thanks in advance
    How to deploy and run EJB in eclipse without XDoclet

    HI Welcome to J2ee...
    I am also new to this...But i ll share my ideas with you...
    In EJB 3.0 No need of any Deployment Descriptors....
    And If you are using Eclipse You can Deploy(as jar) using Export in File tab...
    XDoclet is not mandatory...
    Gopal V

Maybe you are looking for