5.7 Update

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Dave, Jon, Steve, Ian

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

5.7 Update

#1

Postby Segi » Mon Mar 23, 2020 8:03 pm

I was looking at the upgrade README for 5.7 and am confused about something.

I thought that the 5.6 update which split the user and app data into 2 directories was going to let us have an automated installer for future updates but 5.7 is still a manual upgrade for all versions of Verj 5.X according to the README

If that is correct, when will we be able to have automates updates through an installer ?

Thanks,

Segi
0 x

Jon
Moderator
Moderator
Posts: 1308
Joined: Wed Sep 12, 2007 12:49 pm

Re: 5.7 Update

#2

Postby Jon » Tue Mar 24, 2020 9:46 am

Apologies for this, the Readme file has not been updated.

If you are currently using V5.6, you can just point the V5.7 installer at your current system and it will automatically upgrade. Obviously it would be wise to take a backup of the file system first.
0 x

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

Re: 5.7 Update

#3

Postby Segi » Tue Mar 24, 2020 9:11 pm

After backing up my existing Verj 5.6 folders (VerjIO and VerjIOData), I ran the 5.7 Windows 64 bit installer and chose to upgrade my installation which ran successfully.

The installer restarted the Verj IO Windows service.

After entering our domain intranet.example.com into my browser I saw the login page which uses Ebase' built in authentication service to authenticate the user against our database. After submitting the login, I got the following error: https://imgur.com/w1o4LFV

I checked the server logs and saw the following errors in the errors log

Code: Select all


2020-03-24 13:45:52 Commons Daemon procrun stdout initialized
Copying startup files from C:\VerjIO\Server\initData to C:\VerjIOData
Startup files not copied.  Already up to date.
Done Copying startup files.
No org.slf4j.impl.StaticLoggerBinder found in ClassPath, trying with log4j2...
No org.apache.logging.log4j.Logger found found in ClassPath, trying with log4j...
No org.apache.log4j.Logger found found in ClassPath, falling back default...
Tue Mar 24 13:46:00:  log4j configured with C:\VerjIOData\apps\ufs\ebaseConf\log4j.xml
Tue Mar 24 13:46:00:  verjio.server.userdata C:\VerjIOData
Tue Mar 24 13:46:00:  verjio.server.home C:\VerjIO\Server\winservice\..
Tue Mar 24 13:46:00:  Application found at C:\VerjIOData\apps\ufs
Tue Mar 24 13:46:00:  Ebase configuration found at C:\VerjIOData\apps\ufs\ebaseConf
Tue Mar 24 13:46:01:  Ebase Server initialising....
Tue Mar 24 13:46:01: ERROR Error merging with system truststore
java.security.UnrecoverableKeyException: Password must not be null
	at java.base/sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:133)
	at java.base/sun.security.util.KeyStoreDelegator.engineGetKey(KeyStoreDelegator.java:90)
	at java.base/java.security.KeyStore.getKey(KeyStore.java:1050)
	at java.base/sun.security.ssl.SunX509KeyManagerImpl.<init>(SunX509KeyManagerImpl.java:145)
	at java.base/sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(KeyManagerFactoryImpl.java:70)
	at java.base/javax.net.ssl.KeyManagerFactory.init(KeyManagerFactory.java:271)
	at com.ebasetech.common.compositejks.SslContextUtils.getSystemKeyManager(SslContextUtils.java:94)
	at com.ebasetech.common.compositejks.SslContextUtils.buildMergedWithSystem(SslContextUtils.java:79)
	at com.ebasetech.common.compositejks.SslContextUtils.mergeWithSystem(SslContextUtils.java:35)
	at com.ebasetech.common.compositejks.SslContextUtils.mergeWithSystem(SslContextUtils.java:63)
	at com.ebasetech.ufs.security.ssl.InitCATrustore.mergeWithSystemTruststore(InitCATrustore.java:29)
	at com.ebasetech.ufs.security.ssl.InitCATrustore.mergeTrustoreStore(InitCATrustore.java:48)
	at com.ebasetech.ufs.kernel.UFSServletContextProxy.init(UFSServletContextProxy.java:118)
	at com.ebasetech.ufs.kernel.UFSServletContextProxy.Initialise(UFSServletContextProxy.java:299)
	at formservlets.EbaseContextListener.contextInitialized(EbaseContextListener.java:57)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4745)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5207)
	at com.ebasetech.tomcat.EbaseContext.startInternal(EbaseContext.java:102)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
	at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1842)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:835)
Tue Mar 24 13:46:01:  Loading Property file UFSSetup.properties
Tue Mar 24 13:46:01:  UFSSetup.properties property file found
Tue Mar 24 13:46:01:  ************************************************************
Logging to file C:\VerjIOData\apps\logs\ebase-server.log
Tue Mar 24 13:46:01:  ***  Starting Verj.io Server version 5.7.0, Build 20200129
Tue Mar 24 13:46:01:  ************************************************************
Tue Mar 24 13:46:07:  Runtime resources found at C:\VerjIOData\apps\ufs\runtimeResources
Tue Mar 24 13:46:09:  Verj.io designer server component initialised successfully
Tue Mar 24 13:46:09:  Workflow servlet component initialised successfully
Tue Mar 24 13:46:10:  FormCacheLoader: start
Tue Mar 24 13:46:10:  FormCacheLoader: end
Tue Mar 24 13:46:10:  ******************************************************************
Tue Mar 24 13:46:10:  ***  Verj.io Server V5.7.0 successfully initialized in 8 seconds
Tue Mar 24 13:46:10:  ***  Using workspace C:\VerjIOData\apps\ufs\workspace
Tue Mar 24 13:46:10:  ******************************************************************
Tue Mar 24 14:10:16:  Error invoking logon system service: com.ebasetech.ws.core.cxf.client.CXFExceptionWrapper: Could not invoke service. java.lang.IllegalStateException: Local destination does not have a MessageObserver on address local://ufs/defaultLogonService

0 x

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

Re: 5.7 Update

#4

Postby Segi » Tue Mar 24, 2020 11:58 pm

Update: I was trying to figure out why the truststore error was happening and I fixed it by removing truststore from VerjIOData\security and this message disappeared from the server logs but the underlying error about no MessageObserver is still there
0 x

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

Re: 5.7 Update

#5

Postby Segi » Wed Mar 25, 2020 12:10 am

I just found the solution to this problem and wanted to post it here in case anyone else runs into this after upgrading.

I am using ebaseLogonService to authenticate. I fixed this error by going into the Verj Admin console at http://localhost/ufs/eBaseAdmin.eb and went to Security->Authentication. At the very bottom in the Default Logon Service section the Default Logon Service Web Service Name showed please select so I selected ebaseLogon and saved the setting and now everything works fine again. Somehow this setting was forgotten during the upgrade.
0 x

Jon
Moderator
Moderator
Posts: 1308
Joined: Wed Sep 12, 2007 12:49 pm

Re: 5.7 Update

#6

Postby Jon » Wed Mar 25, 2020 9:52 am

I'm trying to find out what happened during the upgrade, particularly with the default Logon Service. Do you have a copy of security.properties before and after the upgrade that you could send to us at support@ebasetech.com. This file will be in userData/Server/apps/<webappname>/ebaseConf.

The truststore error is just a warning message, it doesn't stop anything working and was probably there in your V5.6 system.
0 x

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

Re: 5.7 Update

#7

Postby Segi » Wed Mar 25, 2020 7:25 pm

Jon,

I just emailed you the 2 security.properties from 5.6 and 5.7 which I found in VerjIOData/apps/ufs/ebaseConf

I did a compare on these 2 files and noticed that the 5.7 config has a lot more properties than 5.6 including the line Logonexit.WebService=ebaseLogonService that specifies the default logon service.

thanks,

Segi
0 x

Jon
Moderator
Moderator
Posts: 1308
Joined: Wed Sep 12, 2007 12:49 pm

Re: 5.7 Update

#8

Postby Jon » Thu Mar 26, 2020 2:51 pm

Thanks for this. We've identified the problem. There will be a small fix to the V5.7 distribution but you will not need to apply this as you have already fixed the problem locally.
0 x


Who is online

Users browsing this forum: Google [Bot] and 8 guests