Wls 6.0 httpproxyservlet problems

We're trying to set up a weblogic 6 box to be able to have multiple
managed servers on one machine, fed by a proxy server. The goal is to
have the site requests come in through port 80 (in production), but
still go to the individual managed servers, looking at different ports
-- no money for clustering :(
we decided to stick with wls as our web server as most of the site is
dynamic anyway.
I have the following mapping code in my web.xml file of the proxy
server
<!-- DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
Application 1.2//EN"
"file:///weblogic/dev/myserver/servlet2.2/WEB-INF/web-jar.dtd"-->
<web-app>
<servlet-mapping>
<servlet-name>StudentEmploymentProxy</servlet-name>
<url-pattern>/sep/*</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>StudentEmploymentProxy</servlet-name>
<servlet-class>weblogic.t3.srvr.HttpProxyServlet</servlet-class>
<init-param>
<param-name>redirectURL</param-name>
<param-value>studentemployment:9001</param-value>
</init-param>
</servlet>
that's all that's in the default app of the proxy server. the
individual apps have only the basic web.xml
file and a small .jsp test page that is just html.
so here's the summary:
server 1:
proxyserver (dns proxy), listening on port 8001, with a default
application called proxy that has the
above mappings
server 2:
studentemploymentserver (dns studentemployment), listening on port
9001, with a default application
called studentemployment
url call:
http://proxy:8001/sep/studentemployment.jsp
getting a 404 error, not sure what the h is going on.
any guidance much appreciated.

We're trying to set up a weblogic 6 box to be able to have multiple
managed servers on one machine, fed by a proxy server. The goal is to
have the site requests come in through port 80 (in production), but
still go to the individual managed servers, looking at different ports
-- no money for clustering :(
we decided to stick with wls as our web server as most of the site is
dynamic anyway.
I have the following mapping code in my web.xml file of the proxy
server
<!-- DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
Application 1.2//EN"
"file:///weblogic/dev/myserver/servlet2.2/WEB-INF/web-jar.dtd"-->
<web-app>
<servlet-mapping>
<servlet-name>StudentEmploymentProxy</servlet-name>
<url-pattern>/sep/*</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>StudentEmploymentProxy</servlet-name>
<servlet-class>weblogic.t3.srvr.HttpProxyServlet</servlet-class>
<init-param>
<param-name>redirectURL</param-name>
<param-value>studentemployment:9001</param-value>
</init-param>
</servlet>
that's all that's in the default app of the proxy server. the
individual apps have only the basic web.xml
file and a small .jsp test page that is just html.
so here's the summary:
server 1:
proxyserver (dns proxy), listening on port 8001, with a default
application called proxy that has the
above mappings
server 2:
studentemploymentserver (dns studentemployment), listening on port
9001, with a default application
called studentemployment
url call:
http://proxy:8001/sep/studentemployment.jsp
getting a 404 error, not sure what the h is going on.
any guidance much appreciated.

Similar Messages

  • WLS 6.1 SP2, problem starting Struts

    Hi,
              We have recently upgraded our Weblogic Server from 6.1(no service pack) to
              6.1 SP2. Now the problem is when I access a jsp page in my web application,
              I get this nasty error:
              <Feb 20, 2002 9:10:24 AM SGT> <Error> <HTTP>
              <[WebAppServletContext(5743047,sme,/sme)] Root cause of Servl
              javax.servlet.jsp.JspException: Cannot find ActionMappings or
              ActionFormBeans collection
              at org.apache.struts.taglib.html.FormTag.lookup(FormTag.java:781)
              at
              org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:481)
              at jsp_servlet._security.__login._jspService(__login.java:132)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :265)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :304)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :200)
              at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              ntext.java:2495)
              at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              :2204)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              I didn't change any of the configuration files that were working well with
              the previous version of WLS. In fact even classpath also I didn't modify.
              This problem is seen on Windows as well as Solaris env. Yesterday I played
              with classpath in Solaris env. and kept the "struts.jar" as the fist in
              classpath. It worked and I got an idea to remove it and see if it doesn't
              work. It didn't work as expected, but didn't work even if I put it back form
              then on.
              Has any of you guys had the same problem and if yes, pl. let me know your
              fix for it.
              Thanks & Regards
              Vijay
              

    Hi,
              We have recently upgraded our Weblogic Server from 6.1(no service pack) to
              6.1 SP2. Now the problem is when I access a jsp page in my web application,
              I get this nasty error:
              <Feb 20, 2002 9:10:24 AM SGT> <Error> <HTTP>
              <[WebAppServletContext(5743047,sme,/sme)] Root cause of Servl
              javax.servlet.jsp.JspException: Cannot find ActionMappings or
              ActionFormBeans collection
              at org.apache.struts.taglib.html.FormTag.lookup(FormTag.java:781)
              at
              org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:481)
              at jsp_servlet._security.__login._jspService(__login.java:132)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :265)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :304)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :200)
              at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              ntext.java:2495)
              at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              :2204)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              I didn't change any of the configuration files that were working well with
              the previous version of WLS. In fact even classpath also I didn't modify.
              This problem is seen on Windows as well as Solaris env. Yesterday I played
              with classpath in Solaris env. and kept the "struts.jar" as the fist in
              classpath. It worked and I got an idea to remove it and see if it doesn't
              work. It didn't work as expected, but didn't work even if I put it back form
              then on.
              Has any of you guys had the same problem and if yes, pl. let me know your
              fix for it.
              Thanks & Regards
              Vijay
              

  • JMS bridge from Tibco to WLS 8.1(sp4) problems

    We have a WLS that contains a MDB for receiving messages from another system. When messages are received on the Tibco topic and are try to be delivered to the WLS, we get the exception below.
              However, if we change the MDB to connect directly to the topic in the other WLS (the publisher), the message is received fine. Also, when using the Tibco bridge, if we use a simple command-line client to place a simple text-based message on the message topic, it is delivered to our server just fine.
              Is this an authentication related issue? If so, then why does it work when the WLS servers are linked directly, but not when Tibco server is being used as bridge between them?
              The publisher of the message is running on Linux, and the subscriber on Windows/XP. The Tibco server on Solaris and is v4.2.
              Thanks,
              Craig
              <Nov 1, 2005 4:11:02 PM MST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MyMessaging Bridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception
              : javax.resource.ResourceException: Error sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Error creating producer or sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:719)
              at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
              at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:647)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:644)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              .)>

    We have a WLS that contains a MDB for receiving messages from another system. When messages are received on the Tibco topic and are try to be delivered to the WLS, we get the exception below.
              However, if we change the MDB to connect directly to the topic in the other WLS (the publisher), the message is received fine. Also, when using the Tibco bridge, if we use a simple command-line client to place a simple text-based message on the message topic, it is delivered to our server just fine.
              Is this an authentication related issue? If so, then why does it work when the WLS servers are linked directly, but not when Tibco server is being used as bridge between them?
              The publisher of the message is running on Linux, and the subscriber on Windows/XP. The Tibco server on Solaris and is v4.2.
              Thanks,
              Craig
              <Nov 1, 2005 4:11:02 PM MST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MyMessaging Bridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception
              : javax.resource.ResourceException: Error sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Error creating producer or sending message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
              at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:719)
              at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
              at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:647)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:644)
              at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
              at $Proxy8.send(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
              at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
              at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
              at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
              at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
              at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
              .)>

  • Apache Plugin for WLS 6.1 - Timeout Problem

    Hi!
    We are discovering some problems in a WLS-Cluster setup at one of our customers.
    Environment: 2 x WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716, running
    on Solaris 8 machines. (2 x Managed, 1 x Admin) The WLS are served by an Apache
    Server (Solaris8), running the DSO-Plugin from 6.1 SP1. (Build date/time: Sep
    4 2001 16:45:41)
    Our problem is as following: Due to other problems (network), we sometimes have
    timeouts when the Plugin tries to contact the WLS. As a result, the client is
    transferred to the next server in the cluster, which does not have the session.
    (The Session is not (yet) clusterable)
    Questions: How long is this timeout? Can it be configured?
    As a clarification: I am not talking about the 'ConnectTimeoutSecs', this one
    is 10 seconds. And the 'failover' to the next server in the cluster happens almost
    immediately. Also at this point there is no way for us to solve either the network-problems
    or make the session clusterable.
    We simply need a way to make a client 'sticky' to one Weblogic-Server.
    Any help would be greatly welcome!! Many thanx, Andreas Liebrich
    I will attach the Config as shown in __WebLogicBridgeConfig:
    WebLogic Cluster List:
    Host: 'x.y.z.128' Port: 7001 Primary
    General Server List:
    Host: 'x.y.z.145' Port: 7001 Status: OK
    Host: 'x.y.z.128' Port: 7001 Status: OK
    ConnectRetrySecs: '2'
    ConnectTimeoutSecs: '10'
    CookieName: JSESSIONID Debug: '0'
    DebugConfigInfo: 'ON'
    DefaultFileName: ''
    DisableCookie2Server: OFF
    DynamicServerList: 'ON'
    ErrorPage: ''
    FileCaching: ON
    HungServerRecoverSecs: '300'
    Idempotent: ON
    KeepAliveEnabled: OFF
    KeepAliveSecs: 0
    MaxPostSize: '0'
    MaxSkips: '10'
    PathPrepend: ''
    PathTrim: ''
    QueryFromRequest: OFF
    SecureProxy: 'OFF'
    StatPath: false
    WLLogFile: '/log/itest/www1.wlproxy.log'
    WLProxySSL: OFF

    Nope.
    If the plugin is unable to make a socket connection to WLS, it will try the
    next server in the list.
    I would suggest working on the WLS side and if a sessionId does come into
    the server and it does not exist, then reject that.
    Otherwise, you will have to either use clustering, or a single server in the
    httpd.conf for apache.
    Eric
    "Andreas Liebrich" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi!
    We are discovering some problems in a WLS-Cluster setup at one of ourcustomers.
    >
    >
    Environment: 2 x WebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716,running
    on Solaris 8 machines. (2 x Managed, 1 x Admin) The WLS are served by anApache
    Server (Solaris8), running the DSO-Plugin from 6.1 SP1. (Build date/time:Sep
    4 2001 16:45:41)
    Our problem is as following: Due to other problems (network), we sometimeshave
    timeouts when the Plugin tries to contact the WLS. As a result, the clientis
    transferred to the next server in the cluster, which does not have thesession.
    (The Session is not (yet) clusterable)
    Questions: How long is this timeout? Can it be configured?
    As a clarification: I am not talking about the 'ConnectTimeoutSecs', thisone
    is 10 seconds. And the 'failover' to the next server in the clusterhappens almost
    immediately. Also at this point there is no way for us to solve either thenetwork-problems
    or make the session clusterable.
    We simply need a way to make a client 'sticky' to one Weblogic-Server.
    Any help would be greatly welcome!! Many thanx, Andreas Liebrich
    I will attach the Config as shown in __WebLogicBridgeConfig:
    WebLogic Cluster List:
    Host: 'x.y.z.128' Port: 7001 Primary
    General Server List:
    Host: 'x.y.z.145' Port: 7001 Status: OK
    Host: 'x.y.z.128' Port: 7001 Status: OK
    ConnectRetrySecs: '2'
    ConnectTimeoutSecs: '10'
    CookieName: JSESSIONID Debug: '0'
    DebugConfigInfo: 'ON'
    DefaultFileName: ''
    DisableCookie2Server: OFF
    DynamicServerList: 'ON'
    ErrorPage: ''
    FileCaching: ON
    HungServerRecoverSecs: '300'
    Idempotent: ON
    KeepAliveEnabled: OFF
    KeepAliveSecs: 0
    MaxPostSize: '0'
    MaxSkips: '10'
    PathPrepend: ''
    PathTrim: ''
    QueryFromRequest: OFF
    SecureProxy: 'OFF'
    StatPath: false
    WLLogFile: '/log/itest/www1.wlproxy.log'
    WLProxySSL: OFF

  • WLS 7.0 installation problem on HP-UX 11

    When I try to start the net installer net_platform700_hpux.bin on our HP machine,
    it throws the following error:
    End-of-central-directory signature not found.
    ** Error during init, error code = 2.
    Any help will be appreciated.
    Thanks,
    Ayan

    Ayan,
    I did a quick search on the error you posted - I found that most times the problem is
    that the .zip file has been corrupted. Maybe you should try the download again.
    Regards,
    Glenn Dougherty
    Developer Relations Engineer
    BEA Technical Support
    Ayan wrote:
    When I try to start the net installer net_platform700_hpux.bin on our HP machine,
    it throws the following error:
    End-of-central-directory signature not found.
    ** Error during init, error code = 2.
    Any help will be appreciated.
    Thanks,
    Ayan

  • Java Pet Store Deployathon - wls 6.1 deplyment problem

    Hi All,
    I get following exception when i run build.bat on step 6 for building petstore.ear
    file.
    I have checked all the required resources for compiling the ejb classes are there
    in the required structure.
    EXCEPTION
    org.xml.sax.SAXException: Could not locate a local resource corresponding to public
    Id -//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN.
    Is the XML DOCTYPE header correct?
    at weblogic.ejb.deployment.xml.EJBEntityResolver.resolveEntity(EJBEntityResolver.java:55)
    at com.sun.xml.parser.ExternalEntity.getInputSource(ExternalEntity.java:46)
    at com.sun.xml.parser.Parser.pushReader(Parser.java:2748)
    at com.sun.xml.parser.Parser.externalParameterEntity(Parser.java:2500)
    at com.sun.xml.parser.Parser.maybeDoctypeDecl(Parser.java:1136)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:480)
    at com.sun.xml.parser.Parser.parse(Parser.java:283)
    ANY IDEA? Thanks !
    Alok Sharma

    Hi All,
    I get following exception when i run build.bat on step 6 for building petstore.ear
    file.
    I have checked all the required resources for compiling the ejb classes are there
    in the required structure.
    EXCEPTION
    org.xml.sax.SAXException: Could not locate a local resource corresponding to public
    Id -//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN.
    Is the XML DOCTYPE header correct?
    at weblogic.ejb.deployment.xml.EJBEntityResolver.resolveEntity(EJBEntityResolver.java:55)
    at com.sun.xml.parser.ExternalEntity.getInputSource(ExternalEntity.java:46)
    at com.sun.xml.parser.Parser.pushReader(Parser.java:2748)
    at com.sun.xml.parser.Parser.externalParameterEntity(Parser.java:2500)
    at com.sun.xml.parser.Parser.maybeDoctypeDecl(Parser.java:1136)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:480)
    at com.sun.xml.parser.Parser.parse(Parser.java:283)
    ANY IDEA? Thanks !
    Alok Sharma

  • Steve Muenchs "Dynamic JDBC" on WLS 11g (10.3.1)?

    Hi,
    I try to run Steves Example "11g Dynamic JDBC Credentials for Model 1, Struts, Trinidad, and ADF Faces Rich Client" on Standalone WLS 11g (10.3.1) but it doesn't works... on integrated WLS it runs without problems. The WLS-Log shows:
    Modul:     oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack
    Message:     Failed to create config mbean.
    details: java.lang.Exception: oracle.mds.core.MetadataNotFoundException: MDS-00013: No Metadate for Metaobject "/META-INF/adf-config.xml" found.
    Does somebody have the example to run brought? Or if new settings are necessary for the example on WLS 11g?
    Kind regards
    Martin

    Hi,
    since Steve's solution has nothing to do with the adf-config, I suggest you create a simple testcase that reproduces the problem. It appears as if the ADF binding is not set up properly
    Frank

  • JAX-WS SOAPHandler can not deployed in BEA WLS 10.0 - Bug?

    Hi,
    currently I'm trying tp deploy a simple JAX-WS webservice with JAX-WS SOAPHandler in BEA WLS 10.0.
    Therefore I provide a WAR file with the webservice and handler classes.
    The SOAP Handler is defined in the webservice via the @HandlerChain(file="handler.xml")
    My handler.xml looks as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <javaee:handler-chain>
    <javaee:handler> <javaee:handler-class>com.bmw.wss.server.handler.AuthenticationHandler</javaee:handler-class>
    </javaee:handler>
    </javaee:handler-chain>
    </javaee:handler-chains>
    This handlers.xml is in the classpath within the WAR file.
    If i trying to deploy this WAR file I always get the following exception from BEA WLS 10:
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "WSAATestService" failed to preload on startup in Web application: "wsaa-jaxwshandlertest.war".
    java.lang.NullPointerException
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsHandlers(WseeRuntimeMBeanManager.java:108)
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsPort(WseeRuntimeMBeanManager.java:80)
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsMBean(WseeRuntimeMBeanManager.java:57)
    I seems BEA WLS 10 has some problems with the JAX-WS SOAPHandler. I've deployed the same WAR-file on a Glassfish v2 server... without any problems!
    Does anyone already used the JAX-WS handler mechanism in BEA WLS 10? Any ideas?
    Thx.

    Hi,
    thx for your answer. Now I've found the problem. The BEA WLS don't accept null return value of the SOAPHandler method getHeaders(). If I return a dummy object everything wotks fine:
    public Set<QName> getHeaders() {
    return new TreeSet<QName>();
    However I think this behaviour of the BEA WLS 10 is some kind of strange. Why do I have to implement the method getHeaders() if I don't want to use it.
    Sun's Glassfish allows a null return value like expected.

  • Stateless Session EJB hangs using URLConnection but WLS doesn't clean up

    Hi
    We have a stateless session EJB running under WLS 5.1 with service
    pack 10 on Solaris.
    The bean calls a remote HTTP server using the java.net.URLConnection
    class and forwards the response to the EJB client. The bean is largely
    working fine but some threads hang waiting on the HTTP response. Debug
    statements, which are written immediately after the response has been
    read and the connection has been closed, do not appear in our log for
    the hung threads. The WebLogic Console displays these threads as "in
    use" and a "netstat -an" displays the tcp connections as ESTABLISHED.
    However, the access logs of the remote Apache server show the HTTP
    connections of the threads in question completed successfully with
    HTTP code 200. The Apache server is using keep-alive connections.
    Some EJB threads are still waiting for something it seems.
    Has anyody else experienced this when using URLConnection from
    stateless session EJBs under WLS?
    The second problem is why doesn't WLS time these threads out after
    trans-timeout-seconds (we're using the default of 300 seconds)? The
    WLS log shows no error messages relating to this problem.
    I'm grateful for any info offered.
    Thanks in advance
    Steve

    If you suspect that WLS protocol handler is at fault (and quite often it is),
    one thing to try is (if you use Sun's JVM) to use Sun's HTTP protocol handler
    instead of WLS (the most common symptom is when code which makes HTTP requests
    works fine outside of WebLogic and you have problems getting it to work inside
    WebLogic) :
    replace
    URL url = new URL("http://...");
    HttpURLConnection conn = (HttpURLConnection)url.openConnection();
    with
    URL url = new URL(null, "http://...", new sun.net.www.protocol.http.Handler());
    HttpURLConnection conn = (HttpURLConnection)url.openConnection();
    You will have to edit weblogic.policy to allow your code to specify protocol
    handler.
    Also note that transaction timeout is only checked on method boundaries, or
    when your code attempts to do something with the database - it is not going to
    interrupt thread which is waiting for HTTP response.
    Steve Lock <[email protected]> wrote:
    Hi
    Thanks for the info. The remote HTTP server's access log shows that
    the requests were successfully processed. Doesn't this mean that the
    connection is then closed? I know the web server is using keep-alive
    connections but I thought this was transparent to the client...?
    Also why doesn't WLS remove the hung threads?
    Steve
    "Ignacio G. Dupont" <[email protected]> wrote in message news:<[email protected]>...
    We have had a problem like yours with Weblogic 6.1 SP2 on Linux
    The problem is sun's implementation of the HTTP connections doesn't have a
    timeout, so if the other peer doesn't close the connection your threads will
    be "locked" on the connection.
    We have found searching the web that the Jakarta project has a package
    called Jakarta commons that implements HTTP connections with an
    setSoTimeout(int timeout) method so you can open the connections with your
    desired timeout. You have to download the code from the CVS as the released
    version doesn't support the timedout sockets yet.
    When support for the JDK 1.4 version will be announced by Bea you could use
    one of its new features that will allow you to pass arguments to the JVM to
    specify the maximum socket connection stablising timeout and the max
    inactivity on the socket too.
    Hope it helps you.
    Dimitri

  • BPM Clustering on WLS

    Does anyone have a decent cookbook for setting up a BPM cluster in WLS? We are deploying this configuration and have no problems on the WLS side but major problems with BPM. Unfortunately the documentation for this is rather thin and not too intuitive. Any help would be greatly appreciated.
    TIA,
    IGS

    You need to increase the JTA timeout value in WLS to something higher (like 300). Some of the BPM engine transactions take longer than Weblogic's default.
    Please refer to the following document in MetaLink for details:
    Doc ID:      780946.1

  • WLS 8.1 an the XAResource interface

    Hi I wonder if someone could advise me
              I've created a remote JMS client which is using a third party transaction manager to manage an XA global transaction consisting of many JMS Queue from various WLS servers.
              My problem comes when I try to gain an XAResource from the underlying JMS Queues (needed to enlist them in the overall transaction).
              I take an javax XAQueueSession object which points to a JMS Queue on a WLS 8.1 server and try to invoke the .getXAResource() method to produce the javax XAResource. The problem is it keeps returning me a null pointer.
              the creation of the XAQueueSession is built up in this manner
              1.) Look up connectionFactory from context, cast to an XAQueueConnnectionFactory
              2.) XAQueueConnnectionFactory produces an XAQueueConnection
              3.) XAQueueConnection creates an XAQueueSession
              4.) XAQueueConnection is then started
              5.) XAQueueSession is used to gain an XAResource which produces a null pointer
              Question
              -=-=-=-=-=-=
              1) Does WLS 8.1 support the Javax XAResource interface? if it does is it possible to get an XAResource object from the XAQueueSession?
              Any comments on these quesions would be useful
              Kind Regards
              Barry

    Since WLS JMS is clustered, it's a little more complex, because once you start two-phase commit transactions, you need to always go back to the same server in the cluster to resolve them.
              The best-documented way to do this is to use the weblogic.transaction package, which is part of the Javadocs found here:
              http://e-docs.bea.com/wls/docs81/javadocs/index.html
              You need to call the following method from the weblogic.transaction package:
              TxHelper.getClientInterposedTransactionManager()
              This takes a JNDI InitialContext, and also a server name. Once you "prepare" a transaction, you'll have to go back to that server to commit it or roll it back.
              The InterposedTransactionManager object that's returned represents the JTA transaction manager on the server that you named. You can call "getXAResource" on it to get the XAResource that you'll need.
              You will also want to route your JMS calls from your client through the server that you got the transaction manager for. If you don't have a cluster, this is pretty simple. If you have a cluster, then you should create a JMS ConnectionFactory that's targeted to a single server, so that your client calls and your XA calls go to the same node in the cluster.
              The folks on the JTA newsgroup, or BEA Support, should be able to help you with the details if things don't work out, but those are the basics.

  • Weblogic 10.3 deployment problem

    Hi
    Currently I am trying to deploy my application on Weblogic 10.3.
    My application uses
    JDK1.4
    J2EE 2.4
    JSF 1.1
    It also contains some jars related to RAD generators like jsf-ibm.jar.
    After deploying the application it shows me error for FacesServlet. It is not getting this class. The error is
    java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
    What change I need to do so that this deployment should be successful.
    Please help and tell....

    When I deployed jsf1.2 library from deployable libraries provided by WLS 10.3, the problem of FacesServlet was solved but it was giving java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener. So I again deployed jsf-ri-1.1.1 for solving the problem of ConfigureListener. Fortunately that is also solved. But then it was giving the problem
    Error while parsing the JSF Faces Config Descriptor at "C:\bea\user_projects\domains\Domain1\servers\AdminServer\tmp\_WL_user\WebFacesEARWeb\wp5pf0\war\WEB-INF\lib\jsf-ibm.jar!/META-INF/faces-config.xml". This was due to jsf-ibm.jar which was already in my application for few components. My project users Generator and for that generator this jar is essential.
    One more thing my project uses ibm components as well as sun's jsf components so I cannnot remove the ibm jar files as there is mapping for different servlets the code of WEB.xml is here
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5">
         <display-name>WebFacesEARWeb</display-name>
         <context-param>
              <description>
              Monitors Faces JSP files for modifications and synchronizes a running server with
    the changes without restarting the server. If this parameter is set to false or
    removed from the deployment descriptor, any changes made to Faces JSP files may
    not be seen by the server until it is restarted. This parameter is usually set
    to true while the Faces JSP files are being developed and debugged in order to
    improve the performance of the development environment.</description>
              <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
              <param-value>true</param-value>
         </context-param>
         <context-param>
              <description>
              </description>
              <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
              <param-value>true</param-value>
         </context-param>
         <context-param>
              <param-name>javax.faces.CONFIG_FILES</param-name>
              <param-value>
                   /WEB-INF/main-faces-config.xml,
                   /WEB-INF/CL/CLCLFacesConfig.xml,
                   /WEB-INF/CL/manCLCLFacesConfig.xml,
                   /WEB-INF/PD/PDAGFacesConfig.xml,
                   /WEB-INF/PD/PDAUFacesConfig.xml,
                   /WEB-INF/PD/PDBPFacesConfig.xml,
                   /WEB-INF/PD/PDCLFacesConfig.xml,
                   /WEB-INF/PD/PDCOFacesConfig.xml,
                   /WEB-INF/PD/PDCUFacesConfig.xml,
                   /WEB-INF/PD/PDCYFacesConfig.xml,
                   /WEB-INF/PD/PDPDFacesConfig.xml,
                   /WEB-INF/PD/PDPRFacesConfig.xml,
                   /WEB-INF/PD/PDRPFacesConfig.xml,
                   /WEB-INF/PD/PDTCFacesConfig.xml,
                   /WEB-INF/PD/PDTEFacesConfig.xml,
                   /WEB-INF/PD/PDUTFacesConfig.xml,
                   /WEB-INF/PD/PDVRFacesConfig.xml,
                   /WEB-INF/PD/PDVVFacesConfig.xml,
                   /WEB-INF/PD/PDWGFacesConfig.xml,
                   /WEB-INF/PD/PDXTFacesConfig.xml,
                   /WEB-INF/PD/PDZSFacesConfig.xml,
                   /WEB-INF/PS/PSCLFacesConfig.xml,
                   /WEB-INF/PS/PSCPFacesConfig.xml,
                   /WEB-INF/PS/PSECFacesConfig.xml,
                   /WEB-INF/PS/PSEMFacesConfig.xml,
                   /WEB-INF/PS/PSFMFacesConfig.xml,
                   /WEB-INF/PS/PSGMFacesConfig.xml,
                   /WEB-INF/PS/PSMAFacesConfig.xml,
                   /WEB-INF/PS/PSMEFacesConfig.xml,
                   /WEB-INF/PS/PSMHFacesConfig.xml,
                   /WEB-INF/PS/PSMSFacesConfig.xml,
                   /WEB-INF/PS/PSQMFacesConfig.xml,
                   /WEB-INF/PS/PSSFFacesConfig.xml,
                   /WEB-INF/PS/PSTAFacesConfig.xml,
                   /WEB-INF/PS/PSXMFacesConfig.xml
              </param-value>
         </context-param>
         <!-- Filter definitions -->
         <filter>
              <filter-name>SessionCheckFilter</filter-name>
              <filter-class>com.te.faces.filter.SessionCheckFilter</filter-class>
         </filter>
         <filter-mapping>
              <filter-name>SessionCheckFilter</filter-name>
              <url-pattern>*.jsp</url-pattern>
         </filter-mapping>     
         <listener>
              <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
         </listener>
         <servlet id="Servlet_1138264765882">
              <servlet-name>JS Resource Servlet</servlet-name>
              <servlet-class>
              com.ibm.faces.webapp.JSResourceServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <servlet id="Servlet_1138264766203">
              <servlet-name>Faces Servlet</servlet-name>
              <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <servlet>
              <servlet-name>Resource Servlet</servlet-name>
              <servlet-class>com.te.ps.webproject.servlets.ResourceServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <servlet>
         <servlet-name>AxisServlet</servlet-name>
         <servlet-class>
         org.apache.axis.transport.http.AxisServlet
         </servlet-class>
         </servlet>
         <servlet>
         <servlet-name>AdminServlet</servlet-name>
         <servlet-class>
         org.apache.axis.transport.http.AdminServlet
         </servlet-class>
         <load-on-startup>100</load-on-startup>
         </servlet>     
         <servlet-mapping>
              <servlet-name>Resource Servlet</servlet-name>
              <url-pattern>/te_comp_res/*</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>JS Resource Servlet</servlet-name>
              <url-pattern>/.ibmjsfres/*</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>/faces/*</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>*.faces</url-pattern>
         </servlet-mapping>
    <servlet-mapping>
    <servlet-name>AxisServlet</servlet-name>
    <url-pattern>/servlet/AxisServlet</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>AxisServlet</servlet-name>
    <url-pattern>*.jws</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>AxisServlet</servlet-name>
    <url-pattern>/services/*</url-pattern>
    </servlet-mapping>
         <!-- Session Timeout -->
         <!-- session-config>
              <session-timeout>300</session-timeout>
         </session-config -->
    <!-- currently the W3C havent settled on a media type for WSDL;
    http://www.w3.org/TR/2003/WD-wsdl12-20030303/#ietf-draft
    for now we go with the basic 'it's XML' response -->
         <mime-mapping>
              <extension>wsdl</extension>
              <mime-type>text/xml</mime-type>
         </mime-mapping>
         <mime-mapping>
         <extension>xsd</extension>
         <mime-type>text/xml</mime-type>
         </mime-mapping>          
         <welcome-file-list>
              <welcome-file>index.jsp</welcome-file>
         </welcome-file-list>
    </web-app>
    About weblogic.xml the file code is here
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
         <context-root>WebFacesEARWeb</context-root>
    </weblogic-web-app>
    Still now the problem is not solved.
    Will you please give me some suggestion so that I can deploy this application on weblogic 10.3
    In short I would like to ask if my application is using jdk 1.4 and jsf 1.1 how could I make it compitable for weblogic 10.3

  • Sending xml over http

    I have a WLS 6.0 servlet that receives XML transactions via a post method.
              Code snippet as follows:
              public void doPost(HttpServletRequest req, HttpServletResponse res)
              throws ServletException, IOException
              int txContentLength = req.getContentLength();
              //get entire input xml stream and store in a stringbuffer
              InputStream inp = req.getInputStream();
              BufferedReader br = new BufferedReader(new InputStreamReader(inp));
              byte[] ba = new byte[txContentLength];
              System.out.println("Reading...");
              int bytesRead = inp.read(ba);
              System.out.println("bytesRead= " + bytesRead);
              while(bytesRead < txContentLength) {
              int moreRead = inp.read(ba, bytesRead, (ba.length - bytesRead));
              if(moreRead == -1)
              break;
              bytesRead += moreRead;
              System.out.println("finished reading buffer...");
              StringBuffer sb = new StringBuffer(new String(ba));
              I have a java client on my PC that takes an XML file as input and sends the
              information to the servlet without any problems.
              The problem is a client that is connecting to our network via a T1
              connection. When they send transactions, about 1 out of every 4
              transactions makes it past the "Reading..." statement above. The other
              transactions appear to 'hang' when it hits the inp.read(ba) line above.
              From all indications, that servlet's execute thread appears 'hung' as if the
              inp.read() is waiting forever.
              I've tried using readLine() on the InputStream() and my local client program
              is unaffected - it works OK. The remote client is having problems using
              either method. The only difference I've noted with the remote client is
              that they are using HTTP 1.0 and I'm using HTTP 1.1. Initially, their
              mime-type was null but they've changed it to text/xml and no luck. I've
              even sent them my client code that is working and they are still having
              problems...
              Another strange anomoly is that req.getContentLength() is returning a valid
              number on the transactions that fail. For example, I had some debug code
              that showed the content length and it was always something like 4012 or
              3500, etc. Not -1 as I would expect...
              Has anyone run into this problem with receiving XML transactions?
              Thanks
              Rob Mason
              

    Thanks for the suggestion - I went back and added a check on the
              contentLength to make sure it had a valid number before trying to call any
              'read' methods... still no luck.
              I did go in and put a try/catch around the read() logic below. The
              exception thrown is an InterruptedIOException. The docs say that this is
              thrown 'to indicate that an input or output transfer has been terminated
              because the thread performing it was terminated.'
              This would seem to indicate that WLS is having the problem - not the client?
              Via the console, under the Configuration section, my HTTP section has the
              following values:
              POST timeout secs: 10
              Max POST time: 10
              Max POST size: -1
              Is there anything else I can try on the server level?
              Thanks
              Rob Mason
              "Xiang Rao" <[email protected]> wrote in message
              news:[email protected]...
              >
              > T1 shouldn't be the problem. We even use dialup to upload file via HTTP
              POST. HTTP
              > 1.0 shouldn't be problem. If you think this is the only difference, you
              can ask
              > other developers to change it to HTTP 1.1 when they request your servlet.
              >
              > The hang at read(ba) most likely means no request data are sent to your
              servlet
              > even if you think there should be some data. In your code, you are better
              to add
              > a block to check if the content_length is GREATER THAN 0 (-1 or 0), if
              not, you
              > shouldn't open any inputstream and shouldn't call any read method. If the
              content_length
              > is 0, your character buffer will have length 0 and I really don't know
              what you
              > can put into such buffer. It is not necessary to set a buffer with the
              length
              > of expected Content_Length. Since you use BufferedReader, you can create a
              buffere
              > with large enough size (see 1K, 8K, 16K, etc)and the return value of read
              will
              > give you the exact length you get for each read call, then append result
              to your
              > Stringbuffer. On the other hand, it is better for you to handle
              IOException in
              > your servlet.
              >
              > Ask the other side developers to send you their client code and compare
              their
              > code with your test code word by word. Check how they compute the
              Content_Length
              > and how they send Content_Length field to you. If this field is not
              explicitly
              > set, I think you should get -1 or 0, even there are request data out. Also
              you
              > should check how the data are sent out to make sure they really send you
              request
              > data.
              >
              >
              >
              >
              > "Rob Mason" <[email protected]> wrote:
              > >I have a WLS 6.0 servlet that receives XML transactions via a post
              method.
              > >Code snippet as follows:
              > >
              > > public void doPost(HttpServletRequest req, HttpServletResponse res)
              > > throws ServletException, IOException
              > > {
              > > int txContentLength = req.getContentLength();
              > >
              > > //get entire input xml stream and store in a stringbuffer
              > > InputStream inp = req.getInputStream();
              > > BufferedReader br = new BufferedReader(new InputStreamReader(inp));
              > >
              > > byte[] ba = new byte[txContentLength];
              > > System.out.println("Reading...");
              > > int bytesRead = inp.read(ba);
              > > System.out.println("bytesRead= " + bytesRead);
              > > while(bytesRead < txContentLength) {
              > > int moreRead = inp.read(ba, bytesRead, (ba.length - bytesRead));
              > > if(moreRead == -1)
              > > break;
              > > bytesRead += moreRead;
              > > }
              > >
              > > System.out.println("finished reading buffer...");
              > > StringBuffer sb = new StringBuffer(new String(ba));
              > >}
              > >
              > >
              > >I have a java client on my PC that takes an XML file as input and sends
              > >the
              > >information to the servlet without any problems.
              > >The problem is a client that is connecting to our network via a T1
              > >connection. When they send transactions, about 1 out of every 4
              > >transactions makes it past the "Reading..." statement above. The other
              > >transactions appear to 'hang' when it hits the inp.read(ba) line above.
              > >From all indications, that servlet's execute thread appears 'hung' as
              > >if the
              > >inp.read() is waiting forever.
              > >
              > >I've tried using readLine() on the InputStream() and my local client
              > >program
              > >is unaffected - it works OK. The remote client is having problems using
              > >either method. The only difference I've noted with the remote client
              > >is
              > >that they are using HTTP 1.0 and I'm using HTTP 1.1. Initially, their
              > >mime-type was null but they've changed it to text/xml and no luck. I've
              > >even sent them my client code that is working and they are still having
              > >problems...
              > >
              > >Another strange anomoly is that req.getContentLength() is returning a
              > >valid
              > >number on the transactions that fail. For example, I had some debug
              > >code
              > >that showed the content length and it was always something like 4012
              > >or
              > >3500, etc. Not -1 as I would expect...
              > >
              > >Has anyone run into this problem with receiving XML transactions?
              > >
              > >Thanks
              > >Rob Mason
              > >
              > >
              > >
              >
              

  • The administration console doesn't refresh

    Hello,
    I used WebCenter Portal Administration Console (http://<server>:<port>/<context_root>/admin to delete a page at runtime.
    Then I added new pages in the page hierarchy in my portal application, which I would like to see in the admin console too, but it seems they don't show up
    I mention that the admin console looks fine on my integrated environment but on the managed server it doesn't refresh.
    How the admin console should be refreshed to reflect the latest changes?
    Thanks,
    Constantin

    Yes, your understanding is correct. I added the pages in the pages folder in JDeveloper (11.1.1.4) and then added them to the page hierarchy.
    Here is the pages.xml content
    <?xml version="1.0" encoding="UTF-8" ?>
    <pagesDef xmlns="http://xmlns.oracle.com/webcenter/page"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://xmlns.oracle.com/webcenter/page/pagesDef.xsd">
    <pageDef contentMRef="/oracle/webcenter/portalapp/pages/home.jspx"
    hidden="false" shared="false" hasSubPages="false" id="home"
    overridePolicy="true"/>
    <pageDef contentMRef="/oracle/webcenter/portalapp/pages/ipc.jspx"
    hidden="true" shared="false" hasSubPages="false" id="ipc"/>
    <pageDef contentMRef="/oracle/webcenter/portalapp/pages/google.jspx"
    hidden="true" shared="false" hasSubPages="false" id="google"
    overridePolicy="true"/>
    <pageDef contentMRef="/oracle/webcenter/portalapp/pages/services.jspx"
    hidden="true" shared="false" hasSubPages="false" id="services"/>
    </pagesDef>
    I can see all the pages in the IWLS admin but in WLS admin I can see only the "home" page.
    Previously I deleted "ipc", "google" and "services" from WLS admin and I cannot see them again after a new deployment.
    I can add new pages in WLS admin without any problem.
    For IWLS, although I deleted the same pages in admin console, after a new deployment all the pages are shown.
    I guess it is the setting "delete customization before each run" in JDeveloper which allows the refresh of the IWLS admin console too.
    The question is what is the equivalant for WLS? Do I need to "clean" the customization?
    Thanks,
    Constantin

  • ADF application deployed to Weblogic producing runtime error

    Hi all,
    We are trying to deploy a new ADF application built by JDeveloper 11.1.1.5.0 to a standalone weblogic (*version 10.3.1.0*)
    The app deploys and runs on integrated wls without any problems, and deploys to the standalone wls without any warnings or errors, but does not run on standalone wls :(
    I checked many possible errors and tried many possible solutions, including, but not limited to;
    --> Checked tag references and page components on jsp/jspx pages, deleted unused or possibly unsupported tags from pages and taglibs from ui project (trinidad components 1.2), but still I get the error
    --> Using 2 different machines with JDev 11.1.1.5 we created test applications with same tech stack, tag libraries and tag references, deployed to standalone wls and they run without problems (!)
    --> Checked web.xml, the file contents and references are the same as of other applications whic are deployed from same environment to the same standalone wls and running without problems (these applications are referenced as "other working applications" following this line)
    --> In sessions.xml, the db connection is default, the file includes 2 references <server-platform xsi:type="weblogic-10-platform"/> and <primary-project xsi:type="xml">META-INF/tlMap.xml</primary-project>
    --> All projects (Model and view) are cleaned and rebuilt, deployment files are recreated, application ear is recreated, runtime application name and context root name ise changed, but still no luck, I get the same error
    --> Project technology stacks are checked and all tech stacks are configured same as "other working apllications" (since their technical architectures are the same)
    --> Checked application datasources; database connections of this application automatically create datasources, for connection dbconn1 there exists a datasource named dbconn1DS as a module in the deployed application. Other working applications had datasources with same name; to prevent a possible conflict in JNDI names of these datasources I changed the name of the db connection to a unique name, deleted the old connection and datasource. But still no luck, error is still SAME.
    --> Test applications (which have trinidad components 1.2 as tag library and there are references to it from page files) run on standalone wls, removing this taglib and the references does not make a difference. But the real application gives error when trinidad is removed from the tag libraries (java.lang.NoSuchMethodError: resetADFContext)
    --> Created new jspx pages which are not using backing beans and tried to access these, but I received the SAME error for these pages as well. Removed all jspx pages except the dummy test pages, and still no change.
    One final note; html pages in the project open without problems, as their url are different from the jspx files ( "host/appName/Test.html instead" of "host/appName/faces/Test.jspx" ) and when these pages open, the server log and console indicates new sessions created by this request.
    This is the famous error I get on the server log every time I try to access a jspx file:
    ####<Jul 31, 2012 9:14:12 AM EEST> <Error> <HTTP> <hostname> <ADF_SRV1> <[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1343715252920> <BEA-101020>
    <[ServletContext@142296767[app:KiymetliEvrak module:KiymetliEvrak path:/KiymetliEvrak spec-version:2.5]] Servlet failed with Exception
    java.lang.NullPointerException
         at oracle.adfinternal.controller.util.AdfvInterfaceImpl.addQueryParameters(AdfvInterfaceImpl.java:162)
         at oracle.adfinternal.controller.state.ControllerState.initializeUrl(ControllerState.java:708)
         at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:467)
         at oracle.adfinternal.controller.application.SyncNavigationStateListener.afterPhase(SyncNavigationStateListener.java:46)
         at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.afterPhase(ADFLifecycleImpl.java:531)
         at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchAfterEvent(LifecycleImpl.java:120)
         at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchAfterPagePhaseEvent(LifecycleImpl.java:168)
         at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchAfterPagePhaseEvent(ADFPhaseListener.java:124)
         at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.afterPhase(ADFPhaseListener.java:70)
         at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.afterPhase(ADFLifecyclePhaseListener.java:53)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:352)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:165)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96)
         at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    Could anybody please help, where to focus to see the REAL indications and solutions of this annoying error? Soon I will get this application to production environment, so any help would be appreciated.
    Thanks in advance...

    Ok, I think I should give the update, on how I struggled to solve the problem;
    --> I did NOT update the wls, since it is the production server and has many applications and services running on it , I could not take the risk of breaking those.
    --> I migrated, or rewrote the application on JDeveloper 11.1.1.1.0, rewrote the toplink map file, descriptors, pageDefs bla bla, to make it compatible with wls 10.3.1.0.
    --> Then I tested the app on JDev 11.1.1.1.0 ok, then opened the same application on JDev 11.1.1.5.0 then tested ok....
    --> And I deployed the application from JDev 11.1.1.5.0 to the standalone wls, and this is where the magic happened, the app worked without error on standalone wls 10.3.1.0
    +( Just a note: I really wonder, where is the backward, or forward compatibility of ide and server runtimes? )+
    Anyway, it is a big lesson for me about choosing the ide version for a specific server.
    Thank you...

Maybe you are looking for

  • Almost every program not from Apple crashes at startup, every time

    Hi! I have a Macbook, with a fresh OS X 10.6.6 installation (about 1 month old). I have installed MS Office, Firefox, Chrome and Skype as 3rd Party programs. Suddenly, I don't know why this happens, most of the programs don't run anymore. If I try to

  • Creating a Static IP address with this data

    This is the output from my server that I am trying to create a Static IP address:  I have tried many attempts to specify a static IP address that will no lose internet connection the last of which allowed me to get all the way through installing DNS,

  • Windows 7, RV082, QuickVPN hangs

    Hi Experts, I have a tough one.  I have installed QuickVPN on a few systems now for an office I administer and have had relatively few issues.  I have a tough one now though.  I installed QuickVPN 1.4.1.2 on a Windows 7 system.  The connection with t

  • Multiple hierarchies with shared members

    Hello, is it just a common practice to have unique parents for hierarchies built on the same Essbase dimension, or it is a system level restriction? Only in Hyperion Planning, or this is true also on Essbase level? Is it right that only the leaf node

  • Problems with WebUtil under Sun Java plugin

    Hi, I have a Forms application using WebUtil which works fine under Oracle jinitiator for years. It works with both MS IE and Mozilla Firefox (some other browsers were also successfully tested). Now when Mozilla released Firefox 3.6 requiring next ge