Weblogic.jar in server java proxy

Hi,
weblogic.jar is so big size, when i have I/F item  that's number of 30 for server java proxy. i have to deploy individual ear file included individual weblogic.jar,
like common jar, do i have to deploy it with ear every time?
is there a way?
thanks
venjamin
null

> Hi,
>
> you mean,   like external driver setting with
> aii_af_jmsproviderlib.sda,
>
>     <jars>
>  <jar-name>ojdbc14.jar</jar-name>
>      <jar-name>weblogic.jar</jar-name>
> /jars>
>
> and then deploy it?
Yes.
> i do not need to add weblogic.jar into InboundEjb for server java proxy in
> order to call target ejb?
I do not understand this sentence.
What is your scenario?
Stefan

Similar Messages

  • Call Client Java Proxy from Server Java Proxy

    Hi Gurus!!
    I'm trying to call a Client Java Proxy from a Server Java Proxy.
    Is possible to do this? I think must be possible.
    I have called this Client Java Proxy from another application, and run ok.
    I have tried to call it following the Guide to call Java Client Proxies:
                    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome queryOutHome = null;
                    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeRemote queryOutRemote = null;                     
                    try {
                         //      Get naming context
                         Properties p = new Properties();
                         p.put(
                              Context.INITIAL_CONTEXT_FACTORY,
                              "com.sap.engine.services.jndi.InitialContextFactoryImpl");
                         p.put(Context.PROVIDER_URL, "myurl:50104");
                         p.put(Context.SECURITY_PRINCIPAL, "MMIGUEZ");
                         p.put(Context.SECURITY_CREDENTIALS, mypasswrod);
                         Context ctx = new InitialContext(p);
                         Object ref = ctx.lookup("RobotOut");
                         //      Look up jndi name of proxy bean
                        try {
                         queryOutHome =
                              (MIRobotOut_PortTypeHome) PortableRemoteObject.narrow(
                                   ref,
                                   MIRobotOut_PortTypeHome.class);
                        } catch (Exception e) {
                             throw new RuntimeException(e + "1");
                         //        Get Remote interface
                         queryOutRemote = queryOutHome.create();
                    } catch (Exception e) {
                        throw new RuntimeException(e + "2");
    but I get this error
    "com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome"
    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortTypeHome is the corresponding PortTypeHome to the Client Java Proxy.
    I have tried to call too calling directly from the server Java Proxy to the method correcponding to the Client Java Proxy. The error I get is:
    "com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTRobot_Type: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTRobot_Type"
    Tha call to the client is:
    es.navantia.xi.mm.dispositivosRobotizadosKasto.MIRobotOut_PortType clase = null;
    es.navantia.xi.mm.dispositivosRobotizadosKasto.DTRobot_Type client_req = null;
    es.navantia.xi.mm.dispositivosRobotizadosKasto.DTRobotResponse_Type client_res = null;
    client_res = clase.mIRobotOut(client_req);
    Please, any help will be useful.
    Thanks and regards,
    Manuel Míguez.

    Hi,
    Now I get another error message:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/MITextoOut_PortTypeRemote: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/MITextoOut_PortTypeRemote
    Now, my source is:
      MITextoOut_PortTypeHome queryOutHome = null;
      MITextoOut_PortTypeRemote queryOutRemote = null;
      try {
    //     Get naming context
    Context ctx = new InitialContext();
    //     Look up the EJB name in the environment
    Object ref = ctx.lookup("java:comp/env/ejb/TextoOut");
    // Object ref = ctx.lookup("java:comp/env/ejb/MITextoOut_PortTypeBean");
    //     Cast to Home interface
         queryOutHome = (MITextoOut_PortTypeHome)
    PortableRemoteObject.narrow(ref,
    MITextoOut_PortTypeHome.class);
    //     Get Remote interface
    queryOutRemote = queryOutHome.create();
    } catch (Exception e) {
    System.out.println("RemoteException occurred: "+e.getMessage());
    e.printStackTrace();
    //return;
    try {
          queryOutRemote.$messageSpecifier();
    } catch (RemoteException e2) {
          // TODO Auto-generated catch block
          e2.printStackTrace();
    DTTexto_Type Texto_type = new DTTexto_Type();
    Texto_type.setTexto(req_texto);
    DTTextoResponse_Type Texto_response = new DTTextoResponse_Type();
    try {
         Texto_response = queryOutRemote.mITextoOut(Texto_type);
    } catch (SystemFaultException e1) {
          // TODO Auto-generated catch block
          e1.printStackTrace();
    } catch (ApplicationFaultException e1) {
          // TODO Auto-generated catch block
          e1.printStackTrace();
    } catch (RemoteException e) {
          // TODO Auto-generated catch block
          e.printStackTrace();
    I have tryed removing queryOutRemote.$messageSpecifier() and I get the error:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTTexto_Type: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method mIRobotIn of proxy bean $Proxy351: es/navantia/xi/mm/dispositivosRobotizadosKasto/DTTexto_Type
    Somebody knows what could be the cause of these errors?
    Thanks and regards,
    Manuel.

  • Server java proxy in PI 7.1

    Hi ,
    I am implementing Java server Proxy in PI 7.1.  Got below files when generated  java proxy from ESR. can you tell me in which file I have to write the code. Please share if you have sample code.
    ActiveDirectoryListOIn_PortType.java
    ActiveDirectoryListOIn_PortTypeBean.java
    ActiveDirectoryListOIn_PortTypeHome.java
    ActiveDirectoryListOIn_PortTypeLocal.java
    ActiveDirectoryListOIn_PortTypeLocalHome.java
    ActiveDirectoryListOIn_PortTypeRemote.java
    DepartmentResponseType_Type.java
    DepartmentType_Type.java
    Thanks,
    Madhu Pusala

    Hi Bhasker,
    That  document  for XI 3.0 or 7.0.  We don't write the coode XXXBean.java.  we have to impliment the code in ActiveDirectoryListOIn_PortTypeImpl.template. But this file not created when I genarate the java proxy from ESR.
    Pelase let me know if you find anything.
    Thanks,
    Madhu Pusala

  • Problem with Server Java Proxy

    I have got an error: Delivery of the message to the application using connection JPR failed, due to: RecoverableException.
    Could you help me what is wrong with JPR?
    RWB monitoring doesn't show errors
    defaultTrace.trc - no errors
    Messafing System monitor
    Error Category:  XI_J2EE_MESSAGING_SYSTEM 
    Error Code:  INBOUND_DELIVERY_ERROR 
    I have deployed Java proxy on the same server (as XI)

    Hi Sergey,
    These may help you..
    User exit  or Badi for VL31N (create inbound delivery)
    Idoc WHSORD for inbound delivery
    cheers,
    Prashanth

  • JAVA Proxy :: Exception in ejb-jar.xml in NWDS

    Hi All
    I am getting exception while Importing (Inbound) JAVA Proxy ZIP file in NWDS, ejb-jar.xml shows the red cross & when I double click on it got following error -->
    The content of element type "ejb-jar" is incomplete, it must match "(description?,display-name?,small-icon?,large-icon?,enterprise-beans,relationships?,assembly-descriptor?,ejb-client-jar?)".
    I already add the following JAR files in class-path -->
    aii_proxy_xirt.jar
    aii_msg_runtime.jar
    aii_utilxi_misc.jar
    guidgenerator.jar
    One different thing I also notice is that after adding these JAR files in classpath I am not getting my Inbound Interface BEAN under EJB candidates.
    Also nothing is visible under ejbModule usually it shows 4 JAVA files & one template file.
    As a solution I tried searching in google & forum for above exception, most threads suggest to add the Beans to xml files but I am not getting my interface Bean under EJB candidates.
    I also tried reloading all the external JAR files again from System but still same issue.
    Also within the same NWDS one another version of EJB is working fine but I worked on it 6months back, I tried copy its contents to ejb-jar.xml source code but then also nothing happens.
    I am using NWDS Version: 7.0.10
    Can you pls. suggest & let me know what further information I can provide from my side which can help you to investigate it.
    Regards
    Lalit

    hi,
    Your are using server java proxy.
    You can use some other jar files apart from what you are using,.
    ejb20.jar
    exception.jar
    sapj2eeclient.jar
    and after importing your zip file (create a ejb project first ,then add the zar files and then click on the ejbModule and then import your zip file ) close and open your project.
    Do not directly click on ejb-jar.xml.Click on ejbModule and import the .zip file.
    then save your .template file in ejbModule as a .java project.
    then there should not be any error.
    you can refer
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
    regards,
    ujjwal kumar

  • Deploy XI java Proxy inside JBoss application server

    Hello,
    Can I deploy XI java Proxy inside JBoss application server
    Appreciate you response.
    Thanks

    Hi,
    <b>Yes</b>
    You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
    I have succesfully completed those scenarios.
    After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
    Then you can access that EJB to pass inputs either in standalone application or some JSP.
    Regards,
    Uma

  • XI Java Proxy deploy on JBoss

    Hello,
    Can I deploy XI java Proxy inside JBoss application server
    Appreciate you response.
    Thanks

    Hi,
    <b>Yes</b>
    You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
    I have succesfully completed those scenarios.
    After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
    Then you can access that EJB to pass inputs either in standalone application or some JSP.
    Regards,
    Uma

  • Problem in starting weblogic server as proxy

    I am using weblogic server as Proxy to forward the requests to weblogic cluster.
    When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
    I am Pasting my complete logs below.
    Setting JVM memory params for server IRISProxy
    Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
    WLS Production Mode=true
    ./startWebLogic.sh[68]: B: not found.
    maxfiles=8192
    CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.4.1.05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
    Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
    Starting WLS with line:
    /home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
    Bad level value for property: com.iplanet.services.debug.level
    Bad level value for property: com.sun.identity.agents.logging.level
    Bad level value for property: com.sun.am.policy.amFilter.audit.level
    <Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
    WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
    WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
    WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
    <Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
    <Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
    java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
         at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
         at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
         at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
    >
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
    Can someone help me in solving this problem
    Thanks
    Kris

    I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
    WebLogic Temporary Patch for CR211812
    WebLogic Temporary Patch for CR235145
    Once i commented the above patches in the CLASSPATH.
    The issue is resolved.

  • Unable to invoke WebLogic 8.1 sp2 web service from a java proxy client...

    I am not able to invoke a web service deployed on WebLogic 8.1 SP2 via a client using the proxy jar provided by WebLogic's JWS > Overview > Generate Java Proxy tool.
    I am getting a java.net.ConnectException.
    Both the client and the WebService are on the same server.
    Thanks!!
    Inder./

    Please see the instructions below. If this does not help, please open a case with customer support and tell them it may be related to CR235479
    DESCRIPTION:
    When a platform domain is created, the admin server can be started without
    any issues and a managed server can also be started without any errors if
    using startManagedWebLogic.sh. But when a managed server is started using the
    nodemanager, the managed server fails to start with the following error.
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
    (Complete stack trace with be added as a note)
    The reason for this is that:
    startWebLogic.sh(cmd) and startManagedWebLogic.sh(cmd) for platform domains
    call <User domain>/setDomainEnv.sh which includes all the jars necessary for
    a platform domain in the CLASSPATH.
    Whereas startNodeManager.sh calls <WL_HOME>/common/bin/commEnv.sh, which is
    the same for both platform and server installations of weblogic and has only
    weblogic.jar in the CLASSPATH.
    Looking at historical cases, the steps to start NodeManager successfully in a
    platform domain are:
    1.
    a. Copy admin server classpath (from <user Domain>/startWebLogic.sh) to
    that of all managed servers in the 'Remote Start' tab of the WLS Console
    OR
    b. Copy admin server classpath to <WL_HOME>/server/bin/startNodeManager.sh
    (If the same nodemanager is used to manage server domain servers and platform
    domain servers, will there be any issue with this approach??)
    2. Copy the wsrpKeystore.jks file from your domain directory to the
    nodemanager directory (the parent of the directory where all the server
    directories are replicated in the node manager. By default: <WL
    HOME>/common/nodemanager)
    But these steps are not publicly documented in edocs.
    CONFIGURATION:
    Weblogic Platform Domain 8.1 (all service packs)
    WORKAROUND:
    Steps 1 and 2 above.

  • Including helper classes in java proxy jar file

    I must not be using the right header search criteria because I'm sure this question
    has been asked before. In a Web Service File (.jws) I've imported a couple of
    helper classes that function as data transfer objects. I did this to maintain
    consistency with other portions of the application. The Java Proxy jar file generated
    by Workshop does not include these files. Is there a way of including these dependencies
    or do I need to distribute another jar file with my helper classes?

    Hi Naichen,
    I was able to successfully run both the autotype and clientgen Ant task, on the
    WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
    Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
    to try with that version.
    Regards,
    Mike Wooten
    "Naichen Liu" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am having a warning message when trying to generate java proxy jar
    file on weblogic8.1
    webservice test web app, the message is as follows:
    "Warning Failed to generate client proxy from WSDL definition for this
    service.
    Prescription Please verify the <types> section of the WSDL."
    in the mean time, on weblogic starting terminal, I saw the following
    exceptions,
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils"
    Can anybody help me about this issue? I attached WSDL file, also United
    Airlines
    got an enterprise weblogic license deal with BEA, any help will be highly
    appreciated.
    Thanks!!!
    Naichen

  • Got error when trying to generate Java proxy jar file for webservice

    Hi,
    I am having a warning message when trying to generate java proxy jar file on weblogic8.1
    webservice test web app, the message is as follows:
    "Warning Failed to generate client proxy from WSDL definition for this service.
    Prescription Please verify the <types> section of the WSDL."
    in the mean time, on weblogic starting terminal, I saw the following exceptions,
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils"
    Can anybody help me about this issue? I attached WSDL file, also United Airlines
    got an enterprise weblogic license deal with BEA, any help will be highly appreciated.
    Thanks!!!
    Naichen
    [ModifyPNRWSContract.wsdl]

    Hi Naichen,
    I was able to successfully run both the autotype and clientgen Ant task, on the
    WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
    Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
    to try with that version.
    Regards,
    Mike Wooten
    "Naichen Liu" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am having a warning message when trying to generate java proxy jar
    file on weblogic8.1
    webservice test web app, the message is as follows:
    "Warning Failed to generate client proxy from WSDL definition for this
    service.
    Prescription Please verify the <types> section of the WSDL."
    in the mean time, on weblogic starting terminal, I saw the following
    exceptions,
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils"
    Can anybody help me about this issue? I attached WSDL file, also United
    Airlines
    got an enterprise weblogic license deal with BEA, any help will be highly
    appreciated.
    Thanks!!!
    Naichen

  • Connection timeout when using iPlanet web-server uses Weblogic 6.1 proxy server to proxy requests to an HTTP server

    Hi all,
    My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
    6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
    for 120 seconds. This causes Weblogic to timeout after a while. The error I get
    is as follows:
    <Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
    java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
    at java.net.Socket.<init>(Socket.java:273)
    at java.net.Socket.<init>(Socket.java:127)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
    at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
    at weblogic.net.http.HttpClient.New(HttpClient.java:149)
    at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
    at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
    t.java:285)
    at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
    >
    I get the same error when I added the following plug-in configuration parameters
    (in obj.conf):
    ConnectTimeoutSecs="170" ConnectRetrySecs="170".
    What do I need to do to extend this timeout? Any help you can provide will be
    greatly appreciated..
    Thanks
    Manish

    Hi all,
    My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
    6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
    for 120 seconds. This causes Weblogic to timeout after a while. The error I get
    is as follows:
    <Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
    java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
    at java.net.Socket.<init>(Socket.java:273)
    at java.net.Socket.<init>(Socket.java:127)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
    at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
    at weblogic.net.http.HttpClient.New(HttpClient.java:149)
    at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
    at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
    t.java:285)
    at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
    >
    I get the same error when I added the following plug-in configuration parameters
    (in obj.conf):
    ConnectTimeoutSecs="170" ConnectRetrySecs="170".
    What do I need to do to extend this timeout? Any help you can provide will be
    greatly appreciated..
    Thanks
    Manish

  • Weblogic 9.2 server not starting up : Could not create the Java virtual mac

    Hi
    I have created Weblogic domain.
    Now I am trying to bring my server up by using the startWeblogic.cmd present in domain\bin.
    I get the following error -
    java version "1.5.0_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
    Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
    Unrecognized option: -
    Could not create the Java virtual machine.
    The output when i run the start script is as follows -
    JAVA Memory arguments: -Xms1024m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m
    WLS Start Mode=Development
    CLASSPATH=S:local;;D:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;P:\JDK150~1\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient51.jar;D:\bea\WEBLOG~1\server\lib\xqrl.jar;;Q:\VODAFO~1\lib\WSDLProxy.jar;
    PATH=D:\bea\patch_weblogic923\profiles\default\native;D:\bea\WEBLOG~1\server\native\win\32;D:\bea\WEBLOG~1\server\bin;P:\JDK150~1\jre\bin;P:\JDK150~1\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\TortoiseSVN\bin;D:\ProgramFiles\Rational\common;C:\Program Files\CVSNT\;D:\bea\WEBLOG~1\server\native\win\32\oci920_8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Starting WLS with line:
    P:\JDK150~1\bin\java -client -Xms1024m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m -Xverify:none -da -Dplatform.home=D:\bea\WEBLOG~1 -Dwls.home=D:\bea\WEBLOG~1\server -Dwli.home=D:\bea\WEBLOG~1\integration -Dweblogic.management.discover=true -Dweblogic.http.descriptor.merge=true -Dejbruntime.database=pointbase44 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\bea\patch_weblogic923\profiles\default\sysext_manifest_classpath -Djava.protocol.handler.pkgs=com.vodafone.vgsg.wsdlproxy -Dcom.vodafone.vgsg.wsdlproxy.protocol=http -Dcom.vodafone.vgsg.wsdlproxy.host=localhost -Dcom.vodafone.vgsg.wsdlproxy.port=7001 -Dweblogic.Name=portalServer -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy - weblogic.Server
    I checked all configurations. All seem fine but I am surely missing something.
    I recreated the domain thinking I messed up something but that did not help.
    I tried using jrockit instead of sun jdk. It still could not create JVM.
    I really appreciate any help!
    Regards,
    Smita

    Extra dash in the java start line ( before the weblogic.Server ):
    -Dweblogic.Name=portalServer -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy - weblogic.Server
    might be why you get the message:
    Unrecognized option: -
    I can get the same error with this example:
    /bin> java -
    Unrecognized option: -
    Could not create the Java virtual machine.

  • No use giving weblogic.jar *.java

    still getting compilation errors on giving javac -classpath weblogic.jar *.java on the prompt C:\bea\user_projects\applications\Untitled4\Untitled4Web\WEB-INF\src\pooja
    i tried giving this command on C:\bea\user_projects\applications\Untitled4\Untitled4Web\WEB-INF where weblogic.jar is actually there,i tried setting envoirment variable also by adding a new classpath C:\bea\user_projects\applications\Untitled4\Untitled4Web\WEB-INF\ ,but in vain same compilation errors occur.
    POOJA

    Hi,
    Your best bet is to let weblogic.jar where it is, probably :
    C:\bea\weblogicXXX\server\lib
    Then move your prompt to the root of your sources (C:\bea\user_projects\applications\Untitled4\Untitled4Web\WEB-INF\src?) .
    And type :
    javac -classpath C:\bea\weblogicXXX\server\lib\weblogic.jar pooja\*.java

  • Give me description about JAVA Proxy Runtime and JAVA Proxy Server

    Give me description about JAVA Proxy Runtime and JAVA Proxy Server with some examples.

    Hi,
    Java proxy runtime :
    Using the Java proxy runtime you can receive messages or send messages to the Integration Server.
    This will help you
    http://help.sap.com/saphelp_nw04/helpdata/en/64/7e5e3c754e476ee10000000a11405a/frameset.htm
    Java proxy server :
    The connection to the Integration Server by using the Java proxy runtime.
    This will help you
    http://help.sap.com/saphelp_nw04/helpdata/en/87/5305adc23540b8ac7bce08dbe96bd5/frameset.htm
    Regards
    Agasthuri Doss

Maybe you are looking for