Announcement

Collapse
No announcement yet.

Rätselhafte Nullpointerexception in Vaadin

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Okay, ich frage mal bei den Activitileuten weiter, denn an sich geht es jetzt sogar, nachdem ich einige jars nachinstalliert habe, nur habe ich jetzt erneut Probleme mit der DB :-)

    Comment


    • #17
      Es funktioniert nicht, die ProcessEngine zu erschaffen.

      Ich habe nun folgenden Code in meiner Vaadin-UI-Klasse:

      Code:
      package com.example.xyhg;
      
      import javax.servlet.annotation.WebServlet;
      
      import org.activiti.engine.ProcessEngine;
      import org.activiti.engine.ProcessEngineConfiguration;
      
      import com.vaadin.annotations.Theme;
      import com.vaadin.annotations.VaadinServletConfiguration;
      import com.vaadin.server.VaadinRequest;
      import com.vaadin.server.VaadinServlet;
      import com.vaadin.ui.Button;
      import com.vaadin.ui.Button.ClickEvent;
      import com.vaadin.ui.Label;
      import com.vaadin.ui.UI;
      import com.vaadin.ui.VerticalLayout;
      
      @SuppressWarnings("serial")
      @Theme("xyhg")
      public class XyhgUI extends UI {
      
      	@WebServlet(value = "/*", asyncSupported = true)
      	@VaadinServletConfiguration(productionMode = false, ui = XyhgUI.class)
      	public static class Servlet extends VaadinServlet {
      	}
      
      	@Override
      	protected void init(VaadinRequest request) {
      
      		ProcessEngineConfiguration pec = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration()
      				  .setDatabaseSchemaUpdate(ProcessEngineConfiguration.DB_SCHEMA_UPDATE_FALSE)
      				  .setJdbcUrl("jdbc:mysql://127.0.0.1:3306/activiti;DB_CLOSE_DELAY=1000")
      				  .setJobExecutorActivate(true);
      		ProcessEngine processEngine = pec.buildProcessEngine();
      		
      		final VerticalLayout layout = new VerticalLayout();
      		layout.setMargin(true);
      		setContent(layout);
      		
      		Button button = new Button("Click Me");
      		button.addClickListener(new Button.ClickListener() {
      			public void buttonClick(ClickEvent event) {
      				layout.addComponent(new Label("Thank you for clicking"));
      			}
      		});
      		layout.addComponent(button);
      	}
      
      }

      Ich habe in der WEB-INF-classes-Datei die war von avtiviti herausgesucht un die db.properties-Datei wie folgt modifiziert:

      Code:
      db=mysql
      
      jdbc.driver=com.mysql.jdbc.Driver
      
      jdbc.url=jdbc:mysql://127.0.0.1:3306/
      DB_CLOSE_DELAY=1000
      
      jdbc.username=root
      
      jdbc.password=
      supergeheim

      Dennoch beomme ich folgenden stacktrace:

      org.activiti.engine.ActivitiException: Error while building ibatis SqlSessionFactory: Error creating document instance. Cause: java.net.ConnectException: Connection timed out: connect
      at org.activiti.engine.impl.cfg.ProcessEngineConfigur ationImpl.initSqlSessionFactory(ProcessEngineConfi gurationImpl.java:706)
      at org.activiti.engine.impl.cfg.ProcessEngineConfigur ationImpl.init(ProcessEngineConfigurationImpl.java :436)
      at org.activiti.engine.impl.cfg.ProcessEngineConfigur ationImpl.buildProcessEngine(ProcessEngineConfigur ationImpl.java:408)
      at com.example.xyhg.XyhgUI.init(XyhgUI.java:34)
      at com.vaadin.ui.UI.doInit(UI.java:639)
      at com.vaadin.server.communication.UIInitHandler.getB rowserDetailsUI(UIInitHandler.java:222)
      at com.vaadin.server.communication.UIInitHandler.sync hronizedHandleRequest(UIInitHandler.java:74)
      at com.vaadin.server.SynchronizedRequestHandler.handl eRequest(SynchronizedRequestHandler.java:41)
      at com.vaadin.server.VaadinService.handleRequest(Vaad inService.java:1402)
      at com.vaadin.server.VaadinServlet.service(VaadinServ let.java:305)
      at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
      at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:303)
      at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:208)
      at org.apache.tomcat.websocket.server.WsFilter.doFilt er(WsFilter.java:52)
      at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:241)
      at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:208)
      at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:220)
      at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:122)
      at org.apache.catalina.authenticator.AuthenticatorBas e.invoke(AuthenticatorBase.java:501)
      at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:171)
      at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:103)
      at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:950)
      at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:116)
      at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:408)
      at org.apache.coyote.http11.AbstractHttp11Processor.p rocess(AbstractHttp11Processor.java:1070)
      at org.apache.coyote.AbstractProtocol$AbstractConnect ionHandler.process(AbstractProtocol.java:611)
      at org.apache.tomcat.util.net.JIoEndpoint$SocketProce ssor.run(JIoEndpoint.java:316)
      at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
      at org.apache.tomcat.util.threads.TaskThread$Wrapping Runnable.run(TaskThread.java:61)
      at java.lang.Thread.run(Unknown Source)
      Caused by: org.apache.ibatis.builder.BuilderException: Error creating document instance. Cause: java.net.ConnectException: Connection timed out: connect
      at org.apache.ibatis.parsing.XPathParser.createDocume nt(XPathParser.java:136)
      at org.apache.ibatis.parsing.XPathParser.<init>(XPath Parser.java:32)
      at org.apache.ibatis.builder.xml.XMLConfigBuilder.<in it>(XMLConfigBuilder.java:45)
      at org.activiti.engine.impl.cfg.ProcessEngineConfigur ationImpl.initMybatisConfiguration(ProcessEngineCo nfigurationImpl.java:714)
      at org.activiti.engine.impl.cfg.ProcessEngineConfigur ationImpl.initSqlSessionFactory(ProcessEngineConfi gurationImpl.java:702)
      ... 30 more
      Caused by: java.net.ConnectException: Connection timed out: connect
      at java.net.DualStackPlainSocketImpl.connect0(Native Method)
      at java.net.DualStackPlainSocketImpl.socketConnect(Un known Source)
      at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
      at java.net.AbstractPlainSocketImpl.connectToAddress( Unknown Source)
      at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
      at java.net.PlainSocketImpl.connect(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at sun.net.NetworkClient.doConnect(Unknown Source)
      at sun.net.www.http.HttpClient.openServer(Unknown Source)
      at sun.net.www.http.HttpClient.openServer(Unknown Source)
      at sun.net.www.http.HttpClient.<init>(Unknown Source)
      at sun.net.www.http.HttpClient.New(Unknown Source)
      at sun.net.www.http.HttpClient.New(Unknown Source)
      at sun.net.http://www.protocol.http.HttpURLConn...Client(Unknown Source)
      at sun.net.http://www.protocol.http.HttpURLConn...onnect(Unknown Source)
      at sun.net.http://www.protocol.http.HttpURLConn...onnect(Unknown Source)
      at sun.net.http://www.protocol.http.HttpURLConn...Stream(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.setupCurrentEntity(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.startEntity(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLEntityM anager.startDTDEntity(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDTDScan nerImpl.setInputSource(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumen tScannerImpl$DTDDriver.dispatch(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumen tScannerImpl$DTDDriver.next(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumen tScannerImpl$PrologDriver.next(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumen tScannerImpl.next(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumen tFragmentScannerImpl.scanDocument(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Co nfiguration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Co nfiguration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XMLPars er.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.DOMPars er.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.jaxp.DocumentBu ilderImpl.parse(Unknown Source)
      at org.apache.ibatis.parsing.XPathParser.createDocume nt(XPathParser.java:134)
      ... 34 more

      Nov 17, 2014 10:40:02 AM org.apache.catalina.core.StandardWrapperValve invoke
      SCHWERWIEGEND: Servlet.service() for servlet [com.example.xyhg.XyhgUI$Servlet] in context with path [/Xyhg] threw exception [com.vaadin.server.ServiceException: org.activiti.engine.ActivitiException: Error while building ibatis SqlSessionFactory: Error creating document instance. Cause: java.net.ConnectException: Connection timed out: connect] with root cause
      Selbstverständlich habe ich auch die mysql-Driver-jar in das lib verzeichnis des Tomcat hineinkopiert. Ich dachte, dass ich doch lieber mal hier frage

      Comment


      • #18
        jdbc.url=jdbc:mysql://127.0.0.1:3306/
        DB_CLOSE_DELAY=1000
        Es fehlt der DB Name und nimm endlich das unsiinge DB_CLose... weg
        Christian

        Comment


        • #19
          Auf diese Weise...

          Code:
          ProcessEngineConfiguration pec = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration()
          				  .setDatabaseSchemaUpdate(ProcessEngineConfiguration.DB_SCHEMA_UPDATE_FALSE)
          				  .setJdbcUrl("jdbc:mysql://127.0.0.1:3306/")
          				  .setJobExecutorActivate(true);
          		ProcessEngine processEngine = pec.buildProcessEngine();
          ...will er aber auch nicht, d. h. der StackTrace kmmt nach wie vor.

          Comment


          • #20
            Es fehlt immer noch der DB-Name!
            jdbc:mysql://localhost:3306/DEIN_DB_NAME
            Christian

            Comment


            • #21
              Okay, sorry, das habe ich jetzt. Es geht aber trotzdem nicht, ich habe meinen MySQL-Server angeworfen, und eine Datenbank activiti ist vorhanden, ich habe aber keine Ahnung, wie ich die Datenbank konfugurieren soll, bzw. ob. Denn wenn ich jetzt use activiti mache und dann show tables eingebe, dann gibt es noch keine Tabellen in der Datenbank, die Datenbank isi quasi Jungfrau.

              db=mysql
              jdbc.driver=com.mysql.jdbc.Driver
              jdbc.url=jdbc:mysql://127.0.0.1:3306/activiti
              DB_CLOSE_DELAY=1000
              jdbc.username=root
              jdbc.password=topsecret

              Comment


              • #22
                DB_CLOSE_DELAY=1000 nimm das raus!!
                Dann musst du Tabellen und deren Spalten anlegen
                Christian

                Comment


                • #23
                  Im Userguide steht:

                  Add the activiti-engine jars to your classpath >> habe ich

                  Add a suitable database driver >> habe ich

                  Add an Activiti configuration file (activiti.cfg.xml) to your classpath, pointing to your database (see database configuration section) >>habe ich, siehe weiter unten

                  Execute the main method of the DbSchemaCreate class >> habe ich, siehe unten
                  Code:
                  /////
                  		ProcessEngineConfiguration pec = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration()
                  				  .setDatabaseSchemaUpdate(ProcessEngineConfiguration.DB_SCHEMA_UPDATE_FALSE)
                  				  .setJdbcUrl("jdbc:mysql://127.0.0.1:3306/activiti")
                  				  .setJobExecutorActivate(true);
                  			
                  		ProcessEngine processEngine = pec.buildProcessEngine();
                           ///Das bis hierhin ist doch ide main-Methode von DBSchemacreate siehe: http://svn.codehaus.org/activiti/activiti/tags/activiti-5.9/modules/activiti-engine/src/main/java/org/activiti/engine/impl/db/DbSchemaCreate.java
                  	    /////
                  Und meine activiti.cfg.xml sieht so aus:

                  Code:
                  <beans xmlns="http://www.springframework.org/schema/beans" 
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                         xsi:schemaLocation="http://www.springframework.org/schema/beans   http://www.springframework.org/schema/beans/spring-beans.xsd">
                  
                    <bean id="processEngineConfiguration" class="org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration">
                    
                      <property name="jdbcUrl" value="jdbc:mysql://127.0.0.1:3306/activiti" />
                      <property name="jdbcDriver" value="org.h2.Driver" />
                      <property name="jdbcUsername" value="root" />
                      <property name="jdbcPassword" value="" />
                      
                      <property name="databaseSchemaUpdate" value="true" />
                      
                      <property name="jobExecutorActivate" value="false" />
                      
                      <property name="mailServerHost" value="mail.my-corp.com" /> 
                      <property name="mailServerPort" value="5025" />    
                    </bean>
                  
                  </beans>

                  ...naja, aber es geht nicht, dies ist der stacktrace:

                  Code:
                  org.activiti.engine.ActivitiException: Error while building ibatis SqlSessionFactory: Error creating document instance.  Cause: java.net.ConnectException: Connection timed out: connect
                  	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.initSqlSessionFactory(ProcessEngineConfigurationImpl.java:706)
                  	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.init(ProcessEngineConfigurationImpl.java:436)
                  	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:408)
                  	at com.example.xyhg.XyhgUI.init(XyhgUI.java:38)
                  	at com.vaadin.ui.UI.doInit(UI.java:639)
                  	at com.vaadin.server.communication.UIInitHandler.getBrowserDetailsUI(UIInitHandler.java:222)
                  	at com.vaadin.server.communication.UIInitHandler.synchronizedHandleRequest(UIInitHandler.java:74)
                  	at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)
                  	at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1402)
                  	at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:305)
                  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
                  	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
                  	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
                  	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
                  	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
                  	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
                  	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
                  	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
                  	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
                  	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
                  	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
                  	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
                  	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
                  	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
                  	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
                  	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
                  	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
                  	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
                  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                  	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
                  	at java.lang.Thread.run(Unknown Source)
                  Caused by: org.apache.ibatis.builder.BuilderException: Error creating document instance.  Cause: java.net.ConnectException: Connection timed out: connect
                  	at org.apache.ibatis.parsing.XPathParser.createDocument(XPathParser.java:136)
                  	at org.apache.ibatis.parsing.XPathParser.<init>(XPathParser.java:32)
                  	at org.apache.ibatis.builder.xml.XMLConfigBuilder.<init>(XMLConfigBuilder.java:45)
                  	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.initMybatisConfiguration(ProcessEngineConfigurationImpl.java:714)
                  	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.initSqlSessionFactory(ProcessEngineConfigurationImpl.java:702)
                  	... 30 more
                  Caused by: java.net.ConnectException: Connection timed out: connect
                  	at java.net.DualStackPlainSocketImpl.connect0(Native Method)
                  	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
                  	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
                  	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
                  	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
                  	at java.net.PlainSocketImpl.connect(Unknown Source)
                  	at java.net.SocksSocketImpl.connect(Unknown Source)
                  	at java.net.Socket.connect(Unknown Source)
                  	at java.net.Socket.connect(Unknown Source)
                  	at sun.net.NetworkClient.doConnect(Unknown Source)
                  	at sun.net.www.http.HttpClient.openServer(Unknown Source)
                  	at sun.net.www.http.HttpClient.openServer(Unknown Source)
                  	at sun.net.www.http.HttpClient.<init>(Unknown Source)
                  	at sun.net.www.http.HttpClient.New(Unknown Source)
                  	at sun.net.www.http.HttpClient.New(Unknown Source)
                  	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
                  	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
                  	at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
                  	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
                  	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
                  	at org.apache.ibatis.parsing.XPathParser.createDocument(XPathParser.java:134)
                  	... 34 more

                  Comment


                  • #24
                    MySQL arbeitet nur mit dem MySQL-Driver

                    <property name="jdbcUrl" value="jdbc:mysql://127.0.0.1:3306/activiti" />

                    <property name="jdbcDriver" value="org.h2.Driver" />
                    Zuletzt editiert von Christian Marquardt; 17.11.2014, 20:44.
                    Christian

                    Comment


                    • #25
                      *autsch* entschuldige. Ich habe jetzt die Verbesserung vorgenommen, aber eine Veränderung hat sich nicht ergeben:

                      Ich habe nach wie vor den Stack, aber nur dann wenn ich an der processEngine die Methode buildProcessEngine() aufrufe, wenn ich dies nicht tue, dann wird eine ProcessEngineConfiguration erzeugt, die nicht null ist.

                      Die MySQL-DB läuft, die Änderung, welche ich vorgenommen habe, lautet nun wie folgt:

                      Code:
                        <property name="jdbcUrl" value="jdbc:mysql://127.0.0.1:3306/activiti" />
                          <property name="jdbcDriver" value="com.mysql.jdbc.Driver" />
                      Ich habe die Treiber-jar überprüft, diese ist ebenfalls vorhanden. Ich dachte, dass es eventuell daran liegen könnte, dass das JDBC-Passwort noch gesetzt werden muss, also habe ich es auch so versucht ...

                      [/code].setJobExecutorActivate(true)
                      .setJdbcPassword("supergeheim");[/code]

                      Das hat aber auch nichts gebracht.

                      Comment


                      • #26
                        Der User muss auch das Recht an der DB (activiti) haben.
                        Der Stacktrace sollte schon eine andere Ausgabe haben
                        Christian

                        Comment


                        • #27
                          Ich habe mal Folgendes gemacht:

                          Code:
                          GRANT ALL ON activiti.* TO 'root'@'%';
                          GRANT ALL ON activiti TO 'root'@'%';
                          GRANT CREATE ON activiti TO 'root'@'%';
                          FLUSH PRIVILEGES;

                          An diesem hier:

                          Code:
                          	ProcessEngineConfiguration pec = ProcessEngineConfiguration.createStandaloneProcessEngineConfiguration()
                          				  .setDatabaseSchemaUpdate(ProcessEngineConfiguration.DB_SCHEMA_UPDATE_FALSE)
                          				  .setJdbcUrl("jdbc:mysql://127.0.0.1:3306/activiti")
                          				  .setJdbcUsername("root")
                          				  .setJdbcPassword("geheim")
                          				  .setJobExecutorActivate(true);
                          ...kann ich nichts falsches erkennen, ich habe dieselben Daten in der activiti.cfg.xml und ich habe zur Probe sogar einmal die activiti.cfg.xml entfernt. Dennoch funktioniert es nicht, der stacktrace lautet:
                          Der Stacktrace lautet:

                          Code:
                          SCHWERWIEGEND: 
                          org.activiti.engine.ActivitiException: Error while building ibatis SqlSessionFactory: Error creating document instance.  Cause: java.net.ConnectException: Connection timed out: connect
                          	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.initSqlSessionFactory(ProcessEngineConfigurationImpl.java:706)
                          	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.init(ProcessEngineConfigurationImpl.java:436)
                          	at org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:408)
                          	at com.example.xyhg.XyhgUI.init(XyhgUI.java:43)
                          	at com.vaadin.ui.UI.doInit(UI.java:639)
                          	at com.vaadin.server.communication.UIInitHandler.getBrowserDetailsUI(UIInitHandler.java:222)
                          	at com.vaadin.server.communication.UIInitHandler.synchronizedHandleRequest(UIInitHandler.java:74)
                          	at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)
                          	at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1402)
                          	at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:305)
                          	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
                          	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
                          	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
                          	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
                          	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
                          	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
                          	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
                          	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
                          	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
                          	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
                          	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
                          	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
                          	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
                          	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
                          	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
                          	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
                          	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
                          	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
                          	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                          	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
                          	at java.lang.Thread.run(Unknown Source)

                          Comment


                          • #28
                            Jedenfalls bedeutet der Fehler, dass die DB nicht erreicht werden kann und mit einem Timeout abgebrochen wird. Mögliche Ursache könnte sein, dass der Server nicht läuft, falscher Port, Rechte nicht stimmen. Teste das mit der MySQL GUI http://dev.mysql.com/downloads/workbench/
                            Christian

                            Comment


                            • #29
                              Naja, ich habe MySQL auf einem XAMPP-Controllpanel aus gestartet, dort wird der Port ja angezeigt, udn der sitmmt. Überdies habe ich aus der Kommandozeile heraus alle Rechte zugewiesen, daran kann es eigentlich auch nicht liegen. Der Server läuft (wird ja auch angezeigt).

                              Comment


                              • #30
                                Was willst du mit XAMPP? Apache brauchst du nicht, PHP nicht. Warum all das überflüssige installieren.
                                Jedenfalls lässt sich aus der Ferne nix anderes sagen. Schreibfehler, Groß-/Kleinschreibung?
                                Christian

                                Comment

                                Working...
                                X