Connection problems in a Web Application

hi everybody.
I'm developing a struts-based Web Application to investigate an Oracle 9.2 DB, using Exadel Studio / Eclipse and Tomcat 5.0.
Here is the problem: I've made a class to test data-displaying, which simply connects to db using oci8 and returns a resultset, using the base procedure:
// load driver
Class.forName("oracle.jdbc.driver.OracleDriver");
// open connection
Connection conn=DriverManager.getConnection(...);
Statement st = conn.createStatement();
rs = st.executeQuery(sql);Now, everytime I call this method from my Action, to get back the resultset and display it in my jsp, I get a ClassNotFoundException on the Class.forName instruction.
Note that classes12.jar is correctly mounted, in fact if I run stand-alone the class containing this method, it connects without problems and returns the expected results. The exception is raised ONLY when the entire web application is running and the method is triggered by the struts Action.
Can anyone help me please?
Thank you in advance, I'm crushing my head on this for 2 weeks!
Emanuele

This means that your driver jar is unavailable to your web application; I'm pretty sure that Tomcat overrides the classpath set by your IDE. You can add application jars to the WEB-INF/lib of your web application. You can also set a container classpath that points to the jars...
here's some instructions for add the jars for cactus to Tomcat; just substitute your driver jars in these instructions.
http://jakarta.apache.org/cactus/integration/howto_tomcat.html
Also, classes12.jar is for Java 1.2 and Java 1.3 Since you are using Struts, I suspect you're also using Java 1.4 or Java 1.5 and you should probably be developing with the appropriate driver (classes12.jar does mostly work with Java 1.4, but Oracle doesn't support it.)

Similar Messages

  • I am facing a caching problem in the Web-Application that I've developed us

    Dear Friends,
    I am facing a caching problem in the Web-Application that I've developed using Java/JSP/Servlet.
    Problem Description: In this application when a hyperlink is clicked it is supposed to go the Handling Servlet and then servlet will fetch the data (using DAO layer) and will store in the session. After this the servlet will forward the request to the view JSP to present the data. The JSP access the object stored in the session and displays the data.
    However, when the link is clicked second time then the request is not received by our servlet and the cached(prev data) page is shown. If we refresh the page then request come to the servlet and we get correct data. But as you will also agree that we don't want the users to refresh the page again and again to get the updated data.
    We've included these lines in JSPs also but it does no good:
    <%
    response.setHeader("Expires", "0");
    response.setHeader("Cache-Control" ,"no-cache, must-revalidate");
    response.setHeader("Pragma", "no-cache");
    response.setHeader("Cache-Control","no-store");
    %>
    Request you to please give a solution for the same.
    Thanks & Regards,
    Mohan

    However, when the link is clicked second time then the request is not received by our servlet Impossible mate.. can you show your code. You sure there are no javascript errors ?
    Why dont you just remove your object from the session after displaying the data from it and see if your page "automatically" hits the servlet when the link is clicked.
    cheers..
    S

  • Problem deploying a web application (war)

    Hello,
    I am having a problem deploying a web application in Tomcat.
    Here is what happens:
    -I copied the war file into the webapps directory.
    -I started Tomcat.
    -Tomcat automatically expanded the war file into a directory of the same name.
    The problem is that I get the following error: "The requested resource (/jadmin) is not available." when I try to access my web application
    Can anyone please help?
    Thanks in advance,
    Balteo.

    Hi,
    check the Tomcat log file <tomcat_dir>/logs/localhost_log.yyyy-mm-dd.txt and see if there is an error corresponding to the deployement of the (/jadmin) context.

  • 3 BUGS  WITH LION CONNECTING PROBLEMS TO SOME WEB SITES & MAIL SERVERS

    I HAVE 3 BUGS  WITH LION FOR MORE THAN ONE MONTH & GETTING WORSE
    1 - CONNECTING PROBLEMS TO SOME WEB SITES  SERVERS
    I TRY  EVERY BROWSER I HAVE ( SAFARI \ FIREFOX \ CHROME )
    I CAN NOT OPEN SOME SITES ALMOST ALL TIMES
    SOME TIMES OPEN THIS SITES BUT AFTER MINUTES DO NOT CONNECT TO IT
    I GET THIS BUG IN THE PAST  BUT LATLY IT GONE WORSE
    NOW IT IS MORE FREQUENT  & MORE  SITES
    2 - CONNECTING PROBLEMS TO SOME MAIL SERVERS
    THE MAIL APP CAN NOT CONNECT TO
    ( INCOMING  HOTMAIL SERVER \  OUTGOING  HOTMAIL SERVER \  OUTGOING  YAHOO SERVER  )
    MOST OF THE TIME
    MORE FREQUENT
    3 - CHECKING OUT SHOPPING BAG FROM SHOPPING SITES PROBLEMS
    I TRY TO CHECKOUT THE SHOPPING BAG IN 2 SITES & COULD NOT CHECKOUT THE ORDER 
    I HAD TO USE ANOTHER COMPUTER
    FIRST TIME I HAVE THIS
    I HAVE LITTLE SNITCH 3 ON & LION FIREWALL ON
    I TRIED EVERY ACCOUNT  IN THIS COMPUTER
    with Little Snitch disabled   >>>>>>>  i have the same problem !!!!!
    with lion firewall off    >>>>>>>  i have the same problem !!!!! 
    I STILL HAVE THE SAME CONNECTION PROBLEM
    IF YOU HAVE ANY SUGGESTION PLEASE HELP ME
    LION  BUGS IS DRIVING ME CRAZY   IT IS BY FAR THE 2ND WORSE OS Produced by APPLE AFTER IOS 2.0 FOR IPHONE
    I WANT TO GO TO LEOPARD AGAIN
    IF YOU HAVE ANY IDEA HOW TO INSTALL LEOPARD TO THE NEW MACBOOK PRO
    PLEASE LET ME KNOW

    Biggest bug is that your key caps key gets stuck. Repost, without the all caps stuff, which is tantamount to shouting, and maybe we can read what your problems are all about.

  • Access problem in a  web application

    I have a web application with JSP, and in my pages, at the top, there is a sliding text (applet) from right to left, which has dynamic content from a database. The pages using the applet is at the root of the site, and the applet class located in the "WEB-INF/classes/WebClasses " directory. When I start the application, the pages using the applet complain that the class cannot be found. Pages' code and codebase attributes are fine, there is nothing wrong with these. What can be the problem?..

    What could be a good solution while keeping
    this connection class available to both of them (the
    sliding text class and the beans in the
    'WEB-INF/classes/WebBeans' directory) ?You would need two copies, one in the WEB-INF/classes/WebBeans directory for the server to access, the other in the JAR or directory structure you use for the applet. Remember what malcolmmc said, the applet runs on the client and the JSP/servlets run on the server. That means you have to provide the code for each of the server and the client.
    And this is besides the point that malcolmmc made that applets usually aren't able to make DB connections...

  • Connection pool for big web application

    hi,
    i am developing an application which had more then 20 classes and each class use databases.
    i made an connection bean and use it for database connectivity but as my code expand and my application run for longer time i start getting error of connection limit.
    then i start using connection pool. in this i start using one connection for whole application.
    now i want that my
    1-whole application use that connection pool and i dont need to initialize it in different classes.
    2- The main problem is that may at a time i have to connect database with different user and these connections should remain active.
    my application will be used for enterprise level and remain active for months .
    following is my connection pool
    public class ConnectionPool implements Runnable
          private Log log=new Log();
          private String driver, url, username, password;
          private int maxConnections;
          private boolean waitIfBusy;
          private Vector availableConnections, busyConnections;
          private boolean connectionPending = false;
          public ConnectionPool(String driver, String url,String username, String password,int initialConnections, int maxConnections, boolean waitIfBusy) 
              this.driver         =     driver;
              this.url            =     url;
              this.username       =     username;
              this.password       =     password;
              this.maxConnections =     maxConnections;
              this.waitIfBusy     =     waitIfBusy;
              if (initialConnections > maxConnections)
                initialConnections = maxConnections;
              availableConnections = new Vector(initialConnections);
              busyConnections = new Vector();
              try
                  for(int i=0; i<initialConnections; i++)
                    availableConnections.addElement(makeNewConnection());
              catch(Exception e)
                log.write(e.getMessage());
          }//EO constructor
      public synchronized Connection getConnection()
             if (!availableConnections.isEmpty())
                  log.write("Total connections="+availableConnections.size());
                  Connection existingConnection =  (Connection)availableConnections.lastElement();
                  int lastIndex = availableConnections.size() - 1;
                  availableConnections.removeElementAt(lastIndex);
                  // If connection on available list is closed (e.g.,it timed out), then remove it from available list
                  // and repeat the process of obtaining a connection. Also wake up threads that were waiting for a connection because maxConnection limit was reached.
                        try
                            if (existingConnection.isClosed())
                              notifyAll(); // Freed up a spot for anybody waiting
                              return(getConnection());
                            else
                              log.write(  "in available connection"  );
                              busyConnections.addElement(existingConnection);
                              return(existingConnection);
                        catch(SQLException se)
                            log.write(se.getMessage());
              } else {
                        // Three possible cases:
                        // 1) You haven't reached maxConnections limit. So establish one in the background if there isn't
                        //    already one pending, then wait for the next available connection (whether or not it was the newly established one).
                        // 2) You reached maxConnections limit and waitIfBusy flag is false. Throw SQLException in such a case.
                        // 3) You reached maxConnections limit and waitIfBusy flag is true. Then do the same thing as in second
                        //    part of step 1: wait for next available connection.
                        if ((totalConnections() < maxConnections) &&  !connectionPending)
                          makeBackgroundConnection();
                        else if (!waitIfBusy)
                            log.write("Connection limit reached");
                        // Wait for either a new connection to be established (if you called makeBackgroundConnection) or for
                        // an existing connection to be freed up.
                        try {
                          wait();
                        catch(InterruptedException ie)
                          log.write(ie.getMessage());
                  // Someone freed up a connection, so try again.
                return(getConnection());
              }//EO main if-else
          return null;
    }//EO getconnection method
      // You can't just make a new connection in the foreground
      // when none are available, since this can take several
      // seconds with a slow network connection. Instead,
      // start a thread that establishes a new connection,
      // then wait. You get woken up either when the new connection
      // is established or if someone finishes with an existing
      // connection.
      private void makeBackgroundConnection() {
        connectionPending = true;
        try {
          Thread connectThread = new Thread(this);
          connectThread.start();
        } catch(OutOfMemoryError oome) {
          // Give up on new connection
          log.write(oome.getMessage());
      public void run() {
        try {
          Connection connection = makeNewConnection();
          synchronized(this) {
            availableConnections.addElement(connection);
            connectionPending = false;
            notifyAll();
        } catch(Exception e) { // SQLException or OutOfMemory
          // Give up on new connection and wait for existing one free up.
          log.write(e.getMessage());
      // This explicitly makes a new connection. Called in
      // the foreground when initializing the ConnectionPool,
      // and called in the background when running.
      private Connection makeNewConnection()
        //log.write("make new connection with  "+url+" "+username+" "+password +" and driver= "+driver);
        Connection connection=null;
          try
            // Load database driver if not already loaded
            //Class.forName(driver);
             DriverManager.registerDriver(new OracleDriver());
            // Establish network connection to database
            connection =  DriverManager.getConnection(url, username, password);
                    if( connection.isClosed() )
                      log.write("ooooooops no connection");
                    else
                      log.write("yahoooo get connection");
          catch(Exception e)
            log.write(e.getMessage());
        return(connection);
      public synchronized void free(Connection connection) {
        busyConnections.removeElement(connection);
        availableConnections.addElement(connection);
        // Wake up threads that are waiting for a connection
        notifyAll();
      public synchronized int totalConnections() {
        return(availableConnections.size() + busyConnections.size());
      /** Close all the connections. Use with caution:
       *  be sure no connections are in use before
       *  calling. Note that you are not <I>required</I> to
       *  call this when done with a ConnectionPool, since
       *  connections are guaranteed to be closed when
       *  garbage collected. But this method gives more control
       *  regarding when the connections are closed.
      public synchronized void closeAllConnections() {
        closeConnections(availableConnections);
        availableConnections = new Vector();
        closeConnections(busyConnections);
        busyConnections = new Vector();
      private void closeConnections(Vector connections) {
        try {
          for(int i=0; i<connections.size(); i++) {
            Connection connection =
              (Connection)connections.elementAt(i);
            if (!connection.isClosed()) {
              connection.close();
        } catch(SQLException sqle) {
          // Ignore errors; garbage collect anyhow
          log.write(sqle.getMessage());
      }i get this code from internet, in which it also mention that use following code
    public class BookPool extends ConnectionPool {
    private static BookPool pool = null;
    private BookPool(...) {
    super(...); // Call parent constructor
    public static synchronized BookPool getInstance() {
    if (pool == null) {
    pool = new BookPool(...);
    return(pool);
    }if some one want to use it for whole application then use connection pool by BookPool,
    now main point is i m not getting the BookPool class could some one explain it to me???
    and second by using it can i connect to different users of DB at a time, if cant then how i can.
    its good if some one explain it by little code.
    thxxxxxxxxxxxxxxxxxx

    If this is a real, serious application and not just for practice, then why are you trying to write your own connection pool implementation?
    You'd better use Jakarta's Commons Pool and Commons DBCP, which are widely used, well tested implementations of connection pools.
    If this is a web application running in a J2EE container, you'd normally configure the connection pool in the container. The container will register the pool in JNDI and you'd look it up in JNDI from your application.
    Here's some documentation on how to do that in Tomcat 5.5: JNDI Datasource HOW-TO

  • Problem deploying a web application to oc4j in Unix

    Hi! I would like to ask for someone's help on a problem I encountered while accessing a web app deployed to oc4j in Unix. Before deploying the application in Unix, I tried it on a Windows2000 server and it worked fine. I copied the same files (classes, jsps, js, css) to the Unix server and modified the same xml files (data-sources, global-web-application, http-web-site, server). I could access index.jsp of my application but I get a HTTP 404 error on the other pages. Also, the css applied on index.jsp doesn't seem to reflect on the page. Could someone share some insights on this and if you have experienced the same problem, kindly post your suggestions/solutions.
    Thanks a lot,
    Mildred

    Reposting... css problem has been resolved (case sensitivity issue)
    Hi! I would like to ask for someone's help on a problem I encountered while accessing a web app deployed to oc4j in Unix. Before deploying the application in Unix, I tried it on a Windows2000 server and it worked fine. I copied the same files (classes, jsps, js, css) to the Unix server and modified the same xml files (data-sources, global-web-application, http-web-site, server). I could access index.jsp of my application but I get a HTTP 404 error on the other pages. Could someone share some insights on this and if you have experienced the same problem, kindly post your suggestions/solutions.
    Thanks a lot,
    Mildred

  • Acces key problem in Mobile web application

    Hi experts,
    I am just trying a mobile web application according to the link given below:
    /people/john.moy3/blog/2010/11/21/build-your-first-mobile-web-app-using-jquery-mobile-and-abap--part-2
    tutorial by John Moy.
    While reimplementing the controller class i am getting one message "Method DO_INIT is implemented in class CL_BSP_CONTROLLER" and asking for Access key.
    Why this is happening and how i can overcome this problem?
    Please help me.
    Arun

    Use REDEFINE key....

  • Problem with BEx Web Application Designer

    Hi,
    we use since last week the Web Application Designer with the SAP GUI 7.2.
    Now I have a big problem since last week. I can call existing templates but unfortunately not change! I make a change in the template and save it. When I viewed the template again but no change is saved!
    A new template I can create and change
    Does anyone know the problem? The behavior also occurs with the old Gui 7.1.
    Regards
    Edited by: Jana VOGL on Oct 18, 2010 10:14 AM

    Hi Jana,
    Do you get any error before opening of an existing template in WAD? Doesn't look to be a problem with the different SAP GUI versions. Maybe somethings gone wrong with the Java - ABAP config settings or Java Portal communication settings. Maybe you should check with your BASIS team on the same. Tell them what the problem is & they will run a trace to figure out.
    --Priya

  • Connecting more than two web application

    I have 2 struts web application projects both are using different databases.
    how can i connect both web application in single web application.

    ravi.choudhary wrote:
    I have 2 struts web application projects both are using different databases.OK.
    how can i connect both web application in single web application.This question is too general and not technical. The statement "connect two applications in single application" makes also completely no sense. Please elaborate at a more technical level.

  • Problem running any web applications in netbean

    I receive this error message whenever i wanted to run any web applications in my netbeans. The following messages usually come up and I want people to help me:
    init:
    deps-module-jar:
    deps-ear-jar:
    deps-jar:
    library-inclusion-in-archive:
    library-inclusion-in-manifest:
    compile:
    compile-jsps:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    C:\usr\JavaProjects\LtlProjects\nbproject\build-impl.xml:568: Deployment error:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    See the server log for details.
    BUILD FAILED (total time: 1 minute 1 second)

    Netbeans is unable to deal with alias host name "localhost". But it isn't the only local server.
    Search for *::1 localhost* in your host file.
    I have Windows OS so host file is in this folder
    C:\Windows\System32\drivers\etc\hosts
    add *127.0.0.1 localhost* to the hosts file above the existing entry
    Should look like this:
    127.0.0.1 localhost
    ::1 localhost
    Stop server and close netbeans (if not already done).
    Restart and test. Server startup should be quicker.

  • Problems with deployed web applications

    Hi,
              currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta. So i deployed our application which was working on Weblogic 6.0 on the newly installed Weblogic 6.1 beta. Now when i try to access my application i recieve the following error page:
              Compilation of 'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java' failed:
              D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
              (No more information available, probably caused by another error)
              Full compiler error(s):
              D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
              pageContext.handlePageException(__ee);
              ^
              1 error
              Wed Jun 20 17:27:28 EEST 2001
              Does anyone know what could cause the problem ?
              Any help will be appreciated.
              Bybye.
              [att1.html]
              

              I have the same problem. My apps work in WebLogic 6.0, but not in 6.1 beta. Is
              it compatibility issue?
              Andi
              "Michael Li" <[email protected]> wrote:
              >Hi all,
              >
              >Anybody resolve this problem yet? We are experiencing the same problem
              >here.
              >
              >Thanks,
              >Michael
              >
              >===
              >"Evgenya Borisenko" <[email protected]> wrote in message
              >news:[email protected]...
              >Sure,
              >here goes:
              >
              >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.html: init>
              >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.html: Using standard I/O>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >init>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param verbose initialized to: true>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param packagePrefix initialized to: jsp_servlet>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param compilerclass initialized to: javac>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param srcCompiler initialized to weblogic.jspc>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param superclass initialized to null>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param workingDir initialized to:
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >param pageCheckSeconds initialized to: 1>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >initialization complete>
              >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >*.jsp:
              >pageCheckSeconds over-ruled in JSPServlet to : 1>
              >####<10:23:45 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101047>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >Generated java file:
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java>
              >####<10:23:53 EEST 24/06/2001> <Error> <HTTP> <evgenya> <evgyServer>
              ><ExecuteThread: '11' for queue: 'default'> <> <> <101046>
              ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)]
              >Compilation of
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java failed:
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java:165:
              >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
              >cannot be applied to (java.lang.Throwable)
              > pageContext.handlePageException(__ee);
              > ^
              >1 error
              >>
              >java.io.IOException: Compiler failed
              >executable.exec(java.lang.String[d:\bea\jdk131\bin\javac.exe, -classpath,
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotd
              >elete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_
              >evgyServer\WEB-INF\lib\993367393172activation.jar;D:\bea\wlserver6.1_beta\.\
              >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t
              >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393212ant.j
              >ar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyS
              >erver\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\
              >WEB-INF\lib\993367393532bsf.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\ap
              >plications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_
              >evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393613concurrent_classes.jar;
              >D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServ
              >er\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB
              >-INF\lib\993367393673cos.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli
              >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg
              >yServer_WebApp_evgyServer\WEB-INF\lib\993367393763dbConnBroker.jar;D:\bea\wl
              >server6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_com
              >p51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\
              >993367393773jasper.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\application
              >s\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServe
              >r_WebApp_evgyServer\WEB-INF\lib\993367393823java40.jar;D:\bea\wlserver6.1_be
              >ta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-I
              >NF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394103
              >jaxp.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete
              >_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyS
              >erver\WEB-INF\lib\993367394133jsdt.jar;D:\bea\wlserver6.1_beta\.\config\mydo
              >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy
              >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394263junit.jar;D:\bea
              >\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_
              >comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\l
              >ib\993367394324Jwap-0.7.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applic
              >ations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgy
              >Server_WebApp_evgyServer\WEB-INF\lib\993367394354log.jar;D:\bea\wlserver6.1_
              >beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB
              >-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\9933673943
              >74mail.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdele
              >te_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evg
              >yServer\WEB-INF\lib\993367394404orajdbc816-12.jar;D:\bea\wlserver6.1_beta\.\
              >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t
              >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394484parse
              >r.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_ev
              >gyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServ
              >er\WEB-INF\lib\993367394514servlet.jar;D:\bea\wlserver6.1_beta\.\config\mydo
              >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy
              >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394544webserver.jar;D:
              >\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-I
              >NF\lib\993367394584xalan.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli
              >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg
              >yServer_WebApp_evgyServer\WEB-INF\lib\993367394634xerces.jar;D:\bea\wlserver
              >6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442
              >\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367
              >394914_log.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnot
              >delete_evgyServer\wl_comp51442\WEB-INF\classes;D:\bea\wlserver6.1_beta\confi
              >g\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_wa
              >r_evgyServer_evgyServer_WebApp_evgyServer;D:\bea\wlserver6.1_beta\.\config\m
              >ydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_e
              >vgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\jaxp.jar;D:\bea\wlserver6
              >..1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\
              >WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\xerces.
              >jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgy
              >Server\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer
              >\WEB-INF\lib\crimson.jar;d:\bea\jdk131\jre\lib\rt.jar;d:\bea\jdk131\jre\lib\
              >i18n.jar;d:\bea\jdk131\jre\lib\sunrsasign.jar;d:\bea\jdk131\jre\classes;.;D:
              >\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF
              >\lib\xerces.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_
              >evgyServer\WEB-INF\lib\xalan.jar;D:\bea\wlserver6.1_beta\config\mydomain\app
              >lications\WebApp_evgyServer\WEB-INF\lib\mail.jar;D:\bea\wlserver6.1_beta\con
              >fig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\activation.jar;.\lib
              >\weblogic_sp.jar;.\lib\weblogic.jar;D:\bea\wlserver6.1_beta\config\mydomain\
              >applications\WebApp_evgyServer\WEB-INF\lib\bsf.jar;D:\bea\wlserver6.1_beta\c
              >onfig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\concurrent_classes
              >..jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\
              >WEB-INF\lib\cos.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\Web
              >App_evgyServer\WEB-INF\lib\dbConnBroker.jar;D:\bea\wlserver6.1_beta\config\m
              >ydomain\applications\WebApp_evgyServer\WEB-INF\lib\log.jar;D:\bea\wlserver6.
              >1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\orajdbc816
              >-12.jar;D:\bea\wlserver6.0\config\mydomain\applications\WebApp_evgyServer\WE
              >B-INF\classes, -d,
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer,
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java])
              > at
              >weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.jav
              >a:575)
              > at
              >weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354)
              > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:360)
              > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:181)
              > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:149)
              > at
              >weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:34
              >4)
              > at
              >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              >:240)
              > at
              >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              >:284)
              > at
              >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              >:200)
              > at
              >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              >ntext.java:2279)
              > at
              >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              >:1923)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              >hope that helps.
              >10x alot.
              >"Srinagesh Susarla" <[email protected]> wrote in message
              >news:[email protected]...
              >can u send the server side error-message!
              >thanks
              >nagesh
              >Evgenya Borisenko wrote:
              >Hi, currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta.
              >So
              >i deployed our application which was working on Weblogic 6.0 on the newly
              >installed Weblogic 6.1 beta. Now when i try to access my application
              >i
              >recieve the following error page: Compilation of
              >'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServe
              >r\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_
              >servlet\_ngroot\_web\__index.java' failed:
              >
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java:165:
              >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
              >cannot be applied to (java.lang.Throwable)
              >(No more information available, probably caused by another error)
              >
              >
              >Full compiler error(s):
              >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer
              >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s
              >ervlet\_ngroot\_web\__index.java:165:
              >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext
              >cannot be applied to (java.lang.Throwable)
              > pageContext.handlePageException(__ee);
              > ^
              >1 error
              >
              >
              >Wed Jun 20 17:27:28 EEST 2001 Does anyone know what could cause the problem
              >? Any help will be appreciated.Bybye.
              >
              >
              

  • *Connection problems Sap A Java Application*

    Hi Gurus,
    I have a problem. I'm riding the part of the JCO SERVER for SAP from sending information to a Java application.
    I created the RFC destination of the type TCP / IP and I have registered my JAVA application in the visual administrator. This application java is already deployed listening to SAP and I can think of the following error when I run a BAPI created in the ABAP fate that I created.
    It's not that I can think of that might be.
    Or if someone was going another way of doing it from using sap we can send things to JAVA without having to java call the BAPI please help.
    Errores tiempo ejecucióCALL_FUNCTION_REMOTE_ERROR
    "JCO.Server could not find server function 'Z_BAPI_RFC'"
    ¿Qué ha sucedido?
    Error in ABAP application program.
    The current ABAP program "Z_BAPI_RFC====================FT" had to be terminated because one of the statements could not be
    executed.
    This is probably due to an error in the ABAP program.
    The error occurred in an RFC call to another system.
    The target system has also written a short dump.
    Consult this short dump for more precise information about
    the cause of the error.

    Please note that this forum is dedicated to all other development-related questions which are not directly addressed by other forums. This includes Business Objects SDKs, products, or technologies which do not fall under BusinessObjects Enterprise, BusinessObjects Edge, Crystal Reports Server, or Crystal Reports (for example Desktop Intelligence SDK, Universe Designer SDK, Portal Integration Kits, Java User Function Libraries, and other third party technologies or development languages).
    As your query relates to an SAP product, please post to an SAP forum.
    Ludek

  • Error deploying Web application

    Hello Everyone, i have a problem with my web application that is not able to be deployed.
    the first time i deployed the application everything worked correctly i performed the contex lookup with no problem as was able to connect to the EJB application, i performed some changes, and now everytime i tried to deploy again the application i get this error
    [#|2010-02-12T23:03:34.661+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-434;Servlet;WebServiceInterface;http://vmlinux:8024/WebServiceInterface/WebServiceInterface;|DPL5306:Servlet Web Service Endpoint [WebServiceInterface] listening at address [http://vmlinux:8024/WebServiceInterface/WebServiceInterface]|#]
    [#|2010-02-12T23:03:38.107+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-434;_RequestID=3610621f-da38-477d-b37a-088311a00a42;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Deployment Error -- Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.testing.myEJBapplication.ReferenceServiceLocalBean/entityManager] in the scope of the module called [product/servers/glassfish/domains/domain1/applications/j2ee-modules/WebServiceInterface]. Please verify your application.
         at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPCRefs(BundleDescriptor.java:702)
         at com.sun.enterprise.deployment.WebBundleDescriptor.findReferencedPUs(WebBundleDescriptor.java:722)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.getAllPersistenceUnitDescriptors(PersistenceProcessor.java:171)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:132)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172)
         at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122)
         at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.handlePostDeployEvent(ModuleDeployer.java:636)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.postDeploy(ModuleDeployer.java:625)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:188)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:788)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
    |#]
    any ideas for this?? Thank you in advance regards
    Edited by: White_Merovingian on Feb 13, 2010 5:55 AM

    yeah these stacktraces are big scary blobs of text, but somewhere hidden among all the nonsense there is always the little piece of information you need:
    "Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.testing.myEJBapplication.ReferenceServiceLocalBean/entityManager]"
    So you are referring to a persistence unit in ReferenceServiceLocalBean that does not seem to exist. Do you have your persistence.xml deployed in the META-INF directory of the EJB module? Does it contain a persistence unit with the name that is declared in the bean?

  • Web Application and Serialization

    Hi, i have a problem with a web application that is running on an Application server (BEA WebLogic 7.0). I have only the war file of the web application and i must know if in this war there is a class that is not serializable.
    How can i find it ? Is there a tool that can help me to find not serializable classes ?
    Thanks.
    claudiozx2006

    One way to do that is to decompile Java classes with Java decompiler and see which one doesn't implement Serializable interface. Here is a link to a good decompiler: http://www.kpdus.com/jad.html

Maybe you are looking for