#Maven DB compilation problem

56 messages · Page 1 of 1 (latest)

vague rose
#

Wildfly

rain owlBOT
#

⌛ This post has been reserved for your question.

Hey @vague rose! Please use /close or the Close Post button above when you're finished. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

vague rose
#

I know that these errors could have been caused by a variety of factors

#

But can u give me some sort of direction to look

lost trench
#

are you closing the connections anywhere?

vague rose
#

No

honest ferry
#

you should lol

lost trench
vague rose
#

Im looking into xml

lost trench
#

Can you share only the first stack trace?

vague rose
#

The top one ?

image.png
#

I did

lost trench
#

Do you know what a stack trace is?

#

the file is so big, it's hard to read on mobile phones

#

Can you maybe run a single one of the failing tests?

vague rose
lost trench
#

the stack trace is the actual information about a specific exception

#

the part with An exception occured in thread ... and at ...

vague rose
#

It does not seem to be displayed

#

I rerun the failing test

lost trench
#

Can you find a single one of the failing tests?

#

and just run that one test from IntelliJ

vague rose
lost trench
#

seems like it tried to write to ..\standalone\log\server.log.sendgrid.log but failed at doing that

#

kolgroups.web.common.WebhookHandleController.updateFromSendgrid(WebhookHandleController.java:86)

#

this line means it happened in WebhookHandleController line 86

#

is that one of your classes?

vague rose
#

Hm, should I check permisions for writing in standalone\log

lost trench
#

also check if that directory exists

vague rose
#

I am deploying it on Wildfly

#

It will, once it is deployed

lost trench
#

and server.log.sendgrid.log should be a file or nonexistent

#

This happens when running the tests, right?

vague rose
#

Yes

lost trench
#

are the tests running in Wildfly as well?

vague rose
#

Mhm

lost trench
#

Do the tests have a ../standalone/log directory?

#

Maven typically doesn't use wildfly for running tests

#

unless you are doing weird stuff

vague rose
#

It should not be contained in tests

#

Let me check

lost trench
#

well, it attempts to access it and fails at that

#

that's how you diagnose errors like that - you check the stack trace, look for your classes and check the message

vague rose
#

How can I create a reliable test that I can use before deploying the Wildfly application?

#

Since I can not test logs

lost trench
#

you could make the log file location configurable

#

so that during tests, it logs to a different file

vague rose
#

But more concerning factor

#

is this

lost trench
#

run that single test from IntelliJ without Maven

#

500 (internal server error) typically means some error occured during the request