Fwd: [OpenBoxes] [general] [OpenBoxes] [bugs] Old WAR file under v0.8.17

Justin,

Can you help me out with this latest issue?

Charles Burki | CTO
Innovative Logics LLC | SBA 8(a) Certified SDB | SBE/MBE/DBE/Texas HUB
7 Home Place Ct, Dalworthington Gardens TX 76016
M: 414-399-3762

Email: cburki@innovativelogics.com
Website: https://www.innovativelogics.com

Outlook-wlb053uf.png

From: Ranjul Dayal <ranjul@gmail.com>

Subject: Re: [OpenBoxes] [general] [OpenBoxes] [bugs] Old WAR file under v0.8.17

Date: June 13, 2022 at 10:58:28 PM CDT

To: Charles Burki <cburki@innovativelogics.com>

Missed the attachments. Attached it now.

What log files?

Charles Burki | CTO
Innovative Logics LLC | SBA 8(a) Certified SDB | SBE/MBE/DBE/Texas HUB
7 Home Place Ct, Dalworthington Gardens TX 76016
M: 414-399-3762

Email: cburki@innovativelogics.com
Website: https://www.innovativelogics.com

Charles,

Received different errors following the instruction.

I restarted twice to see if on the second start, it will create the missing tables/views. That didnt help.
Then I created the tables and views as mentioned. It still didnt start properly.

See attached logs.

Regards,
Ranjul

Ranjul,

Please follow Justin’s workaround below and let me know if this works.

Regards,

Charles Burki | CTO
Innovative Logics LLC | SBA 8(a) Certified SDB | SBE/MBE/DBE/Texas HUB
7 Home Place Ct, Dalworthington Gardens TX 76016
M: 414-399-3762

Email: cburki@innovativelogics.com
Website: https://www.innovativelogics.com

<Outlook-wlb053uf.png>

From: Justin Miranda via OpenBoxes <discuss@openboxes.com>

Subject: [OpenBoxes] [general] [OpenBoxes] [bugs] Old WAR file under v0.8.17

Date: June 7, 2022 at 12:52:15 PM CDT

To: cburki@innovativelogics.com

Reply-To: OpenBoxes <discuss+e9f183b4861d430250448f11b8ec488e@openboxes.com>

jmiranda
June 7

So it looks like you are running into the same issue as another user.

How to run openboxes in Apache Netbeans?

To elaborate, we have a view that depends on a derived data table that is created at runtime. If the view definition is executed before that table is run, we’ll run into this bug. The temporary fix was to allow the view creation to fail as it would be recreated on the next restart. https://github.com/openboxes/openboxes/blob/develop/grails-app/migrations/views/changelog.xml#L81 I’m not super happy with that solution, so I would recommend manually executing the following SQL script on your dat…

The current version has a workaround in which the error that occurs during view creation is still allowed to occur but it doesn’t prevent the application from starting up. We’re working to figure out how to fix the timing issue (psuedo-race condition) that occurs when creating the product demand tables and the views that depend on them.

As a workaround, I would recommend executing the SQL included in the post above and then restart the application.


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

Outlook-wlb053uf.png

catalina.2022-06-13.log (39.6 KB)

commons-daemon.2022-06-13.log (568 Bytes)

localhost.2022-06-13.log (150 Bytes)

tomcat8-stderr.2022-06-13.log (45.9 KB)

tomcat8-stdout.2022-06-13.log (30.5 KB)

Hey Charles

The database properties from the installation instructions should be saved in a file called openboxes-config.properties, not openboxes-config.groovy. The .properties file allows comments using hash sign (#). The openboxes-config.groovy file does not recognize the hash sign (#) as a comment.

Unable to load specified config location file:C:\Windows\ServiceProfiles\LocalService/.grails/openboxes-config.groovy : startup failed:
script16551250765381827448647.groovy: 1: expecting '!', found ' ' @ line 1, column 2.
   # Database connection settings
    ^

1 error

I would recommend saving the required properties (like database settings and grails.serverURL) in openboxes-config.properties while other optional configuration can go into openboxes-config.groovy. However, the .groovy configuration file is only really necessary for boolean configuration properties, as well as properties with nested objects.