URGENT*** Test Client testpoint not generated in WebLogic 10.3.0.0

Hi,
I have created very basic "Java EE 1.5 with support for jax-ws Annotations" web service and deploying in to web logic server 10.3.0.0. I am using Jdeveloper 11g for convert my java file to web service and deploying the same in to WLS directly from Jdev IDE.
Problem is, I cant able to see "Test Client" testPoint in order to test my webservice. When I access my web service via WLS admin console can able to see only "?WSDL" test point at TESTING tab and WSDL is accessible. But Test client is not getting generated.
Please help me, what am I missing here, why the WLServer not generating the test client. Am I missing any setting at server side. Please help me. Below is my web service code.
package edu.ws;
import javax.jws.WebService;
*@WebService(serviceName = "demoWS", portName = "demoWSSoapHttpPort")*
public class demoWS
public demoWS()
public String fullName(String fn, String ln)
String fullName = fn + ln;
return fullName;
WSDL file:
*<!--*
Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Oracle JAX-WS 2.1.3-07/10/2008 08:41 PM(bt).
-->
*<!--*
Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is Oracle JAX-WS 2.1.3-07/10/2008 08:41 PM(bt).
-->
*<definitions targetNamespace="http://ws.syu.edu/" name="demoWS">*
*<types>*
*<xsd:schema>*
*<xsd:import namespace="http://ws.syu.edu/" schemaLocation="http://192.168.88.131:7001/DemoWebService-DemoWS-context-root/demoWSSoapHttpPort?xsd=1"/>*
*</xsd:schema>*
*</types>*
*<message name="fullName">*
*<part name="parameters" element="tns:fullName"/>*
*</message>*
*<message name="fullNameResponse">*
*<part name="parameters" element="tns:fullNameResponse"/>*
*</message>*
*<portType name="demoWS">*
*<operation name="fullName">*
*<input message="tns:fullName"/>*
*<output message="tns:fullNameResponse"/>*
*</operation>*
*</portType>*
*<binding name="demoWSSoapHttpPortBinding" type="tns:demoWS">*
*<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>*
*<operation name="fullName">*
*<soap:operation soapAction=""/>*
*<input>*
*<soap:body use="literal"/>*
*</input>*
*<output>*
*<soap:body use="literal"/>*
*</output>*
*</operation>*
*</binding>*
*<service name="demoWS">*
*<port name="demoWSSoapHttpPort" binding="tns:demoWSSoapHttpPortBinding">*
*<soap:address location="http://192.168.88.131:7001/DemoWebService-DemoWS-context-root/demoWSSoapHttpPort"/>*
*</port>*
*</service>*
*</definitions>*
Thanks
klogube

Hi LJ,
I did the same. I configured my WLS for development mode by making production_mode = false. But still I cant able to open http://localhost:7001/wls_utc window and so far cant able to test my WS :(
Please check my config file and let me know where else I suppose to make the production mode false!!
#!/bin/sh
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
# --- Start Functions ---
BP=100
SP=$BP
pushd()
     if [ -z "$1" ]
     then
          return
     fi
     SP=`expr $SP - 1`
     eval _stack$SP=`pwd`
     cd $1
     return
popd()
     if [ $SP -eq $BP ]
     then
          return
     fi
     eval cd \${_stack$SP}
     SP=`expr $SP + 1`
     return
# --- End Functions ---
# This script is used to setup the needed environment to be able to start Weblogic Server in this domain.
# This script initializes the following variables before calling commEnv to set other variables:
# WL_HOME - The BEA home directory of your WebLogic installation.
# JAVA_VM - The desired Java VM to use. You can set this environment variable before calling
# this script to switch between Sun or BEA or just have the default be set.
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server. Depends directly on which JAVA_VM value is set by default or by the environment.
# USER_MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
# DOMAIN_PRODUCTION_MODE
# - The variable that determines whether the workshop related settings like the debugger,
# testconsole or iterativedev should be enabled. ONLY settable using the
# command-line parameter named production
# NOTE: Specifying the production command-line param will force
# the server to start in production mode.
# Other variables used in this script include:
# SERVER_NAME - Name of the weblogic server.
# 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)
# For additional information, refer to the WebLogic Server Administration
# Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
ORACLE_HOME="/opt/oracle/middleware/jdeveloper"
export ORACLE_HOME
WL_HOME="/opt/oracle/middleware/wlserver_10.3"
export WL_HOME
BEA_JAVA_HOME="/opt/oracle/middleware/jrockit_160_05"
export BEA_JAVA_HOME
SUN_JAVA_HOME=""
export SUN_JAVA_HOME
if [ "${JAVA_VENDOR}" = "BEA" ] ; then
     JAVA_HOME="${BEA_JAVA_HOME}"
     export JAVA_HOME
else
     if [ "${JAVA_VENDOR}" = "Sun" ] ; then
          JAVA_HOME="${SUN_JAVA_HOME}"
          export JAVA_HOME
     else
          JAVA_VENDOR="BEA"
          export JAVA_VENDOR
          JAVA_HOME="/opt/oracle/middleware/jrockit_160_05"
          export JAVA_HOME
     fi
fi
# We need to reset the value of JAVA_HOME to get it shortened AND
# we can not shorten it above because immediate variable expansion will blank it
JAVA_HOME="${JAVA_HOME}"
export JAVA_HOME
SAMPLES_HOME="${WL_HOME}/samples"
export SAMPLES_HOME
DOMAIN_HOME="/opt/oracle/middleware/user_projects/domains/base_domain"
export DOMAIN_HOME
LONG_DOMAIN_HOME="/opt/oracle/middleware/user_projects/domains/base_domain"
export LONG_DOMAIN_HOME
if [ "${DEBUG_PORT}" = "" ] ; then
     DEBUG_PORT="8453"
     export DEBUG_PORT
fi
if [ "${SERVER_NAME}" = "" ] ; then
     SERVER_NAME="AdminServer"
     export SERVER_NAME
fi
POINTBASE_FLAG="false"
export POINTBASE_FLAG
enableHotswapFlag=""
export enableHotswapFlag
PRODUCTION_MODE="false"
export PRODUCTION_MODE
doExitFlag="false"
export doExitFlag
verboseLoggingFlag="false"
export verboseLoggingFlag
while [ $# -gt 0 ]
do
     case $1 in
     nodebug)
          debugFlag="false"
          export debugFlag
     production)
          DOMAIN_PRODUCTION_MODE="true"
          export DOMAIN_PRODUCTION_MODE
     notestconsole)
          testConsoleFlag="false"
          export testConsoleFlag
     noiterativedev)
          iterativeDevFlag="false"
          export iterativeDevFlag
     noLogErrorsToConsole)
          logErrorsToConsoleFlag="false"
          export logErrorsToConsoleFlag
     nopointbase)
          POINTBASE_FLAG="false"
          export POINTBASE_FLAG
     doExit)
          doExitFlag="true"
          export doExitFlag
     noExit)
          doExitFlag="false"
          export doExitFlag
     verbose)
          verboseLoggingFlag="true"
          export verboseLoggingFlag
     enableHotswap)
          enableHotswapFlag="-javaagent:${WL_HOME}/server/lib/diagnostics-agent.jar"
          export enableHotswapFlag
          PROXY_SETTINGS="${PROXY_SETTINGS} $1"
          export PROXY_SETTINGS
     esac
     shift
done
MEM_DEV_ARGS=""
export MEM_DEV_ARGS
if [ "${DOMAIN_PRODUCTION_MODE}" = "true" ] ; then
     PRODUCTION_MODE="${DOMAIN_PRODUCTION_MODE}"
     export PRODUCTION_MODE
fi
if [ "${PRODUCTION_MODE}" = "true" ] ; then
     debugFlag="false"
     export debugFlag
     testConsoleFlag="false"
     export testConsoleFlag
     iterativeDevFlag="false"
     export iterativeDevFlag
fi
# If you want to override the default Patch Classpath, Library Path and Path for this domain,
# Please uncomment the following lines and add a valid value for the environment variables
# set PATCH_CLASSPATH=[myPatchClasspath] (windows)
# set PATCH_LIBPATH=[myPatchLibpath] (windows)
# set PATCH_PATH=[myPatchPath] (windows)
# PATCH_CLASSPATH=[myPatchClasspath] (unix)
# PATCH_LIBPATH=[myPatchLibpath] (unix)
# PATCH_PATH=[myPatchPath] (unix)
. ${WL_HOME}/common/bin/commEnv.sh
WLS_HOME="${WL_HOME}/server"
export WLS_HOME
MEM_ARGS="-Xms256m -Xmx512m"
export MEM_ARGS
MEM_PERM_SIZE="-XX:PermSize=48m"
export MEM_PERM_SIZE
MEM_MAX_PERM_SIZE="-XX:MaxPermSize=192m"
export MEM_MAX_PERM_SIZE
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
     if [ "${PRODUCTION_MODE}" = "" ] ; then
          MEM_DEV_ARGS="-XX:CompileThreshold=8000 ${MEM_PERM_SIZE} "
          export MEM_DEV_ARGS
     fi
fi
# Had to have a separate test here BECAUSE of immediate variable expansion on windows
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
     MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
     export MEM_ARGS
fi
if [ "${JAVA_VENDOR}" = "HP" ] ; then
     MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
     export MEM_ARGS
fi
# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
if [ "${USER_MEM_ARGS}" != "" ] ; then
     MEM_ARGS="${USER_MEM_ARGS}"
     export MEM_ARGS
fi
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} "
export JAVA_PROPERTIES
# To use Java Authorization Contract for Containers (JACC) in this domain,
# please uncomment the following section. If there are multiple machines in
# your domain, be sure to edit the setDomainEnv in the associated domain on
# each machine.
# -Djava.security.manager
# -Djava.security.policy=location of weblogic.policy
# -Djavax.security.jacc.policy.provider=weblogic.security.jacc.simpleprovider.SimpleJACCPolicy
# -Djavax.security.jacc.PolicyConfigurationFactory.provider=weblogic.security.jacc.simpleprovider.PolicyConfigurationFactoryImpl
# -Dweblogic.security.jacc.RoleMapperFactory.provider=weblogic.security.jacc.simpleprovider.RoleMapperFactoryImpl
EXTRA_JAVA_PROPERTIES="-Ddomain.home=${DOMAIN_HOME} -Doracle.home=${ORACLE_HOME} -Doracle.security.jps.config=${DOMAIN_HOME}/config/oracle/jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${EXTRA_JAVA_PROPERTIES}"
export JAVA_PROPERTIES
ARDIR="${WL_HOME}/server/lib"
export ARDIR
pushd ${LONG_DOMAIN_HOME}
# Clustering support (edit for your cluster!)
if [ "${ADMIN_URL}" = "" ] ; then
     # The then part of this block is telling us we are either starting an admin server OR we are non-clustered
     CLUSTER_PROPERTIES="-Dweblogic.management.discover=true"
     export CLUSTER_PROPERTIES
else
     CLUSTER_PROPERTIES="-Dweblogic.management.discover=false -Dweblogic.management.server=${ADMIN_URL}"
     export CLUSTER_PROPERTIES
fi
if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
     JAVA_PROPERTIES="${JAVA_PROPERTIES} -Dlog4j.configuration=file:${LOG4J_CONFIG_FILE}"
     export JAVA_PROPERTIES
fi
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${CLUSTER_PROPERTIES}"
export JAVA_PROPERTIES
# Clear the pre_classpath here in case an application template wants to set it before the larger pre_classpath is invoked below
PRE_CLASSPATH=""
export PRE_CLASSPATH
JAVA_DEBUG=""
export JAVA_DEBUG
if [ "${debugFlag}" = "true" ] ; then
     JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
     export JAVA_DEBUG
     JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
     export JAVA_OPTIONS
else
     JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da"
     export JAVA_OPTIONS
fi
if [ ! -d ${JAVA_HOME}/lib ] ; then
     echo "The JRE was not found in directory ${JAVA_HOME}. (JAVA_HOME)"
     echo "Please edit your environment and set the JAVA_HOME"
     echo "variable to point to the root directory of your Java installation."
     popd
     read _val
     exit
fi
if [ "${POINTBASE_FLAG}" = "true" ] ; then
     DATABASE_CLASSPATH="${POINTBASE_CLASSPATH}"
     export DATABASE_CLASSPATH
else
     DATABASE_CLASSPATH="${POINTBASE_CLIENT_CLASSPATH}"
     export DATABASE_CLASSPATH
fi
POST_CLASSPATH=""
export POST_CLASSPATH
POST_CLASSPATH="${ORACLE_HOME}/modules/features/adf.share_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"
export POST_CLASSPATH
POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${DATABASE_CLASSPATH}${CLASSPATHSEP}${ARDIR}/xqrl.jar"
export POST_CLASSPATH
# PROFILING SUPPORT
JAVA_PROFILE=""
export JAVA_PROFILE
SERVER_CLASS="weblogic.Server"
export SERVER_CLASS
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${WLP_JAVA_PROPERTIES}"
export JAVA_PROPERTIES
JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag}"
export JAVA_OPTIONS
# -- Setup properties so that we can save stdout and stderr to files
if [ "${WLS_STDOUT_LOG}" != "" ] ; then
     echo "Logging WLS stdout to ${WLS_STDOUT_LOG}"
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stdout=${WLS_STDOUT_LOG}"
     export JAVA_OPTIONS
fi
if [ "${WLS_STDERR_LOG}" != "" ] ; then
     echo "Logging WLS stderr to ${WLS_STDERR_LOG}"
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stderr=${WLS_STDERR_LOG}"
     export JAVA_OPTIONS
fi
# ADD EXTENSIONS TO CLASSPATHS
if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
     PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
     export PRE_CLASSPATH
fi
if [ "${EXT_POST_CLASSPATH}" != "" ] ; then
     POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${EXT_POST_CLASSPATH}"
     export POST_CLASSPATH
fi
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
     export JAVA_OPTIONS
fi
JAVA_OPTIONS="${JAVA_OPTIONS}"
export JAVA_OPTIONS
# SET THE CLASSPATH
CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
export CLASSPATH
JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE}"
export JAVA_VM
Edited by: klogube on Oct 23, 2009 10:58 AM

Similar Messages

  • Client Code not connecting to WebLogic 8.1 with Mutual Authentication

    I am trying to connect to a WebLogic 8.1 web services application. The weblogic instance has mutual authentication enabled, so the client needs to send a certificate when it does an SSL handshake with the server. I am trying to connect with standalone Java JUnit tests. Both the web services and the JUnit tests are using Apache Axis 1.4.0. I've obtained what I believe to be the appropriate certificates from the weblogic administrator that configured the mutual authentication. There is a certificate for the machine I'm trying to connect to, and two other certificates in the chain (three certificates all together, including the root). I've tried several different methods of putting those three certificates in keystores and trust keystores, reading in those keystores in my java code, and connecting to the web services, and I always end up with the same error in the WebLogic server logs. "Certificate chain receved from <ip address> was incomplete."
    Here is an example of my code:
    I initialize like so:
         Properties tempProperties = // (here is where I obtain my properties from a properties file... code removed for security reasons)
         System.setProperty("javax.net.ssl.trustStore", tempProperties.getProperty("trust.keystore.file"));
         System.setProperty("javax.net.ssl.trustStorePassword", tempProperties.getProperty("trust.keystore.password"));
         System.setProperty("javax.net.ssl.trustStoreType", "jks");
         System.setProperty("javax.net.ssl.keyStore", tempProperties.getProperty("keystore.file"));
         System.setProperty("javax.net.ssl.keyStorePassword", tempProperties.getProperty("keystore.password"));                         System.setProperty("javax.net.ssl.keyStoreType", "jks");
         System.setProperty ( "java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol" );
         Security.addProvider ( new com.sun.net.ssl.internal.ssl.Provider ( ) );
    I bind to the appropriate port and locate the service, etc. using auto-generated methods descendant from Apache Axis. No matter what I try, I get the same results. The client says: main, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    The server log says: Certificate chain received from <ip address> was incomplete.
    I've even tried implementing a custom SSL handler as described here http://alweb.homeip.net/dw0rm/dblog/?p=38, and I can verify by stepping into my code that everything gets initialized and set up correctly, and that all three certificates in the chain that I need are obtained from my keystore, but I still get the same error on the client and the server. I've enabled ssl handshake debugging on my client and I can see the whole certificate chain being output to the debug console.
    Any idea what I might be doing wrong?

    My guess would be that the server is not able to validate your certificate. Make sure that the CA for your certificate is trusted by WLS.
    I always like to debug something like this by add -Djavax.net.debug=ssl to both the client and server. It should give you a complete picture of what is going on.
    Edited by: joshbregmanoracle on May 20, 2009 8:49 PM

  • WebLogic Test Client,  throws java.lang.NoSuchMethodException

    In weblogic server 10.3, the  WebLogic Test Client,  throws java.lang.NoSuchMethodException for “any” soap fault message from the web  service.
    In Detail:
    Our web services uses JAX-WS spec and are deployed in WebLogic server 10.3.The web service ear file is generated using standard ant utility. We are using “WebLogic Test Client” available through WebLogic server administration console .The issue is, for “any” soap fault message from the web service, the test client generates “java.lang.NoSuchMethodException:” . The key point is we are creating this class. We are not using our own client. WebLogic Test Client 's service response section has the following stack trace.
    S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
    <faultcode>S:Server</faultcode>
    <faultstring>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</faultstring>
    <detail>
    <ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="com.sun.xml.ws.encoding.soap.SerializationException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
    <message>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
    <ns2:stackTrace>
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="328" method="createDetailFromUserDefinedException" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
    <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
    <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
    <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
    <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
    <ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
    </ns2:stackTrace>
    <ns2:cause class="java.lang.NoSuchMethodException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
    <message>our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
    <ns2:stackTrace>
    <ns2:frame class="java.lang.Class" file="Class.java" line="1605" method="getMethod" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="323" method="createDetailFromUserDefinedException" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
    <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
    <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
    <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
    <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
    <ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
    </ns2:stackTrace>
    </ns2:cause>
    </ns2:exception>
    </detail>
    </S:Fault>
    </S:Body>
    </S:Envelope>

    Thanks for your assistance. Here is the log from weblogic. You may find "xxx" and "yyy" terms. these are given to our specific project oriented names. If you need any further info please let me know. Again a brief about the issue. when the service returns a fault soap message, the server trying to set the error code in a class generated by it's own where the method is not avilable. this happens for all fault soap message. In case of right response from the service no issues. all are working fine.
    Note: Max 3000 characters are allowed to post. so truncating initial stack trace.
    Thanks, ganesh.
    <xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2e0bd8e
    Bound datums[Lxxx.sql.STRUCT;@1b2d059
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1aa0f36
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@191d9ba
    Bound datums[Lxxx.sql.STRUCT;@1dc70ec
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1def11c
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2683f76
    Bound datums[Lxxx.sql.STRUCT;@197400e
    Caused by: our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
    at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
    at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy188.findxxxxxx(Unknown Source)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
    at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
    at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
    ... 30 more
    Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
    at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
    ... 56 more
    Nov 21, 2008 9:38:27 AM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
    INFO: Service Provider API did not return any object back.
    our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
    at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
    at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy188.findxxxxxx(Unknown Source)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
    at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
    at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:71)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
    at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
    ... 56 more
    com.sun.xml.ws.encoding.soap.SerializationException: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:328)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.getFaultDetail(SOAPFaultBuilder.java:306)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:170)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:265)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
    at java.lang.Class.getMethod(Class.java:1605)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:323)
    ... 30 more

  • Webservice is not working on browser test client

    Hi,
    I am using Weblogic 9.2 server, and have deployed a webservice application. While accessing the Websevice browser test client (which is a https url) it renders all the available Web Service methods of that service.
    When i click on any of the methods the request goes to http and it says page not found. when i change the http to https it renders the method attributes correctly.
    I am able to access the web service from some test clients (like SoapUI) without any issues. So the problem is only with the browser based weblogic test client which uses http request internally.
    Anybody have idea what could be the reason for this.
    Regards,
    Chandran

    Hi,
    I am using Weblogic 9.2 server, and have deployed a webservice application. While accessing the Websevice browser test client (which is a https url) it renders all the available Web Service methods of that service.
    When i click on any of the methods the request goes to http and it says page not found. when i change the http to https it renders the method attributes correctly.
    I am able to access the web service from some test clients (like SoapUI) without any issues. So the problem is only with the browser based weblogic test client which uses http request internally.
    Anybody have idea what could be the reason for this.
    Regards,
    Chandran

  • How to run ADF command-line test-client on standalone weblogic host

    I have followed the steps to create a test client for the ADF application. In used the following link:
    http://download.oracle.com/docs/cd/B31017_01/web.1013/b25947/bcquerying007.htm
    The above link does not talk about how to setup the environment where the standalone weblogic is installed to be able to run the test client.
    I can run it in the jdeveloper environment.
    I can also run from the command line on the development host, by cut-paste the command from the jdeveloper output log tab.
    I am trying to run this client on the machine where we have a weblogic installed (standalone) for testing. We can run our ADF application from the browser with no issues. We want to automate and run some testing related to the ADF model (non-viewcontroller part) from the command line on this test stage.
    Which/Where are the ADF libraries?
    How can I add our application jar deployed on the weblogic (ear file) to the CLASSPATH?
    What other libraries ADF/Weblogic do I need for the command line test client?
    What am I missing?
    Thanks for any help.
    Edited by: mmunawar on Jul 2, 2011 1:03 PM
    Edited by: mmunawar on Jul 2, 2011 1:04 PM

    create weblogic application server connection from jdeveloper and then Deploy that application through jdeveloper in the weblogic application server and then run it from jdeveloper and see if its working.

  • SWN_SELSEN not working in test client after client-copy

    Hi all,
    We are using extended notification without problem until test client was refreshed by client-copy from production client. In test client, report SWN_SELSEN did not generated notification even there are newly generated workflow items.  Because of client-copy, I found that tables SWN_NOTIF, SWN_NOTIFTSTMP, SWN_SENDLOG, SWN_TIMESTAMPS are all empty in test client.
    Please advise how to make report SWN_SELSEN back to work in test client.  Thanks.
    << Additional information >>
    (1) Run report SWN_SELSEN_TEST with test Case 5 - Simulate Send Only.  After this, some entries were written to above tables.  But test on new workflow item, the schedule report SWN_SELSEN still fail to trigger notification.
    (2) Run report SWN_SELSEN_TEST with test Case 4 - Send One Message Only.  It triggered notifications for all active workflow items and sent out several hundred emails including workflow item created in step 1.  However, further test on new workflowitem, the schedule report SWN_SELSEN is still unable to trigger notification.
    I think there may be something else missing, like the timestamp of delta.  Please help.
    Regards,
    Donald

    Hello,
    I've experienced a few cases where stopping SWN_SELSEN and then restarting it helped to fill up SWN_TIMESTAMPS with proper values. How does that table look after you run it?
    What is SWN_SELSEN_TEST?
    Chck in SLG1 to get an idea of why it's not working. You can also run SWN_SELSEN in the foreground and debug it to see exactly where and why it goes wrong. Also check ST22.
    regards
    Rick Bakker
    hanabi technology

  • Urgent Please help: Error Testing EJB in Universal Test Client

    Hi,
    I have to get this working by tommrow guys - can you please help.
    I wonder if someone can assist. I am new to WSAD 5.1 and am trying to test an EJB I have created with both local and remote interfaces.
    The bean has been created OK and ithe stub files have created for the bean via Generate->Deploy and RMIC code.
    The RJB project has been defind in my WAS server correctly. The JNDI name in the EJB is \ejb\MyEJBHome
    I start the Universal Test client (UTC) via the options on my WAS Server and then click on the JNDI explorer icon option and see my local EJB Folder and an ejb folder (plus others). If I go to the local EJB folder the stub for my local home inteface appears , I am able to click on it and consumme the bean.
    However if I go to the ejb folder I see my home stub for the remote inteface , I do indded need to click on this to get at the remote inteface for my bean. However on clicking it I get a WAS error "null reference found".
    It does not appear to be able to get at the MyBeanHome stub (no reference to it).
    Ok what am I doing wrong! The project build with no errors and I can see all the stubs in the ejbModule folder. Now is the UTC expecting these stubs to be sitting in a particular directory? if so where?

    Hi Problem is with
    public class MyEJBBean extends AbstractStatelessSessionBean {
         private javax.ejb.SessionContext mySessionCtx;
    extends AbstractStatelessSessionBean causes a problem in UTC.
    Regards.

  • Can weblogic test client be used in weblogic 8.1 version

    Can anyone confirm whether we can use weblogic test client in weblogic server 8.1 version

    We figured out that Oracle SQL Flavor can be used with WebLogic, but only with DB connections created from JDBC URL, not work with DB connections from WebLogic connection pool.

  • Error "Test Agent could not connect to the test controller" while configuring the Test Agent on Client machine

    Hi,
    I am getting an Error “Test Agent could not connect to the test controller”
     while configuring The Test Agent on Client machine.
    Pre-requisite used:  
    VS2012 update 4, Test agent & Test controller of same version used
    User has TFS admin access.
    Same user id used for configuring Test Agent.
    Description:
    Test controller is installed on server A. I want to install test agent on client machine B.
    Windows Fire wall is OFF on both Machines A & B. While configuring Test Agent below error is occurred:
    “Test Agent could not connect to the test controller”
    In log file error was “I, 2015/04/02, 15:32:21.723, Could not get the status from the test agent. Exception: Failed to connect to an IPC Port: The system cannot find the file specified.”
    In Event viewer below error details given:
    Unable to connect to the controller on ‘My Server: 6901’. The agent can connect to the controller but the controller cannot connect to the agent because of following reason: The requested name is valid, but no data of the requested type was found.
    Make sure that the firewall on the test agent machine is not blocking the connection.
    Could you please help me to find solution?
    Thanks in advance!
    Kanchan M
    Kanchan

    Hi Kanchan,
    So on each computer, you create a local user account that is a member of the Administrators group, and use the same account and password on each machine(controller and Agent), am I right?
    Could you enable the detailed log message?
    http://blogs.msdn.com/b/aseemb/archive/2010/03/07/how-to-enable-test-agent-logs.aspx
    http://blogs.msdn.com/b/aseemb/archive/2009/11/28/how-to-enable-test-controller-logs.aspx
    >>In log file error was “I, 2015/04/02, 15:32:21.723, Could not get the status from the test agent. Exception: Failed to connect to an IPC Port: The system cannot find the file specified.”I
    met a similar issue before which was related to the Firewall exceptions, maybe you could refer to it here:
    http://stackoverflow.com/questions/12249093/test-agent-could-not-connect-to-the-test-controller-vs2012-agents
    Best Regards,
    Jack
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Weblogic 10.0 MP1: Client VM not supported

    Dear All,
    Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
    Please provide suggestion or an idea on what to do. The details are provided below.
    Processor: Intel Quad core 64bit
    OS: windows server 2008 R2 64 bit
    Java: JDK 1.5 update 21 64 bit
    Weblogic: Server 10.0 MP1 64 bit for windows
    Regards,
    Edited by: user4198347 on Feb 5, 2011 11:49 PM

    Re: Installation error: Weblogic Server 10.0 MP2

  • TAXINN not working in test client

    Hi ,
    We have done golden master configuration and there TAXINN is working when we create purchase order . A client copy of the same has been done to make it a test client. Here the TAXINN for PO is not working. It is not calculating TAX.
    Please suggest remedy.
    Regards
    Nandini

    check all the requests have been transfered to the test client and have u maintained the condition record for the vendor material combination, check the procedure assigned to the country in.
    hope this will help u.

  • Custom Infotype not visible in Unit Testing Client

    I created Infotype in client 110.I can see IT 9000 in Development client 110.But It is not in the client 120 which is Unit test client.I think Infotypes are client independent....Then why can not I see in client 120.

    Hi,
    I guess you are refering to the client of the same server....
    Since the infotypes are not client independent , you have to go to transaction
    SCC1 of unit testing client and copy both customizing and workbench request.
    After this you can view the infotype.
    Have Fun!!
    Ira!!

  • In other words jQuery mobile does not generate code with result can not test Apps in dw cs6

    from the time compiled in phonegap dw c6 tools and tested from dw the App in Android sdk, for a jQuery mobile App the, code in split/Live is the same as split/Live/Live Code.... in other words jQuery mobile does not generate code with result can not test Apps in dw cs6, but design shown without jQ mobile generated code, well?

    well, jQuery mobile stopped to generate code with result can not test Apps in dw cs6, but design shown without jQ mobile generated code, well (neither generated code seems nor design as seem in mobile)....????

  • Weblogic Server 10.0 MP1 while starting: Client VM not supported

    Dear All,
    Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
    Please provide suggestion or an idea on what to do. The details are provided below.
    Processor: Intel Quad core 64bit
    OS: windows server 2008 R2 64 bit
    Java: JDK 1.5 update 21 64 bit
    Weblogic: Server 10.0 MP1 64 bit for windows
    Regards,
    Edited by: user4198347 on Feb 5, 2011 11:48 PM

    Re: Installation error: Weblogic Server 10.0 MP2

  • Testing webservice using Weblogic's test client

    Hi,
    Getting this when I start the test client to test the webservice, looks like its a MAC address....what i expect is the IP address, bit of a pain having to type the ip address each time. Any help would be great.
    http://[2002:1011:cd64::1011:cd64]:7001/wls_utc?wsdlUrl=http%3A%2F%2F%5B2002%3A1011%3Acd64%3A0%3A0%3A0%3A1011%3Acd64%5D%3A7001%2Ftransactions%2FTransactionService%3FWSDL
    Using weblogic 11g running on Windos 7, this is my test machine.
    regards
    David

    An alternative is:
    use txn WSADMIN and open the node for your web-service. Then, press the 'Rench' button or F8 to open the web based test tool.
    You need to provide logon credentials if basic authentication was required for the WS.
    Pls reward points if helpful.

Maybe you are looking for

  • Template Cell Background Color

    Hi, I'm creating Dreamweaver templates with the pages built from them being edited in Contribute.  There is a need for the Contribute users to be able to change the background color of individual cells in a table (on a page built from a DWT).  I can'

  • Itunes Type Software For The Fascinate

    Is there an itunes type software to install on a computer for the Fascinate? I'm looking for something that will do the same thing as itunes, backing up apps, music etc.

  • Latest PATCH for java engine 2004s_SR1 ( 7.00, SP-Number: 06)

    hello,          I have installed NW 2004s_SR1 in a clustered environment. I am looking for "Latest <u><b>PATCH for java engine</b>"</u>. Current j2EE version details are as: Specifies the version of the system <b>Cluster-Version: 7.00   PatchLevel  <

  • Looping through Objects

    Hi, I'm trying to design business entities with ABAP Objects. I have been able to create internal tables of custom object types. I stumbled into a very peculiar situation in which i have to loop through my custom object internal table. i couldn't use

  • Groove agent 3 with logic

    is anyone using groove agent 3 with logic 8 if so what method r u using to run it i think im having problems with mine