Fails to start after upgrade (different reason)

Post any questions regarding Installing or Upgrading to V5, including problems starting and using the Ebase Server or Designer

Moderators: Jon, Steve, Ian, Dave

Locked
Segi
Ebase User
Posts: 649
Joined: Mon Dec 09, 2013 6:37 pm

Fails to start after upgrade (different reason)

#1

Postby Segi » Wed Jul 15, 2015 4:26 pm

I made a copy of my server and followed the instructions exactly as the guide says to do an upgrade from 4.X to the 5 beta.

When I start the server I get a severe error:

Code: Select all

Jul 15, 2015 9:27:18 AM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.27.
Jul 15, 2015 9:27:18 AM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Jul 15, 2015 9:27:18 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-80"]
Jul 15, 2015 9:27:18 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-apr-8009"]
Jul 15, 2015 9:27:18 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 496 ms
Jul 15, 2015 9:27:18 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jul 15, 2015 9:27:18 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.27
Jul 15, 2015 9:27:18 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\ebaseXi\UfsServer\tomcat\conf\Catalina\localhost\ufs.xml
Jul 15, 2015 9:27:18 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/ufs]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
	at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.UnsupportedClassVersionError: com/ebasetech/ufs/licence/SessionMonitor : Unsupported major.minor version 51.0 (unable to load class com.ebasetech.ufs.licence.SessionMonitor)
	at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2893)
	at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1170)
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1678)
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1556)
	at org.apache.catalina.startup.WebAnnotationSet.loadClass(WebAnnotationSet.java:480)
	at org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:82)
	at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:64)
	at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:381)
	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:858)
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:345)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5161)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 11 more
Jul 15, 2015 9:27:18 AM org.apache.catalina.startup.HostConfig deployDescriptor
SEVERE: Error deploying configuration descriptor C:\ebaseXi\UfsServer\tomcat\conf\Catalina\localhost\ufs.xml
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/ufs]]
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:898)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
	at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Jul 15, 2015 9:27:18 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\ebaseXi\UfsServer\tomcat\webapps\docs
Jul 15, 2015 9:27:19 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\ebaseXi\UfsServer\tomcat\webapps\examples
Jul 15, 2015 9:27:19 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\ebaseXi\UfsServer\tomcat\webapps\host-manager
Jul 15, 2015 9:27:19 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\ebaseXi\UfsServer\tomcat\webapps\manager
Jul 15, 2015 9:27:19 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\ebaseXi\UfsServer\tomcat\webapps\ROOT
Jul 15, 2015 9:27:19 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-80"]
Jul 15, 2015 9:27:19 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
Jul 15, 2015 9:27:19 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 453 ms
0 x
Steve
Moderator
Moderator
Posts: 414
Joined: Fri Sep 07, 2007 3:44 pm
Location: Sandy, UK
Contact:
Contact Steve

#2

Postby Steve » Wed Jul 15, 2015 4:57 pm

Hi Segi,

It looks as though the Java version is incorrect. Version 5 of Ebase is compatible with Java 7 on-wards.

Could you check that you have upgraded your java version when you applied the update?

This also applies to the Client.

Kind regards

Steve Upton
0 x
Segi
Ebase User
Posts: 649
Joined: Mon Dec 09, 2013 6:37 pm

#3

Postby Segi » Wed Jul 15, 2015 5:11 pm

Steve

thanks,

That solved the problem.

I've noticed that the URL format has changed in the 5 beta where before it would be something like: localhost/ufs/ufsmain?formid=HOMEPAGE and now its localhost/ufs/HOMEPAGE.eb

Is there any chance that I can enable the legacy URL format while we make the transition from 4 to 5 ? I have a lot of place in my code where I reference the old URL format and will have to find and correct them all.
0 x
User avatar
dvanhussel
Ebase User
Posts: 161
Joined: Fri Oct 19, 2007 12:45 pm
Location: Haarlem, the Netherlands

#4

Postby dvanhussel » Wed Jul 15, 2015 7:17 pm

Hi Segi,

The documentation states:

Code: Select all

Form Names and URLs, workflow process names

In V5.0 forms and workflow processes can be created anywhere in the workspace, but both form names and workflow process names must be unique within a workspace i.e. it is not possible to have two forms with the same name at different locations within the workspace; ditto workflow processes.

In V5.0, two URL formats are supported to request a form:

 
•New V5.0 format: hostname:port/webapp/formname.eb 

e.g. www.mysite.com/ufs/PortalApp.eb

 
•Old V4.0 format: hostname:port/webapp/ufsmain?formid=formname 

e.g. www.mysite.com/ufs/ufsmain?formid=PortalApp
I did a quick test on a 'HelloWorld' form I just made and the old V4.0 format worked ok there.

So, this should not be a problem :D

Regards,

David
0 x
Segi
Ebase User
Posts: 649
Joined: Mon Dec 09, 2013 6:37 pm

#5

Postby Segi » Wed Jul 15, 2015 8:21 pm

Thanks,

Found that in the documentation after I posted that question here. Glad to see that eBase is aware that it would be a great deal of work otherwise
0 x
Locked

Return to “Version 5 Beta”

Who is online

Users browsing this forum: No registered users and 102 guests