IIS 4.0 with weblogic 5.1 sp8, URGENT

Hi,
I m running Weblogic 5.1(runs on port 7001) on NT 4.0 with IIS 4.0(runs on
port 80) with IIS plugin configured properly.
I can access or run http://www.myhost.com/hello.jsp Hello.jsp is compiled
by weblogic and returned by back to IIS(browser). However if I access
http://www.myhost.com/portal/signin.jsp. signin.jsp is compiled by weblogic
and returned by back to browser through IIS. But my url get change in
between. It becomes http://www.myhost.com:7001/portal/index.jsp. How Can I
fix it so that every request is through webserver.
Any help,

Hey KP,
Try redirect by extension instead of redirect by path.
I tried redirect jsp, gif, and jpg by extension using WLS6SP1/
EFS3.5(Solaris) and IIS4(NT) and I didn't have any problem with
the 7001 port number. By the way, have you tried using https to
request /portal/index.jsp with WLS6 on either NT or
Solaris platform? My web server (either iplanet or iis) cannot
render the result return by the WLS and displays "Internal
Server failure, NSAPI plugin. Cannot continue." when I tried
https://www.myhost.com/portal/index.jsp or
https://www.myhost.com/portal/diag.jsp.
Do you know what's wrong? Help!
Tony
"K.P. Patel" <[email protected]> wrote:
Hi,
I m running Weblogic 5.1(runs on port 7001) on NT 4.0 with IIS 4.0(runs
on
port 80) with IIS plugin configured properly.
I can access or run http://www.myhost.com/hello.jsp Hello.jsp is compiled
by weblogic and returned by back to IIS(browser). However if I access
http://www.myhost.com/portal/signin.jsp. signin.jsp is compiled by weblogic
and returned by back to browser through IIS. But my url get change in
between. It becomes http://www.myhost.com:7001/portal/index.jsp. How
Can I
fix it so that every request is through webserver.
Any help,

Similar Messages

  • IIS configuration with Weblogic 10gR3

    Hi All,
    We are using IIS 6.0 as the proxy server in our portal application. The portal server is Weblogic 10gR3. I have followed some documents to configure it. (http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs103
    /plugins/isapi.html). But I am not able to configure that. Can any body help me in configuring IIS server as a proxy server.
    Thanks & Regrads
    Abani R. Behera

    Configure IIS Plug-in with Weblogic Server
    1. Make a directory on the IIS box for the plug-in.
    For instance: c:\Inetpub\WLS_IIS_Plugin\
    2. Copy iisforward.dll and iisproxy.dll to this new directory.
    These files are located at:
    10.0: \wlserver_10.0\server\plugin\win\32
    10.3: \wlserver_10.3\server\plugin\win\32
    3. To install iisforward.dll as an ISAPI filter, do the following:
    Go to Start->Administrative Tools->Internet Information Services
    (IIS) Manager
    In the left pane, drill down to the active website
    (like "Default Web Site")
    Right-click the active website and select Properties
    Select the ISAPI Filters tab and press the Add button
    Filter name: WLS IIS Plugin
    Or whatever you want
    Executable: C:\Inetpub\WLS_IIS_Plugin\iisforward.dll
    Or whatever path you created
    Press OK twice
    IIS6 does not allow the iisforward.dll ISAPI Extension to run by default.
    To enable:
    In the left pane of the Internet Information Services (IIS) Manager,
    click on Web Service Extension (located under the computer name)
    In the right pane, highlight All Unknown ISAPI Extensions and press
    the Allow button
    4. To map .wlforward to use iisproxy.dll, do the following:
    a. In the left pane, drill down to the active website (like
    "Default Web Site")
    b. Right-click the active website and select Properties
    c. Select Home Directory tab
    d. Click the Configuration... button.
    e. In the Application Mapping tab, click the Add... button.
    a. Executable: C:\Inetpub\WLS_IIS_Plugin\iisproxy.dll
    b. Extension: .wlforward
    f. Uncheck Verify that file exists
    g. IMPORTANT: Ensure .wlforward is not mapped to iisforward.dll.
    While this seems intuitive, it is wrong. .wlforward maps to
    iisproxy.dll.
    h. Press OK three times
    i. Exit the IIS Manager MMC console.
    5. Create a text file named iisproxy.ini and place it in the plug-in
    directory (e.g. c:\Inetpub\WLS_IIS_Plugin\iisproxy.ini)
    iisproxy.ini
    WebLogicCluster=localhost:7001,localhost:7003
    WlForwardPath=/
    Debug=ALL
    DebugConfigInfo=ON
    WLLogFile=c:/temp/iisproxy.log
    6. Restart IIS using the following CLI statement: iisreset /restart
    7. Use a browser to access IIS. This will 'turn on' the IIS->WLS
    ISAPI filter.
    8. Relaunch the IIS Manager and check the ISAPI filter tab to ensure
    the iisforward.dll is now 'turned on', as evidenced by a green arrow.

  • Wildcard certifications in Weblogic 5.1,SP8

    Has anyone had success in using Thawte's wildcard SSL certificates which are supposed to work with weblogic and allow for multiple sub domains? We have many subdomains running from one weblogic instance that is also clustered across several servers tied to 1 virtual IP address for load balancing. Basically, any advice on using and obtaining SSL certs INEXPENSIVELY to support many subdomains would be appreciated.

    Pratik Chatterjee wrote:
    Hi,
    We are using weblogic connection pool for Oracle 8i databases. For some reason, if the database goes down for only a few hours (after which it becomes available again), then the connection pool automatically refreshes all its connections. As a result our java applications get data normally after the database is back up.
    However, we had a very long period of database down (about 24 hours) in production recently and finally when the database became available then we noticed that our java applications were not getting data from the database. Apparently weblogic server did NOT refresh its connections in pool (it seems that after a long period of databse down, the server gave up and did not attempt to refresh connections). We just restarted the weblogic servers in production and that resolved the issue. If you encountered similar issues in the past (with WEblogic 5.1 sp8) and happen to know the resolution then please let us know.
    Also, someone in our company reported that if the database servers are down when the weblogic servers are started then weblogic does not create the connection pool at all. As a result if the database became available some time after the weblogic server started, then the java applications didn't get data (even after the DB because available). Again, if you know about this issue and the resolution, please let us know.
    Thanks,
    PratikHi. If the pool is defined with an initial capacity > 0, then when weblogic starts up,
    if it can't create that minimum number of connections, then the pool will not be created
    at all. If the initial capacity is zero, then the pool will be created whether or not
    the DBMS is up. Once a pool exists, if it needs a connection it will try to create one
    and will throw an exception to the application if it can't. Do you have test-connections-on-reserve
    set? You should. That would always ensure you get a good connection if it's possible to
    provide one.
    Joe

  • Weblogic 5.1 SP8 with JDK1.3 installed as an NT Service Fails

    I've just completed the installation of sp8 of Weblogic Server. I used wlconfig to set the environment parameters as outlined in the sp8_readme.html file. I have Weblogic Server installed as a NT Service. When I start the service with Weblogic configured to use JDK1.2 it works just fine. However, when I switch Weblogic to use the JDK1.3, using wlconfig, I receive an Application error stating:"The instruction at "0x04e4d0d6" referenced memory at "0x00000000". The memory could not be written."If I start the WEblogic Server from the command line and configure the environment to use the JDK1.3, everything works fine. It's only when you are trying to run the Weblogic server as an NT Service.Any suggestions?

    I don't think this problem was specific at all to SP8 - I ran into
    this with an earlier version of the fixpack and just decided to run it
    from the startweblogic.cmd file, instead. I never did try to set the
    compiler to none as you did. BTW - it wasn't just as a service that
    this problem existed for me - it also happened if you used the program
    shortcut to start the server - i.e. any way you started it that used
    those registry settings would experience the problem.
    How has the stability been under 1.3 - have you seen any problems with
    that? I was running with 1.3 and the Sun Server Hotspot VM and the
    server kept crashing after just a few pages being displayed from my
    site. This problem could have also been the -noclassgc switch though
    since with that switch I was still seeing the problem under 1.2 - just
    not as fast.
    On Tue, 23 Jan 2001 09:49:05 -0800, "Christopher A. Mathrusse"
    <[email protected]> wrote:
    Seeing as no one has come up with a solution for me, I thought I would at
    least post the fix. If you use JDK1.3 with WLS and are running the server as
    an NT Service, you will need to set your JAVA_HOME value to the JDK1.3 using
    wlconfig, and then set your java.compiler=NONE using
    wlconfig -Djava.copiler=NONE. After completing these changes, WLS will run
    as a service with JDK1.3.
    "Christopher Mathrusse" <[email protected]> wrote in
    message news:[email protected]...
    I've just completed the installation of sp8 of Weblogic Server. I usedwlconfig to set the environment parameters as outlined in the
    sp8_readme.html file. I have Weblogic Server installed as a NT Service. When
    I start the service with Weblogic configured to use JDK1.2 it works just
    fine. However, when I switch Weblogic to use the JDK1.3, using wlconfig, I
    receive an Application error stating:"The instruction at "0x04e4d0d6"
    referenced memory at "0x00000000". The memory could not be written."If I
    start the WEblogic Server from the command line and configure the
    environment to use the JDK1.3, everything works fine. It's only when you are
    trying to run the Weblogic server as an NT Service.Any suggestions?

  • How to configure IIS webserver with weblogic so that I can invoke servlets without the .wlforward extension

    How to configure IIS webserver with weblogic so that I can
    invoke servlets without the .wlforward extension
    As per the documentation iisforward.dll is registered as a filter and .wlforward
    has also been
    included as a special file type. However this requires me to key-in ".wlforward"
    after my servlet name.
    What I want is something like this
    http://iis/MyServlet
    Please help me find a solution to this
    Thanks,
    Rishi

    I am able to invoke the servlet without the wlforward extension now.
    However, now I am required to add /weblogic before the servlet
    name otherwise it does not execute the pathtrim property.
    I have tried with the pathprepend thing also.
    Can we get rid of the /weblogic part also. I just want to execute
    my servlet as http://iis/myServlet.
    Your help in this regard is greatly appreciated...
    Thanks..
    "Rishi" <[email protected]> wrote:
    >
    Thanks for the reply Kumar.
    I did follow the instructions as given in the Weblogic documentation
    The documentation said to add iisforward.dll as a filter service
    and register .wlforward as a special
    file type to be handled by iisproxy.dll. For this,
    while configuring the IIS server in the Home Directory tab
    I added an extension ".wlforward" and the executable as
    iisproxy.dll. Is this the way it should have been done...
    I also modified the iisproxy.ini file as per the documentation.
    I have added the WLForwardPath property and set it to /weblogic.
    My server works fine when I give the url as
    http://iis/myServlet.wlforward
    but it does not work for
    http://iis/myServlet and this is the way i'd want it to work.
    Please tell me if I am missing something on the configuration part
    and if there is something special that needs to be done. I shall
    be grateful to you.
    Kumar Allamraju <[email protected]> wrote:
    http://e-docs.bea.com/wls/docs61/adminguide/isapi.html#101184
    Rishi wrote:
    How to configure IIS webserver with weblogic so that I can
    invoke servlets without the .wlforward extension
    As per the documentation iisforward.dll is registered as a filter
    and
    .wlforward
    has also been
    included as a special file type. However this requires me to key-in".wlforward"
    after my servlet name.
    What I want is something like this
    http://iis/MyServlet
    Please help me find a solution to this
    Thanks,
    Rishi

  • IIS 6 Plug-in with Weblogic 8.1

    Hello there,
    I am just wondering if there is anyone out there, who got IIS 6 plug-in working
    with WebLogic 8.1. Plug-in perfectly works with IIS 5. When we upgraded W2K to
    W2003 plug-in didn't work with Weblogic. If there is anyone who knows how to get
    this up and running, your help will be appreciated.
    Thank you.

    Hi Vishwas,
    Thank you for the reply. I forgot to mention that Apache and WebLogic are on Solaris 9 platform.
    Accesing a webapp hosted on WebLogic through Apache->plug-in->WebLogic return 500 internal server error, but other webapps hosted on the same WebLogic domain works properly. Looking at the Response Hdrs from WebLogic shows that WLS returns transfer-encoding=chunked. The other webapps which work properly has content-length set and transfer-encoding is not chunked.
    So, the question is does Apache Plug-in for weblogic 8.1 SP5 read the chunked data properly?
    Thanks,
    Janani

  • Servlet reloading not working with WLS 5.1 sp8

              I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              the servler reloading works fine.
              Does anybody experience similar problem or have I forgot to do something?
              WLS properties/env vars setting:
              - weblogic.httpd.servlet.reloadCheckSecs=0
              - WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              - JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              Thanks in advance for any help.
              

              I've experienced the same problem with both sp6 and sp8. In both cases I performed several test, including
              - varied the value of weblogic.httpd.servlet.reloadCheckSecs
              - changes to the package depth the servlet belonged to
              - changes to the string length of the package names the servlet belonged to
              At best, the servlet would reload sometimes. I've moved back to sp5 and the problem has subsided.
              Note: I did not try registering the servlet to see how that would effect the dynamic reloading.
              Hope this helps
              - Dave
              "Michel Dinh" <[email protected]> wrote:
              >
              >I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              >problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              >work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              >the servler reloading works fine.
              >
              >
              >Does anybody experience similar problem or have I forgot to do something?
              >
              >WLS properties/env vars setting:
              >
              >- weblogic.httpd.servlet.reloadCheckSecs=0
              >- WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              >- JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              >
              >Thanks in advance for any help.
              

  • IPlanet 4.0 and Weblogic 5.10 SP8

    I'm using iPlanet 4.0 as a web server and Weblogic 5.10 SP8 as an application server.
    Everything is OK when the line "weblogic.httpd.enable=true" is written in the
    weblogic.properties file.
    When I replace "true" by "false", it declares an error :
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization
    will not help
    and the request SHOULD NOT be repeated. If the request method was not HEAD and
    the server
    wishes to make public why the request has not been fulfilled, it SHOULD describe
    the reason for
    the refusal in the entity. This status code is commonly used when the server
    does not wish to
    reveal exactly why the request has been refused, or when no other response is
    applicable.
    Is it possible to put weblogic.httpd.enable=false to use Weblogic without its
    HTTP Server, and only as an application server ?

    The certification was recently completed. It is in the process of being
    placed on the web site. At that point, it will be officially supported.
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    "Venkat K" <[email protected]> wrote in message
    news:399035f4$[email protected]..
    Hello,
    Is the NSAPI plugin provided with Weblogic 5.1 Server compatible with
    iPlanet 4.1? The Weblogic documentation doesn't seem to be clear to me on
    this one. We plan to run in this setup on Solaris 8.
    Any details on this are appreciated.
    Thanks in advance and Best Regards,
    Venkat K.

  • Weblogic 5.1 SP8 on WIN NT Hangs

    Hi,
    I have the following configuration being tested for load.
    Weblogic 5.1 SP8, Windows NT, Java 1.2.2, Oracle 8.1.6.
    I am running load scripts that access JSP. There are about 15 users doing
    fixed number of different things repeatedly i.e. they login, do a few things
    and logout. Everything runs fine for about 1 to 2 hours and after that I
    observe CPU at 100 % and users cannot do anything. I took the thread dump,
    but this does not reveal any user doing any CPU intesive operations. All the
    JSP being accessed do finite number of things that take finite time. I do
    not see anything that should make the CPU shoot up to 100 %. Do you have any
    suggestions on how to debug this problem ? I am enclosing the thread dump
    (do you think it is odd that all threads are waiting on signal dispatcher).
    Would really appreciate some suggestions.
    Thanks,
    Mihir
    Full thread dump Classic VM (JDK-1.2.2-W, native threads):
    "HighPriority TimeEventGenerator" (TID:0x6bd85f8,
    sys_thread_t:0x24c7fdc8, state:CW, native ID:0x648) prio=9
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java, Compiled
    Code)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    , Compiled Code)
    at java.lang.Thread.run(Thread.java:479)
    "ListenThread" (TID:0x632eb98, sys_thread_t:0x24ed8f80, state:R, native
    ID:0x94) prio=5
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java, Compiled Code)
    at java.net.ServerSocket.implAccept(ServerSocket.java, Compiled Code)
    at java.net.ServerSocket.accept(ServerSocket.java, Compiled Code)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java, Compiled Code)
    "NBExecuteThread-1" (TID:0x6323590, sys_thread_t:0x2245f660, state:CW,
    native ID:0x4b4) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "NBExecuteThread-0" (TID:0x6323300, sys_thread_t:0x2245e530, state:CW,
    native ID:0x618) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-14" (TID:0x6323218, sys_thread_t:0x22448ff0, state:R,
    native ID:0x260) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-13" (TID:0x63230e0, sys_thread_t:0x22448e80, state:MW,
    native ID:0x534) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at com.mycompany.expr.fn.Invoke.eval(Invoke.java, Compiled Code)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-12" (TID:0x6322fb0, sys_thread_t:0x22448d10, state:R,
    native ID:0x540) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-11" (TID:0x6322e78, sys_thread_t:0x22448ba0, state:R,
    native ID:0x5cc) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-10" (TID:0x6322a98, sys_thread_t:0x22448a30, state:R,
    native ID:0x3ec) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-9" (TID:0x6322968, sys_thread_t:0x2244a0a0, state:R,
    native ID:0x47c) prio=5
    "ExecuteThread-8" (TID:0x6322838, sys_thread_t:0x22449f30, state:MW,
    native ID:0x550) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-7" (TID:0x6322708, sys_thread_t:0x22449dc0, state:MW,
    native ID:0x6c0) prio=5
    "ExecuteThread-6" (TID:0x63225d0, sys_thread_t:0x22449c50, state:MW,
    native ID:0x624) prio=5
    "ExecuteThread-5" (TID:0x6322520, sys_thread_t:0x22449ae0, state:MW,
    native ID:0x6dc) prio=5
    "ExecuteThread-4" (TID:0x6322370, sys_thread_t:0x2244ed68, state:MW,
    native ID:0x60c) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-3" (TID:0x6322240, sys_thread_t:0x2244ebf8, state:R,
    native ID:0x62c) prio=5
    "ExecuteThread-2" (TID:0x6321fb8, sys_thread_t:0x2244ea88, state:R,
    native ID:0x6c4) prio=5
    "ExecuteThread-1" (TID:0x6321d30, sys_thread_t:0x22447930, state:MW,
    native ID:0x53c) prio=5
    "ExecuteThread-0" (TID:0x63217c0, sys_thread_t:0x2242fac8, state:MW,
    native ID:0x6a0) prio=5
    "TimeEventGenerator" (TID:0x63141c8, sys_thread_t:0x2242bb48, state:CW,
    native ID:0x5c0) prio=5
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java, Compiled
    Code)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    , Compiled Code)
    at java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" (TID:0x6313b30, sys_thread_t:0x223c0de8, state:CW,
    native ID:0x6ac) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at
    weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java,
    Compiled Code)
    at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java,
    Compiled Code)
    "SymcJIT-LazyCompilation-1" (TID:0x61afc60, sys_thread_t:0x219a5d48,
    state:CW, native ID:0x6bc) prio=1
    at SymantecJITCompilationThread.DoCompileMethod(Native Method)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "SymcJIT-LazyCompilation-0" (TID:0x61afca8, sys_thread_t:0x219a4c18,
    state:CW, native ID:0x640) prio=1
    at SymantecJITCompilationThread.DoCompileMethod(Native Method)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "SymcJIT-LazyCompilation-PA" (TID:0x61afc70, sys_thread_t:0x219a3ae8,
    state:CW, native ID:0x6a8) prio=10
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java, Compiled Code)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "Finalizer" (TID:0x61a9320, sys_thread_t:0x2105dfe0, state:CW, native
    ID:0x3cc) prio=8
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
    "Reference Handler" (TID:0x61a93b0, sys_thread_t:0x2105c638, state:CW,
    native ID:0x6b8) prio=10
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java, Compiled Code)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
    "Signal dispatcher" (TID:0x61a93e0, sys_thread_t:0x21059408, state:R,
    native ID:0x498) prio=5
    "main" (TID:0x61a91e0, sys_thread_t:0x2f5f90, state:CW, native ID:0x710)
    prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:107)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    Monitor Cache Dump:
    weblogic.time.common.internal.TimeTable@6BD8660/6F2AFE8: <unowned>
    Waiting to be notified:
    "HighPriority TimeEventGenerator" (0x24c7fdc8)
    java.net.PlainSocketImpl@6BDBA70/7357B08: owner "ListenThread"
    (0x24ed8f80) 1 entry
    oracle.jdbc.driver.OraclePreparedStatement@5E403B8/D4CF580: owner
    "ExecuteThread-8" (0x22449f30) 1 entry
    weblogic.kernel.ExecuteThread@6323590/7A400B0: <unowned>
    Waiting to be notified:
    "NBExecuteThread-1" (0x2245f660)
    weblogic.t3.srvr.T3Srvr@61CE7B0/6FC2158: <unowned>
    Waiting to be notified:
    "main" (0x2f5f90)
    SymantecJITCompilationThread@61AFCA8/6EB0288: <unowned>
    Waiting to be notified:
    "SymcJIT-LazyCompilation-PA" (0x219a3ae8)
    com.mycompany.server.proxy.MycompanyProxyBeanEOImpl@5F6FCE0/CBCB850:
    owner "ExecuteThread-8" (0x22449f30) 1 entry
    weblogic.security.SpinnerThread@6313B30/79AEB20: <unowned>
    Waiting to be notified:
    "SpinnerRandomSource" (0x223c0de8)
    java.lang.ref.ReferenceQueue$Lock@61A9338/6E786E8: <unowned>
    Waiting to be notified:
    "Finalizer" (0x2105dfe0)
    oracle.jdbc.ttc7.TTC7Protocol@63653F0/6FFF008: owner "ExecuteThread-1"
    (0x22447930) 1 entry
    java.lang.Object@62FCAA8/6FB1388: owner "ExecuteThread-4" (0x2244ed68) 1
    entry
    java.lang.ref.Reference$Lock@61A93C0/6E78228: <unowned>
    Waiting to be notified:
    "Reference Handler" (0x2105c638)
    weblogic.kernel.ExecuteThread@6323300/7A3F210: <unowned>
    Waiting to be notified:
    "NBExecuteThread-0" (0x2245e530)
    weblogic.time.common.internal.TimeTable@6314D88/79BB7C8: <unowned>
    Waiting to be notified:
    "TimeEventGenerator" (0x2242bb48)
    weblogic.jdbc.common.internal.ConnectionEnv@63652E8/6FFDF70: owner
    "ExecuteThread-1" (0x22447930) 1 entry
    oracle.jdbc.driver.OracleStatement@5E3EF90/D4DD8C0: owner
    "ExecuteThread-1" (0x22447930) 1 entry
    Registered Monitor Dump:
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Lazy Queue Lock: <unowned>
    Waiting to be notified:
    "SymcJIT-LazyCompilation-0" (0x219a4c18)
    "SymcJIT-LazyCompilation-1" (0x219a5d48)
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method List Monitor: <unowned>
    SymcJIT Lock: <unowned>
    utf8 hash
    table: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class linking lock: <unowned>
    System class loader lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Monitor cache lock: owner "Signal dispatcher" (0x21059408) 1 entry
    Waiting to enter:
    "ExecuteThread-13" (0x22448e80)
    "ExecuteThread-8" (0x22449f30)
    "ExecuteThread-7" (0x22449dc0)
    "ExecuteThread-6" (0x22449c50)
    "ExecuteThread-5" (0x22449ae0)
    "ExecuteThread-4" (0x2244ed68)
    "ExecuteThread-1" (0x22447930)
    "ExecuteThread-0" (0x2242fac8)
    Thread queue lock: owner "Signal dispatcher" (0x21059408) 1 entry
    Monitor registry: owner "Signal dispatcher" (0x21059408) 1 entry

    Going through the thread dump
    1. it looks like you are not using the Performance Packs (check if
    weblogic.system.nativeIO.enable = true in weblogic.properties)
    2. since it happens only after about an hour the garbage collector might be
    busy which consumes the processor, try using incremental GC while you start
    the weblogic server. This could be done with -Xincgc flag.
    Hope and wish this solves your problem.
    - Nirmal R.
    "Michael Reiche" <[email protected]> wrote in message
    news:[email protected]...
    It looks like the Symantec JIT Compiler is busy compiling methods andthat
    the ExecuteThreads (your JSPs) are waiting for them to finish so they can
    execute a method (presumably the method that the JIT is busy compiling) -
    just a guess.
    You may want to try a different JVM - maybe 1.3.0
    You could try turning off JIT - then your app would run impossibly slow,but
    it would still run.
    If you have any large methods - you could try and make them smaller - JVMs
    have a hard time with large/complex methods - especially nested try/catch
    blocks.
    There's no need to cross post - a lot of people read all the groups.
    Mike
    "Mihir Mehta" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I have the following configuration being tested for load.
    Weblogic 5.1 SP8, Windows NT, Java 1.2.2, Oracle 8.1.6.
    I am running load scripts that access JSP. There are about 15 users
    doing
    fixed number of different things repeatedly i.e. they login, do a fewthings
    and logout. Everything runs fine for about 1 to 2 hours and after that
    I
    observe CPU at 100 % and users cannot do anything. I took the threaddump,
    but this does not reveal any user doing any CPU intesive operations. Allthe
    JSP being accessed do finite number of things that take finite time. I
    do
    not see anything that should make the CPU shoot up to 100 %. Do you haveany
    suggestions on how to debug this problem ? I am enclosing the thread
    dump
    (do you think it is odd that all threads are waiting on signaldispatcher).
    Would really appreciate some suggestions.
    Thanks,
    Mihir
    Full thread dump Classic VM (JDK-1.2.2-W, native threads):
    "HighPriority TimeEventGenerator" (TID:0x6bd85f8,
    sys_thread_t:0x24c7fdc8, state:CW, native ID:0x648) prio=9
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java,Compiled
    Code)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.ja
    va
    , Compiled Code)
    at java.lang.Thread.run(Thread.java:479)
    "ListenThread" (TID:0x632eb98, sys_thread_t:0x24ed8f80, state:R,native
    ID:0x94) prio=5
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java, Compiled Code)
    at java.net.ServerSocket.implAccept(ServerSocket.java, Compiled Code)
    at java.net.ServerSocket.accept(ServerSocket.java, Compiled Code)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java, Compiled Code)
    "NBExecuteThread-1" (TID:0x6323590, sys_thread_t:0x2245f660,
    state:CW,
    native ID:0x4b4) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "NBExecuteThread-0" (TID:0x6323300, sys_thread_t:0x2245e530,state:CW,
    native ID:0x618) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-14" (TID:0x6323218, sys_thread_t:0x22448ff0, state:R,
    native ID:0x260) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-13" (TID:0x63230e0, sys_thread_t:0x22448e80,
    state:MW,
    native ID:0x534) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at com.mycompany.expr.fn.Invoke.eval(Invoke.java, Compiled Code)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-12" (TID:0x6322fb0, sys_thread_t:0x22448d10, state:R,
    native ID:0x540) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-11" (TID:0x6322e78, sys_thread_t:0x22448ba0, state:R,
    native ID:0x5cc) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-10" (TID:0x6322a98, sys_thread_t:0x22448a30, state:R,
    native ID:0x3ec) prio=5
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-9" (TID:0x6322968, sys_thread_t:0x2244a0a0, state:R,
    native ID:0x47c) prio=5
    "ExecuteThread-8" (TID:0x6322838, sys_thread_t:0x22449f30, state:MW,
    native ID:0x550) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-7" (TID:0x6322708, sys_thread_t:0x22449dc0, state:MW,
    native ID:0x6c0) prio=5
    "ExecuteThread-6" (TID:0x63225d0, sys_thread_t:0x22449c50, state:MW,
    native ID:0x624) prio=5
    "ExecuteThread-5" (TID:0x6322520, sys_thread_t:0x22449ae0, state:MW,
    native ID:0x6dc) prio=5
    "ExecuteThread-4" (TID:0x6322370, sys_thread_t:0x2244ed68, state:MW,
    native ID:0x60c) prio=5
    at java.lang.reflect.Method.invoke(Native Method)
    at
    com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
    Compiled Code)
    at jsp._myapp._login._jspService(_login.java, Compiled Code)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    >
    , Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java, Compiled Code)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java, Compiled Code)
    atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
    "ExecuteThread-3" (TID:0x6322240, sys_thread_t:0x2244ebf8, state:R,
    native ID:0x62c) prio=5
    "ExecuteThread-2" (TID:0x6321fb8, sys_thread_t:0x2244ea88, state:R,
    native ID:0x6c4) prio=5
    "ExecuteThread-1" (TID:0x6321d30, sys_thread_t:0x22447930, state:MW,
    native ID:0x53c) prio=5
    "ExecuteThread-0" (TID:0x63217c0, sys_thread_t:0x2242fac8, state:MW,
    native ID:0x6a0) prio=5
    "TimeEventGenerator" (TID:0x63141c8, sys_thread_t:0x2242bb48,state:CW,
    native ID:0x5c0) prio=5
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java,Compiled
    Code)
    at
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    , Compiled Code)
    at java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" (TID:0x6313b30, sys_thread_t:0x223c0de8,state:CW,
    native ID:0x6ac) prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at
    weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java,
    Compiled Code)
    at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java,
    Compiled Code)
    "SymcJIT-LazyCompilation-1" (TID:0x61afc60, sys_thread_t:0x219a5d48,
    state:CW, native ID:0x6bc) prio=1
    at SymantecJITCompilationThread.DoCompileMethod(Native Method)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "SymcJIT-LazyCompilation-0" (TID:0x61afca8, sys_thread_t:0x219a4c18,
    state:CW, native ID:0x640) prio=1
    at SymantecJITCompilationThread.DoCompileMethod(Native Method)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "SymcJIT-LazyCompilation-PA" (TID:0x61afc70,sys_thread_t:0x219a3ae8,
    state:CW, native ID:0x6a8) prio=10
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java, Compiled Code)
    at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
    Code)
    "Finalizer" (TID:0x61a9320, sys_thread_t:0x2105dfe0, state:CW,native
    ID:0x3cc) prio=8
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, CompiledCode)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, CompiledCode)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
    "Reference Handler" (TID:0x61a93b0, sys_thread_t:0x2105c638,
    state:CW,
    native ID:0x6b8) prio=10
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java, Compiled Code)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
    "Signal dispatcher" (TID:0x61a93e0, sys_thread_t:0x21059408,state:R,
    native ID:0x498) prio=5
    "main" (TID:0x61a91e0, sys_thread_t:0x2f5f90, state:CW, nativeID:0x710)
    prio=5
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:424)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:107)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    Monitor Cache Dump:
    weblogic.time.common.internal.TimeTable@6BD8660/6F2AFE8: <unowned>
    Waiting to be notified:
    "HighPriority TimeEventGenerator" (0x24c7fdc8)
    java.net.PlainSocketImpl@6BDBA70/7357B08: owner "ListenThread"
    (0x24ed8f80) 1 entry
    oracle.jdbc.driver.OraclePreparedStatement@5E403B8/D4CF580: owner
    "ExecuteThread-8" (0x22449f30) 1 entry
    weblogic.kernel.ExecuteThread@6323590/7A400B0: <unowned>
    Waiting to be notified:
    "NBExecuteThread-1" (0x2245f660)
    weblogic.t3.srvr.T3Srvr@61CE7B0/6FC2158: <unowned>
    Waiting to be notified:
    "main" (0x2f5f90)
    SymantecJITCompilationThread@61AFCA8/6EB0288: <unowned>
    Waiting to be notified:
    "SymcJIT-LazyCompilation-PA" (0x219a3ae8)
    com.mycompany.server.proxy.MycompanyProxyBeanEOImpl@5F6FCE0/CBCB850:
    owner "ExecuteThread-8" (0x22449f30) 1 entry
    weblogic.security.SpinnerThread@6313B30/79AEB20: <unowned>
    Waiting to be notified:
    "SpinnerRandomSource" (0x223c0de8)
    java.lang.ref.ReferenceQueue$Lock@61A9338/6E786E8: <unowned>
    Waiting to be notified:
    "Finalizer" (0x2105dfe0)
    oracle.jdbc.ttc7.TTC7Protocol@63653F0/6FFF008: owner
    "ExecuteThread-1"
    (0x22447930) 1 entry
    java.lang.Object@62FCAA8/6FB1388: owner "ExecuteThread-4"(0x2244ed68)
    1
    entry
    java.lang.ref.Reference$Lock@61A93C0/6E78228: <unowned>
    Waiting to be notified:
    "Reference Handler" (0x2105c638)
    weblogic.kernel.ExecuteThread@6323300/7A3F210: <unowned>
    Waiting to be notified:
    "NBExecuteThread-0" (0x2245e530)
    weblogic.time.common.internal.TimeTable@6314D88/79BB7C8: <unowned>
    Waiting to be notified:
    "TimeEventGenerator" (0x2242bb48)
    weblogic.jdbc.common.internal.ConnectionEnv@63652E8/6FFDF70: owner
    "ExecuteThread-1" (0x22447930) 1 entry
    oracle.jdbc.driver.OracleStatement@5E3EF90/D4DD8C0: owner
    "ExecuteThread-1" (0x22447930) 1 entry
    Registered Monitor Dump:
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Lazy Queue Lock: <unowned>
    Waiting to be notified:
    "SymcJIT-LazyCompilation-0" (0x219a4c18)
    "SymcJIT-LazyCompilation-1" (0x219a5d48)
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method List Monitor: <unowned>
    SymcJIT Lock: <unowned>
    utf8 hash
    table: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class linking lock: <unowned>
    System class loader lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Monitor cache lock: owner "Signal dispatcher" (0x21059408) 1 entry
    Waiting to enter:
    "ExecuteThread-13" (0x22448e80)
    "ExecuteThread-8" (0x22449f30)
    "ExecuteThread-7" (0x22449dc0)
    "ExecuteThread-6" (0x22449c50)
    "ExecuteThread-5" (0x22449ae0)
    "ExecuteThread-4" (0x2244ed68)
    "ExecuteThread-1" (0x22447930)
    "ExecuteThread-0" (0x2242fac8)
    Thread queue lock: owner "Signal dispatcher" (0x21059408) 1 entry
    Monitor registry: owner "Signal dispatcher" (0x21059408) 1 entry

  • WebLogic Security in sp8

    "There is a security issue with the JDK that we are using, 1.2.2_05a. It can only be exploited in certain circumstances. I have some questions that I can not find an answer to on ASK BEA:1. Is WebLogic 5.1 sp8 vulnerable to the exploit described in Sun Security Bulletin

    为了方便Weblogic用户管理JKS证书，我发布了一个Eclipse插件，代号SecureX，该插件将集成Keytool, Axis数字签名，加密，和SSO/SSL向导，目前版本为1.0.0，改自于KeytoolGUI1.6版本。
    作了不少的增强，原来的版本已经停止开发并被作者商业化，开源版本以后将由我提供：）
    SecureX 的URL: http://www.blogjava.net/openssl/archive/2006/03/17/35781.html
    关于SecureX，请参看http://www.blogjava.net/openssl/archive/2006/02/08/29886.aspx
    该Project遵循GPL，参见https://sourceforge.net/projects/securex/
    源代码将在2.0发布到SF。
    代替Keytool的图形化界面，增加了数字签名功能，原来的版本来自于Keytool Gui 1.6（基于SWing）,我重写了SWT界面，集成到SecureX并以SecureX为基础，不断扩展Java Security功能，包括加密，签名，SSO向导，SSL向导之类的功能。
    下载：
    http://www.blogjava.net/Files/openssl/plugins.part1.rar
    http://www.blogjava.net/Files/openssl/plugins.part2.rar
    http://www.blogjava.net/Files/openssl/plugins.part3.rar
    http://www.blogjava.net/Files/openssl/plugins.part4.rar
    http://www.blogjava.net/Files/openssl/plugins.part5.rar
    http://www.blogjava.net/Files/openssl/plugins.part6.rar
    http://www.blogjava.net/Files/openssl/plugins.part7.rar
    下载完毕后，解压到plugins目录，然后找到
    其子目录SecureX_1.0.0
    然后，将其整个Copy到Eclipse目录下的Plugin目录下，重启Eclipse，
    然后点击菜单项Securex下KeyTool，就可以运行。
    如对SecureX有兴趣，请加入SecuritySite群（14966586）或者email给我：openssl(at)163.com

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Crystal Report 9 connectivity with WebLogic 10.3.5

    Hello,
    Is the Crystal Report 9 certified with WebLogic 10.x? Currently WebLogic 8.x is in use. Trying to upgrade the WebLogic.
    Thanks

    What does this have to do with Database Connectivity?
    An I doubt it, CR 9 is about 8 or 9 years old well before 10.3 was released. Check the Platforms PDF's for more info.
    Don

  • Has anyone used JAAS with WebLogic?

    Has anyone used JAAS with Weblogic? I was looking at their example, and I have a bunch of questions about it. Here goes:
    Basically the problem is this: the plug-in LoginModule model of JAAS used in WebLogic (with EJB Servers) seems to allow clients to falsely authenticate.
    Let me give you a little background on what brought me to this. You can find the WebLogic JAAS example (to which I refer below) in the pdf: http://e-docs.bea.com/wls/docs61/pdf/security.pdf . (I believe you want pages 64-74) WebLogic, I believe goes about this all wrong. They allow the client to use their own LoginModules, as well as CallBackHandlers. This is dangerous, as it allows them to get a reference (in the module) to the LoginContext's Subject and authenticate themselves (i.e. associate a Principal with the subject). As we know from JAAS, the way AccessController checks permissions is by looking at the Principal in the Subject and seeing if that Principal is granted the permission in the "policy" file (or by checking with the Policy class). What it does NOT do, is see if that Subject
    has the right to hold that Principal. Rather, it assumes the Subject is authenticated.
    So a user who is allowed to use their own Module (as WebLogic's example shows) could do something like:
    //THEIR LOGIN MODULE (SOME CODE CUT-OUT FOR BREVITY)
    public class BasicModule implements LoginModule
    private NameCallback strName;
    private PasswordCallback strPass;
    private CallbackHandler myCB;
    private Subject subj;
             //INITIALIZE THIS MODULE
               public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options)
                      try
                           //SET SUBJECT
                             subj = subject;  //NOTE: THIS GIVES YOU REFERENCE
    TO LOGIN CONTEXT'S SUBJECT
                                                     // AND ALLOWS YOU TO PASS
    IT BACK TO THE LOGIN CONTEXT
                           //SET CALLBACKHANDLERS
                             strName = new NameCallback("Your Name: ");
                             strPass = new PasswordCallback("Password:", false);
                             Callback[] cb = { strName, strPass };
                           //HANDLE THE CALLBACKS
                             callbackHandler.handle(cb);
                      } catch (Exception e) { System.out.println(e); }
         //LOG THE USER IN
           public boolean login() throws LoginException
              //TEST TO SEE IF SUBJECT HOLDS ANYTHING YET
              System.out.println( "PRIOR TO AUTHENTICATION, SUBJECT HOLDS: " +
    subj.getPrincipals().size() + " Principals");
              //SUBJECT AUTHENTICATED - BECAUSE SUBJECT NOW HOLDS THE PRINCIPAL
               MyPrincipal m = new MyPrincipal("Admin");
               subj.getPrincipals().add(m);
               return true;
             public boolean commit() throws LoginException
                   return true;
        }(Sorry for all that code)
    I tested the above code, and it fully associates the Subject (and its principal) with the LoginContext. So my question is, where in the process (and code) can we put the LoginContext and Modules so that a client cannot
    do this? With the above example, there is no Security. (a call to: myLoginContext.getSubject().doAs(...) will work)
    I think the key here is to understand JAAS's plug-in security model to mean:
    (Below are my words)
    The point of JAAS is to allow an application to use different ways of authenticating without changing the application's code, but NOT to allow the user to authenticate however they want.
    In WebLogic's example, they unfortunately seem to have used the latter understanding, i.e. "allow the user to authenticate however they want."
    That, as I think I've shown, is not security. So how do we solve this? We need to put JAAS on the server side (with no direct JAAS client-side), and that includes the LoginModules as well as LoginContext. So for an EJB Server this means that the same internal permission
    checking code can be used regardless of whether a client connects through
    RMI/RMI-IIOP/JEREMIE (etc). It does NOT mean that the client gets to choose
    how they authenticate (except by choosing YOUR set ways).
    Before we even deal with a serialized subject, we need to see how JAAS can
    even be used on the back-end of an RMI (RMI-IIOP/JEREMIE) application.
    I think what needs to be done, is the client needs to have the stubs for our
    LoginModule, LoginContext, CallBackHandler, CallBacks. Then they can put
    their info into those, and everything is handled server-side. So they may
    not even need to send a Subject across anyways (but they may want to as
    well).
    Please let me know if anyone sees this problem too, or if I am just completely
    off track with this one. I think figuring out how to do JAAS as though
    everything were local, and then putting RMI (or whatever) on top is the
    first thing to tackle.

    Send this to:
    newsgroups.bea.com / security-group.

  • EJB 3.0 MDB deployment issue with weblogic 10.0

    Hi there,
    I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
    After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
    weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
    Unable to deploy EJB: MessageBean from Message.jar:
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         Truncated. see log file for complete stacktrace
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
         at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
         Truncated. see log file for complete stacktrace
    >
    Any help really appreciated. It's too urgent.
    Thanks in advance,
    Piyush

    here is the code for my bean.
    package com.ups;
    import java.util.logging.Logger;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.EJBException;
    import javax.ejb.MessageDriven;
    import javax.ejb.MessageDrivenContext;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    * Message-Driven Bean implementation class for: MessageBean
    @MessageDriven(
              activationConfig = { @ActivationConfigProperty(
                        propertyName = "destinationType", propertyValue = "javax.jms.Queue"
    public class MessageBean implements MessageListener {
         private MessageDrivenContext mdc;
    * Default constructor.
    public MessageBean() {
    // TODO Auto-generated constructor stub
    * @see MessageListener#onMessage(Message)
    public void onMessage(Message message) {
         TextMessage tmsg = null;
    try {
    tmsg = (TextMessage) message;
    System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
    System.out.println ("The onMessage() is called");
    } catch (JMSException e) {
    e.printStackTrace( );
    mdc.setRollbackOnly( );
    catch (Throwable th) {
    th.printStackTrace();
    public void ejbRemove( )throws EJBException{
         System.out.println("ejbRemove() is executed >>>>>>>");
    I have configured my JMS Distributed queue in the Weblogic.
    If possible please provide more details so that I can get rid of this error as soon as possible.
    Thanks for reply.
    Piyush

  • Security violation exception with Weblogic cluster installation on OIm 9.1

    Hi,
    I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
    m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
    DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
    e, signature={}.
    at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
    riptor.java:486)
    at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
    :80)
    at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
    tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
    ... 126 more
    ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
    Interface encounter some problems: {1}
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.in
    Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
    Any suggestions would be useful...

    No Response???
    Where are the good guys??

Maybe you are looking for