Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

What's New

• Chapter 2, "Installation and Upgrade Issues"

1 Introduction

• 1.1 Latest Release Information
• 1.2 Purpose of this Document
• 1.3 Operating System Requirements
• 1.4 Certification Information
• 1.5 Licensing Information

2 Installation and Upgrade Issues

• 2.1 Installation Issues
  • 2.1.1 Java Access Bridge
• 2.2 Upgrade Issues
  • 2.2.1 Additional Data Source Requirement for OEMS JMS Database Applications
• 2.3 Documentation Errata
  • 2.3.1 Incorrect Reference to Installation Media
  • 2.3.2 Incorrect Command for Finding Processor Speed

3 General Management and Security Issues

• 3.1 General Issues and Workarounds
  • 3.1.1 Limited Management Support for Multiple-JVM OC4J Instances
  • 3.1.2 OC4J Restart Required When Changing the Name or URL of a JDBC Data Source or Connection Pool
  • 3.1.3 Problem Removing a Property from a Native Data Source
  • 3.1.4 Important Restriction When Setting Thread Pool Size on the Thread Pool Configuration Page
  • 3.1.5 Use the Cluster Topology Page to Restart the OC4J Instance
  • 3.1.6 TopLink Sessions Not Available in Application Server Control Console
  • 3.1.7 Unable to Receive MBean Notification Using OPMN to Start or Stop OC4J
  • 3.1.8 Using the Java Server Pages Standard Tag Libraries
  • 3.1.9 Error While Generating Web Service
  • 3.1.10 Problem with Deployment of non-English Character Java Server Pages
  • 3.1.11 RMD Conditional Does Not Fully Evaluate
  • 3.1.12 Additional Step Required When Configuring ODL Logging for Oracle HTTP Server
• 3.2 Clustering and Replication Issues
  • 3.2.1 State Replication Framework
  • 3.2.2 Using Oracle Universal Installer Provided Sample Cluster Discovery Address May Inadvertently Cluster Servers
  • 3.2.3 Configuration of Oracle Application Server Clusters
• 3.3 Documentation Errata
  • 3.3.1 Incorrect Recommendation for opmn.xml File Edit
  • 3.3.2 Incorrect Default Value for start-mode Element in Oracle HTTP Server opmn.xml file
  • 3.3.3 Incorrect Remote Security Cross Reference

4 Oracle HTTP Server

• 4.1 Documentation Errata
  • 4.1.1 Default Values for Oc4jCacheSize
  • 4.1.2 UseOutputStreamSize

5 Oracle Containers for J2EE

• 5.1 Configuration, Deployment, and Administration
  • 5.1.1 Deprecated Environment Variables dedicated.connection, dedicated.rmicontext, and LoadBalanceOnLookup
  • 5.1.2 Deprecated Environment Variable ejb.batch.compile
  • 5.1.3 Deprecated orion-ejb-jar.xml Attributes
  • 5.1.4 Web-Site-Related Options No Longer Available
  • 5.1.5 Unsupported Methods in JMX MBeanServer and MBeanServerConnection Interfaces
  • 5.1.6 Upgrade to Latest JDK Release
  • 5.1.7 Workaround for ORA-604/ORA-12705 Error Using a Not-Fully Supported Locale
  • 5.1.8 Incompatibility When Moving Between JDK 1.5 and 1.4
  • 5.1.9 Configuring a Machine to Work With and Without a Network Connection
  • 5.1.10 Converting Pre-10.1.3 Data Sources to 10.1.3 Format
  • 5.1.11 Xalan Library Not Supported as a Shared Library with JDK1.4
  • 5.1.12 Recommendation for <cluster> Element write-quota Setting
  • 5.1.13 The oracle.home and oracle. j2ee.home System Properties
  • 5.1.14 Maximum Threads in Work Manager Thread Pool
  • 5.1.15 Configuring Multicast Discovery with opmnassociate
  • 5.1.16 Downgraded JDK and <java-compiler> in server.xml
  • 5.1.17 Configuration of Application Mount Points
  • 5.1.18 Hot Deployment in OC4J
    • 5.1.18.1 Deployment of Applications
    • 5.1.18.2 Deployment of Shared Libraries
• 5.2 Release Notes for Servlets
  • 5.2.1 Servlet Invocation by Classname Disabled by Default
  • 5.2.2 Physical File Required for Welcome File
  • 5.2.3 Warning Issued for servlet.init() Not Working with run-as
  • 5.2.4 Request Parameters Not Available During Filter Execution
  • 5.2.5 The default-charset Setting Does Not Apply to Servlets
  • 5.2.6 Form Authentication Filter
• 5.3 Release Notes for EJB
  • 5.3.1 EJB 3.0 Support
  • 5.3.2 Orion CMP is Deprecated
  • 5.3.3 Orion CMP and Non-Oracle Databases
  • 5.3.4 Stateful Session Bean Replication Trigger Configuration
  • 5.3.5 EJB 3.0 Entities and Application Server Control
  • 5.3.6 Entity and Session Deployment Attribute tx-retry-wait
• 5.4 Release Notes for Web Services
  • 5.4.1 Long File Names Cause Deployment to Fail
  • 5.4.2 SoapFaultException Will Not Invoke a Handler's handleFault Method
  • 5.4.3 Clients Cannot Deserialize SOAP-Encoded anyType Arrays
  • 5.4.4 Arrays in Document-Literal Encoding May Not be Supported when Mapped to a Single Array Parameter
  • 5.4.5 NLS Characters in SYS.XMLTYPE Values May Not be Supported
  • 5.4.6 Self Referential WSDL Imports Fail to Load in the Test Page
  • 5.4.7 SOAP 1.2 Results May Not be Properly Deserialized
  • 5.4.8 WSIF Mapping of Nillable XSD Types
  • 5.4.9 Support for NLS Characters in the WSDL
  • 5.4.10 Multiple Service Elements in Top Down Web Service Assembly
  • 5.4.11 Multiple Message Formats in a WSDL Application
  • 5.4.12 Invalid Configuration Not Detected for EJB 2.1 Web Services
  • 5.4.13 Schema Features Limitations
    • 5.4.13.1 Schema Features that are Mapped to a SOAPElement
    • 5.4.13.2 Derived complexTypes Are Not Handled Properly
    • 5.4.13.3 RPC Encoded Does Not Support Complex Types With Attributes
    • 5.4.13.4 XML Types xsd:choice and xsd:group are Not Supported for Proxy or Top Down Web Service Assembly
  • 5.4.14 Limitations on Top Down Processing of Type Mappings
  • 5.4.15 REST-Enabled Web Services Cannot be Deployed with Application Server Control
  • 5.4.16 Explicit HTTP Data Chunking is Not Supported
  • 5.4.17 Runtime Exception Masked By java.io.NotSerializableException
  • 5.4.18 Get NodeLists by Using getFirstChild and getNextSibling Instead of getChildNode
  • 5.4.19 Performing Client Call-out to Web Services from the Database
    • 5.4.19.1 How to Perform Web Services Call-Out using Static Proxy and JPublisher
    • 5.4.19.2 How to Perform Web Services Callout using Dynamic Invocation Interface and the SYS.UTL_DBWS Utility
• 5.5 Release Notes for Web Services Security
  • 5.5.1 Stale Indirect User Accounts Must be Removed Manually
• 5.6 Release Notes for OC4J Services
  • 5.6.1 JNDI
    • 5.6.1.1 New Package Names for RMI and Application Client Initial Context Factories
    • 5.6.1.2 These Environment Properties Are No Longer Supported
    • 5.6.1.3 Context Factory Restructuring
    • 5.6.1.4 Objects that Implement javax.naming.Referenceable Interface
  • 5.6.2 Oracle Enterprise Messaging Service (OEMS)
    • 5.6.2.1 Special Considerations For Undeploying the Default Instance of the Oracle gJRA Resource Adapter
    • 5.6.2.2 OC4J May Fail to Restart after Abnormal OC4J Shutdown
    • 5.6.2.3 getconfigProperties() Lists Some Unsupported Properties
    • 5.6.2.4 XA-styled JMS Connections Not Supported Between OC4J Versions
  • 5.6.3 Data Sources
    • 5.6.3.1 New Syntax for Data Source Configuration
    • 5.6.3.2 OracleConnectionCacheImpl Deprecated
    • 5.6.3.3 Converting Existing Data Sources to Release 3 Format
    • 5.6.3.4 SQLServer Named Instance Definition Corrected
    • 5.6.3.5 Use the Current Oracle JDBC Drivers when Using Shared Libraries
    • 5.6.3.6 Fast Connection Failover Is Disabled When Using OracleXADataSource
  • 5.6.4 OC4J Transaction Support
    • 5.6.4.1 Change the Default JTA Recovery Password Immediately
    • 5.6.4.2 New Configuration File for Transaction Manager
    • 5.6.4.3 The In-DB Coordinator Is Deprecated
    • 5.6.4.4 The Mid-Tier Coordinator Does Not Use a Persistent Store By Default
    • 5.6.4.5 DMS must be enabled to obtain JTA statistics
    • 5.6.4.6 Transaction Propagation Between 10.1.3 Instances Only
  • 5.6.5 RMI
    • 5.6.5.1 RMI Recommendations
    • 5.6.5.2 Excessive ORMI Connections Created
    • 5.6.5.3 Workaround for HTTP Tunnelling Failover
    • 5.6.5.4 Incorrect "Provider URL..." Error Message
  • 5.6.6 XQS
    • 5.6.6.1 Implementation Restriction on the fn:doc() and fn:collection() Functions
• 5.7 Release Notes for J2EE Connector Architecture (J2CA)
  • 5.7.1 J2CA Lifecycle Issues
  • 5.7.2 Cannot Cast a Connection Handle to a Concrete Type
  • 5.7.3 RAR Name Must Be Unique
  • 5.7.4 Set inactivity-timeout-check in oc4j-ra.xml
  • 5.7.5 Revised Release Note - Stop the Resource Adapter Before Redeploying or Undeploying It
  • 5.7.6 Explicit Configuration Is Necessary For Resource Adapter To Support XA Transaction Recovery
  • 5.7.7 ASControl Changes to Work Manager Thread Pool Not Persisted If <work-manager-thread-pool> Not Defined
• 5.8 Release Notes for OracleAS JAAS Provider and Security
  • 5.8.1 COREid Status for 10.1.3.0.0
  • 5.8.2 Restart Application After Configuring Through Security Provider MBean
  • 5.8.3 Necessary Permission Grants When Using Security Manager
  • 5.8.4 Indirect Users for Password Indirection
  • 5.8.5 JAAS Policy Configuration with Custom Realms
  • 5.8.6 User Manager Delegation for the File-Based Provider
  • 5.8.7 JNDI Context Pool Timeout Property for Oracle Internet Directory
  • 5.8.8 Miscellaneous OracleAS JAAS Provider and Security Release Notes
  • 5.8.9 Signature Verification Fails for X.509 Token-Based Authentication On Windows Platforms
  • 5.8.10 J2EE SSO Is Deprecated in the OC4J 10.1.3.0 Implementation
  • 5.8.11 Basic Authentication Fallback for Digest Authentication Module
• 5.9 Release Notes for Documentation Errata
  • 5.9.1 Web Services Documentation Errata
    • 5.9.1.1 WebServicesAssembler Command genInterface Does Not Use the use and style Arguments
    • 5.9.1.2 Error in Ant Task for Assembling JMS Web Services
  • 5.9.2 Oracle Application Server Advanced Web Services Developer's Guide Documentation Errata
    • 5.9.2.1 Auditing and Logging File Path Corrections
  • 5.9.3 Oracle Containers for J2EE Services Guide
    • 5.9.3.1 Incorrect URL in Native Data Source Example for Fast Connection Failover
    • 5.9.3.2 Correction to the OEMS JMS Database Certification Matrix Table
    • 5.9.3.3 SQLServer Named Instance Definition Corrected
    • 5.9.3.4 Correction to ORMI Tunneling URL
    • 5.9.3.5 Missing Tables in Transaction Support Chapter
    • 5.9.3.6 Packager Flag to Prevent Generation of Web Services Web Module
  • 5.9.4 Oracle Containers for J2EE Developer's Guide Documentation Errata
    • 5.9.4.1 Import Example Only for Thin JDBC Drivers
  • 5.9.5 Oracle Containers for J2EE Security Guide Documentation Errata
    • 5.9.5.1 Correct Package Name for getUserPrincipal() and getCallerPrincipal()
• 5.10 Oracle Application Server Containers for J2EE Job Scheduler
  • 5.10.1 Invalid Data Source Configuration May Result in Initialization Exception
  • 5.10.2 Cancel API is not Transactional
  • 5.10.3 Lower Than Expected Throughput may be Experienced for Large Number of Jobs
  • 5.10.4 Removing a Job May Impact Job Scheduler Event Listener Processing
  • 5.10.5 Preemptory Shutdown of OC4J Container may Prevent Subsequent Restart

6 Oracle Application Server Portal

• 6.1 General Issues and Workarounds
  • 6.1.1 Ensure Correct JDK Version in Compiler Settings
• 6.2 Portlet and Provider Issues and Workarounds
  • 6.2.1 Error Configuring OC4J Standalone for OmniPortlet Deployment
• 6.3 Documentation Errors
  • 6.3.1 Edit Defaults Mode

7 Oracle TopLink

• 7.1 General Issues and Workarounds
  • 7.1.1 Links to Hosted Documentation and Web-Based Resources from TopLink Workbench
  • 7.1.2 Using Non-ASCII Characters with a JAXB 1.0 TopLink Project
  • 7.1.3 TopLink Workbench Look and Feel With Linux GTK
  • 7.1.4 Unit of Work and JTA Transactions

8 Oracle Business Rules

• 8.1 Windows File Sharing and File Repositories
• 8.2 Using RL Reserved Words in Java Package Names
• 8.3 Ancestor Methods are not Visible from Sub-Classes
• 8.4 New and Deleted Patterns are not Immediately Available
• 8.5 Changes to the Bind Variable Name are not Immediately Reflected
• 8.6 Refreshing Imported Java Facts After Changing the Underlying Classes

9 OracleAS Disaster Recovery

• 9.1 General Issues and Workarounds
  • 9.1.1 Adding an Instance from a Remote Client Adds an Instance on the Local Instance and Not on the Remote Instance
  • 9.1.2 Switchover Operation in an Asymmetric Topology Requires All Components to be Shutdown on Instances on the Primary Site that Do Not Have a Standby Peer

10 Oracle Sensor Edge Server

• 10.1 Installation and Configuration Issues
  • 10.1.1 Valid 10.1.3 OC4J in Correct Oracle Home Required for Oracle Sensor Edge Mobile
  • 10.1.2 OC4J 10.1.2 Must be Stopped if Installing Against It
  • 10.1.3 Default Database Tablespaces
  • 10.1.4 Oracle Sensor Edge Server Installation Fails
  • 10.1.5 Resolving the Reboot Issue for XML Configuration
• 10.2 General Issues
  • 10.2.1 Using UTL_EDG.REMOVE_RULE Displays an Error
  • 10.2.2 Adding a Rule Displays an Error
  • 10.2.3 Localization -- Navigation Tree in the SES Console Renders as the Server Locale-Defined Character Set
  • 10.2.4 Reassignment of Audio Event Type (207)
• 10.3 Documentation Issues
  • 10.3.1 Documentation for Oracle Sensor Edge Server Extensions
  • 10.3.2 Manually Deploying Sensor Data Streams Against an Existing Sensor Data Repository