Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.
TUTORIALVaadin lets you build secure, UX-first PWAs entirely in Java.
Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Where to include a web components css file when integrating a third party w by Martin Vyšný, 1 week ago
Bug or not with Vaadin?
Event: 87.495 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/ui/UIState$PushConfigurationStateBeanInfo> (0x6bcdda60) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp,
Event: 87.500 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/ui/UIState$PushConfigurationStateCustomizer> (0x6bcfe4a0) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp
Event: 87.508 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/ui/UIState$LocaleDataBeanInfo> (0x6bd21200) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 87.512 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/ui/UIState$LocaleDataCustomizer> (0x6bd3e018) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 87.520 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/button/ButtonStateBeanInfo> (0x6bd5d310) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 87.524 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/button/ButtonStateCustomizer> (0x6bd79568) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 87.531 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/label/LabelStateBeanInfo> (0x6bd98f58) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 87.535 Thread 0x00c34000 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/ui/label/LabelStateCustomizer> (0x6bdb4330) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 98.843 Thread 0x6aeb6800 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/MouseEventDetailsBeanInfo> (0x6bbd1008) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]
Event: 98.852 Thread 0x6aeb6800 Exception <a 'java/lang/ClassNotFoundException': com/vaadin/shared/MouseEventDetailsCustomizer> (0x6bbebe88) thrown at [/HUDSON3/workspace/8-2-build-glinux-arm-vfp-hflt/jdk8u72/5059.nc/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210]( This is running on a Raspberry PI with Tomcat 8)
I am geting the above core dump only thing I see is Vaadin So I opened a TRAC ticket and got this:
Comment (by Artur Signell):
Probably a problem in your setup as classes like ButtonStateCustomizer are
not included in the framework.
You could try the forums http://vaadin.com/forum or if you need immediate
help, Vaadin support http://vaadin.com/support
Based on the given information, it does not look like a bug in the
framework .
So is a bug or how do I fix it?
Pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>YT-100_ATU_Controller</groupId>
<artifactId>YT-100_ATU_Controller</artifactId>
<packaging>war</packaging>
<version>0.0.1-SNAPSHOT</version>
<name>YT-100_ATU_Controller</name>
<!-- properties -->
<properties>
<vaadin.version>7.5.8</vaadin.version>
<productionMode>false</productionMode>
<vaadin.theme>theme01</vaadin.theme>
<vaadin.plugin.version>${vaadin.version}</vaadin.plugin.version>
<jetty.plugin.version>9.3.1-SNAPSHOT</jetty.plugin.version>
<project.source.version>1.8</project.source.version>
<project.target.version>1.8</project.target.version>
<project.encoding>UTF-8</project.encoding>
<log4j2.version>2.4.1</log4j2.version>
<pi4j.version>1.1-SNAPSHOT</pi4j.version>
<loginform.version>0.5.2</loginform.version>
<javax.servlet.version>3.1.0</javax.servlet.version>
<maven-compiler-plugin.version>3.3</maven-compiler-plugin.version>
<maven-resources-plugin.version>2.7</maven-resources-plugin.version>
<maven-war-plugin.version>2.6</maven-war-plugin.version>
<maven-source-plugin.version>2.4</maven-source-plugin.version>
<maven-clean-plugin.version>2.6.1</maven-clean-plugin.version>
<maven-antrun-plugin.version>1.8</maven-antrun-plugin.version>
<jsch.version>0.1.53</jsch.version>
<ant-jsch.version>1.6.5</ant-jsch.version>
<docs-maven-plugin.version>1</docs-maven-plugin.version>
<lifecycle-mapping.version>1.0</lifecycle-mapping.version>
<exec-maven-plugin.version>1.4</exec-maven-plugin.version>
</properties>
<!-- end properties -->
<!-- repositories -->
<repositories>
<repository>
<id>vaadin-addons</id>
<url>http://maven.vaadin.com/vaadin-addons</url>
</repository>
<repository>
<id>vaadin-snapshots</id>
<url>https://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>oss-snapshots-repo</id>
<name>Sonatype OSS Maven Repository</name>
<url>https://oss.sonatype.org/content/groups/public</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
</repository>
</repositories>
<!-- end repositories -->
<!-- dependencyManagement -->
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-archetype-widget</artifactId>
<version>${vaadin.version}</version>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-archetype-application</artifactId>
<version>${vaadin.version}</version>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-bom</artifactId>
<version>${vaadin.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<!-- end dependencyManagement -->
<!-- dependenciest -->
<dependencies>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>${javax.servlet.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-server</artifactId>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-push</artifactId>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-client</artifactId>
<!--
<scope>provided</scope>
-->
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-client-compiler</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-themes</artifactId>
</dependency>
<dependency>
<groupId>com.pi4j</groupId>
<artifactId>pi4j-core</artifactId>
<version>${pi4j.version}</version>
</dependency>
<dependency>
<groupId>org.vaadin.addons</groupId>
<artifactId>loginform</artifactId>
<version>${loginform.version}</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>${log4j2.version}</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>${log4j2.version}</version>
</dependency>
</dependencies>
<!-- dependenciest -->
<!-- build -->
<build>
<!-- plugins -->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven-compiler-plugin.version}</version>
<configuration>
<encoding>${project.encoding}</encoding>
<source>${project.source.version}</source>
<target>${project.target.version}</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>${maven-resources-plugin.version}</version>
<configuration>
<encoding>${project.encoding}</encoding>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>${maven-war-plugin.version}</version>
<configuration>
<failOnMissingWebXml>false</failOnMissingWebXml>
<!-- Exclude some unnecessary files generated by the GWT compiler. -->
<packagingExcludes>WEB-INF/classes/VAADIN/gwt-unitCache/**,
WEB-INF/classes/VAADIN/widgetsets/WEB-INF/**</packagingExcludes>
<warName>${project.artifactId}</warName>
</configuration>
</plugin>
<plugin>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-maven-plugin</artifactId>
<version>${vaadin.plugin.version}</version>
<configuration>
<extraJvmArgs>-Xmx512M -Xss1024k</extraJvmArgs>
<webappDirectory>${basedir}/target/classes/VAADIN/widgetsets</webappDirectory>
<draftCompile>false</draftCompile>
<compileReport>false</compileReport>
<style>OBF</style>
<strict>true</strict>
</configuration>
<executions>
<execution>
<goals>
<goal>clean</goal>
<goal>resources</goal>
<goal>update-theme</goal>
<goal>update-widgetset</goal>
<goal>compile-theme</goal>
<goal>compile</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>${maven-source-plugin.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>${maven-clean-plugin.version}</version>
<!-- Clean up also any pre-compiled themes -->
<configuration>
<filesets>
<fileset>
<directory>WebContent/VAADIN/themes</directory>
<includes>
<include>**/styles.css</include>
<include>**/styles.scss.cache</include>
</includes>
</fileset>
</filesets>
</configuration>
</plugin>
<!-- The Jetty plugin allows us to easily test the development build by
running jetty:run on the command line. -->
<plugin>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>${jetty.plugin.version}</version>
<configuration>
<scanIntervalSeconds>2</scanIntervalSeconds>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>${maven-antrun-plugin.version}</version>
<executions>
<execution>
<id>clean</id>
<phase>prepare-package</phase>
<configuration>
<target>
<!-- This target increments the build number -->
<tstamp>
<format property="maven.release.date" pattern="MM-dd-yyyy" />
<format property="maven.release.time" pattern="hh.mm" />
</tstamp>
<propertyfile file="${basedir}\version.properties"
comment="Version Properties">
<!-- Increment the build number -->
<entry key="release.build" default="1" type="int"
operation="+" />
<entry key="release.date" value="${maven.release.date}" />
<entry key="release.time" value="${maven.release.time}" />
</propertyfile>
<!-- Load the updated version properties file info -->
<property file="${basedir}/version.properties" />
<property name="release.date" value="${maven.release.date}" />
<property name="release.time" value="${maven.release.time}" />
<property name="build_number"
value="${release.type}${release.major}.${release.minor}.${release.build}" />
<property name="build_time"
value="${maven.release.date}${maven.release.time}" />
<echo>Build Number: ${build_number}</echo>
<echo>Build Time: ${date}</echo>
<copy file="version.properties" todir="${basedir}/src/main/webapp/WEB-INF/conf/" />
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
<execution>
<id>compile</id>
<phase>package</phase>
<configuration>
<target>
<scp file="${basedir}/target/${project.artifactId}.war"
todir="${ftp-userid}@${ftp-server}:${deployment.dir}/${project.artifactId}.war"
trust="true" port="${ftp-port}" password="${ftp-password}" />
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.jcraft</groupId>
<artifactId>jsch</artifactId>
<version>${jsch.version}</version>
</dependency>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-jsch</artifactId>
<version>${ant-jsch.version}</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<artifactId>docs-maven-plugin</artifactId>
<groupId>org.neo4j.build.plugins</groupId>
<version>${docs-maven-plugin.version}</version>
<!-- the directories below will be added by default, using the config
element will _replace_ the defaults. -->
<configuration>
<sourceDirectories>
<sourceDirectory>${basedir}/src/docs</sourceDirectory>
<sourceDirectory>${project.build.directory}/docs</sourceDirectory>
</sourceDirectories>
</configuration>
</plugin>
</plugins>
<!-- plugins -->
<!-- pluginManagement -->
<pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse m2e settings
only. It has no influence on the Maven build itself. -->
<!-- TODO Remove when http://dev.vaadin.com/ticket/14924 is resolved -->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>${lifecycle-mapping.version}</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>com.vaadin</groupId>
<artifactId>
vaadin-maven-plugin
</artifactId>
<versionRange>[${vaadin.version},)</versionRange>
<goals>
<goal>clean</goal>
<goal>resources</goal>
<goal>update-theme</goal>
<goal>update-widgetset</goal>
<goal>compile-theme</goal>
<goal>compile</goal>
</goals>
</pluginExecutionFilter>
<action>
<ignore></ignore>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>${exec-maven-plugin.version}</version>
<configuration>
<mainClass>com.vaadin.sass.SassCompiler</mainClass>
<arguments>
<argument>
${project.basedir}/src/main/webapp/VAADIN/themes/mytheme/styles.scss
</argument>
<argument>${project.build.directory}/styles.css</argument>
</arguments>
</configuration>
<executions>
<execution>
<goals>
<goal>java</goal>
</goals>
<phase>process-resources</phase>
</execution>
</executions>
</plugin>
</plugins>
</pluginManagement>
<!-- end pluginManagement -->
</build>
<!-- end build -->
</project>code:
package com.na7kr.Interrupt;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import com.na7kr.GPIOController.GPIOController;
import com.na7kr.rpi_gpio_controller.Rpi_gpio_controllerApplicationUI;
import com.pi4j.wiringpi.Gpio;
import com.pi4j.wiringpi.GpioInterruptCallback;
public class Interrupt {
Rpi_gpio_controllerApplicationUI mApplication = new Rpi_gpio_controllerApplicationUI(); // NO_UCD
// (use
// private)
private static final Logger LOG = LogManager.getLogger(Rpi_gpio_controllerApplicationUI.class);
// ***************************************
public synchronized void GetInput1(int trigerpin, int outputpin) throws InterruptedException {
LOG.debug("GPIO interrupt setup");
// setup wiringPi
if (Gpio.wiringPiSetup() == -1) {
LOG.error("GPIO SETUP FAILED");
return;
}
Gpio.pinMode(trigerpin, Gpio.INPUT);
Gpio.pullUpDnControl(trigerpin, Gpio.PUD_UP);
Gpio.wiringPiISR(trigerpin, Gpio.INT_EDGE_FALLING, new GpioInterruptCallback() {
@Override
public void callback(int pin) {
System.out.println(" ==>> GPIO PIN " + pin + " - INTERRUPT DETECTED");
LOG.debug("1");
GPIOController.INSTANCE.mGPIOPins[outputpin].toggle();
mApplication.refreshGPIOPinState();
LOG.debug("2");
}
});
}
// ***************************************
}For full code https://github.com/NA7KR/YT-100_ATU_Controller.git
Last updated on
The first thing I notice is you mention running on Tomcat, but your pom references Jetty. Is that on purpose?
The BeanInfo and Customizer stuff is not normal behavior for Vaadin, something is causing that to happen. Have you tried running this application on a desktop rather than a RPI, and comparing the behavior?
You can also try excluding dependencies, checking for the ClassNotFoundException, and then re-introduce them individually to find the culrpit.
Last updated on
You cannot reply to this thread.