EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB441154: After deploying MicroStrategy Library in WebSphere, the application cannot be started


Community Admin

• Strategy


This Knowledgebase Article describes and issue when after MicroStrategy Library WAR file is deployed, the application cannot be started in Websphere

SYMPTOM:
An Administrator sets up Websphere as per https://www2.microstrategy.com/producthelp/10.10/Library/WebHelp/Lang_1033/Content/setup_application_servers.htm?tocpath=Library%20Administration%7CInstalling%20and%20Configuring%20Library%7C_____3 to be able to use Strategy Library.
After the Strategy Library War file has been deployed in Websphere, the application cannot be started. When analyzing the SystemErr.log file, the next entry can be seen:


[6/25/18 21:38:41:563 BST] 0000008c SystemErr     R com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: SRVE8111E: The application, StrategyLibrary, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list [domain=*, name=JSESSIONID, path=/]

STEPS TO REPRODUCE:

  1. Deploy the Out of the Box Strategy War file in WebSphere.
  2. After deployment, try to start the Application from the WAS-Console.

CAUSE:
By default, WebSphere Application server prohibits programmatic configuration of the JSESSIONID cookie which is used by Strategy to track the Application server session. More information can be found in:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/usec_progcookieconfig.html
ACTION:
Remove the cookie from Security > Global security > Programmatic session cookie configuration in the WAS Admin Console. The global security page should look like the following:

ka04W000000OaqHQAS_0EM44000000WUz2.jpeg

  KB441154


Comment

0 comments

Details

Knowledge Article

Published:

June 26, 2018

Last Updated:

January 3, 2019