Pega 7.3.1 High Availability issue
Hi All,
I would like to ask for your help regarding Pega High Availability. I'm trying to configure a multi-node Pega 7.3.1 system with High Availability following the Pega 7.3.1 High Availability Administration Guide. The quiesce scenario test is failing as passivated sessions are not restored in the surviving node.
Environment:
I have two Jboss 6.4 EAP instances on my localhost and a shared PostgreSQL database. I'm using Pega 7.3.1 with WAR deployment and OS is Ubuntu 16.04.
After I start both of the application servers then based on the logs Hazelcast cluster seems ok:
Hi All,
I would like to ask for your help regarding Pega High Availability. I'm trying to configure a multi-node Pega 7.3.1 system with High Availability following the Pega 7.3.1 High Availability Administration Guide. The quiesce scenario test is failing as passivated sessions are not restored in the surviving node.
Environment:
I have two Jboss 6.4 EAP instances on my localhost and a shared PostgreSQL database. I'm using Pega 7.3.1 with WAR deployment and OS is Ubuntu 16.04.
After I start both of the application servers then based on the logs Hazelcast cluster seems ok:
server1's log
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (til.HazelcastMembershipManager) INFO - New member joined cluster: Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Members [2] {
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=f9448d8fca317ede15b128a19c691e4c, address=mycomputer/ Proprietary information hidden:5701, uuid=c2c9fcb3-de47-49d1-a8e7-acc9b08ac43c, mode=SERVER] <== THIS node
13:31:25,007 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER] <== NEW node
13:31:25,008 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:25,007 [21c6282be11c.event-2] [ ] [ ] [ ] (.util.ClusterMembershipManager) INFO - }
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - Updated member detail(s)
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - Old identifier = Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:27,890 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,890 [21c6282be11c.event-1] [ ] [ ] [ ] (l.MemberAliasIMapEntryListener) INFO - New identifier = Member: [name=292f5f2b55a80e13dd6448b62035cedf, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
server2's log:
13:31:16,398 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,398 [ mycomputer] [ STANDARD] [ ] [ ] (uster.internal.ClusterProvider) INFO - Initializating Cluster Provider: HazelcastClusterProvider
13:31:16,399 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Name: c4bddd8fd7f1aaaca5d021c6282be11c
13:31:16,399 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Identifier: Default
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Cluster Procotol: HAZELCAST
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Transport Protocol: cluster
13:31:16,400 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Port Range: 5701-5800
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Encryption Enabled: false
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Public Address: Not specified
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - Discovery Timeout: 10 MINUTES
13:31:16,401 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:16,399 [ mycomputer] [ STANDARD] [ ] [ ] (.internal.ClusterConfiguration) INFO - # Discoverable Nodes: 2
13:31:27,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,057 [ mycomputer] [ STANDARD] [ ] [ ] (til.HazelcastMembershipManager) INFO - New member joined cluster: Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER]
13:31:27,061 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Members [2] {
13:31:27,061 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=f9448d8fca317ede15b128a19c691e4c, address=mycomputer/ Proprietary information hidden:5701, uuid=c2c9fcb3-de47-49d1-a8e7-acc9b08ac43c, mode=SERVER]
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER] <== THIS node <== NEW node
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,061 [ mycomputer] [ STANDARD] [ ] [ ] (.util.ClusterMembershipManager) INFO - }
13:31:27,062 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,062 [ mycomputer] [ STANDARD] [ ] [ ] (uster.internal.ClusterProvider) INFO - Successfully joined cluster _hzInstance_1_c4bddd8fd7f1aaaca5d021c6282be11c as Member: [name=SERVER@localhost:5702, address=mycomputer/ Proprietary information hidden:5702, uuid=9a4eee28-5570-4014-8d32-76bf97edc9cb, mode=SERVER].
13:31:27,081 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 13:31:27,080 [ mycomputer] [ STANDARD] [ ] [ ] (internal.PRClusterProviderImpl) INFO - Using system pulse type: cluster
In Pega Designer Studio I also can see cluster members.
Regarding my test scenario I logged into server1 with [email protected] operator and created a new GeneralTask case. After that I initiated "Quiesce" on server1.
New messages in the log of server1:
14:16:07,027 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 14:16:07,026 [http-/ Proprietary information hidden:8180-5] [ STANDARD] [ ] [ ] ( pega.highavailability.quiesce) INFO - [BeginQuiesce] This node has started the quiesce process. Mode: immediateDrain
14:16:22,447 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) 2017-11-23 14:16:22,446 [ Thread-326] [ ] [ ] [ ] ( pega.highavailability.quiesce) INFO - Node has entered state Quiesce Complete
In server2's log there were no any messages.
At this moment I didn't see [email protected]'s session on the requestors tab in Designer Studio.
After that I changed the routing and routed portaluser's requests from server1 to server2. I got the login screen of server2 after I hit the submit button in user portal. There is no SSO configured. (Note: As far as I understood from HA administration guide SSO is not a must. It provides seamless user experience but my HA configuration should work without SSO as well.) So I had to do login with Portaluser but after login I didn't see the previously opened case. Even if I tried to open the given work object then I got a warning message regarding the missing lock.
On the requestors tab I saw a new [email protected] session with new requestorID:
Could you please help me out? What did I miss?
How could I debug my configuration?
Thank you in advance,
Attila
***Updated by moderator: Lochan to mask proprietary information***
***2/2/18: Updated by moderator: Lochan to close post***
Tech Mahindra
IN
Hi,
I would check if the Passivation location is readable by the participating nodes.
In your case, it is a localhost, so I would check the passivation location details properly referred by the nodes' configuration entry (And I am assuming you are using a file system based passivation method!)
Bye.
Saltech Consulting
DE
Hi,
Thanks for your reply!
I didn't configure the passivation method and based on the HA Administration guide database passivation is used as default. So in my view it should be fine, or does it require extra settings?
Regards
Tech Mahindra
IN
Hi Attila,
Not sure, you were able to resolve this issue.
If not, why don't you give a try of the file system based passivation menthod by manually configuring? if it works, at least you will know the HA feature works for you by this and then you could check on the DB way of passivation.
Regards.
Saltech Consulting
DE
Hi,
Sorry for the long silence, I was busy with other tasks.
As you suggested I tried out the file system based passivation method. Unfortunately it doesn't work either. It's strange but the related article("Creating a custom passivation method") is disappeared from PDN. I was able to find this article only in Google cache(https://webcache.googleusercontent.com/search?q=cache:6p6N_czvzLsJ:https://pdn.pega.com/creating-custom-passivation-method/creating-custom-passivation-method+&cd=1&hl=hu&ct=clnk&gl=hu)
I followed the instructions and imported the jar files and added the needed lines to prconfig.xml. When I try to start prweb then I see the following error messages in the log:
Hi,
Sorry for the long silence, I was busy with other tasks.
As you suggested I tried out the file system based passivation method. Unfortunately it doesn't work either. It's strange but the related article("Creating a custom passivation method") is disappeared from PDN. I was able to find this article only in Google cache(https://webcache.googleusercontent.com/search?q=cache:6p6N_czvzLsJ:https://pdn.pega.com/creating-custom-passivation-method/creating-custom-passivation-method+&cd=1&hl=hu&ct=clnk&gl=hu)
I followed the instructions and imported the jar files and added the needed lines to prconfig.xml. When I try to start prweb then I see the following error messages in the log:
2017-12-27 13:25:09.134 INFO net.spy.memcached.MemcachedConnection: Connection state changed for sun.nio.ch.SelectionKeyImpl@2c1f1b37
2017-12-27 13:25:09.134 INFO net.spy.memcached.MemcachedConnection: Reconnecting due to failure to connect to {QA sa=localhost/ Proprietary information hidden:11211, #Rops=0, #Wops=12, #iq=0, topRop=null, topWop=Cmd: 0 Opaque: 1 Key: THREAD:A0CK7SOOW6HMYA10BO916TSTPEZ9434P8/STANDARD/*, toWrite=0, interested=0}
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:369)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:242)
at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:836)
2017-12-27 13:25:09.134 WARN net.spy.memcached.MemcachedConnection: Closing, and reopening {QA sa=localhost/ Proprietary information hidden:11211, #Rops=0, #Wops=12, #iq=0, topRop=null, topWop=Cmd: 0 Opaque: 1 Key: THREAD:A0CK7SOOW6HMYA10BO916TSTPEZ9434P8/STANDARD/*, toWrite=0, interested=0}, attempt 47.
I didn't debug memcached-example yet.
Regards
Tech Mahindra
IN
Hi Attila,
I am not sure what you mean by 'Not working'
However,
1. Did you check the passivation location (mentioned on the config) on file system to see any files and folders are created? If there is, then the other nodes will be able to pick it up from there in case of disasters and resume the case journey of the user when they get re-routed by the webserver to the next available Pega node. Also, I am sure you would have configured a webserver (apache will do) to the available pega nodes / JBoss Servers with the required algorithm (default algorithm will do, to make it simple)
2. Without a single sign-on (SSO) setup, do not expect the load sharing incoming pega node to allow the troubled case operator to get in to the application. In the absence of the SSO, the new Pega node that gets the troubled user will challenge that user to logon, upon successful logon, with the session ID they carry, which is going to be same as before the disaster, provided by the webserver, the new Pega node goes to the passivation location and reconstructs the case data, resumes the case journey to the max extent (per theory) along with the "case resuming blah blah..." message on the operator's browser screen (which you enable on the HA config)
Hope this helps to debug further. Also check if the
Saltech Consulting
DE
Hi Jayakumar,
Thanks again for your answer!
1. At the first look it was not clear where I should set the passivation location. Finally I realized that I can find this setting in prconfig, and it is different from what I tried to achieve with com.pega.example.MemcachedPassivationMechanism which can be set via initialization/persistrequestor/storage/custom/class variable in prconfig. If I am right.
Here is my current prconfig settings:
<env name="initialization/settingsource" value="merged" />
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="security/urlaccesslog" value="NORMAL" />
<env name="security/urlaccessmode" value="WARN" />
<env name="session/ha/Enabled" value="true"/>
<env name="session/ha/crash/RecordWorkInProgress" value="true"/>
<env name="initialization/persistrequestor/storage" value="filesystem" />
<!--env name="initialization/persistrequestor/storage/custom/class" value="com.pega.example.MemcachedPassivationMechanism" /-->
<env name=" storage/class/passivation:/rootpath" value=" /tmp/mypassivation" />
Hi Jayakumar,
Thanks again for your answer!
1. At the first look it was not clear where I should set the passivation location. Finally I realized that I can find this setting in prconfig, and it is different from what I tried to achieve with com.pega.example.MemcachedPassivationMechanism which can be set via initialization/persistrequestor/storage/custom/class variable in prconfig. If I am right.
Here is my current prconfig settings:
<env name="initialization/settingsource" value="merged" />
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="security/urlaccesslog" value="NORMAL" />
<env name="security/urlaccessmode" value="WARN" />
<env name="session/ha/Enabled" value="true"/>
<env name="session/ha/crash/RecordWorkInProgress" value="true"/>
<env name="initialization/persistrequestor/storage" value="filesystem" />
<!--env name="initialization/persistrequestor/storage/custom/class" value="com.pega.example.MemcachedPassivationMechanism" /-->
<env name=" storage/class/passivation:/rootpath" value=" /tmp/mypassivation" />
So my passivation location is /tmp/mypassivation folder on my local machine(where prweb runs). My OSuser has full access(read, write) to this folder and I run tomcat with the same user.
I also copied the following activities into my application ruleset:
- pyPrePassivation
- pyPostActivation
They contain only a Log-Message method step in order to be able to check whether they are called or not.
My test case:
After finish of quiesce process I still send some requests from the user portal to the node in quiesce mode. If I'm correct then because of "immadiate mode" the expected behaviour would be that the given requester data should be passivated after all of the interactions. So I should see that the requestor data is stored in my passivation location.
In the log file I can find the following lines:
2018-01-10 17:09:42,431 [ttp-bio-8080-exec-13] [ STANDARD] [ ] [ ] ( pega.highavailability.quiesce) INFO - [BeginQuiesce] This node has started the quiesce process. Mode: immediateDrain
2018-01-10 17:09:42,446 [ttp-bio-8080-exec-13] [ STANDARD] [ ] [ ] (ePassivation._baseclass.Action) INFO - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:09:57,904 [ Thread-39] [ ] [ ] [ ] ( pega.highavailability.quiesce) INFO - Node has entered state Quiesce Complete
2018-01-10 17:10:09,626 [ttp-bio-8080-exec-11] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:09,888 [ttp-bio-8080-exec-11] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:10,204 [ttp-bio-8080-exec-11] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:10,270 [ttp-bio-8080-exec-11] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:15,679 [http-bio-8080-exec-1] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:16,114 [http-bio-8080-exec-1] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:16,651 [http-bio-8080-exec-1] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:16,758 [http-bio-8080-exec-1] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:16,993 [http-bio-8080-exec-1] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:17,099 [http-bio-8080-exec-1] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:18,309 [http-bio-8080-exec-4] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:18,676 [http-bio-8080-exec-4] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:19,043 [http-bio-8080-exec-8] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:19,165 [http-bio-8080-exec-8] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:19,462 [http-bio-8080-exec-8] [ STANDARD] [ ] [ ] (stActivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPostActivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
2018-01-10 17:10:19,585 [http-bio-8080-exec-9] [ STANDARD] [ ] [ MyApp:01.01.01] (ePassivation._baseclass.Action) INFO localhost| Proprietary information hidden - pyPrePassivation !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!User.MyAppSESSINID: HS5BC3X8G9IZU04HKEBVXQYPC4MQ6LNRO
It looks that the passivation is initiated, at least pyPrePassivation and pyPostActivation activities are called by Pega.
But unfortunately /tmp/mypassivation folder is still empty.
2. Yes, the SSO part is clear and I expect the behaviour what you described.
it seems your last sentence in your comment has been truncated:
"Hope this helps to debug further. Also check if the "
Could you please resend it?
Thanks in advance
Saltech Consulting
DE
UPDATE
I've just noticed that in home directory there is a new folder, its name is a space character(' ') and under this folder I can find my passivation directory.
In my prconfig settings there is a space character before the path of the passivation folder, probably this caused the problem and this is why I didn't find the stored session data in the /tmp folder. So it was my fault, but now I can move forward once I will have time for that.
<env name=" storage/class/passivation:/rootpath" value=" /tmp/mypassivation" />
Pegasystems Inc.
US
Can you also verify that you have the following setting configured?
<env name="session/ha/crash/RecordWorkInProgress" value="true"/>
Saltech Consulting
DE
Hi,
yes, it is true but I set it as Dynamic System Settings and not in prconfig.xml. As far as I know DSS should be ok as well but I'll do a test with prconfig.xml.
Regards