search

OpenIotOrg / openiot

The Open Source Project for the Internet of Things
457 stars 190 forks source link

Cannot Log in and/or Register #82

Open keithsptr opened 9 years ago

keithsptr commented 9 years ago

Hi all,

I have completely set up the new code to jboss etc.

When I go to /scheduler.core/rest/services or sdum.core/rest/services the console displayes the methods available but when I go to ui.requestDefinition/pages/login.xhtml and try to log in or Register it gives me error either: account with the supplied email already exists or Invalid Credentials.

No error is displayed on the Console.

hylkevds commented 9 years ago

can you post your openiot.properties config file? Usually this means the connection to virtuoso fails, so make sure you check if the config file is pointing to the correct one (localhost:8890 usually)

keithsptr commented 9 years ago

Yep virtuoso is there: http://92.251.103.22:8890/sparql.

Config Below:

Request Definition

ide.core.navigation.requestDefinition.title=Request Definition ide.core.navigation.requestDefinition.url=http://192.168.0.26:1098/ui.requestDefinition/pages/applicationDesign.xhtml ide.core.navigation.requestDefinition.monitoring=true

Request Presentation

ide.core.navigation.requestPresentation.title=Request Presentation ide.core.navigation.requestPresentation.url=http://192.168.0.26:1098/ui.requestPresentation/pages/requestPresentation.xhtml ide.core.navigation.requestPresentation.monitoring=true

Sensor Schema Editor

ide.core.navigation.sensorSchemaEditor.title=Sensor Schema Editor ide.core.navigation.sensorSchemaEditor.url=http://192.168.0.26:1098/sensorschema/index.xhtml ide.core.navigation.sensorSchemaEditor.monitoring=true

Scheduler Properties

scheduler.core.lsm.openiotMetaGraph=http://lsm.acrosslimits.com/OpenIoT/sensormeta# scheduler.core.lsm.openiotDataGraph=http://lsm.acrosslimits.com/OpenIoT/sensordata# scheduler.core.lsm.openiotFunctionalGraph=http://lsm.acrosslimits.com/OpenIoT/functionaldata# scheduler.core.lsm.access.username=openiot_guest scheduler.core.lsm.access.password=openiot scheduler.core.lsm.sparql.endpoint=http://192.168.0.26:8890/sparql scheduler.core.lsm.remote.server=http://192.168.0.26:1098/lsm-light.server/

Service Delivery & Utility Manager (SD&UM) Properties

sdum.core.lsm.openiotFunctionalGraph=http://lsm.acrosslimits.com/OpenIoT/functionaldata# sdum.core.lsm.sparql.endpoint=http://192.168.0.26:8890/sparql sdum.core.lsm.remote.server=http://192.168.0.26:1098/lsm-light.server/

Request Definition

Request Presentation

LSM-LIGHT Properties

lsm-light.server.connection.driver_class=virtuoso.jdbc4.Driver lsm-light.server.connection.url=jdbc:virtuoso://192.168.0.26:1111/log_enable=2

lsm-light.server.connection.username=dba lsm-light.server.connection.password=dba lsm-light.server.minConnection=10 lsm-light.server.maxConnection=15 lsm-light.server.acquireRetryAttempts=5

for local virtuoso instance

lsm-light.server.localMetaGraph = http://lsm.acrosslimits.com/OpenIoT/sensormeta# lsm-light.server.localDataGraph = http://lsm.acrosslimits.com/OpenIoT/sensordata#

QoS Manager

qos.name=QualityOfService qos.brokerIP=192.168.0.26 qos.brokerPort=10000

qos.gsnAddress=192.168.0.26:22001 qos.wrapperPort=30000

qos.numberOfSensors = 3 qos.highBatteryLevel = 70 qos.lowBatteryLevel = 30

qos.sensorParameters = Temperature,Humidity,Pressure,NO2,SO2,CO,BatteryS,BatteryMP,Area,Timestamp,SensorID,Latitude,Longitude qos.sensorTypes = double,double,double,double,double,double,double,double,string,bigint,string,double,double qos.lsmProperty = http://lsm.deri.ie/OpenIoT/Temperature,http://lsm.deri.ie/OpenIoT/Humidity,http://lsm.deri.ie/OpenIoT/Pressure,http://lsm.deri.ie/OpenIoT/NO2,http://lsm.deri.ie/OpenIoT/SO2,http://lsm.deri.ie/OpenIoT/CO,http://lsm.deri.ie/OpenIoT/BatterySensor,http://lsm.deri.ie/OpenIoT/BatteryMobilePhone,http://lsm.deri.ie/OpenIoT/Area,http://lsm.deri.ie/OpenIoT/Timestamp,http://lsm.deri.ie/OpenIoT/SensorID,http://lsm.deri.ie/OpenIoT/Latitude,http://lsm.deri.ie/OpenIoT/Longitude qos.lsmUnit = C,Percent,hPa,ug/m3,ug/m3,mg/m3,Percent,Percent,Unit,Unit,Unit,Unit,Unit qos.testing = true qos.logWriting = true

hylkevds commented 9 years ago

One thing I do notice is your virtuoso connection url: jdbc:virtuoso://192.168.0.26:1111/log_enable=2 That indicates you run virtuoso on a separate machine from jboss? You'll have to make sure virtuoso accepts connections from other machines. Though I think LSM gives an error when starting when it can't make a connection to virtuoso.

keithsptr commented 9 years ago

No it is on the same machine. same ip different port

hylkevds commented 9 years ago

Then you could try: jdbc:virtuoso://localhost:1111/log_enable=2 Though if lsm didn't give an error it should be fine. Can you check the jboss log file, right after you've tried to log in? That should contain some relevant message.

keithsptr commented 9 years ago

I did that just now and did not work either. and no log file under the log folder

hylkevds commented 9 years ago

No log file? Is the output going to the console you started jboss on?

keithsptr commented 9 years ago

Yes it is

hylkevds commented 9 years ago

So, look there for interesting messages right when you get the login error.

keithsptr commented 9 years ago

There is nothing.. not even a single error like not even going to jboss

keithsptr commented 9 years ago

Anyone please? I just installed a new version of ubuntu on a different pc. installed jboss. install virtuoso deployed the code. No Errors!!!

nmqhoan commented 9 years ago

can you please copy and paste all the output from your console?

On 20 Aug 2014, at 14:38, keithsptr notifications@github.com wrote:

Anyone please?

— Reply to this email directly or view it on GitHub.

keithsptr commented 9 years ago

Console output:

JBoss Bootstrap Environment

JBOSS_HOME: /usr/local/share/jboss

JAVA: /usr/lib/jvm/java-7-oracle/bin/java

JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

15:28:45,730 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 15:28:47,583 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 15:28:47,739 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 15:28:53,440 INFO [org.xnio] XNIO Version 3.0.3.GA 15:28:53,435 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) 15:28:53,518 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA 15:28:53,587 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA 15:28:53,748 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers 15:28:53,818 INFO [org.jboss.as.naming](ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem 15:28:53,823 INFO [org.jboss.as.osgi](ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem 15:28:53,840 INFO [org.jboss.as.security](ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem 15:28:53,912 INFO [org.jboss.as.clustering.infinispan](ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem. 15:28:53,917 INFO [org.jboss.as.webservices](ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension 15:28:54,018 INFO [org.jboss.as.security](MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final 15:28:55,554 INFO [org.jboss.as.connector.subsystems.datasources](ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 15:28:55,747 INFO [org.jboss.as.connector](MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final) 15:28:56,668 INFO [org.jboss.ws.common.management.AbstractServerConfig](MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA 15:28:56,694 INFO [org.jboss.as.naming](MSC service thread 1-1) JBAS011802: Starting Naming Service 15:28:57,376 INFO [org.jboss.as.mail.extension](MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default] 15:28:57,590 INFO [org.apache.coyote.http11.Http11Protocol](MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--192.168.0.108-8080 15:28:58,054 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "ui.requestDefinition.war" 15:28:58,091 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "ide.core.war" 15:28:58,103 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "sensorschema.war" 15:28:58,105 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "lsm-light.server.war" 15:28:58,112 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "ui.requestPresentation.war" 15:28:58,136 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "scheduler.core.war" 15:28:58,150 INFO [org.jboss.as.server.deployment](MSC service thread 1-1) JBAS015876: Starting deployment of "sdum.core.war" 15:28:58,167 INFO [org.jboss.as.server.deployment.scanner](MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/share/jboss/standalone/deployments 15:29:02,585 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jaxb-api.jar in "/content/ui.requestDefinition.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:02,587 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry activation.jar in "/content/ui.requestDefinition.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:02,607 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jsr173_1.0_api.jar in "/content/ui.requestDefinition.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:02,615 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jaxb1-impl.jar in "/content/ui.requestDefinition.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:15,805 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb-api.jar in "/content/ui.requestPresentation.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:15,807 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry activation.jar in "/content/ui.requestPresentation.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:15,816 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/content/ui.requestPresentation.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:15,826 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb1-impl.jar in "/content/ui.requestPresentation.war/WEB-INF/lib/jaxb-impl-2.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:22,460 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb-api.jar in "/content/scheduler.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:22,462 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry activation.jar in "/content/scheduler.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:22,470 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/content/scheduler.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:22,482 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb1-impl.jar in "/content/scheduler.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:26,826 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb-api.jar in "/content/sdum.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:26,836 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry activation.jar in "/content/sdum.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:26,837 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/content/sdum.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:26,839 WARN [org.jboss.as.server.deployment](MSC service thread 1-1) Class Path entry jaxb1-impl.jar in "/content/sdum.core.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:26,906 INFO [org.jboss.as.remoting](MSC service thread 1-1) JBAS017100: Listening on /192.168.0.108:9999 15:29:27,879 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry xml-apis.jar in "/content/lsm-light.server.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,029 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jaxb-api.jar in "/content/lsm-light.server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,039 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry activation.jar in "/content/lsm-light.server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,076 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jsr173_1.0_api.jar in "/content/lsm-light.server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,078 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry jaxb1-impl.jar in "/content/lsm-light.server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,080 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry xercesImpl.jar in "/content/lsm-light.server.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,092 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry xml-apis.jar in "/content/lsm-light.server.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:28,112 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) Class Path entry serializer.jar in "/content/lsm-light.server.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. 15:29:29,537 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider' 15:29:29,539 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider' 15:29:29,824 INFO [org.jboss.as.remoting](MSC service thread 1-2) JBAS017100: Listening on /192.168.0.108:4447 15:29:30,148 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) JBAS015893: Encountered invalid class name 'http://java.sun.com/jaxp/xpath/dom: net.sf.saxon.xpath.XPathFactoryImpl' for service type 'javax.xml.xpath.XPathFactory' 15:29:30,150 WARN [org.jboss.as.server.deployment](MSC service thread 1-2) JBAS015893: Encountered invalid class name 'http://saxon.sf.net/jaxp/xpath/om: net.sf.saxon.xpath.XPathFactoryImpl' for service type 'javax.xml.xpath.XPathFactory' 15:29:30,968 INFO [org.jboss.as.jpa](MSC service thread 1-1) JBAS011401: Read persistence.xml for primary 15:29:34,913 INFO [org.jboss.as.connector.subsystems.datasources](MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 15:29:35,130 INFO [org.jboss.weld.deployer](MSC service thread 1-2) JBAS016002: Processing weld deployment ide.core.war 15:29:39,805 INFO [org.jboss.weld.deployer](MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: ide.core.war 15:29:39,972 INFO [org.jboss.weld.Version](MSC service thread 1-1) WELD-000900 1.1.5 (AS71) 15:29:42,481 INFO [stdout](MSC service thread 1-2) 15:29:42.470 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody listener init started 15:29:42,498 INFO [stdout](MSC service thread 1-1) 15:29:42.481 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody listener init started 15:29:42,600 INFO [stdout](MSC service thread 1-1) 15:29:42.600 [MSC service thread 1-1] DEBUG net.bull.javamelody - datasources found in JNDI: [] 15:29:42,602 INFO [stdout](MSC service thread 1-2) 15:29:42.601 [MSC service thread 1-2] DEBUG net.bull.javamelody - datasources found in JNDI: [] 15:29:42,603 INFO [stdout](MSC service thread 1-2) 15:29:42.603 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody listener init done in 2857 ms 15:29:42,608 INFO [stdout](MSC service thread 1-1) 15:29:42.608 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody listener init done in 2516 ms 15:29:42,766 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-1) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/sdum.core' 15:29:42,767 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-2) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/scheduler.core' 15:29:47,110 INFO [org.hibernate.validator.util.Version](MSC service thread 1-2) Hibernate Validator 4.2.0.Final 15:29:51,528 INFO [stdout](MSC service thread 1-1) 15:29:51.528 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody filter init started 15:29:51,532 INFO [stdout](MSC service thread 1-2) 15:29:51.531 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody filter init started 15:29:51,538 INFO [stdout](MSC service thread 1-1) 15:29:51.538 [MSC service thread 1-1] DEBUG net.bull.javamelody - OS: Linux unknown, amd64/64 15:29:51,542 INFO [stdout](MSC service thread 1-1) 15:29:51.542 [MSC service thread 1-1] DEBUG net.bull.javamelody - Java: Java(TM) SE Runtime Environment, 1.7.0_67-b01 15:29:51,552 INFO [stdout](MSC service thread 1-1) 15:29:51.551 [MSC service thread 1-1] DEBUG net.bull.javamelody - Server: JBoss Web/7.0.13.Final 15:29:51,552 INFO [stdout](MSC service thread 1-1) 15:29:51.552 [MSC service thread 1-1] DEBUG net.bull.javamelody - Webapp context: /sdum.core 15:29:51,553 INFO [stdout](MSC service thread 1-1) 15:29:51.553 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody version: 1.45.0 15:29:51,554 INFO [stdout](MSC service thread 1-1) 15:29:51.554 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody classes loaded from: vfs:/content/sdum.core.war/WEB-INF/lib/javamelody-core-1.45.0.jar 15:29:51,561 INFO [stdout](MSC service thread 1-2) 15:29:51.559 [MSC service thread 1-2] DEBUG net.bull.javamelody - OS: Linux unknown, amd64/64 15:29:51,562 INFO [stdout](MSC service thread 1-2) 15:29:51.562 [MSC service thread 1-2] DEBUG net.bull.javamelody - Java: Java(TM) SE Runtime Environment, 1.7.0_67-b01 15:29:51,564 INFO [stdout](MSC service thread 1-2) 15:29:51.564 [MSC service thread 1-2] DEBUG net.bull.javamelody - Server: JBoss Web/7.0.13.Final 15:29:51,566 INFO [stdout](MSC service thread 1-2) 15:29:51.566 [MSC service thread 1-2] DEBUG net.bull.javamelody - Webapp context: /scheduler.core 15:29:51,567 INFO [stdout](MSC service thread 1-2) 15:29:51.567 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody version: 1.45.0 15:29:51,569 INFO [stdout](MSC service thread 1-1) 15:29:51.569 [MSC service thread 1-1] DEBUG net.bull.javamelody - Host: keith-Extensa-5230@127.0.1.1 15:29:51,571 INFO [stdout](MSC service thread 1-2) 15:29:51.571 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody classes loaded from: vfs:/content/scheduler.core.war/WEB-INF/lib/javamelody-core-1.45.0.jar 15:29:51,573 INFO [stdout](MSC service thread 1-2) 15:29:51.573 [MSC service thread 1-2] DEBUG net.bull.javamelody - Host: keith-Extensa-5230@127.0.1.1 15:29:51,630 INFO [stdout](MSC service thread 1-1) 15:29:51.630 [MSC service thread 1-1] DEBUG net.bull.javamelody - log listeners initialized 15:29:51,634 INFO [stdout](MSC service thread 1-2) 15:29:51.632 [MSC service thread 1-2] DEBUG net.bull.javamelody - log listeners initialized 15:29:51,637 INFO [stdout](MSC service thread 1-2) 15:29:51.637 [MSC service thread 1-2] DEBUG net.bull.javamelody - datasources found in JNDI: [] 15:29:51,638 INFO [stdout](MSC service thread 1-1) 15:29:51.636 [MSC service thread 1-1] DEBUG net.bull.javamelody - datasources found in JNDI: [] 15:29:51,654 INFO [stdout](MSC service thread 1-1) 15:29:51.654 [MSC service thread 1-1] DEBUG net.bull.javamelody - jsf action listener initialized 15:29:51,656 INFO [stdout](MSC service thread 1-1) 15:29:51.656 [MSC service thread 1-1] DEBUG net.bull.javamelody - counters initialized 15:29:51,664 INFO [stdout](MSC service thread 1-2) 15:29:51.662 [MSC service thread 1-2] DEBUG net.bull.javamelody - jsf action listener initialized 15:29:51,667 INFO [stdout](MSC service thread 1-2) 15:29:51.667 [MSC service thread 1-2] DEBUG net.bull.javamelody - counters initialized 15:29:51,719 INFO [stdout](MSC service thread 1-1) 15:29:51.719 [MSC service thread 1-1] DEBUG net.bull.javamelody - counters data read from files in /tmp/javamelody/sdum.core_keith-Extensa-5230 15:29:51,731 INFO [stdout](MSC service thread 1-2) 15:29:51.731 [MSC service thread 1-2] DEBUG net.bull.javamelody - counters data read from files in /tmp/javamelody/scheduler.core_keith-Extensa-5230 15:29:52,207 INFO [stdout](MSC service thread 1-1) 15:29:52.205 [MSC service thread 1-1] DEBUG net.bull.javamelody - collect task scheduled every 60s 15:29:52,225 INFO [stdout](MSC service thread 1-2) 15:29:52.225 [MSC service thread 1-2] DEBUG net.bull.javamelody - collect task scheduled every 60s 15:29:58,770 INFO [stdout](MSC service thread 1-1) 15:29:58.770 [MSC service thread 1-1] DEBUG net.bull.javamelody - first collect of data done 15:29:58,772 INFO [stdout](MSC service thread 1-1) 15:29:58.771 [MSC service thread 1-1] DEBUG net.bull.javamelody - JavaMelody filter init done in 7243 ms 15:29:58,816 INFO [stdout](MSC service thread 1-2) 15:29:58.816 [MSC service thread 1-2] DEBUG net.bull.javamelody - first collect of data done 15:29:58,830 INFO [stdout](MSC service thread 1-2) 15:29:58.829 [MSC service thread 1-2] DEBUG net.bull.javamelody - JavaMelody filter init done in 7292 ms 15:29:58,919 INFO [org.jboss.web](MSC service thread 1-2) JBAS018210: Registering web context: /scheduler.core 15:29:58,923 INFO [org.jboss.web](MSC service thread 1-1) JBAS018210: Registering web context: /sdum.core 15:29:59,117 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-2) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/ui.requestPresentation' 15:29:59,138 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-1) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/ui.requestDefinition' 15:30:02,029 INFO [org.primefaces.webapp.PostConstructApplicationEventListener](MSC service thread 1-1) Running on PrimeFaces 3.5 15:30:02,101 INFO [org.primefaces.webapp.PostConstructApplicationEventListener](MSC service thread 1-2) Running on PrimeFaces 3.5 15:30:02,150 INFO [org.primefaces.extensions.application.PostConstructApplicationEventListener](MSC service thread 1-1) Running on PrimeFaces Extensions 0.6.3 15:30:02,151 INFO [org.primefaces.extensions.application.PostConstructApplicationEventListener](MSC service thread 1-2) Running on PrimeFaces Extensions 0.6.3 15:30:02,231 INFO [org.openiot.ui.request.commons.logging.LoggerService](MSC service thread 1-1) OpenIoT:RequestDefinition: [INFO] Setting log level to 'FINE' 15:30:02,236 INFO [org.openiot.ui.request.commons.logging.LoggerService](MSC service thread 1-1) OpenIoT:RequestDefinition: [INFO] Initializing 15:30:02,235 INFO [org.openiot.ui.request.commons.logging.LoggerService](MSC service thread 1-2) OpenIoT:RequestPresentation: [INFO] Setting log level to 'FINE' 15:30:02,238 INFO [org.openiot.ui.request.commons.logging.LoggerService](MSC service thread 1-2) OpenIoT:RequestPresentation: [INFO] Initializing 15:30:08,966 INFO [org.jboss.web](MSC service thread 1-2) JBAS018210: Registering web context: /ui.requestPresentation 15:30:08,975 INFO [org.jboss.as.jpa](MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'ide.core.war#primary' 15:30:09,259 INFO [org.jboss.web](MSC service thread 1-1) JBAS018210: Registering web context: /ui.requestDefinition 15:30:09,437 INFO [org.apache.catalina.core.StandardContext](MSC service thread 1-1) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored. 15:30:09,480 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-1) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/sensorschema' 15:30:10,716 INFO [org.hibernate.annotations.common.Version](MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final} 15:30:10,826 INFO [org.hibernate.Version](MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final} 15:30:10,833 INFO [org.hibernate.cfg.Environment](MSC service thread 1-2) HHH000206: hibernate.properties not found 15:30:10,847 INFO [org.hibernate.cfg.Environment](MSC service thread 1-2) HHH000021: Bytecode provider name : javassist 15:30:11,015 INFO [org.hibernate.ejb.Ejb3Configuration](MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [ name: primary ...] 15:30:11,630 INFO [org.primefaces.webapp.PostConstructApplicationEventListener](MSC service thread 1-1) Running on PrimeFaces 3.5 15:30:11,631 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator](MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 15:30:11,682 INFO [org.primefaces.extensions.application.PostConstructApplicationEventListener](MSC service thread 1-1) Running on PrimeFaces Extensions 0.7.1 15:30:11,748 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-1) Monitoring jndi:/default-host/sensorschema/WEB-INF/faces-config.xml for modifications 15:30:11,805 INFO [org.jboss.web](MSC service thread 1-1) JBAS018210: Registering web context: /sensorschema 15:30:11,939 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/lsm-light.server]](MSC service thread 1-1) No Spring WebApplicationInitializer types detected on classpath 15:30:11,973 INFO [org.openiot.lsm.pooling.ConnectionManager](MSC service thread 1-1) Loading property file 15:30:11,973 INFO [org.openiot.lsm.pooling.ConnectionManager](MSC service thread 1-1) loading database server driver virtuoso.jdbc4.Driver 15:30:13,675 INFO [org.hibernate.dialect.Dialect](MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect 15:30:13,696 WARN [org.hibernate.dialect.H2Dialect](MSC service thread 1-2) HHH000431: Unable to determine H2 database version, certain features may not work 15:30:13,711 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder](MSC service thread 1-2) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4 15:30:13,749 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator](MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory 15:30:13,770 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory](MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory 15:30:14,554 INFO [org.openiot.lsm.pooling.ConnectionManager](MSC service thread 1-1) contextInitialized.....Connection Pooling is configured 15:30:14,554 INFO [org.openiot.lsm.pooling.ConnectionManager](MSC service thread 1-1) Total connections ==> 20 15:30:14,708 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-1) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/lsm-light.server' 15:30:14,803 INFO [org.hibernate.tool.hbm2ddl.SchemaExport](MSC service thread 1-2) HHH000227: Running hbm2ddl schema export 15:30:14,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport](MSC service thread 1-2) HHH000230: Schema export complete 15:30:14,988 INFO [org.jboss.weld.deployer](MSC service thread 1-2) JBAS016008: Starting weld service for deployment ide.core.war 15:30:24,436 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-2) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/ide.core' 15:30:25,606 INFO [org.jboss.web](MSC service thread 1-1) JBAS018210: Registering web context: /lsm-light.server 15:30:27,019 INFO [org.primefaces.webapp.PostConstructApplicationEventListener](MSC service thread 1-2) Running on PrimeFaces 4.0 15:30:27,020 INFO [org.primefaces.extensions.application.PostConstructApplicationEventListener](MSC service thread 1-2) Running on PrimeFaces Extensions 1.2.1 15:30:27,025 INFO [org.omnifaces.VersionLoggerEventListener](MSC service thread 1-2) Using OmniFaces version 1.6.3 15:30:27,026 INFO [javax.enterprise.resource.webcontainer.jsf.config](MSC service thread 1-2) Monitoring jndi:/default-host/ide.core/WEB-INF/faces-config.xml for modifications 15:30:31,241 INFO [org.jboss.web](MSC service thread 1-2) JBAS018210: Registering web context: /ide.core 15:30:31,302 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "sensorschema.war" 15:30:31,303 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "ui.requestPresentation.war" 15:30:31,304 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "ui.requestDefinition.war" 15:30:31,305 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "ide.core.war" 15:30:31,306 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "sdum.core.war" 15:30:31,307 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "scheduler.core.war" 15:30:31,307 INFO [org.jboss.as.server](Controller Boot Thread) JBAS018559: Deployed "lsm-light.server.war" 15:30:31,862 INFO [org.jboss.as](Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.0.108:9990 15:30:31,863 INFO [org.jboss.as](Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 108407ms - Started 809 of 898 services (88 services are passive or on-demand)

keithsptr commented 9 years ago

You see no error.. Code I am using is developer branch

hylkevds commented 9 years ago

That's just the starting of the server. There's nothing after you try to log in?

keithsptr commented 9 years ago

no.. if I do the link to see the scheduler methods and sdum it works and display them on console. if I go to log in nothing happens

hylkevds commented 9 years ago

You should see more output regardless. Can you try changing all instances of the ip address to localhost in openiot.properties?

nmqhoan commented 9 years ago

as I saw in the output, the lsm connection was fine.

15:30:13,770 INFO org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory HHH000397: Using ASTQueryTranslatorFactory 15:30:14,554 INFO org.openiot.lsm.pooling.ConnectionManager contextInitialized.....Connection Pooling is configured 15:30:14,554 INFO org.openiot.lsm.pooling.ConnectionManager Total connections ==> 20

Could you please check the http://192.168.0.26:1098/lsm-light.server/? Is http://192.168.0.26:1098 your JBoss server host?

On 20 Aug 2014, at 15:39, Hylke van der Schaaf notifications@github.com wrote:

You should see more output regardless. Can you try changing all instances of the ip address to localhost in openiot.properties?

— Reply to this email directly or view it on GitHub.

keithsptr commented 9 years ago

yes 192.169.0.26:1098 is where jboss is installed

nmqhoan commented 9 years ago

Could you please check the http://192.168.0.26:1098/lsm-light.server/? Is there any output?

On 20 Aug 2014, at 15:48, keithsptr notifications@github.com wrote:

yes 192.169.0.26:1098 is where jboss is installed

— Reply to this email directly or view it on GitHub.

keithsptr commented 9 years ago

when I type that I have welcome to .... but no output to console

nmqhoan commented 9 years ago

humm, it means the lsm modules was deployed correctly. I just wonder if you deployed your JBoss server with the public IP or local IP?

On 20 Aug 2014, at 16:00, keithsptr notifications@github.com wrote:

when I type that I have welcome to .... but no output to console

— Reply to this email directly or view it on GitHub.