- 3,728,037 Users
- 2,245,522 Discussions
- 7,853,258 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.6K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.4K Databases
- 691 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 499 MySQL Community Space
- 10 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 425 SQLcl
- 69 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.7K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.9K Development Tools
- 18 DevOps
- 3K QA/Testing
- 388 Java
- 16 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 3 Java 25
- 14 Java APIs
- 141.2K Java Development Tools
- 15 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 158 LiveLabs
- 36 Workshops
- 13 Software
- 7 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 19 Español
- 1.9K Japanese
- 4 Portuguese
CLI property changed from Boolean to String gives ClassCastException.
User_DE80A
Member Posts: 1 Green Ribbon
Changed CLI property from boolean to String in current Release.
On upgrading servers from previous ICP to current ICP then getting below exception:-
java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String
This is an intermittent issue . Please let us know why the OSGI container's behavior is abrupt.
Sometimes property is considered as String and no exception is received , while sometimes it is treated as Boolean and exception is thrown.
Requirement is it must always be treated as String.