Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

mbpro scripts fails when executing a .p that uses the ClientConnect feature (-SMQCONNECT)

Same procedure works fine when executed from "mpro -b"

jvmStart returned an error. (12670)

Error connecting to the JMS AppServer service.

FACT(s) (Environment):

OpenEdge 10.1x

CAUSE:

The problem is that the mbpro script does not set the java environment.

CAUSE:

Bug# OE00136021

FIX:

Upgrade to OpenEdge version 10.1B01 or later.
There are two ways to workaround this problem:
1. Use "mpro -b" instead of mbpro.
2. Modify mbpro to set the java environment. The modified mbpro script should look like the following script below. Ensure that you change the script to reflect your DLC location.
#!/bin/sh
DLC=${DLC-/usr/dlc};export DLC
PROEXE=${PROEXE-$DLC/bin/_progres}
ICU_DATA=${ICU_DATA-$DLC/lib/icu/data/};export ICU_DATA
# set the Progress shared lib environment
if [ ! -f $DLC/bin/slib_env ]
then
echo "Progress $PROG Messages:"
echo
echo "slib_env could not be found."
echo
echo "Progress shared library environment not set correctly."
echo "Progress DLC environment variable may not be set correctly."
echo "Set DLC variable to Progress installation directory."
echo
echo "Progress DLC setting: $DLC"
echo
echo
exit 1
fi
# Set the Progress Shared lib environment
. $DLC/bin/slib_env
# Set Java environment for Java-based Debugger
if [ ! -n "$JREHOME" ]
then
# Make sure that the script exists
if [ -f $DLC/bin/java_env ]
then
. $DLC/bin/java_env
PATH=$JREHOME/bin:$PATH
fi
fi
echo Batch processing will be performed using:
cat $DLC/version
echo
trap "" 1
$PROEXE -b "$@" 2>&1 &