After deploying a WAR file to a test server and trying to run a j_spring_security_check I get an unauthorized error back and the only trace of the failure is in the ABL Application Log File.
The app works fine on my development machine, but when deployed to a test server it will not work.
Seems like an internet setting causing the problem.
Any help would be greatly appreciated.
62.15:16:08.942/27083 [catalina-exec-6] ERROR c.p.a.s.s.OERealmUserDetailsImpl - Username load error for derekl re: Realm o4gl error: com.progress.open4gl.dynamicapi.SessionPool$NoAvailableSessionsException: SessionPool : NoAvailableSessions[The http protocol connection failed: HTTP client error (403): Forbidden (9990)]
63.15:16:08.942/27083 [catalina-exec-6] WARN c.p.a.s.security.OERealmAuthProvider - User not found: derekl
Hi Irfan,
I found the problem, the section [AppServer.Agent.LT1720Test] was missing all the other properties that are in the [AppServer.Agent] section.
Once I added in the ones from my development machine (which match the [AppServer.Agent] section) it worked.
Thank you for pointing me in the right direction.
Derek
Hi Derek,
The error "No Available Sessions" refers that the agent did not even start. Did you verify if your agent was started successfully, you can find that information in the <PASOE Instance>.agent.log
Hi Irfan,
I believe I have 5 agents running:
The last few lines of the agen log file look like this:
When I compare the logs to my dev machine they look very similar, the difference being in dev it is using the appserver license built in were as in test I am using the Progress Prod AppServer and the OE DataSvrfor MS SQL only.
Hi Irfan, my first response seems to have lost the screen shots, there are 5 AVAILABLE agents, the the end of the agent log file looks like this:
67.[17/03/15@08:32:20.091-0700] P-006660 T-004304 2 AS-10 CONN Database ltracksh Options: (12699)
68.[17/03/15@08:32:20.092-0700] P-006660 T-010144 2 AS-13 CONN Database ltracksh Options: (12699)
69.[17/03/15@08:32:20.092-0700] P-006660 T-006060 2 AS-11 CONN Database ltracksh Options: (12699)
70.[17/03/15@08:32:20.092-0700] P-006660 T-010576 2 AS-12 CONN Database ltracksh Options: (12699)
71.[17/03/15@08:32:20.093-0700] P-006660 T-004304 2 AS-10 CONN Connected to database ltracksh, single user. (9542)
72.[17/03/15@08:32:20.093-0700] P-006660 T-004304 2 AS-10 CONN Dbn:ltracksh Ldb:psi-app user:psi DSN:LT641720Test
73.[17/03/15@08:32:20.093-0700] P-006660 T-010144 2 AS-13 CONN Connected to database ltracksh, single user. (9542)
74.[17/03/15@08:32:20.093-0700] P-006660 T-010144 2 AS-13 CONN Dbn:ltracksh Ldb:psi-app user:psi DSN:LT641720Test
75.[17/03/15@08:32:20.094-0700] P-006660 T-006060 2 AS-11 CONN Connected to database ltracksh, single user. (9542)
76.[17/03/15@08:32:20.094-0700] P-006660 T-006060 2 AS-11 CONN Dbn:ltracksh Ldb:psi-app user:psi DSN:LT641720Test
77.[17/03/15@08:32:20.094-0700] P-006660 T-010576 2 AS-12 CONN Connected to database ltracksh, single user. (9542)
78.[17/03/15@08:32:20.094-0700] P-006660 T-010576 2 AS-12 CONN Dbn:ltracksh Ldb:psi-app user:psi DSN:LT641720Test
79.[17/03/15@08:32:20.225-0700] P-006660 T-004304 1 AS-Aux MSAS Worker Thread exiting. Number: 4, Status: 0
80.[17/03/15@08:32:20.229-0700] P-006660 T-010576 1 AS-Aux MSAS Worker Thread exiting. Number: 6, Status: 0
81.[17/03/15@08:32:20.229-0700] P-006660 T-006060 1 AS-Aux MSAS Worker Thread exiting. Number: 5, Status: 0
82.[17/03/15@08:32:20.230-0700] P-006660 T-010144 1 AS-Aux MSAS Worker Thread exiting. Number: 8, Status: 0
Size
Hi Derek,
What does your RealmURL point to ? If it is pointing to a different PASOE Instance then did you verify if it is up and running.
This is the URI for the server LTTEST01:8910/LumberTrack
I get the same error if I use the IP Address instead of LTTEST01
Clicking on that URI I get the following, with a button to Login at the bottom:
Welcome to Progress Application Server for OpenEdge
Current session:
RemoteUser: null
Principal: null
Session: FE28FF1520B2412EA568E275F6BA2D2F7B50768EFE00.LT1720Test
RemoteAddr: fe80:0:0:0:9d7c:35b4:a01c:5a88%14
ServerName: lttest01.psi.corp
Login: no
Username: anonymousUser
Derek,
Do you see any errors on that PASOE server logs ? Try to access the server using the below URL and see what you get
This would run the default REST Service which is deployed in every OEABL Application. It will run a ping program on the MS-Agent and gives back response.
I get this (with the PROGRESS OpenEdge banner at the top, Progress Application Server underneath):
An error occurred while executing your request!
Forbidden
Okay, If you are running a Production server then you have to enable the transports in openedge.properties.Did you do that ?
I did not change that file manually, what should I change. This is how it looks now:
%% Update from OEManager
%% Mar 15, 2017 9:21:52 AM
##########################################################################
## ##
## Copyright (c) 1998-2014 by Progress Software Corporation ##
## ##
## All rights reserved. No part of this program or document may be ##
## reproduced in any form or by any means without permission in writing ##
## from Progress Software Corporation. ##
## ##
##########################################################################
#
# -------------------- openedge.properties ------------------------------
#
# Property File for the Pacific Application Server for OpenEdge
#
#
# This definition file includes the properties that you can define in
# a Pacific AppServer for OpenEdge.
#
# All information about the properties in this property file may be found
# in the file:
#
# openedge.properties.README.
#
##########################################################################
##
#
# AppServer specific properties
#
[AppServer]
allowRuntimeUpdates=0
applications=LT1720Test
collectMetrics=1
statusEnabled=1
[LT1720Test]
webApps=ROOT,LumberTrack
[LT1720Test.ROOT]
allowRuntimeUpdates=0
collectMetrics=1
statusEnabled=0
[LT1720Test.LumberTrack]
statusEnabled=0
# Transport properties for the REST protocol
[LT1720Test.LumberTrack.REST]
adapterEnabled=1
[LT1720Test.ROOT.WEB]
adapterEnabled=0
defaultCookieDomain=
defaultCookiePath=
defaultHandler=OpenEdge.Web.DefaultWebHandler
srvrAppMode=production
srvrDebug=0
wsRoot=/static/webspeed
[LT1720Test.ROOT.SOAP]
adapterEnabled=0
adminEnabled=1
adminSoapAction=urn:services-progress-com:wsa-admin:01
debugClients=
wsaUrl=http://${psc.as.host.name}:${psc.as.http.port}/soap
wsdlEnabled=1
[AppServer.Agent]
agentMaxPort=62202
agentMinPort=62002
agentShutdownProc=
agentStartupProc=
agentStartupProcParam=
collectStatsData=0
flushStatsData=0
infoVersion=9010
keyAlias=
keyAliasPasswd=
# keyStorePasswd=
keyStorePath=.\keys\
lockAllExtLib=
lockAllNonThreadSafeExtLib=
noSessionCache=0
numInitialSessions=5
PROPATH=${CATALINA_BASE}/openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl
sessionActivateProc=
sessionConnectProc=
sessionDeactivateProc=
sessionDisconnProc=
sessionShutdownProc=
sessionStartupProc=
sessionStartupProcParam=
sessionTimeout=180
sslAlgorithms=
sslEnable=0
usingThreadSafeExtLib=
uuid=
workDir=${CATALINA_BASE}/work
[AppServer.Agent.LT1720Test]
PROPATH=C:\LT\LT17200Test64,${CATALINA_BASE}/webapps/LumberTrack/WEB-INF/openedge,C:\LT\LT17200Test64\src\psi,${CATALINA_BASE}/openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl
sessionActivateProc=
sessionStartupProc=04536spro.r
sessionStartupProcParam=
workDir=C:\LT\LT17200Test64
# Transport properties for the WEB protocol
[LT1720Test.LumberTrack.WEB]
adapterEnabled=1
defaultCookieDomain=
defaultCookiePath=
defaultHandler=OpenEdge.Web.CompatibilityHandler
handler1=SalesOrdersHandler:/v1/SalesOrders
handler2=ShipmentsHandler:/v1/Shipments
srvrAppMode=production
srvrDebug=0
wsRoot=/LumberTrack/static/webspeed
# Transport properties for the SOAP protocol
[LT1720Test.LumberTrack.SOAP]
adapterEnabled=1
adminEnabled=1
adminSoapAction=urn:services-progress-com:wsa-admin:01
debugClients=
wsaUrl=http://${psc.as.host.name}:${psc.as.http.port}/LumberTrack/soap
wsdlEnabled=1
[LT1720Test.ROOT.APSV]
adapterEnabled=0
enableRequestChunking=1
useHTTPSessions=1
#
# Default properties for Session Manager
#
[AppServer.SessMgr]
agentExecFile=${psc.as.oe.dlc}/bin/_mproapsv
agentListenerTimeout=300000
agentLogEntryTypes=
agentLogFile=
agentLoggingLevel=2
agentLogThreshold=0
agentNumLogFiles=3
agentStartupParam=-T "${catalina.base}/temp"
connectionWaitTimeout=3000
idleAgentTimeout=300000
idleConnectionTimeout=300000
idleResourceTimeout=0
idleSessionTimeout=300000
ipver=IPv4
maxABLSessionsPerAgent=200
maxAgents=10
maxConnectionsPerAgent=16
numInitialAgents=1
publishDir=${catalina.base}/openedge
requestWaitTimeout=15000
socketTimeout=3000
[AppServer.SessMgr.LT1720Test]
agentLogEntryTypes=ASPlumbing,DB.Connects
agentLogFile=${catalina.base}/logs/LT1720Test.agent.log
agentStartupParam=-T "${catalina.base}/temp" -pf control\psi-app.pf -U psi -P 20app02 -s 256
collectMetrics=3
[LT1720Test.ROOT.REST]
adapterEnabled=0
# See $CATALINA_HOME/conf/openedge.properties.README for details on the properties below.
# DO NOT MODIFY any ${} tags
# Transport properties for the APSV protocol
[LT1720Test.LumberTrack.APSV]
adapterEnabled=1
enableRequestChunking=1
useHTTPSessions=1
Looks like those files are already enabled, did you restart the server after doing this change ? If you did that and still you were having problems then someone needs to look at your instance and debug it. Please raise a TS case if it did not work even after restart of PASOE Instance.
Other things, I would try to do is to compare PASOE Instance openedge.properties in Production with the one that was working in development environment.
Hi Irfan,
I found the problem, the section [AppServer.Agent.LT1720Test] was missing all the other properties that are in the [AppServer.Agent] section.
Once I added in the ones from my development machine (which match the [AppServer.Agent] section) it worked.
Thank you for pointing me in the right direction.
Derek
> On Mar 15, 2017, at 11:51 AM, Derek Lord wrote:
>
> 71.[17/03/15@08:32:20.093-0700] P-006660 T-004304 2 AS-10 CONN Connected to database ltracksh, single user. (9542)
>
>
note related to your problem, but why are you doing this?
it would be better to connect the agents in multi-user mode and keep the connections open as long as possible.=
The back end is SQL Server, I believe each of the 5 agents are making separate connections to the schema holder. No Progress database involved.