WLS 8.1 issue with .ear deployment ....

I think the weblogic8.1 seems to have some NEW bug now. We have a .ear file that
works just PERFECT in WLS6.1. But now when we try to DEPLOY this .ear file our
WLS8.1 server(via the new look and feel of WLS8.1' console)....we are getting
the Exception like ...."pl read inline below":
...All i know is that WLS 8.1 has introduced something like : "single J2EEC -
EAR compiler, replacing the separate compilers in previous releases" ........is
it may be because of this ????
If somebody has any idea ....please let me know asap ...and just above the EXCEPTION
we are also getting something like ...."Deployment descriptor "/WEB-INF/ups-html.tld"
is malformed" ....what is going wrong now ?
Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
Read inline for the Exception:
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
DTD: Element type "info" must be declared. (line 334, column 9).>
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
(line 335, column 8).>
MessageResourcesFactory.createFactory
java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
java.lang.NullPointerException
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
>
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "service"
failed to preload on startup in Web application: "ABL".
javax.servlet.UnavailableException: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1043)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
thx, sangita

Rob,
These are the 3 files that you need:
1) wlstart_cap (this is the start up script that we use to start the Managed server
while on WLS6.1) ....please read inline:
-----------Inline 1-----------------
#!/bin/ksh
# BEA WebLogic Start Script - Version 1.1
# Add support for STARTMODE MKG 03/08/2002
# Set user specified variables
JAVA_HOME=/usr/j2sdk1_3_1_01
JAVA_OPTIONS="-D$1 -ms128m -mx128m -noclassgc"
BEA_HOME=/opt/bea
WL_HOME=$BEA_HOME/wlserver6.1
WL_SCRIPT=$WL_HOME/config/Subsidiary
export WL_SCRIPT
EXPORT_LIB=$WL_HOME/lib
#### Set locale to US English MKG 2003/01/16
LC_MESSAGES=C
LC_TIME=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_MONETARY=en_US.ISO8859-1
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
export LC_MESSAGES LC_TIME LC_NUMERIC LC_MONETARY LC_COLLATE LC_CTYPE
#### End locale settings
#### UPSCAP-clientmanger App settings --- Begin
# workaround for strange bug in code that requires an x-server
# to be present when graph code is initialized.
# Note that this is my sun workstation. MKG 05/16/2002
DISPLAY=bluewolf.telecom.ups.com:0.0
export DISPLAY
#### UPSCAP-clientmanger App settings --- End
#### EUP App settings --- Begin
VANAPI_HOME=/opt/vanapi
VANPATH=$VANPATH:$VANAPI_HOME/vanapi/share
LD_LIBRARY_PATH=$VANAPI_HOME/vanapi:$VANAPI_HOME/vanapi/vanjavi:$LD_LIBRARY_PATH
PATH=$VANAPI_HOME/perl_dir/bin:$PATH
EUP_CLASSPATH=$WL_HOME/config/Subsidiary/serverclasses
export VANPATH LD_LIBRARY_PATH VANAPI_HOME PATH EUP_CLASSPATH
#### EUP App settings --- End
CLASSPATH=$WL_HOME/lib/CR061106_61sp2.jar:$WL_HOME/lib/CR072612_61sp2.jar:$WL_HOME/lib/CR071109_610sp2.jar:$WL_
HOME/lib/CR058352_61sp2.jar:$WL_HOME/lib/weblogic.jar:$BEA_HOME:$EUP_CLASSPATH
if [ -n "$LD_LIBRARY_PATH" ]; then
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/lib/solaris:
else
LD_LIBRARY_PATH=$WL_HOME/lib/solaris:
fi
export LD_LIBRARY_PATH
ADMIN_URL=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerURL|awk '{print  $2}')
ADMIN_SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerName|awk '{print
$2}')
DOMAIN_NAME=$(cat $WL_SCRIPT/config.weblogic|grep Domain|awk '{print  $2}')
PATH=$WL_HOME/bin:$JAVA_HOME/bin:$PATH
export PATH
WLS_PW=$(cat $WL_SCRIPT/bea.check | awk '{print $1}')
export $WLS_PW
#################################export LOG_HOME=/export/bea/netsite/ext-admin/logs/bea
export LOG_HOME=/export/bea/logs
# echo all of the variable settings
#echo
#echo "BEA_HOME=$BEA_HOME"
#echo "WL_HOME=$WL_HOME"
echo "EXPORT_HOME=$EXPORT_HOME"
echo "CLASSPATH=$CLASSPATH"
#echo "LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
#echo "PATH=$PATH"
#echo "JAVA_OPTIONS=$JAVA_OPTIONS"
#echo "DOMAIN_NAME=$DOMAIN_NAME"
#echo "ADMIN_URL=$ADMIN_URL"
#echo "ADMIN_SERVER_NAME=$ADMIN_SERVER_NAME"
#java -fullversion
#echo
#echo
# Grab some file descriptors.
maxfiles='ulimit -H -n'
if [ ! $? -a "$maxfiles" != 1024 ]; then
if [ "$maxfiles" = "unlimited" ]; then
maxfiles=1025
fi
if [ "$maxfiles" -lt 1024 ]; then
ulimit -n $maxfiles
else
ulimit -n 1024
fi
fi
# Set Production Mode. When set to true, the server starts up
# in production mode. When set to false, the server starts up
# in development mode. The default is false.
STARTMODE=true
if [[ -n $1 ]]; then
if [[ $1 = "admin" ]]; then
echo "Starting admin server...."
###### echo "See /export/netsite/ext-admin/logs/bea/admin.start for more info"
# Change to the WebLogic directory
cd $WL_HOME
echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$ADM
IN_SERVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblogic.Production
ModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
-Dweblogic.ma
nagement.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$ADMIN_SE
RVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblogic.ProductionModeE
nabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
-Dweblogic.managem
ent.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
$LOG_HOME/admin.start 2>&1&
echo
shift
# Change back to the domain directory
cd config/$DOMAIN_NAME
echo $! > admin.pid
else
while [[ $# -gt 0 ]];do
SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep $1|awk '{print $2}')
if [[ $SERVER_NAME = "" ]]; then
echo "ERROR: unable to locate an entry for "$1" in config file"
shift
else
echo "Starting server: "$SERVER_NAME
######### echo "See /export/netsite/ext-admin/logs/bea/$SERVER_NAME.start
for more info"
# Change to the WebLogic directory
cd $WL_HOME
echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Nam
e=$SERVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dw
eblogic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW
weblogic.Server
nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
-Dweblogic.Name=$SE
RVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
-Dweblog
ic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW weblogic.Server
$LOG_HOME/$SERVER_NAME.start 2>&1 &
shift
# Change back to the domain directory
cd config/$DOMAIN_NAME
echo $! > $SERVER_NAME".pid"
fi
done
fi
else
echo ""
echo ""
echo "FATAL ERROR: You must specify the server to start. Either 'admin' or
the server token"
echo ""
fi
-----------Inline 1 ends-----------------
2) startManagedWebLogic.sh(this is the Managed server start up script at wls8.1)
---------Inline 2 starts---------
#!/bin/sh
# This script is used to start a managed WebLogic Server for the domain in the
# current working directory. This script reads in the SERVER_NAME and
# ADMIN_URL as positional parameters, sets the SERVER_NAME variable, then
# starts the server.
# Other variables that startWLS takes are:
# WLS_USER - cleartext user for server startup
# WLS_PW - cleartext password for server startup
# PRODUCTION_MODE - Set to true for production mode servers, false for
# development mode
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and MEM_ARGS)
# JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
# -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java
# For additional information, refer to the WebLogic Server Administration Guide
# (http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html).
#Set the New Java Path
PATH=/opt/bea/jdk141_02/bin:$PATH
# set up WL_HOME, the root directory of your WebLogic installation
WL_HOME="/opt/bea/weblogic81"
# set up common environment
# Set Production Mode. When this is set to true, the server starts up in
# production mode. When set to false, the server starts up in development
# mode. If it is not set, it will default to false.
PRODUCTION_MODE="true"
# Set JAVA_VENDOR to java virtual machine you want to run on server side.
JAVA_VENDOR="Sun"
# Set JAVA_HOME to java virtual machine you want to run on server side.
JAVA_HOME="/opt/bea/jdk141_02"
set USE_CURRENT_JAVA_HOME "$@"
. "${WL_HOME}/common/bin/commEnv.sh"
shift 1
# Set SERVER_NAME to the name of the server you wish to start up.
ADMIN_URL=http://153.2.255.51:8001
SERVER_NAME=
# Set WLS_USER equal to your system username and WLS_PW equal
# to your system password for no username and password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=
WLS_PW=
# Set JAVA_VM to java virtual machine you want to run on server side.
# JAVA_VM="-server"
# Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
# are more than one, include quotes around them. For instance:
# JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
usage()
echo "Need to set SERVER_NAME and ADMIN_URL environment variables or specify"
echo "them in command line:"
echo 'Usage: ./startManagedWebLogic.sh [SERVER_NAME] [ADMIN_URL]'
echo "for example:"
echo './startManagedWebLogic.sh managedserver1 http://localhost:7001'
exit 1
# Check for variables SERVER_NAME and ADMIN_URL
# SERVER_NAME and ADMIN_URL must by specified before starting a managed server,
# detailed information can be found at http://e-docs.bea.com/wls/docs81/adminguide/startstop.html.
if [ ${#} = 0 ]; then
if [ "x${SERVER_NAME}" = "x" -o "x${ADMIN_URL}" = "x" ]; then
usage
fi
elif [ ${#} = 1 ]; then
SERVER_NAME=${1}
if [ "x${ADMIN_URL}" = "x" ]; then
usage
fi
elif [ ${#} = 2 ]; then
SERVER_NAME=${1}
ADMIN_URL=${2}
else
usage
fi
# Start WebLogic server
# Reset number of open file descriptors in the current process
# This function is defined in commEnv.sh
resetFd
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
# Start WebLogic server
echo CLASSPATH="${CLASSPATH}"
echo
echo PATH="${PATH}"
echo
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://<hostname>:<port>/console *"
echo "***************************************************"
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} \
-Dweblogic.Name=${SERVER_NAME} \
-Dweblogic.management.username=${WLS_USER} \
-Dweblogic.management.password=${WLS_PW} \
-Dweblogic.management.server=${ADMIN_URL} \
-Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" \
weblogic.Server
-------Inline 2 ends----------
3) startWebLogic.sh(this is the Admin start up script at wls8.1)
---------Inline 3 starts-------
#!/bin/sh
# This script is used to start WebLogic Server for the domain in the current
# working directory. This script simply sets the SERVER_NAME variable
# and calls the startWLS.sh script under ${WL_HOME}/server/bin.
# To create your own start script for your domain, all you need to set is
# SERVER_NAME, then starts server.
# Other variables that startWLS takes are:
# WLS_USER - cleartext user for server startup
# WLS_PW - cleartext password for server startup
# PRODUCTION_MODE - Set to true for production mode servers, false for
# development mode
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and MEM_ARGS)
# JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
# -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java
# For additional information, refer to the WebLogic Server Administration
# Console Online Help(http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html)
#Set the New Java Path
PATH=/opt/bea/jdk141_02/bin:$PATH
# set up WL_HOME, the root directory of your WebLogic installation
WL_HOME="/opt/bea/weblogic81"
# set up common environment
# Set Production Mode. When this is set to true, the server starts up in
# production mode. When set to false, the server starts up in development
# mode. If it is not set, it will default to false.
PRODUCTION_MODE="true"
# Set JAVA_VENDOR to java virtual machine you want to run on server side.
JAVA_VENDOR="Sun"
# Set JAVA_HOME to java virtual machine you want to run on server side.
JAVA_HOME="/opt/bea/jdk141_02"
set USE_CURRENT_JAVA_HOME "$@"
. "${WL_HOME}/common/bin/commEnv.sh"
shift 1
# Set SERVER_NAME to the name of the server you wish to start up.
SERVER_NAME=Admin
# Set WLS_USER equal to your system username and WLS_PW equal
# to your system password for no username and password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=
WLS_PW=
# Set JAVA_VM to java virtual machine you want to run on server side.
# JAVA_VM="-server"
# Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
# are more than one, include quotes around them. For instance:
# JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
# Reset number of open file descriptors in the current process
# This function is defined in commEnv.sh
resetFd
# Start WebLogic server
CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
export CLASSPATH
"$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
-Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW}
-Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
weblogic.Server
--------Inline 3 ends---------
I think we are getting closer to a solution !
thanks rob,
Rob Woollen <[email protected]> wrote:
Yes, your $CLASSPATH could be the issue. Can you show me the $CLASSPATH
used in each version of the server?
-- Rob
sangita wrote:
Thanks Rob, I understood changing the DOCTYPE ...and i will give ita try.
And iam assuming you might have read my previous response in this chain,Iam using
WLS6.1 & WLS8.1 BOTH on the same hardware unix server....iam just wonderingif
there is any CLASSPATH issue that might have been causing this NoClassDefFoundError......?
just wanted to let you know that iam running WLS6.1 + WLS8.1 on thesame BOX.
I will try other options that you have suggested ....thanks again !
Rob Woollen <[email protected]> wrote:
sangita wrote:
Rob,
Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
definition to the Taglib 1.1 DTD or change the tld file to conformto
the 1.2 DTD. how do i do either of the 2 options ?To change your taglib to be the 1.1 DTD you just need to change the
DOCTYPE header to be
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
"http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
Otherwise, you'll need to change the tld file to be JSP 1.2 compliant.
If you post your tld file here, then I can help.
Iam just guessing here, is it may be due to this DTD/.tld issue thatiam not been
able to DEPLOY the .ear file(now that wls8.1 checks the validity beforedeloying
the app)....are the 2 errors that iam getting, in any ways inter-related?
I'm not sure they're related. It is possible.
i.e is it possible that due to DTD/.tld ....am i getting this NoClassDefFoundError
JUST CURIOUS ???
WELL THANKS FOR YOUR TIME ON THIS ...REALLY APPRECIATE IT !
No problem.
-- Rob
Regards, sangita
Rob Woollen <[email protected]> wrote:
sangita wrote:
1) This is how my .tld looks like:
<?xml version="1.0" encoding="UTF-8" ?>^M
<!DOCTYPE taglib^M
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"^M
"http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">^M
Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
definition to the Taglib 1.1 DTD or change the tld file to conformto
the 1.2 DTD. Unfortunately WLS 6.1 didn't validate the tld file
against
the DTD, but it should have, and you'll need to correct your application.
<taglib>^M
<tlib-version>1.0</tlib-version>^M
<jsp-version>1.2</jsp-version>^M
<short-name>html</short-name>^M
2) the MANIFEST.MF file is located within the ABL.war.
3) I will try placing the struts-util.jar in the WEB-INF/lib directoryof the
ABL.war file. And I will let you if it works or not ?Right. My guess is this is a bug in WLS 8.1. I can see no reasonwhy
the manifest class-path isn't working for you. That's why I askedif
you could send the EAR file so I could investigate, but I understand
that's not always possible.
I suspect the WEB-INF/lib will work, but it's just a workaround.
I'm
not sure if you're using 8.1 or 8.1SP1, but if you're not using SP1,
then you might consider trying that. (java weblogic.version willtell
you.)
Otherwise, I think you should open a case with [email protected]
-- Rob
thx, sangita
Rob Woollen <[email protected]> wrote:
sangita wrote:
Rob, here is the information that you need: Please read inline:
---------------------------iam doing cut&paste
<attribute>^M
<name>styleClass</name>^M
<required>false</required>^M
</attribute>^M
(this is the 334 line)<info>applys the style of
the
number text
if it passes the conditional given</info>^M
</tag>^M
</taglib>^MWell, it looks like you have a JSP 1.1 tld, but it's being validated
against the JSP 1.2 tld. I suspect that you have not declareda
DOCTYPE
and 6.1 defaulted to the older JSP spec.
Anyway, check the first line of your tld file. It should look
something
like this:
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
     "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
I have an ABL.ear file and this is what it looks like:
ABL.ear
META-INF/
META-INF/MANIFEST.MF
ABL.jar
ABL.war
lib/
lib/struts-util.jar
META-INF/application.xml
and in the ABL.war ...there is a META-INF/MANIFEST.MF file ...and
when
i open
this file ...this is what it contains:Just to double-check, the MANIFEST.MF file is located within the
ABL.war, right?
Manifest-Version: 1.0
Created-By: Ant 1.4.1
Class-Path: lib/struts-util.jar
there is nothing in the CLASSPATH that contains this application'sspecific .jar/.war
...or any classes specific to this application ........BOTH IN
WLS6.1(and
now
in WLS8.1)Hmm, I'm not sure yet what the problem is here. Does it work ifyou
place the struts-util.jar in the WEB-INF/lib directory of the ABL.war
file? (I suspect it will.)
This might be a WLS bug. If you can post your ear file here (oremail
it to me rwoollen at bea dot com), then I can dig into it more.
-- Rob
thx, sangita
Rob Woollen <[email protected]> wrote:
It looks like there are 2 errors.
The first error /WEB-INF/ups-html.tld is most likely the result
of
WLS
8.1 doing more validation on your tld file. If you'd show us
either
the
entire ups-html.tld or just the part around line 334, then wecan
help.
As for the NoClassDefFoundError, you'll have to provide some
more
details about your ear file and environment. Do you have anythingin
the $CLASSPATH on either the 6.1 or 8.1 environments?
-- Rob
Sangita wrote:
I think the weblogic8.1 seems to have some NEW bug now. We have
a
.ear
file that
works just PERFECT in WLS6.1. But now when we try to DEPLOY
this
.ear
file our
WLS8.1 server(via the new look and feel of WLS8.1' console)....we
are
getting
the Exception like ...."pl read inline below":
...All i know is that WLS 8.1 has introduced something like
"single
J2EEC -
EAR compiler, replacing the separate compilers in previous releases"........is
it may be because of this ????
If somebody has any idea ....please let me know asap ...and
just
above
the EXCEPTION
we are also getting something like ...."Deployment descriptor
"/WEB-INF/ups-html.tld"
is malformed" ....what is going wrong now ?
Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
Read inline for the Exception:
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248>
<[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
against
the
DTD: Element type "info" must be declared. (line 334, column
9).>
<Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248><[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
against
the
DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
(line 335, column 8).>
MessageResourcesFactory.createFactory
java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
<Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
java.lang.NullPointerException
at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.

Similar Messages

  • WLS 11 Policy migration during EAR deployment

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

    We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
    Can anyone explain this behavior and verify if this is expected?
    Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
    /opt/oracle/admin/snidomain/aserver
    /opt/oracle/admin/snidomain/mserver
    The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
    Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

  • Installing the HCA Solution Accelerator - issue with SNC Deploy

    Hello Everyone -
    I am trying to install the HCA Solution Accelerator, and I am having an issue with the "ant deploy" of the Selection and Capture building block.
    I have configured the ~snc_1_0\install\ant.properties file, but I think I may have missed a setting somewhere because I am getting this build error:
    BUILD FAILED
    C:\Adobe\SolutionAccelerators\human-capital-application.1.0\sa\building_blocks\snc_1_0\ins tall\build.xml:113: The following error occurred while executing this line:
    C:\Adobe\SolutionAccelerators\human-capital-application.1.0\sa\building_blocks\snc_1_0\dep loyer\build.xml:107: The following error occurred while executing this line:
    C:\Adobe\SolutionAccelerators\human-capital-application.1.0\sa\building_blocks\snc_1_0\dep loyer\build.xml:91: Java returned: 1
    Does anyone know off-hand what would cause this particular error?
    I am relatively confident in the path information that I have set for the j2eejar, junit.jar, lcsdk, lc.install.dir as well as the database driver and connection settings.
    I am using a simple turnkey LiveCycle install on a Windows XP OS.
    Any suggestions?
    Thank you in advance,
    Ben Lyons
    *I have attached the entire Build output from the command line as a text attachment in case anyone is interested

    Well, I found a "fix" to this issue - I am just going to post it here in case anyone else encouters a similar issue.
    Apparently, it relates to some sort of error in build.xml file in the ~\snc_1_0\deployer folder.
    The particular line that was causing the build to fail was line 91 of this file, which looks like this:
    <target name="data-purge">
    Line 91 -->            <java classname="com.adobe.solutions.snc.utils.DatabaseExporter" failonerror="false" fork="true"
    classpathref="hibernate.setup.path">
                                                    <jvmarg value="-Dhibernate.bytecode.provider=javassist"/>
                                        <arg line="create-drop ${dist.dir}/hibernate-test.cfg.xml ${database.driver.class} ${database.connection.url} ${database.username} ${database.password}"/>
                                    </java>
                    </target>
    The "failonerror" attribute is by default set to "true", thus an error was occurring, so the build was set to fail.  I changed this to false so that I could build this building block, but doing so has filled me with trepidation that something isn't going to be writing to my database correctly.
    Does anyone know what a failure in this segment of this build.xml file means as far as the built SNC building block?  (Remember this is the build.xml file in the deployer folder and not the install folder).
    In other words - does this mean I should be expecting some kind of lingering error in this building block - and if so, what would that issue most likely be so that I can keep an eye out for it?
    -Ben

  • IBFBS failed to deploy in Embedde OC4J but works with EAR deploy.

    Hi
    When i try to deploy IBFBS sample project in JDevloper by Embedde OC4J : its giving
    an error saying "there is no EJB module to deploy".
    But when i deployed through EAR deployment method its working fine.
    PLease kindly help me.
    Sai.

    Hi,
    Can you pls post the Version of JDeveloper and OC4J that you are using?
    I tried to deploy IBFBS using JDeveloper 9.0.3.988 (JDK 1.3.1) on Standalone OC4J server (9.0.3) and it works fine.
    One constraint for not running the application from JDeveloper (by using embedded OC4J) is that, the OC4J where the FBS is deployed needs to have the -userThreads option enabled.
    This option is enabled by starting OC4J with -userThreads option.
    java -jar oc4j.jar -userThreadsRef : Connection to embedded OC4J per FBS Setup Tutorial-Problem.
    Let us know if your problem still persists.
    Thanks
    -- OTN@IDC Team

  • Applied SP 13 but now have issues with Track deploy

    We recently applied SP 13 to NWDI (we were at SP10).
    I re-imported my track into NWDS, made a change to code and activated it.
    The track was configured to allow auto-deploy to dev runtime.
    While the activation resulted in a successful build by CBS (I checked CBS log) the application was not deployed to the dev runtime.
    I had no issue with this before applying SP 13.
    Any ideas?

    Dean,
    Go to the Landscape configurator in the CMS (http://<hostname>:<port>/devinf/ ).
    Click on the track that is affected and then click on the Runtime Systems tab.
    Is the "Disable automatic deployment" checked? If so, uncheck it.
    Next, take a look at the build request queue, you may have some entries pending.
    http://<hostname>:<port>/TCS/Deployer
    HTH!

  • PXE boot issues with Windows Deployment Services

    I am trying to move from FOG to WDS after running in to serious UEFI issues with FOG.Right now I'm stuck with machines PXE booting to WDS server.I keep getting the message ProxyDHCP service didn't reply to request on port 4011.WDS and DHCP are on different servers. There are plenty of IP addresses available, and they are on the same subnet. I did originally configure DHCP option 60, but deleted that option after troubleshooting. I have configured Windows Firewall to allow inbound and outbound connections on UDP ports 67-69 and 4011 on both DHCP server and WDS server. I have also tried just using IP address in DHCP option 66. As for option 67, I don't even know the right bootfile name to use at this point, figured I'd tackle that if I ever get past this error message.I have tried restarting the WDS service several times, as well as the...
    This topic first appeared in the Spiceworks Community

    After working with many companies in their Office 365 Change Management and End User Adoption strategies, we’ve found that companies who make it fun have very high success rates. So what can you to make it fun?Host an Office 365 Showcase.We’ve helped companies produceOffice 365 Showcases, which have a lively, trade show flair. Kiosks are set up in a cafeteria, meeting room or other convenient location. Hosting each kiosk is a departmental Office 365 Power User who demonstrates a unique aspect of the software to everyone who stops by.Read more about how to make Office 365 Change Management and End User Adoption Fun

  • How to run a pure java application client with ear deployed on 9ias

    Hello all,
    We want to run a pure java application client which is packed with target bean in the same ear file. In the application-client.xml we refer to some EJBs.
    We deployed the ear file which contains ejb jar module and application client module to oracle 9ias 904 through enterprise manager on unix. The jndi.properties we used looks like this
    java.naming.factory.initial=com.evermind.server.rmi.ApplciationClientInitialContextFactory
    java.naming.provider.url=opmn:ormi://opmn_host:opmn_port:oc4j_instance_name/application_name
    java.naming.security.principal=test
    java.naming.security.credentials=test
    Is there anybody knows how to run such an application client? Do we need to provide such a jndi.properties or not at all?
    Thanks,
    9ias user

    Refer OpenEJB User - Oracle ADF Essential and TomEE+
    Also refer Bug in tomee 1.5.2. Fixed in 1.6.
    https://issues.apache.org/jira/browse/TOMEE-756

  • Problems with EAR deployment

    When creating an ear-file (using ant 1.6.3) I get an EAR file that I can perfectly examin with the jar tool, I can even unzip it. All jars within can be unzipped as well. The ear file does contain an META-INF/application.xml file as well as a META-INF/sun-application.xml file but whenever I try to deploy, I get an error indicating that there are problems with the zip file.
    Running the verifier manually on the ear file gives the following:
    STATIC VERIFICATION RESULTS
    NUMBER OF FAILURES/WARNINGS/ERRORS
    # of Failures : 0
    # of Warnings : 0
    # of Errors : 1
    ERRORS THAT OCCURED WHILE RUNNING STATIC VERIFICATION
    Error Name : Could not verify successfully.
    Error Description : java.io.IOException: error in opening zip file
    at com.sun.enterprise.tools.verifier.VerificationHandler.explodeArchive(VerificationHandler.java:189)
    at com.sun.enterprise.tools.verifier.VerificationHandler.init(VerificationHandler.java:121)
    at com.sun.enterprise.tools.verifier.VerificationHandler.<init>(VerificationHandler.java:55)
    at com.sun.enterprise.tools.verifier.Verifier.verify(Verifier.java:74)
    at com.sun.enterprise.tools.verifier.Verifier.main(Verifier.java:53)
    Caused by: java.util.zip.ZipException: error in opening zip file
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(ZipFile.java:204)
    at java.util.jar.JarFile.<init>(JarFile.java:132)
    at java.util.jar.JarFile.<init>(JarFile.java:97)
    at com.sun.enterprise.deployment.archivist.InputJarArchive.getJarFile(InputJarArchive.java:204)
    at com.sun.enterprise.deployment.archivist.InputJarArchive.open(InputJarArchive.java:193)
    at com.sun.enterprise.deployment.archivist.JarArchiveFactory.openArchive(JarArchiveFactory.java:41)
    at com.sun.enterprise.deployment.backend.J2EEModuleExploder.explode(J2EEModuleExploder.java:84)
    at com.sun.enterprise.deployment.backend.J2EEModuleExploder.explode(J2EEModuleExploder.java:59)
    at com.sun.enterprise.deployment.backend.EarExploder.explodeEjbs(EarExploder.java:80)
    at com.sun.enterprise.deployment.backend.EarExploder.explode(EarExploder.java:63)
    at com.sun.enterprise.tools.verifier.VerificationHandler.explodeArchive(VerificationHandler.java:179)
    ... 4 more
    Anyone an idea where to look?

    Are you using SP2? If not, try it, as BEA have fixed some tld-related bugs.
    simon.
    "Mike Dunbar" <[email protected]> wrote:
    >
    I'm having trouble deploying/running my application as an EAR file.

  • Could not load file or assembly issue with SSAS Deployment Wizard

    Hi
    I am getting an error when trying to update 'Data Source Connection Strings' under 'Specify Configuration Properties' of the SSAS Deployment Wizard.
    Unhandled exception occurred: Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0 ...
    Well, it used to be 'version = 10.0.0.0. It changed to version 8 after trying to fix it for hours by googling and so on.
    I just can not make it work. I really need to make it work as I need to use the deployment wizard to deploy the project to the production server. (Looks like this is the only way as the server is not part of domain, just a standalone server hosted on a cloud).
    on top of my head, I remember installing everything under SQL2012 DVD  D:\redist\VSTA.
    Visit Micirosoft site and download components and so on..
    I have two other servers, one with SQL2008R@ and SQL2012. Both are ok. But this server which I want to use it as the production server is causing me an issue. ah...  I can not make it work. Please help me!
    Kind regards

    Hi Dustin
    You do  not need to be concerned if your app references 32 or 64 bit assemblies. VS being 32 bit, needs to reference 32 bit assemblies in order to compile correctly. Thus running the app from the VS IDE, you wil be using 32 bit assemblies. Using a compiled exe or a DLL, the app will use 32 bit or 64 bit assemblies depending on how the app was compiled and "bitness" of the OS.
    E.g;; an app compiled as 32 bit will require 32 bit assemblies
    An app compiled as 64 bit will run 64 bit assemblies - on 64 bit OS only.
    An app compiled as "Any CPU", will run 32 b it or 64 bit assemblies, depending on the OS. On a 64 bit OS, the app will by definition use 64 bit assemblies (but it is up to you to deploy the 64 bit runtime - not the 32 bit runtime). On a 32 bit OS the app will use 32 bit assemblies.
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • Issue with local deployment

    I have been using JDev 11.1.1.2.0 (EJB/JPA).
    My app. has been deployed and running successfully for the first time using integrated WL server.
    When I try to run the app. again after some file modifications, it couldn't deploy the app.
    It threw below error.
    'cannot run integrated WL server, 'null'.
    It was working fine and it has started to happen all of the sudden.
    What could be the issue?
    I can run again for one time if I stop the server and rename the app. in the local deployment directory (system/drs folder). It doesn't allow me to delete the app. I'm getting file is too long for recycle bin error. Any help would be greately appreciated.

    Hi All,
    We are having the same issue on JDeveloper 11.1.1.2.0, with an ADF application to deploy.
    The first deployments went well, but for some reasons the other finished with that log :
    [06:03:49 PM] Running dependency analysis...
    [06:03:49 PM] Deploying 2 profiles...
    [06:03:50 PM] #### Deployment incomplete. ####
    [06:03:50 PM] null
    #### Cannot run application PCASUI due to error deploying to IntegratedWebLogicServer.
    [Application PCASUI stopped and undeployed from Server Instance IntegratedWebLogicServer]I already tried to validate the "Active Changes" on the integrated weblogic console, but nothing happened!
    We are completely stuck here!
    If someone has an idea, please help us on this one!
    Yann
    Edited by: user12288042 on 3 août 2010 23:45

  • Issue with create deployment order with BAPI_POSRVAPS_SAVEMULTI3

    Hi Experts,
      We are trying to create deployment orders with BAPI_POSRVAPS_SAVEMULTI3. The following are the input:
    LOGICAL_SYSTEM                  RR1CLNT010
    ORDER_TYPE                      2
    EXT_NUMBER_ASSIGNMENT
    COMMIT_CONTROL                  E
    PLNG_VERSION                    000
    NO_CREATE
    PLANNING_MODE_USAGE             0
    EVENT_CONTROL                   1
    And for receipts and requirement, we put ATP category as EG and EF.
    But it return error 'Events are supported only for Purchase Requisitions'. For u2018EGu2019 and 'EF', I can see it is category typ '2'.
    Does this BAPI able to create deployment STR or it can only create SNP STR?
    Thanks.
    best regards,
    Wenyan

    Hi Wenyan,
    In the BAPI, the following code should be responsible for the error message:
    * -> check: event_control is only available for purchase requisition
      if event_control = gc_apo_bapi_create_event and order_type <> gc_requisition.
    *   -> error message
        _apo_bapi_message_add_itab0 gc_error gc_apo_bapi_msgclass '342'
        return.
        lv_error = gc_true.
      endif.
    The relevant constants are:
    * -> constants for event control
    CONSTANTS:
      gc_apo_bapi_no_event TYPE bapi10503eventcontrol VALUE space,   "collect but no direct sending
      gc_apo_bapi_create_event TYPE bapi10503eventcontrol VALUE '1',     "collect + send event
      gc_apo_bapi_no_event_collect TYPE bapi10503eventcontrol VALUE '2'. " no collect and no sending
    *--> External Order types
    CONSTANTS:
    *  Bestand
    gc_stock              TYPE /sapapo/r3obj VALUE '0',
    *  Bestellanforderung
    gc_requisition        TYPE /sapapo/r3obj VALUE '1',
    *  Bestellung
    gc_purchase_order     TYPE /sapapo/r3obj VALUE '2',
    As you can see, if you want to create an order other than SNP purchase requistion, you cannot set the control_event as '1'.
    Best Regards,
    Ada

  • Struts, JSP 1.1 spec and WLS 5.1 - issue with useBean and getProperty

    Hi there, I am attempting to compile a JSP page using Struts tag libraries and Weblogic 5.1 with Service Pack 9.I have defined the bean using <jsp:UseBean id="myBean" ... > and then attempt to access its methods using <jsp:getProperty name="myBean" ... > This fails with a 'myBean is not defined as bean' error. When I replace the <jsp:getProperty ...> with a scriptlet e.g. <%= myBean.getCustomerName()%> it compiles and runs just fine.I have read that the WLS server may be enforcing a strict implementation of JSP spec 1.1 which the Struts tags may not be adhering to (?).Oddly, when I start WLS without invoking the Service Pack, the error disappears and the <jsp:getProperty> works as expected!Any official reason for this strange behaviour? ... I'd like to avoid using scriptlets if possible.Thanks in advance,Rash
              

    Hi.
    The following link shows supported versions of apache:
    http://edocs.bea.com/wls/platforms/index.html#apach
    In short, WLS 5.1 does not support Apache 1.3.20. The latest supported version is
    1.3.19.
    Regards,
    Michael
    Mauricio Guerra wrote:
    Hello, i've read all the online documentation regarding the apache plug in for
    weblogic, and i haven't
    found an answer to my question:
    Does weblogic 5.1 sp8 works ok with apache 1.3.20/SSL?
    All the documentation talks mention apache 1.3.12 only...
    thanks,
    Mauricio--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Issue with data/deploying

    What I do this I create a new user following with a new location and module.
    Then I import(imp user/pass@orcl file=location full=y) my .dmp file. And everything seems to be working.
    Then I import my data into OWB, I get everything I need. I check the data by (right-click data) and everything is fine, the tables are inserted with data.
    Then I try to deploy the new tables, with action(create) I get 2 erros CREATE - (tablename is already in use) DROP - Cannot because of FK etc. (I guess it tried to create one table then couldnt then tried to drop it)
    My second action then is (replace) which leads me to my deploy sucess and then all of my data is missing. The tables are empty..
    My question is how can I deploy without losing my data..
    Cheers

    Typically you would import the metadata from the source location and either use that location as the data source (and so not need to redeploy), or deploy it to a separate target location.
    The replace action is destructive as you've found, and effectively performs a drop table followed by create table. Hence any data in the table is lost.
    If you just want the Control Center Manager to correctly display that the table is deployed, try setting the action to "Upgrade". This will try to upgrade the deployed object to match the definition in OWB, but as the two are identical this will result in no changes. However, it will update the deployment records to indicate that the object is deployed.
    Nigel.

  • Problem with EAR deployment

    hi,
    i am getting following error while deploying ear application in WAS
    an 10, 2008 11:29:26 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [018]Deployment aborted
    Settings
    SDM host : javadev0002
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/MOBILE1/LOCALS~1/Temp/temp44178ProcurmentEAR3.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/MOBILE1/LOCALS~1/Temp/temp44178ProcurmentEAR3.ear
    Aborted: development component 'ProcurmentEAR3'/'sap.com'/'localhost'/'2008.01.10.11.28.46'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/ProcurmentEAR3.. Reason: Errors while compiling:C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:80: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:87: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:94: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:185: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:192: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:199: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:281: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:288: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:295: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:369: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:376: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:456: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:463: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:79: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:86: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:175: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:182: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:189: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:262: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:269: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:349: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:356: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:436: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:443: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:527: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:534: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    26 errors
    ; nested exception is:      com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:80: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:87: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:94: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:185: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:192: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:199: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:281: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:288: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:295: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:369: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:376: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:456: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSessionHome_Stub.java:463: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:79: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:86: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:175: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:182: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:189: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:262: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:269: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:349: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:356: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:436: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:443: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:527: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/ProcurmentEAR3/EJBContainer/temp/temp1199944747075/in/mobileone/www/SourcesofSupplyEJB/SoSRetrieveSession_Stub.java:534: cannot resolve symbol
    symbol  : method getCategory ()
    location: class com.sap.engine.services.rmi_p4.log.P4Logger
                             if(com.sap.engine.services.rmi_p4.log.P4Logger.getCategory().beDebug()){
                                                                                    ^
    26 errors
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi Guruvulu,
    I think the ear and war has not been successfully build.
    Please build the war and ear successfully. Warning can be skipped.
    Also try to restart your application server once before deployment and check whether all the process are running successfully.
    Hope this will help you!!!
    Regards,
    Prashil

  • Performance issue with OC4J-deployed web service

    I have a web service that can take anywhere from milliseconds to hours to execute, depending on the data set. I also have a "main" for this service to allow me to invoke it outside of the OC4J environment. When run through the main routine with a particular data set, it takes about 13 minutes to complete. When run through the web service, it takes nearly an order of magnitude longer.
    I assume that somehow OC4J is throttling my web service. Is there any way to tell it not to do this? If necessary, I can have my service invoke this work by firing off a separate java process that invokes my main routine, but I'd rather not introduce that complexity.
    I don't know if it's important, but in both cases I'm starting things in from JDeveloper. In the case of using "main" I launch the application through the debugger. In the case of OC4J, I launch the application server with the "Debug Server Instance" icon and then kick off my web service with a browser.

    Hi,
    To solve the error "no portal in java_library_path" make the following actions:
    1. Obtain the file "libportal.so" from the server where yo have installed BRM. This file is found at $PIN_HOME/lib
    2. On BIP server create a folder that can be accessed by the BIP user. In my case, I created folder "brm_lib" located at $BIP_HOME
    3. Copy the file "libportal.so" into the folder created in previous step.
    4. For BIP user's instance, create the environment variable $LD_LIBRARY_PATH with its value the folder created in step 2
    5. Restart OC4J server. Test the WS again, it should work!!.
    Regards

Maybe you are looking for