Marek Korczak (Customer) asked a question.
Hi,
I created a project and generated webapp in oe12.1. When deploying it in 12.2 oepas is down with errors like: Connection failure for host .... transport TCP. (9407)
Is it because the deploying mechanism has changed?
Thanks,
Marek
Deploying a 12.1webapp in 12.2 should not lead to connection failures. Can you please add more details? How are you deploying the webapp? Which utility are you using? Are there more detailed errors in any of the instance logs? Adding such details will help us in understanding the problem 🙂
Hi and thanks for your message. I deploy webapp with the command:
pasman deploy -I mypasoe -v %WRKDIR%\CustomerServ.war
and add the cls and i files to mypasoe\openedge directory. Connection to db is established.
The pasoe runs normally but fails just after deploying the app. The same app on oe12.1 runs normally.
The agent log:
........
2020-05-29T10:15:35.994+0200 015792 004440 2 AS-7 mtapsv:-:? AS Starting MSAS Session for mypasoe.
2020-05-29T10:15:35.994+0200 015792 004440 2 AS-7 mtapsv:-:? AS MSAS Session Startup. (5473)
2020-05-29T10:15:37.138+0200 015792 004440 2 AS-7 ?:?:? CONN Database sports2000 Options: (12699)
2020-05-29T10:15:37.144+0200 015792 004440 2 AS-7 ?:?:? CONN Connected to database sports2000, user number 4. (9543)
2020-05-29T10:15:37.146+0200 015792 004440 1 AS-7 ?:?:? MSAS Successfully ran session startup procedure.
2020-05-29T10:15:38.051+0200 015792 015212 1 AS-Listener mtapsv:-:? MSAS Agent Shutting Down. Status: 1000
2020-05-29T10:15:38.055+0200 015792 004440 1 AS-7 ?:?:? -- Connection failure for host MYLEN port 61875 transport TCP. (9407)
2020-05-29T10:15:38.055+0200 015792 004440 1 AS-7 ?:?:? MSAS csMtSendABLSessionInfo : error sending session info to broker : num_user_sessions= 1 err= -4004
2020-05-29T10:15:38.055+0200 015792 004440 2 AS-7 ?:?:? CONN Disconnecting from database sports2000, user number 4. (9545)
2020-05-29T10:15:38.058+0200 015792 004440 1 AS-4 ?:?:? -- Connection failure for host MYLEN port 61875 transport TCP. (9407)
2020-05-29T10:15:38.058+0200 015792 004440 1 AS-4 ?:?:? MSAS csMtSendABLSessionInfo : error sending session info to broker : num_user_sessions= 0 err= -4004
2020-05-29T10:15:38.058+0200 015792 004440 2 AS-4 ?:?:? CONN Disconnecting from database sports2000, user number 2. (9545)
2020-05-29T10:15:38.060+0200 015792 004440 1 AS-Aux-0 mtapsv:-:? MSAS Worker Thread exiting. Number: 4, Status: 0
2020-05-29T10:15:38.073+0200 015792 015212 1 AS-Listener mtapsv:-:? MSAS Agent Shutdown Complete.
In startupError.log:
"C:\WrkOpenEdge122\mypasoe\logs\mypasoe.2020-05-29.log:1:2020-05-29T10:15:13.995+02:00 ERROR [Catalina-utility-1] - o.s.web.context.ContextLoader - Context initialization failed "
"C:\WrkOpenEdge122\mypasoe\logs\catalina.2020-05-29.log:8:2020-05-29T10:15:24.448+02:00 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - One or more listeners failed to start. Full details will be found in the appropriate container log file"
"C:\WrkOpenEdge122\mypasoe\logs\catalina.2020-05-29.log:10:2020-05-29T10:15:24.882+02:00 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - Context [/CustomerServ] startup failed due to previous errors"
In catalina.log there are entries:
2020-05-29T10:15:09.971+02:00 INFO [Catalina-utility-1] o.apache.catalina.startup.HostConfig.deployWAR - Deploying web application archive [C:\WrkOpenEdge122\mypasoe\webapps\CustomerServ.war]
2020-05-29T10:15:24.448+02:00 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - One or more listeners failed to start. Full details will be found in the appropriate container log file
2020-05-29T10:15:24.881+02:00 WARN [Catalina-utility-1] o.a.c.util.SessionIdGeneratorBase.createSecureRandom - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [431] milliseconds.
2020-05-29T10:15:24.882+02:00 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - Context [/CustomerServ] startup failed due to previous errors
2020-05-29T10:15:25.455+02:00 WARN [Catalina-utility-1] o.a.c.loader.WebappClassLoaderBase.clearReferencesThreads - The web application [CustomerServ] appears to have started a thread named [logback-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
So, the webapp started a few threads but failed to stop them. On OE 12.1 it was OK.
Connection failure error looks like a secondary issue. This looks like an issue due to spring version mismatch. Do you see errors similar to the following in localhost.<date>.log file?
You cannot use a spring-security-2.0.xsd or spring-security-3.0.xsd or spring-security-3.1.xsd schema or spring-security-3.2.xsd schema or spring-security-4.0.xsd schema with Spring Security 5.2. Please update your schema declarations to the 5.2 schema.
If yes, you need to regenerate the war file in 12.2. If there are no such errors, please attach full logs directory.
Yes, I see exactly such messages in the log, thanks!
That explains the issue!
All the best,
Marek
Given the fluid nature of security and vulnerabilities, we are required to stay on top of vulnerabilities published and this has led us to update our Spring Security stack for certain releases. However, starting with OpenEdge 12.3, we have removed the Spring configuration files out of oeabl.war and moved it to the instance. That means in the future, upgrading Spring will be much less disruptive. There still may be reasons you need to regenerate you web applications, but then, maybe not.
David Cleary
Connection failure error looks like a secondary issue. This looks like an issue due to spring version mismatch. Do you see errors similar to the following in localhost.<date>.log file?
You cannot use a spring-security-2.0.xsd or spring-security-3.0.xsd or spring-security-3.1.xsd schema or spring-security-3.2.xsd schema or spring-security-4.0.xsd schema with Spring Security 5.2. Please update your schema declarations to the 5.2 schema.
If yes, you need to regenerate the war file in 12.2. If there are no such errors, please attach full logs directory.