Following issues were coming on migrating from JacORB 2.2.3 to 2.3.0. After putting orb.properties (for implname property) and adding directory property to orb.properties, things are working: Request and Responses are getting through.

issue#1: servers were not getting up

- had to supply implname property. The orb.properties to be placed in jre/lib has this property with a default value.

jacorb.implname=StandardImplName

issue#2:

_nsdb_root*** files are getting generated when namingServer is killed. These files are getting created on the install-root.

Issue: There is a requirement to modify the classpath at runtime.

Solution: I have seen a lot of forum posts about how to modify the classpath at runtime and a lot of answers saying it can't be done. I needed to add JDBC driver JARs at runtime so I figured out the following method.

The system classloader (ClassLoader.getSystemClassLoader()) is a subclass of URLClassLoader. It can therefore be casted into a URLClassLoader and used as one.

Issue: This error occurred in my project when we migrated to JDK5 from JDK4; and also updated the Xalan version from 2.3.0 to 2.7.0.

For developers who will have the same problem as me: I have just discovered the reason of my problem: XSLTC does not like the big stylesheets!

So, I will have to choose another library to transform my XML files. I don't understand why Sun has chosen such a library, even if it provides a quick transformer. My stylesheet is not so big (10 Ko).

SQl to query the DB Server Version:

select * from nls_database_parameters where parameter = 'NLS_RDBMS_VERSION';

Issue:

[Thread-8-29876954-6906832] ERROR: The following system-level error occurred:java.lang.OutOfMemoryError: PermGen space[Thread-8-29876954-6906832] ERROR: Stack trace:java.lang.OutOfMemoryError: PermGen space

Discussion: This issue shows up when too many class are loaded and unloaded from the JVM. Quick solution is to check whether number of classes being loaded and unloaded at a time can be reduced. Or, update the JAVA_OPTS by adding "MaxPermSize" parameter.

Issue: We are migrating from Xalan 2.3.0 to 2.7.0. Getting the following error in the application logs while running a transformation: Server-side Exception: java.lang.Error: java.lang.ClassFormatError: Invalid method Code length 171489 in class file com/xyz/qwr/TRxml2SRxml.

Discussion: Currently, the transformation .xsl stylesheets are compiled into Java bytecode and this compiled form (also called translet) is used for transforming XML data.
Loading