A customer claims that while redeploying a web application in the production system all their customers are having to log in again. What do you recommend?

Question

Options

• ASessions can't be preserved when redeploying applications.
• BChange the flag responsible for the development mode of their environment.
• CChange Hotspot to JRockit. Sessions can't be preserved on HotSpot when redeploying
• DUse flag version when redeploying the application.
• EOpen a service request with Oracle Support.

• A
  5% (3)
• B
  2% (1)
• C
  13% (7)
• D
  77% (43)
• E
  4% (2)

Explanation

Restrictions on Production Redeployment Updates WebLogic Server can host a maximum of two different versions of an application at one time. * When you redeploy a new version of an application, you cannot change: An application's deployment targets An application's security model A Web application's persistent store settings To change any of the above features, you must first undeploy the active version of the Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application. * (not C) Not dependant on whether the application is JRockit or Hotspot. The production redeployment strategy is supported for: Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP). Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Production redeployment is not supported for: Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server. Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources. Applications that include EJB 1.1 containermanaged persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.

No community discussion yet for this question.