Build failed Bika  2023-12-08 00:33
Status: Active
 

Hello,

I want to try to generate deployable software from source code.
I have installed the development environment (https://www.labkey.org/Documentation/wiki-page.view?name=devMachine). It includes:
1.Window Server 2019 Standard
2.jdk_x64_17.0.9_9
3.apache-tomcat-9.0.83
4.postgresql-15.5-1
5.Labkey server-23.12.RC0/platform-23.12.RC0
6.IntelliJ IDEA 2023.2.5 (Community Edition)
Version number: IC-232.10227.8, built on November 9, 2023
Runtime version: 17.0.9+7-b1000.46 amd64
Virtual Machine OpenJDK 64-bit server VM: JetBrains s.r.o.

My first build took a long time but failed. I followed the error message and build again with stacktrace and still got the error message as attached.

Thanks,
Bika

 
 
mohara responded:  2023-12-11 16:12

Hi Bika:

I'm not sure exactly what is happening with that build, but right off, #5 on your list says you're trying to build "server-23.12.RC0/platform-23.12.RC0" which is odd. When you follow the instructions, you'll have the 'develop' branch by default, and may want to switch to the 'release23.11' branch to have the most stable released version. I'm not sure where you got what you're trying to build.

Next, it's unusual that you have your JDK in #2 listed as "jdk_x64_17.0.9_9". The specific JDK that we support and recommend would not default to that name. Did you use another vendor's JDK? The name itself doesn't matter, it just seems an odd rename if that's what you did.

From looking at your log, you may be executing the 'deployApp' task from the server subdirectory, instead of from the LABKEY_HOME location (which it looks like you named"C:\Labkey\LABKEY_HOME" ?). The instructions also include an abbreviated map of what the directory structure should look like to make sure you have cloned the necessary parts correctly.

I'm glad you've reached out, but we're not able to provide custom development support on this forum. Please contact us on our website with details of what you are hoping to accomplish with LabKey Server and why building from source might (or might not) be necessary for your goals. We offer cloud-hosted servers and personalized professional and developer support with our Premium Editions that might better suit your needs.

--Molly

 
Bika responded:  2023-12-13 21:28

Hi Molly:
I'm a big fan of Labkey. I have successfully built Labkey19.1 and Labkey21.3 from source. Now build Labkey23.11 in the same way fails. Has this Labkey23.11 changed significantly from them? If there are changes from that version already?

Thanks,
Bika

 
mohara responded:  2023-12-14 09:37

Hi Bika:

The build process itself hasn't changed in that time, and our documentation is up to date, so perhaps starting from scratch will be your best way forward. To build 23.11, you first need to sync everything in your enlistment to the "release23.11" branch, then run the build commands from the LABKEY_HOME location (not the server subdirectory as it looks like you tried earlier).

Once you get it built, you'll also need to start your 23.11 on a new database since you can't upgrade from 21.3 to 23.11.

--Molly

 
Bika responded:  2024-01-01 23:32

Hi Molly,

My build has become successful. After deploying and starting Apache Tomcat 9.0 Tomcat9 I found that the modules were not unpacked successfully. Checking all the modules in catalina log, there is "2-byte UTF-8 sequence of bytes 2 Invalid" error message. See the attached file. In addition, I tested to install the official Labkey release in the same deployment environment and it works fine.

Thanks,
Bika

 
mohara responded:  2024-01-08 10:56

Hi Bika:

I'm glad to hear the official release is working fine. I'm not exactly following why you're attaching that catalina log - that error implies some sort of encoding mismatch, which is not an error we've seen in this version (or others) so it seems a step was missed or something left over from a previous attempt was not started from scratch? We're not able to provide custom developer support on this forum, and I encourage you to contact us on our website about what you are hoping to accomplish and how we can help.

At any rate, since you can deploy and run the official version successfully, you should be all set.

Thanks,

--Molly