OSB and NodeManager

I have created a OSB 10.3 (doing some archeology work) domain,
when I start ms1 from startManagedWebLogic.sh everything is fine,
when I start with node manager I get a bunch of

"weblogic java.lang.IllegalStateException: zip file closed"

for each deployment, and server fails horribly.

Going up a little in the logs, I find:

weblogic.common.ResourceException: Unknown Data Source cgDataSource

and

weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: com.pointbase.jdbc.jdbcUniversalDriver

I have made sure I was setting JAVA_VENDOR=Sun and JAVA_HOME to Sun jdk in commEnv.sh

I have cleared the tmp, stage and cache directories

In https://kr.forums.oracle.com/forums/thread.jspa?threadID=906756 it suggests to use the hostname rather than localhost in the JDBC configuration XML

Then of course I notice that the pbclient57.jar is not in the classpath as it should be (see the output of the startManagedWebLogic.sh:

CLASSPATH=:/home/orauser/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/orauser/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/orauser/bea/patch_cie670/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/orauser/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/orauser/bea/patch_alsb1031/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/orauser/bea/jdk160_05/lib/tools.jar:/home/orauser/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/home/orauser/bea/wlserver_10.3/server/lib/weblogic.jar:/home/orauser/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/home/orauser/bea/wlserver_10.3/server/lib/webservices.jar:/home/orauser/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/orauser/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/orauser/bea/wlserver_10.3/../modules/features/osb.server.modules_10.3.1.0.jar:/home/orauser/bea/osb_10.3/lib/flow/sb-flow.jar:/home/orauser/bea/wlserver_10.3/../modules/com.bea.core.jaxen_1.0.1.0_1-1-1.jar:/home/orauser/bea/osb_10.3/lib/version.jar:/home/orauser/bea/osb_10.3/lib/alsb.jar:/home/orauser/bea/osb_10.3/3rdparty/lib/j2ssh-ant.jar:/home/orauser/bea/osb_10.3/3rdparty/lib/j2ssh-common.jar:/home/orauser/bea/osb_10.3/3rdparty/lib/j2ssh-core.jar:/home/orauser/bea/osb_10.3/3rdparty/lib/j2ssh-dameon.jar:/home/orauser/bea/osb_10.3/3rdparty/classes:/home/orauser/bea/wlserver_10.3/../modules/com.bea.core.apache.commons.logging_1.1.0.jar:/home/orauser/bea/osb_10.3/lib/transports/jca/jca-binding-api.jar:/home/orauser/bea/osb_10.3/lib/transports/jca/bpm-infra.jar:/home/orauser/bea/osb_10.3/lib/transports/jca/log4j_1.2.8.jar:/home/orauser/bea/osb_10.3/lib/transports/jca/xmlparserv2.jar:%WL_HOME/server/ext/jdbc/oracle/orai18n.jar:/home/orauser/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/orauser/bea/wlserver_10.3/server/lib/xqrl.jar::

)


So really the only way to properly start OSB MS is to set the
"startscriptenabled=true" in the nodemanager.properties.

I have done it and it works.

Paolo Uccello, San Giorgio e il Drago

See also here http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta