After lots of struggles (see https://sourceforge.net/p/guse/discussion/1672628/thread/1f4126db/), we managed to complete the gUSE installation to the point where Liferay is running and an admin user could be created. Unfortunately now we're stuck again:
We followed the remaining steps in the installation manual ("gUSE_Install_Wizard_Manual_v3.6.1.pdf", step II.5 etc.) - imported the "ws-pgrade3.6.1-liferay6.1.lar" file and then ran the gUSE Service Wizard. That seemed to work fine until the last step, where the manual promises "the page named gUSE Service Wizard is called and the success will be reported". We just got stuck on the "My gUSE Configuration" page.
On the main portal page, when we go to any of the gUSE specific tabs, we see only this message: "This portlet has been undeployed. Please redeploy it or remove it from the page." under the heading "[...]_WAR_wspgrade".
In the "liferay.[data].log" in the "logs" folder of our gUSE installation, we see lots of errors like this:
15:26:59,399 INFO [PortalImpl:4873] Current URL /liferay-portal-6.1.0/en_GB//documents/10180/0/Architethtura generates exception: null
15:27:08,185 ERROR [AdvancedPermissionChecker:905] com.liferay.portal.NoSuchResourceActionException: gwkflist_WAR_wspgrade#ADD_TO_PAGE
com.liferay.portal.NoSuchResourceActionException: gwkflist_WAR_wspgrade#ADD_TO_PAGE
I don't know whether the "undeployed" messages on the portal are due to the fact that the Setup Wizard didn't complete, or whether the Wizard couldn't complete because the deployment failed.
Any help, please?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The undeployed message has (AFAIK) nothing to do with the failed setup wizard.
"This portlet has been undeployed." means that for some reason the portles were "removed" from tomcat/liferay. I saw this problems a few times when I tried to deploy/install a broken portlet.
Can you have a look at your tomcat webapps folder? If it contains the gUse portlets (wfi, wfs, storage, see below) the portlets only have been temporarily undeployed, a restart probably solves it. If these folders are not in there, then something is very wrong (reinstall..?)
Cheers,
Lorenz
p-grade@itestportal:~/guse/current/liferay-portal-6.1.1-ce-ga2/tomcat-7.0.27/webapps$ ls
GenericWorkflowInterface-portlet information storage
GuseWorkflowTest-portlet marketplace-portlet welcome-theme
Init-portlet private-plugin-installer-hook wfi
PersonalDB-portlet repository wfs
Ubuntu 10.04.4 LTS
java version "1.6.0_37"
mysql Ver 14.14 Distrib 5.1.72
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can I remove the gUSE/WS-PGRADE content from Liferay without reinstalling everything - in order to try a clean import again? (How?)
Also, your directory structure looks significantly different from mine. In the install directory, I have these directories:
apache-tomcat-6.0.37/ data/ deploy/ _gUSE-3.6.1/ _Liferay-6.1/ logs/
Then, in "apache-tomcat-6.0.37" I have:
bin/ conf/ lib/ logs/ temp/ webapps/ work/
And in "webapps":
dataavenue/ dci_bridge_service/ host-manager/ information/ liferay-portal-6.1.0/ manager/ repository/ ROOT/ stataggregator/ statvisualizer/ storage/ wfi/ wfs/ wspgrade/
So there's only some overlap with what you have. What does that mean?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The directory structure looks good, its the same as ours, except we have some more portlets installed (PersonalDB-portlet GWI-portlet...).
So the wspgrade portlets are installed but even after restart it shows "portlets undeployed"? Is there some logs saying why it could not deploy the wspgrade portlets?
(something like "0 portlets deployed for wspgrade" and a stack trace above.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, I'll do that. By the way, when I try to shut the server down ("shutdown.sh"), I get lots of errors about memory leaks, e.g.:
13-Jan-2014 10:11:58 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/wfi] created a ThreadLocal with key of type [com.sun.xml.bind.v2.ClassFactory$1] (value [com.sun.xml.bind.v2.ClassFactory$1@dad5960]) and a value of type [java.util.WeakHashMap] (value [{class javax.xml.bind.annotation.W3CDomHandler=java.lang.ref.WeakReference@6fc6b4a3}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Also, the Java process ("org.apache.catalina.startup.Bootstrap start") doesn't finish when I execute "shutdown". Is that normal?
Last edit: Hendrik Weisser 2014-01-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bela, setting the levels to ALL doesn't seem to give me more information on the "listenerStart" error. I now get entries in the "localhost", "manager" and "host-manager" logs, but they're all "FINE".
In particular, the "localhost" log has "listenerStart" and "filterStart" entries, but they're "FINE" - no errors.
Are there any log files elsewhere than "apache-tomcat-6.0.37/logs" that I may be missing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you set the level of all the loggers?
It should be in apache-tomcat-6.0.37/logs directory in the catalina.out
just to be sure i attache a sample logging.properties
regarding your other question: yes, from some reason shutdown doesn't properly work with guse, you have to manually kill the java process after you called shutdown
Yes, I double-checked the log levels, they are all "ALL".
And there's really no more about that error. I'm pasting the whole part of "catalina.out" between the error and the finished start-up below.
13-Jan-2014 10:23:16 org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
13-Jan-2014 10:23:16 org.apache.catalina.core.StandardContext start
SEVERE: Context [/wspgrade] startup failed due to previous errors
13-Jan-2014 10:23:16 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor dataavenue.xml
13-Jan-2014 10:23:16 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive liferay-portal-6.1.0.war
Loading jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/system.properties
10:23:17,180 INFO [EasyConf:122] Refreshed the configuration of all components
10:23:17,514 INFO [ConfigurationLoader:56] Properties for jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal loaded from [file:/data/guse/portal-setup-wizard.properties, file:/data/
guse/portal-ext.properties, jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal.properties]
Loading jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/data/guse/portal-ext.properties
Loading file:/data/guse/portal-setup-wizard.properties
10:23:22,166 INFO [DialectDetector:80] Determine dialect for MySQL 5
10:23:22,195 INFO [DialectDetector:145] Found dialect org.hibernate.dialect.MySQLDialect
Starting Liferay Portal Community Edition 6.1.0 CE (Paton / Build 6100 / January 6, 2012)
10:23:39,850 INFO [BaseDB:409] Database does not support case sensitive queries
10:23:40,296 INFO [PluginPackageUtil:1096] Reading plugin package for the root context
10:23:42,232 INFO [AutoDeployDir:105] Auto deploy scanner started for /data/guse/deploy
10:23:45,876 INFO [PluginPackageUtil:1099] Reading plugin package for statvisualizer
10:23:45,878 WARN [PluginPackageUtil:1058] Plugin package on context statvisualizer cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
10:23:46,773 INFO [PortletHotDeployListener:614] Registering portlets for statvisualizer
10:23:46,869 INFO [PortletHotDeployListener:433] 1 portlet for statvisualizer is available for use
10:23:46,923 INFO [PluginPackageUtil:1099] Reading plugin package for wspgrade
10:23:46,923 WARN [PluginPackageUtil:1058] Plugin package on context wspgrade cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load service.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load service.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load portlet.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load portlet.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
10:23:46,927 INFO [PluginPackageUtil:1099] Reading plugin package for dataavenue
10:23:46,927 WARN [PluginPackageUtil:1058] Plugin package on context dataavenue cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
10:23:47,015 INFO [PortletHotDeployListener:614] Registering portlets for dataavenue
10:23:47,047 WARN [PortletLocalServiceImpl:720] Portlet with the name DataAvenue_WAR_dataavenue is described in portlet.xml but does not have a matching entry in liferay-portlet.xml
10:23:47,048 WARN [PortletLocalServiceImpl:731] Portlet with the name DataBridge_WAR_dataavenue is described in liferay-portlet.xml but does not have a matching entry in portlet.xml
Init
----List favorites----------|------------------------
10:23:47,074 INFO [PortletHotDeployListener:433] 1 portlet for dataavenue is available for use
13-Jan-2014 10:23:49 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
13-Jan-2014 10:23:49 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
13-Jan-2014 10:23:49 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
13-Jan-2014 10:23:49 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/26 config=null
13-Jan-2014 10:23:49 org.apache.catalina.startup.Catalina start
INFO: Server startup in 44681 ms
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was only one entry in the "loggin.properties" and I've changed it to ALL, but that didn't affect the log messages. Still no context on the "listenerStart".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We just did a re-install with a local MySQL server, just to make sure that it's not a problem with the database connection, and we get the same results.
I can't think of anything else to try from our side.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please, check the necessary prerequisites that you need for installing gUSE (e.g. you need the latest available Java 6 version etc.). You find them in the Install Wizard Manual.
Regards,
Tibor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately if webapps are deployed through Liferay (this is what has to be done in case of wspgrade, otherwise the portlets won't be visible in Liferay), some stack traces are cast to oblivion.
In order to really see them, you have to:
undeploy the wspgrade webapp through Tomcat's manager interface
deploy the 'wspgrade.war' webapp contained in the gUSE installation package's (guse-3.x.y.tgz) 'webapplications' directory
now you should see any exceptions in catalina.out and/or localhost*.log.
Let us know if you find any exceptions this way.
Other thing: do you see the "SEVERE: Context [/XYZ] startup failed due to previous errors" message only for wspgrade? I.e., have the other webapps started up properly (you can check this through Tomcat's manager interface as well).
Cheers,
Zoltan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could be - thanks for finding this. Unfortunately the bug submitter just writes: "I got passed [should be 'past'] this bump, but the wspgrade portlet is still not starting". He doesn't mention how he solved the problem!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For me, it seems that there are conflicting jars in your $TOMCAT_HOME/lib - related with multiple XML parsers (org.apache.xerces) and/or web service implementations (com.sun.xml.ws). Are there any new jars added to this folder after guse install? (New web applications maybe?)
Somehow we should compare these jars with the lib of a "normal" guse installation, and spot the superfluous (/conflicting) jars...
Regards, Akos Hajnal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After lots of struggles (see https://sourceforge.net/p/guse/discussion/1672628/thread/1f4126db/), we managed to complete the gUSE installation to the point where Liferay is running and an admin user could be created. Unfortunately now we're stuck again:
We followed the remaining steps in the installation manual ("gUSE_Install_Wizard_Manual_v3.6.1.pdf", step II.5 etc.) - imported the "ws-pgrade3.6.1-liferay6.1.lar" file and then ran the gUSE Service Wizard. That seemed to work fine until the last step, where the manual promises "the page named gUSE Service Wizard is called and the success will be reported". We just got stuck on the "My gUSE Configuration" page.
On the main portal page, when we go to any of the gUSE specific tabs, we see only this message: "This portlet has been undeployed. Please redeploy it or remove it from the page." under the heading "[...]_WAR_wspgrade".
In the "liferay.[data].log" in the "logs" folder of our gUSE installation, we see lots of errors like this:
15:26:59,399 INFO [PortalImpl:4873] Current URL /liferay-portal-6.1.0/en_GB//documents/10180/0/Architethtura generates exception: null
15:27:08,185 ERROR [AdvancedPermissionChecker:905] com.liferay.portal.NoSuchResourceActionException: gwkflist_WAR_wspgrade#ADD_TO_PAGE
com.liferay.portal.NoSuchResourceActionException: gwkflist_WAR_wspgrade#ADD_TO_PAGE
I don't know whether the "undeployed" messages on the portal are due to the fact that the Setup Wizard didn't complete, or whether the Wizard couldn't complete because the deployment failed.
Any help, please?
Hello Hendrik
The undeployed message has (AFAIK) nothing to do with the failed setup wizard.
"This portlet has been undeployed." means that for some reason the portles were "removed" from tomcat/liferay. I saw this problems a few times when I tried to deploy/install a broken portlet.
Can you have a look at your tomcat webapps folder? If it contains the gUse portlets (wfi, wfs, storage, see below) the portlets only have been temporarily undeployed, a restart probably solves it. If these folders are not in there, then something is very wrong (reinstall..?)
Cheers,
Lorenz
p-grade@itestportal:~/guse/current/liferay-portal-6.1.1-ce-ga2/tomcat-7.0.27/webapps$ ls
GenericWorkflowInterface-portlet information storage
GuseWorkflowTest-portlet marketplace-portlet welcome-theme
Init-portlet private-plugin-installer-hook wfi
PersonalDB-portlet repository wfs
Ubuntu 10.04.4 LTS
java version "1.6.0_37"
mysql Ver 14.14 Distrib 5.1.72
A restart of Tomcat did not help.
Can I remove the gUSE/WS-PGRADE content from Liferay without reinstalling everything - in order to try a clean import again? (How?)
Also, your directory structure looks significantly different from mine. In the install directory, I have these directories:
apache-tomcat-6.0.37/ data/ deploy/ _gUSE-3.6.1/ _Liferay-6.1/ logs/
Then, in "apache-tomcat-6.0.37" I have:
bin/ conf/ lib/ logs/ temp/ webapps/ work/
And in "webapps":
dataavenue/ dci_bridge_service/ host-manager/ information/ liferay-portal-6.1.0/ manager/ repository/ ROOT/ stataggregator/ statvisualizer/ storage/ wfi/ wfs/ wspgrade/
So there's only some overlap with what you have. What does that mean?
Dear Hendrik
The directory structure looks good, its the same as ours, except we have some more portlets installed (PersonalDB-portlet GWI-portlet...).
So the wspgrade portlets are installed but even after restart it shows "portlets undeployed"? Is there some logs saying why it could not deploy the wspgrade portlets?
(something like "0 portlets deployed for wspgrade" and a stack trace above.)
Hey Lorenz, thanks a lot for your help!
There are some things in the logs that might be relevant. During start-up:
13-Jan-2014 09:38:20 org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
13-Jan-2014 09:38:20 org.apache.catalina.core.StandardContext start
SEVERE: Context [/wspgrade] startup failed due to previous errors
When I click on one of the tabs on the web page:
09:41:39,098 ERROR [AdvancedPermissionChecker:905] com.liferay.portal.NoSuchResourceActionException: localstorage_WAR_wspgrade#ADD_TO_PAGE
com.liferay.portal.NoSuchResourceActionException: localstorage_WAR_wspgrade#ADD_TO_PAGE
[...Java stack trace...]
Does any of that tell you anything?
Hi Hendrik,
It seems tomcat hides the source of the error. Try to set all the logging levels in conf/logging.properties (under tomcat's directory) to ALL.
Okay, I'll do that. By the way, when I try to shut the server down ("shutdown.sh"), I get lots of errors about memory leaks, e.g.:
13-Jan-2014 10:11:58 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/wfi] created a ThreadLocal with key of type [com.sun.xml.bind.v2.ClassFactory$1] (value [com.sun.xml.bind.v2.ClassFactory$1@dad5960]) and a value of type [java.util.WeakHashMap] (value [{class javax.xml.bind.annotation.W3CDomHandler=java.lang.ref.WeakReference@6fc6b4a3}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Also, the Java process ("org.apache.catalina.startup.Bootstrap start") doesn't finish when I execute "shutdown". Is that normal?
Last edit: Hendrik Weisser 2014-01-13
Bela, setting the levels to ALL doesn't seem to give me more information on the "listenerStart" error. I now get entries in the "localhost", "manager" and "host-manager" logs, but they're all "FINE".
In particular, the "localhost" log has "listenerStart" and "filterStart" entries, but they're "FINE" - no errors.
Are there any log files elsewhere than "apache-tomcat-6.0.37/logs" that I may be missing?
Did you set the level of all the loggers?
It should be in apache-tomcat-6.0.37/logs directory in the catalina.out
just to be sure i attache a sample logging.properties
regarding your other question: yes, from some reason shutdown doesn't properly work with guse, you have to manually kill the java process after you called shutdown
Yes, I double-checked the log levels, they are all "ALL".
And there's really no more about that error. I'm pasting the whole part of "catalina.out" between the error and the finished start-up below.
13-Jan-2014 10:23:16 org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
13-Jan-2014 10:23:16 org.apache.catalina.core.StandardContext start
SEVERE: Context [/wspgrade] startup failed due to previous errors
13-Jan-2014 10:23:16 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor dataavenue.xml
13-Jan-2014 10:23:16 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive liferay-portal-6.1.0.war
Loading jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/system.properties
10:23:17,180 INFO [EasyConf:122] Refreshed the configuration of all components
10:23:17,514 INFO [ConfigurationLoader:56] Properties for jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal loaded from [file:/data/guse/portal-setup-wizard.properties, file:/data/
guse/portal-ext.properties, jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal.properties]
Loading jar:file:/data/guse/apache-tomcat-6.0.37/webapps/liferay-portal-6.1.0/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/data/guse/portal-ext.properties
Loading file:/data/guse/portal-setup-wizard.properties
10:23:22,166 INFO [DialectDetector:80] Determine dialect for MySQL 5
10:23:22,195 INFO [DialectDetector:145] Found dialect org.hibernate.dialect.MySQLDialect
Starting Liferay Portal Community Edition 6.1.0 CE (Paton / Build 6100 / January 6, 2012)
10:23:39,850 INFO [BaseDB:409] Database does not support case sensitive queries
10:23:40,296 INFO [PluginPackageUtil:1096] Reading plugin package for the root context
10:23:42,232 INFO [AutoDeployDir:105] Auto deploy scanner started for /data/guse/deploy
10:23:45,876 INFO [PluginPackageUtil:1099] Reading plugin package for statvisualizer
10:23:45,878 WARN [PluginPackageUtil:1058] Plugin package on context statvisualizer cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
10:23:46,773 INFO [PortletHotDeployListener:614] Registering portlets for statvisualizer
10:23:46,869 INFO [PortletHotDeployListener:433] 1 portlet for statvisualizer is available for use
10:23:46,923 INFO [PluginPackageUtil:1099] Reading plugin package for wspgrade
10:23:46,923 WARN [PluginPackageUtil:1058] Plugin package on context wspgrade cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load service.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load service.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load portlet.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
13-Jan-2014 10:23:46 org.apache.catalina.loader.WebappClassLoader findResourceInternal
INFO: Illegal access: this web application instance has been stopped already. Could not load portlet.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate
the thread which caused the illegal access, and has no functional impact.
10:23:46,927 INFO [PluginPackageUtil:1099] Reading plugin package for dataavenue
10:23:46,927 WARN [PluginPackageUtil:1058] Plugin package on context dataavenue cannot be tracked because this WAR does not contain a liferay-plugin-package.xml file
10:23:47,015 INFO [PortletHotDeployListener:614] Registering portlets for dataavenue
10:23:47,047 WARN [PortletLocalServiceImpl:720] Portlet with the name DataAvenue_WAR_dataavenue is described in portlet.xml but does not have a matching entry in liferay-portlet.xml
10:23:47,048 WARN [PortletLocalServiceImpl:731] Portlet with the name DataBridge_WAR_dataavenue is described in liferay-portlet.xml but does not have a matching entry in portlet.xml
Init
----List favorites----------|------------------------
10:23:47,074 INFO [PortletHotDeployListener:433] 1 portlet for dataavenue is available for use
13-Jan-2014 10:23:49 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
13-Jan-2014 10:23:49 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
13-Jan-2014 10:23:49 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
13-Jan-2014 10:23:49 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/26 config=null
13-Jan-2014 10:23:49 org.apache.catalina.startup.Catalina start
INFO: Server startup in 44681 ms
As i see there's a logging.properties file also in webapps/wspgrade/WEB-INF/classes/
try to increase the log level there too.
There was only one entry in the "loggin.properties" and I've changed it to ALL, but that didn't affect the log messages. Still no context on the "listenerStart".
We just did a re-install with a local MySQL server, just to make sure that it's not a problem with the database connection, and we get the same results.
I can't think of anything else to try from our side.
Hi Hendrik,
Please, check the necessary prerequisites that you need for installing gUSE (e.g. you need the latest available Java 6 version etc.). You find them in the Install Wizard Manual.
Regards,
Tibor
Tibor, as far as I can tell we fulfill the requirements.
How can we diagnose what actually goes wrong when we get this message:
13-Jan-2014 09:38:20 org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
13-Jan-2014 09:38:20 org.apache.catalina.core.StandardContext start
SEVERE: Context [/wspgrade] startup failed due to previous errors
Why isn't there information about the error (e.g. a Java stack trace)?
Hi Hendrik,
Unfortunately if webapps are deployed through Liferay (this is what has to be done in case of wspgrade, otherwise the portlets won't be visible in Liferay), some stack traces are cast to oblivion.
In order to really see them, you have to:
Let us know if you find any exceptions this way.
Other thing: do you see the "SEVERE: Context [/XYZ] startup failed due to previous errors" message only for wspgrade? I.e., have the other webapps started up properly (you can check this through Tomcat's manager interface as well).
Cheers,
Zoltan
Hey Zoltan, thanks for getting back to me! (I was getting a bit worried that we'd have to give up without support from you guys.)
I did what you said and now I get the following messages in "catalina.out" when I try to start "/wspagrade" in the Tomcat Manager:
21-Jan-2014 16:32:14 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive wspgrade.war
21-Jan-2014 16:32:15 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
21-Jan-2014 16:32:16 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
SEVERE: WSSERVLET11: failed to parse runtime descriptor: org.apache.xerces.util.ObjectFactory$ConfigurationError: Provider org.apache.xerces.parsers.XML11Configuration could not be instantiated: org.apache.xerces.impl.dv.DVFactoryException: DTD factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from DTDDVFactory.
org.apache.xerces.util.ObjectFactory$ConfigurationError: Provider org.apache.xerces.parsers.XML11Configuration could not be instantiated: org.apache.xerces.impl.dv.DVFactoryException: DTD factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from DTDDVFactory.
[...stack trace...]
21-Jan-2014 16:32:16 org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
21-Jan-2014 16:32:16 org.apache.catalina.core.StandardContext start
SEVERE: Context [/wspgrade] startup failed due to previous errors
21-Jan-2014 16:32:16 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
I really hope that's helpful!
Oh, I forgot about the second question:
Yes, the other web apps seem to have started properly - no errors in the log and "Running" is "true" in the manager.
Last edit: Hendrik Weisser 2014-01-22
Hi Hendrik,
Could you please send us the OS version used and packages deployed?
Thanks,
Zoltan
Ubuntu 12.04 LTS
Java 1.6.0_37
MySQL 5.5.34 client, connecting to a 5.5.31 server
Any others you're interested in?
Isn't this related to this bug http://sourceforge.net/p/guse/bugs/107/ ?
At least google for the same exception this was the first hit.
Bela
2014/1/27 Hendrik Weisser hendrikweisser@users.sf.net
--
Üdvözlettel:
Hullár Béla
Could be - thanks for finding this. Unfortunately the bug submitter just writes: "I got passed [should be 'past'] this bump, but the wspgrade portlet is still not starting". He doesn't mention how he solved the problem!
Would be nice to have a list of all packages (dpkg -l). You can send me it directly (https://sourceforge.net/u/zfarkas/profile/send_message).
Thanks,
Zoltan
I've sent it to you.
For me, it seems that there are conflicting jars in your $TOMCAT_HOME/lib - related with multiple XML parsers (org.apache.xerces) and/or web service implementations (com.sun.xml.ws). Are there any new jars added to this folder after guse install? (New web applications maybe?)
Somehow we should compare these jars with the lib of a "normal" guse installation, and spot the superfluous (/conflicting) jars...
Regards, Akos Hajnal