Visualizzazione dei risultati da 1 a 3 su 3
  1. #1

    [Java+Netbeans+Mysql] Problemi connessione data base

    Salve, ho un problema con neatbeans,
    sto cercando di creare una applicazione con JEE che gestisca i dati contenuti in un dataBase tramite delle interfaccie Jsp.

    Ho trovato sul sito di neatBeans questo esempio,
    [URL=http://netbeans.org/kb/docs/web/mysql-webapp.html ]http://netbeans.org/kb/docs/web/mysql-webapp.html

    creo e riempo le tabelle nel relativo dataBase ma quando vado a lanciare il programma mi da un errore.

    nel brouser mi compare la seguente scritta:
    ----------------------------------------------------------

    HTTP Status 500 -

    type Exception report

    message

    descriptionThe server encountered an internal error () that prevented it from fulfilling this request.

    exception

    javax.servlet.ServletException:
    SELECT subject_id, name FROM Subject
    : Tabella/Vista 'SUBJECT' non esiste.

    root cause

    java.sql.SQLSyntaxErrorException: Tabella/Vista 'SUBJECT' non esiste.

    root cause

    org.apache.derby.client.am.SqlException: Tabella/Vista 'SUBJECT' non esiste.

    note The full stack traces of the exception and its root causes are available in the GlassFish v3 logs.
    GlassFish v3
    ----------------------------------------------------------

    mentre nel output di neatBeans compare la seguete dicitura:


    AVVERTENZA: StandardWrapperValve[jsp]: PWC1406: Servlet.service() for servlet jsp threw exception
    java.sql.SQLSyntaxErrorException: Tabella/Vista 'SUBJECT' non esiste.
    at org.apache.derby.client.am.SQLExceptionFactory40.g etSQLException(Unknown Source)
    at org.apache.derby.client.am.SqlException.getSQLExce ption(Unknown Source)
    at org.apache.derby.client.am.Connection.prepareState ment(Unknown Source)
    at com.sun.gjc.spi.base.ConnectionHolder.prepareState ment(ConnectionHolder.java:475)
    at org.apache.taglibs.standard.tag.common.sql.QueryTa gSupport.doEndTag(QueryTagSupport.java:251)
    at org.apache.jsp.index_jsp._jspx_meth_sql_query_0(in dex_jsp.java from :175)
    at org.apache.jsp.index_jsp._jspService(index_jsp.jav a from :62)
    at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:847)
    at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:406)
    at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:483)
    at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:373)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:847)
    at org.apache.catalina.core.StandardWrapper.service(S tandardWrapper.java:1523)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:279)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:188)
    at org.apache.catalina.core.StandardPipeline.invoke(S tandardPipeline.java:641)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipel ine.java:97)
    at com.sun.enterprise.web.PESessionLockingStandardPip eline.invoke(PESessionLockingStandardPipeline.java :85)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:185)
    at org.apache.catalina.connector.CoyoteAdapter.doServ ice(CoyoteAdapter.java:332)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:233)
    at com.sun.enterprise.v3.services.impl.ContainerMappe r.service(ContainerMapper.java:165)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(P rocessorTask.java:791)
    at com.sun.grizzly.http.ProcessorTask.doProcess(Proce ssorTask.java:693)
    at com.sun.grizzly.http.ProcessorTask.process(Process orTask.java:954)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute (DefaultProtocolFilter.java:170)
    at com.sun.grizzly.DefaultProtocolChain.executeProtoc olFilter(DefaultProtocolChain.java:135)
    at com.sun.grizzly.DefaultProtocolChain.execute(Defau ltProtocolChain.java:102)
    at com.sun.grizzly.DefaultProtocolChain.execute(Defau ltProtocolChain.java:8Cool
    at com.sun.grizzly.http.HttpProtocolChain.execute(Htt pProtocolChain.java:76)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(Pr otocolChainContextTask.java:53)
    at com.sun.grizzly.SelectionKeyContextTask.call(Selec tionKeyContextTask.java:57)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:6 9)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doW ork(AbstractThreadPool.java:330)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run (AbstractThreadPool.java:309)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: org.apache.derby.client.am.SqlException: Tabella/Vista 'SUBJECT' non esiste.
    at org.apache.derby.client.am.Statement.completeSqlca (Unknown Source)
    at org.apache.derby.client.net.NetStatementReply.pars ePrepareError(Unknown Source)
    at org.apache.derby.client.net.NetStatementReply.pars ePRPSQLSTTreply(Unknown Source)
    at org.apache.derby.client.net.NetStatementReply.read PrepareDescribeOutput(Unknown Source)
    at org.apache.derby.client.net.StatementReply.readPre pareDescribeOutput(Unknown Source)
    at org.apache.derby.client.net.NetStatement.readPrepa reDescribeOutput_(Unknown Source)
    at org.apache.derby.client.am.Statement.readPrepareDe scribeOutput(Unknown Source)
    at org.apache.derby.client.am.PreparedStatement.readP repareDescribeInputOutput(Unknown Source)
    at org.apache.derby.client.am.PreparedStatement.flowP repareDescribeInputOutput(Unknown Source)
    at org.apache.derby.client.am.PreparedStatement.prepa re(Unknown Source)
    at org.apache.derby.client.am.Connection.prepareState mentX(Unknown Source)
    ... 35 more


    come posso risolvere il problema

    grazie

  2. #2

    [Java+Netbeans+Mysql] Problemi connessione data base

    Ciao,

    non ho avuto tempo di seguire il tutorial, ma da l'eccezione restituita si capisce che la tabella sul database specificato non esista. Controlla la presenza della tabella nel relativo db.

    Prova a connetterti con un qualsiasi cliente al server mysql e controlla l'esistenza della tabella!!

  3. #3
    grazie per la tua risposta, cmq le tabelle sono presenti e ben popolate. A mio avviso il problema sta nel settare a quale dataBase far collegare l'applicazione.

Permessi di invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi
  •  
Powered by vBulletin® Version 4.2.1
Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.