Weblogic 5.1 not working on my Pentium 4

I recently upgraded to a Pentium 4 and now I'm getting the following error when
I run my start up script(at this point:%JAVA_HOME%\bin\java -ms64m -mx64m)
java.exe - The instruction at '0x500bf974" referenced memory at "0x00000e7f".
The memory could not be "read".
I found this at the intel site:
Intel has identified that applications which use the Symantec Just-In-Time* Compiler
library file ("symcjit.dll" for Microsoft Windows* operating system may not run
properly on Pentium® 4 processor systems because the library does not properly
identify the processor.
Unfortunately their suggestions did not help.
Any ideas?

It has something to do with symcjit.dll, which is a compiler for the java classes.
This dll is not compliant with pentium4 machine instructions.
Solution:
step1: Install weblogic 5.1 (continue even if you find problems)
step2: install jdk 1.4
step3: change the value of registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\BEA Systems\WebLogic\5.1.0\SYSTEM_PROPERTIES
by replacing "symcjit" with "jvm"
it should work now, good luck !!
Regards,
Madhu Narayanan
"Marcusa" <[email protected]> wrote:
>
I recently upgraded to a Pentium 4 and now I'm getting the following
error when
I run my start up script(at this point:%JAVA_HOME%\bin\java -ms64m -mx64m)
java.exe - The instruction at '0x500bf974" referenced memory at "0x00000e7f".
The memory could not be "read".
I found this at the intel site:
Intel has identified that applications which use the Symantec Just-In-Time*
Compiler
library file ("symcjit.dll" for Microsoft Windows* operating system
may not run
properly on Pentium® 4 processor systems because the library does not
properly
identify the processor.
Unfortunately their suggestions did not help.
Any ideas?

Similar Messages

  • Apache-Weblogic Bridge does not work?

    I've gone thru' the documentation regarding setting up of apache-weblogic bridge, but still it does not work. Does anyboday have any more details regarding this...EnvironmentOS - Solars 5.7Weblogic - 5.1 SP 8Apache 1.3.12

    I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
    It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

  • Auto-deployment of java classes in Weblogic 9 is not working

    I have an exploded ear in my autodeploy folder and I am updating some of the java classes inside it. But it looks like weblogic 9 is not reloading new version of them. Did anybody had any success with the similar setup?
    And yes, I am updating timestamp for my REDEPLOY file and -Dweblogic.ProductionModeEnabled=false
    Thanks,

    I think it is missing - you need to do the import on your own. I filed an ER to get this one added.
    Note however that the best practice would be to minimize the usage of scripts in your JSP - since this creates spaghetti code that mixes UI with logic and is hard to maintain.

  • Disabling SSL2 in WebLogic 10.3 not working correctly

    Hey,
    I am trying to disable SSLv2 completely within WebLogic and am using the information contained here (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/ssl.html#wp1194346) and have specifically sure I'm using jsafeFIPS.jar and the "-Dweblogic.security.SSL.nojce=true" argument. I want to allow ONLY TLS and SSLv3 communication. Unfortunately, when I attempt to test this setup by forcing my browser to attempt a connection over SSL2 (and any available cipher), WebLogic will still allow me to initiate a connection and exchange certificates. To be clear, that means the packet flow looks like this when I try https://server/:
    ME-SERVER: SYN
    SERVER-ME: SYN,ACK
    ME-SERVER: ACK
    (the stuff above is just the TCP stream initiation)
    ME-SERVER: SSLv2 Client Hello (with my list of ciphers in here of course)
    SERVER-ME: ACK
    SERVER-ME: SSLv2 Server Hello (and it shows 2 cipher specs -- in the SSL2 space, and it provides my certificate)
    ME-SERVER: ACK
    ME-SERVER: SSLv2 Client Master Key (I choose to use one of the ciphers we both have)
    SERVER-ME: ACK
    (the stuff below is the tear down of the TCP stream)
    SERVER-ME: FIN,ACK
    ME-SERVER: ACK
    ME-SERVER: FIN,ACK
    The problem here is that I don't want WebLogic to walk down the path of offering ciphers it knows it will immediately reject. And I'd prefer it not even respond when SSLv2 hellos are offered. I'm lost at this point -- is this something WebLogic can do?

    I just wanted to add one more thing here: the functionality on the SSL-based node manager is even worse. Here's how that packet flow appears. The thing to focus on here is that the tear down of the TCP stream is actually initiated by me and not by the server. I'm using a browser to test this, so it looks like the browser is trying to make something happen and then timing out. To be clear, it takes me almost exactly 30 seconds before I tear down my side of this TCP session (probably a timeout).
    ME-SERVER: SYN
    SERVER-ME: SYN,ACK
    ME-SERVER: ACK
    (the stuff above is just the TCP stream initiation)
    ME-SERVER: SSLv2 Client Hello (with my list of ciphers in here of course)
    SERVER-ME: ACK
    SERVER-ME: SSLv2 Server Hello (and it shows 2 cipher specs -- in the SSL2 space, and it provides my certificate)
    ME-SERVER: ACK
    ME-SERVER: SSLv2 Client Master Key (I choose to use one of the ciphers we both have)
    SERVER-ME: ACK
    (the stuff below is the tear down of the TCP stream)
    ME-SERVER: FIN,ACK
    SERVER-ME: ACK
    SERVER-ME: FIN,ACK
    ME-SERVER: ACK

  • Custom weblogic instrumentation does not work for me :(

    Hello.
    First of all excuse me about my english.
    I have developed a simple class, I have compile it, and I have packaged it into a war file.
    The application Works ok when I do a request: http://192.168.1.5:7100/simple/hello
    But when I want to instrumentalize it, it cannot works. I have enabled instrumentation, but it I don't see anything in: Request Performance.
    Can you help me?.
    These are the files:
    simple_temp3
    |
    +- hello.html
    |
    +- WEB-INF
         +- web.xml
         |
    +- META-INF
         +- weblogic-diagnostics.xml
              |
         +- classes
             +- edu
                 +- ucla
                     +- hello.class
    [weblogic@localhost simple_temp3]$ cat hello.html
    <html>
        <head><title>Hello World</title></head>
        <body><h1>Hello World</h1></body>
    </html>
    [weblogic@localhost simple_temp3]$ cat META-INF/weblogic-diagnostics.xml
    <wldf-resource xmlns="http://www.bea.com/ns/weblogic/90/diagnostics"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/diagnostics.xsd">
        <name>Sample WLDF resource</name>
        <instrumentation>
              <enabled>true</enabled>
                  <wldf-instrumentation-monitor>
                      <name>sample</name>
                      <enabled>true</enabled>
                      <action>TraceElapsedTimeAction</action>
                      <location-type>around</location-type>
                  </wldf-instrumentation-monitor>
        </instrumentation>
    </wldf-resource>
    [weblogic@localhost simple_temp3]$ cat WEB-INF/web.xml
    <web-app id="simple" version="2.4">
        <welcome-file-list>
                <welcome-file>hello.html</welcome-file>
        </welcome-file-list>
    <servlet>
        <servlet-name>Hello</servlet-name>
            <servlet-class>Hello</servlet-class>
    </servlet>
    <servlet-mapping>
         <servlet-name>Hello</servlet-name>
             <url-pattern>/hello</url-pattern>
    </servlet-mapping>
    </web-app>
    [weblogic@localhost simple_temp3]$ cat WEB-INF/classes/edu/ucla/Hello.java  (this is the source Class)
    import javax.servlet.Servlet;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import java.io.IOException;
    import java.io.PrintWriter;
    public class Hello extends HttpServlet implements Servlet {
        public Hello() {}
        protected void doGet(HttpServletRequest request, HttpServletResponse response)
        throws ServletException, IOException
            PrintWriter out = response.getWriter();
            out.println("<HTML>");
            out.println("<HEAD><TITLE>Hello World</TITLE></HEAD>");
            out.println("<BODY>");
            out.println("<H1>Hello World</H1>");
            out.println("Today is: " + (new java.util.Date().toString()) );
            out.println("</BODY></HTML>");
            out.close();

    Can anyone help me?

  • Hot deploy in weblogic 10.0 not working

    Hi,
    I am trying to do hot deploy in an exploded war deployment. If I deploy the same exploded war in weblogic 9.2, I can update the class files without restarting the sever. However, in weblogic 10.0 system throws “java.lang.ClassCastException: com.xxx.xxx.xxxxx” when it tries to reload the app after the old class file has been updated with a new one. If the server is restarted then the new class file is picked without any errors. Are there different settings in weblogic 10.0 to enable hot deploy? Please let me know.
    Thanks a lot.

    Please don't cross-post.
    Cameron Purdy
    Tangosol Inc.
    Tangosol Coherence: Clustered Coherent Cache for J2EE
    Information at http://www.tangosol.com/
    "vinayvangala" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    Did anybody get hot deploy in an expanded directory format to work
    in weblogic 6.0 sp2. I have tried to follow the documentation but
    couldn't get it to work.
    Thanks
    Vinay

  • Weblogic job scheduler not works in cluster

    I have configured a cluster with two managed servers. I have configured a datasource for job scheduler for this cluster
    if I shut down one server job does not start on other server of cluster.
    manged server logs give below exception
    Exception in thread "Thread-211" java.lang.NullPointerException
         at com.mysql.jdbc.Statement$1.run(Statement.java:96)
    If I remove the option 'datasource for job scheduler' in Clsuter->MyServer->scheduling , this exception goes.
    job scheduler table weblogic_timers also remains empty.
    I feel that there is some issue with the schema of weblogic_timers. How can I see something in log to know what is the issue.
    Please help I am struggling from a week.

    I have configured a cluster with two managed servers. I have configured a datasource for job scheduler for this cluster
    if I shut down one server job does not start on other server of cluster.
    manged server logs give below exception
    Exception in thread "Thread-211" java.lang.NullPointerException
         at com.mysql.jdbc.Statement$1.run(Statement.java:96)
    If I remove the option 'datasource for job scheduler' in Clsuter->MyServer->scheduling , this exception goes.
    job scheduler table weblogic_timers also remains empty.
    I feel that there is some issue with the schema of weblogic_timers. How can I see something in log to know what is the issue.
    Please help I am struggling from a week.

  • Weblogic Application redeployment  not working

    Hi guys
    I am running on WL10.0 (WLP10.2). I was trying to implement application-redeployment. I gave version name to app, and update it. But application just keeps on waiting (deploy Running status). Where as it should come to Active state and the older version should be retired state.
    Is it working for anyone?
    Thanks

    I have seen this many times wls 9 and 10. I usually follow these steps to get it in active state.
    1. Shutdown all the JVMs.
    2. Start Admin server and undo any unactivated changes
    3. delete the cache directory on all the jvms. (check also permission for all the files)
    4. bring up the managed servers
    5. update the application again.
    It works for me most of the time. Hope this helps.
    regards,
    Harsha

  • Apache Abdera deployment is not working in Weblogc9.1

    Hi
    I am accessing Atom feed from one url(www.example.com.rss.xml). I wrote one servlet and deployed it in weblogic9.1 and Tomcat5.5.
    Weblogic deployement is not working. but tomcat deployment is working properly.
    My Code is :
    public void service(HttpServletRequest req, HttpServletResponse res) throws ServletException,IOException
              try
                   Abdera abdera = new Abdera();
                   Client client = new CommonsClient(abdera);
                   RequestOptions options = client.getDefaultRequestOptions();
                   System.out.println("checkFeedModification method RequestOptions options after");
                   Calendar calendar = Calendar.getInstance();
                   options.setIfModifiedSince(calendar.getTime());
                   options.setNoCache(true);
                   System.out.println("Feed URL is : http://xxx.xxxx.xxx/feed/xxxx/v1");     
                   ClientResponse response = client.get(" http://xxx.xxxx.xxx/feed/xxxx/v1", options);
                   Parser parser = Abdera.getNewParser();     
                   Document<Feed> doc = parser.parse(response.getInputStream());
                   PrintWriter out = res.getWriter();
                   out.println(doc.getRoot().toString());
    }catch(Exception e)
                   e.printStackTrace();
    My Classpath jar files are :
    D:\abdera.0.2.2-incubating\abdera.client.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.core.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.extensions.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.parser.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.protocol.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.security.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\abdera.server.0.2.2-incubating.jar;D:\abdera.0.2.2-incubating\lib\axiom-api-1.2.1.jar;D:\abdera.0.2.2-incubating\lib\axiom-impl-1.2.1.jar;D:\abdera.0.2.2-incubating\lib\bcprov-jdk15-134.jar;D:\abdera.0.2.2-incubating\lib\commons-codec-1.3.jar;D:\abdera.0.2.2-incubating\lib\commons-httpclient-3.0.1.jar;D:\abdera.0.2.2-incubating\lib\commons-logging-1.0.4.jar;D:\abdera.0.2.2-incubating\lib\geronimo-activation_1.0.2_spec-1.1.jar;D:\abdera.0.2.2-incubating\lib\jaxen-1.1-beta-7.jar;D:\abdera.0.2.2-incubating\lib\json-1.0.jar;D:\abdera.0.2.2-incubating\lib\log4j-1.2.12.jar;D:\abdera.0.2.2-incubating\lib\stax-api-1.0.jar;D:\abdera.0.2.2-incubating\lib\xmlsec-1.3.0.jar;D:\abdera.0.2.2-incubating\lib\stax-1.2.0.jar
    Could you please suggest me where iam doing wrong?
    Thanks.
    Edited by srinukanta at 04/17/2007 6:21 AM
    Edited by srinukanta at 04/17/2007 6:24 AM

    Hi Prakash,
    The "Run standalone web module from workspace" doesn't publish the application to the server (instead the app is deployed to a temp location).
    This is mainly to help test the app during the development stages. If your app is complete and would like to publish to the server then you might want to try the following option
    - In Server View, double click on the configuration to launch Overview
    - Select "Copy stand-alone web module into separate deployment folder"
    - Save the configuration
    - Start the server
    The application would be deployed to the server as a WAR file.

  • Jrockit multicast bug on RHEL4, WLS cluster does not works!

    OS and Kernel Version: Linux achilles1 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 16:59:36 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
    We use Bea Weblogic 8.1SP5 with Jrockit JVM 1.4.2 on RHEL3. We upgraded to operating system to RHEL4, and found that the interface binding for multicast communication does not bind to the correct interface, it is always using the default interface. We tried it from a sample program, and found that the error is in the JVM.
    This is a critical error for us, because our application server cluster use multicast for cluster communication.
    No error msg. It seems like this BUG:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4082533 but it is solved.
    List steps to reproduce the problem:
    socket = new MulticastSocket(i);
    if(s2 != null)
    try
    InetAddress inetaddress = InetAddress.getByName(s2);
    System.out.println("Using interface at " + inetaddress.getHostAddress());
    socket.setInterface(inetaddress);
    System.out.println(socket.getInterface());
    catch(SocketException socketexception)
    throw socketexception;
    }

    Helo,
    You can reproduce it by this way (we have 6 RHEL4 servers, problem is the same). We tried with programs written in C (mcast,Tibco), multicast perfectly works on all interfaces on all servers. But in Java:
    Server:
    [wlxapp@webex3]$ uname -a
    Linux webex3 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 17:05:24 EDT 2006 i686 i686 i386 GNU/Linux
    Problem - with Bea mukticast tester (or any Java class), using the nondefault webex3-priv interface(eth1):
    [wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3_priv -I webex3_priv -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 192.168.1.1 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3_priv every 2 seconds Will print warning every 600 seconds if no messages are received
    I (webex3_priv) sent message num 1
    I (webex3_priv) sent message num 2
    I (webex3_priv) sent message num 3
    Did not receive any message.
    But if we use the default webex3 interface (eth0)
    [wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3 -I webex3 -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 10.4.20.4 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3 every 2 seconds Will print warning every 600 seconds if no messages are received
    I (webex3) sent message num 1
    I (webex3) sent message num 2 Received message 2 from webex3
    I (webex3) sent message num 3 Received message 3 from webex3
    Works perfectly.
    TCPDUMP:Messages are out from server(other srv also see it), so we have problems probably with receiving them:
    [root@webex3]# tcpdump -i eth1
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
    11:42:56.647362 IP webex3_priv.idmz.t-mobile.intra.afs3-callback > 224.1.1.111.afs3-callback: rx type 95 (1472)
    11:42:56.648168 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
    11:42:56.648245 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
    We examined the lsof output, the tester bind to all interfaces, so it should receive the messages:
    [wlxapp@webex3]$ /usr/sbin/lsof -p 11127
    gij 11127 wlxapp 8u IPv4 150320 UDP *:afs3-callback
    We tried the test with Java 1.4.2 and 1.5 (Jrockit and Sun), the results are the same.
    You can easily reproduce the problem with an RHEL4 server with 2 network interface.
    Our real problem that if multicast have problems, our Weblogic clusters does not works.

  • Eclipse Plugin is not work

    Weblogic plugin is not work, help me!!
    platform : Windows XP Home Edition
    Eclipse Version : 2.1
    J2SDK : 1.3.1_06
    Weblogic plugin 1.0.0c
    Weblogic version : 6.1sp3
    Weblogic install folder : C:\Server\bea
    Eclipse Plugin setting
    Weblogic
    Version : 6.1
    Bea Home : C:\Server\bea
    Domain Name ; mydomain
    Domain Directory : C:\Server\bea\wlserver6.1\config\mydomain
    Serve Name : localhost
    User : System
    Password : passwd
    Hostname : localhost
    Port : null
    Classpath
    Classpath before the Weblogic libraries
    C:\Server\bea
    Classpath after the Weblogic libraries
    Null
    JavaVM Options
    JVM Options
    -hotspot
    -Xms32m
    -Xmx200m
    -Dweblogic.ProductionModeEnabled=
    JNI Library path
    Null
    When Weblogic start in Eclipse, Error Message Occured.
    ----- Error Message --------
    <2003-06-10 ¿ÀÈÄ 01½Ã33ºÐ44ÃÊ> <Info> <Security> <Getting boot password from
    user.>
    Enter password to boot WebLogic server:Starting WebLogic Server ....
    <2003-06-10 ¿ÀÈÄ 01½Ã33ºÐ47ÃÊ> <Notice> <Management> <Loading configuration
    file .\config\mydomain\config.xml ...>
    <2003-06-10 ¿ÀÈÄ 01½Ã33ºÐ50ÃÊ> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    <2003-06-10 ¿ÀÈÄ 01½Ã34ºÐ54ÃÊ> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:409)
         at weblogic.security.SecurityService.initialize(SecurityService.java:119)
    <2003-06-10 ¿ÀÈÄ 01½Ã34ºÐ55ÃÊ> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:409)
         at weblogic.security.SecurityService.initialize(SecurityService.java:119)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:400)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
         at weblogic.Server.main(Server.java:35)
    '>
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:400)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
         at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Originally posted by: eclipse.rizzoweb.com
    Tom Roche wrote:
    > How to set a file exclusion pattern? What I mean:
    >
    > I work on a project that is not natively an Eclipse plugin. In order
    > to make it acceptable to PDE, I run target=eclipse in the project's
    > build.xml: among other things this copies special files (e.g.
    > plugin.xml, build.properties) from the project's eclipse folder to the
    > project's root.
    >
    > After running the target, I can Update Classpath, and I'm *almost*
    > ready to build the project with Eclipse (C-b or rclick>Build Project).
    > First I need to exclude some files. The way I do this in the UI is
    >
    > 0 select the project's Properties>Java Build Path>Source
    >
    > For each of 3 source folders (e.g. /src/foo, /src/bar, /test):
    >
    > 1 expand the folder node, choose the Excluded subnode, and hit Edit
    >
    > 2 in the Exclusion Patterns section of the resulting dialog, hit Add,
    > and enter the exclusion pattern
    >
    > **/Baz*
    >
    > 3 hit OK in that dialog and its parent
    >
    > But this is tedious/error-prone for me and our users. I'm hoping there
    > is a way that I can set the appropriate value in build.properties (or
    > elsewhere) that will allow me to avoid this manual labor. Is there?
    >
    > Feel free to forward, and to reply directly to me (as well as the
    > group), and TIA.
    You can manipulate the .classpath file, if you're careful.
    Do it manually (via the UI) and then go look at the .classpath file.
    You'll see an entry like this:
    <classpathentry excluding="**/Baz*" output="classes" kind="src" path="src"/>
    See the excluding= attribute? That's what you want to create when you're
    "building" for PDE.
    HTH,
    Eric

  • Weblogic Http Apache Plugin not working

    Hi,
    I have installed weblogic server 10.3 on WindowsXP Professional and Http Apache 2.2 is running on port 80. I followed the following document to configure the Apache plugin:
    http://e-docs.bea.com/wls/docs103/plugins/apache.html
    but when I go and test the plugin it always comes back with 404 page not found. As per the documentation I am testing it as
    http://localhost:80/weblogic/
    Here is my httpd.conf
    Include "C:/bea/alui/plumtreeconf/"
    # This is the main Apache HTTP server configuration file.  It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do.  They're here only as hints or reminders.  If you are unsure
    # consult the online docs. You have been warned. 
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path.  If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
    # server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
    # NOTE: Where filenames are specified, you must use forward slashes
    # instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    # If a drive letter is omitted, the drive on which httpd.exe is located
    # will be used by default.  It is recommended that you always supply
    # an explicit drive letter in absolute paths to avoid confusion.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path.  If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk.  If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule authn_alias_module modules/mod_authn_alias.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbd_module modules/mod_authn_dbd.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_host_module modules/mod_authz_host.so
    #LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cache_module modules/mod_cache.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule charset_lite_module modules/mod_charset_lite.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_lock_module modules/mod_dav_lock.so
    #LoadModule dbd_module modules/mod_dbd.so
    #LoadModule deflate_module modules/mod_deflate.so
    LoadModule dir_module modules/mod_dir.so
    #LoadModule disk_cache_module modules/mod_disk_cache.so
    #LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule ext_filter_module modules/mod_ext_filter.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule filter_module modules/mod_filter.so
    #LoadModule headers_module modules/mod_headers.so
    #LoadModule ident_module modules/mod_ident.so
    #LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    #LoadModule ldap_module modules/mod_ldap.so
    #LoadModule logio_module modules/mod_logio.so
    LoadModule log_config_module modules/mod_log_config.so
    #LoadModule log_forensic_module modules/mod_log_forensic.so
    #LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule proxy_module modules/mod_proxy.so
    #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule ssl_module modules/mod_ssl.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule substitute_module modules/mod_substitute.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    #LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule version_module modules/mod_version.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule weblogic_module modules/mod_wl_22.so
    <IfModule mod_weblogic.c>
      WebLogicHost localhost
      WebLogicPort 7001
    </IfModule>
    <Location /weblogic>
      SetHandler weblogic-handler
      PathTrim /weblogic
    </Location>
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch. 
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User daemon
    Group daemon
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition.  These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed.  This address appears on some server-generated pages, such
    # as error documents.  e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName localhost:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features. 
    ProxyRequests On
    <Directory />
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs">
        # Possible values for the Options directive are "None", "All",
        # or any combination of:
        #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
        # Note that "MultiViews" must be named *explicitly* --- "Options All"
        # doesn't give it to you.
        # The Options directive is both complicated and important.  Please see
        # http://httpd.apache.org/docs/2.2/mod/core.html#options
        # for more information.
        Options Indexes FollowSymLinks
        # AllowOverride controls what directives may be placed in .htaccess files.
        # It can be "All", "None", or any combination of the keywords:
        #   Options FileInfo AuthConfig Limit
        AllowOverride None
        # Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
        DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
        Order allow,deny
        Deny from all
        Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here.  If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "logs/error.log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
        # The following directives define some format nicknames for use with
        # a CustomLog directive (see below).
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          # You need to enable mod_logio.c to use %I and %O
          LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        </IfModule>
        # The location and format of the access logfile (Common Logfile Format).
        # If you do not define any access logfiles within a <VirtualHost>
        # container, they will be logged here.  Contrariwise, if you *do*
        # define per-<VirtualHost> access logfiles, transactions will be
        # logged therein and *not* in this file.
        CustomLog "logs/access.log" common
        # If you prefer a logfile with access, agent, and referer information
        # (Combined Logfile Format) you can use the following directive.
        #CustomLog "logs/access.log" combined
    </IfModule>
    <IfModule alias_module>
        # Redirect: Allows you to tell clients about documents that used to
        # exist in your server's namespace, but do not anymore. The client
        # will make a new request for the document at its new location.
        # Example:
        # Redirect permanent /foo http://localhost/bar
        # Alias: Maps web paths into filesystem paths and is used to
        # access content that does not live under the DocumentRoot.
        # Example:
        # Alias /webpath /full/filesystem/path
        # If you include a trailing / on /webpath then the server will
        # require it to be present in the URL.  You will also likely
        # need to provide a <Directory> section to allow access to
        # the filesystem path.
        # ScriptAlias: This controls which directories contain server scripts.
        # ScriptAliases are essentially the same as Aliases, except that
        # documents in the target directory are treated as applications and
        # run by the server when requested rather than as documents sent to the
        # client.  The same rules about trailing "/" apply to ScriptAlias
        # directives as to Alias.
        ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
        # ScriptSock: On threaded servers, designate the path to the UNIX
        # socket used to communicate with the CGI daemon of mod_cgid.
        #Scriptsock logs/cgisock
    </IfModule>
    # "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value.  If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
        # TypesConfig points to the file containing the list of mappings from
        # filename extension to MIME-type.
        TypesConfig conf/mime.types
        # AddType allows you to add to or override the MIME configuration
        # file specified in TypesConfig for specific file types.
        #AddType application/x-gzip .tgz
        # AddEncoding allows you to have certain browsers uncompress
        # information on the fly. Note: Not all browsers support this.
        #AddEncoding x-compress .Z
        #AddEncoding x-gzip .gz .tgz
        # If the AddEncoding directives above are commented-out, then you
        # probably should define those extensions to indicate media types:
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
        # AddHandler allows you to map certain file extensions to "handlers":
        # actions unrelated to filetype. These can be either built into the server
        # or added with the Action directive (see below)
        # To use CGI scripts outside of ScriptAliased directories:
        # (You will also need to add "ExecCGI" to the "Options" directive.)
        #AddHandler cgi-script .cgi
        # For type maps (negotiated resources):
        #AddHandler type-map var
        # Filters allow you to process content before it is sent to the client.
        # To parse .shtml files for server-side includes (SSI):
        # (You will also need to add "Includes" to the "Options" directive.)
        #AddType text/html .shtml
        #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://localhost/subscription_info.html
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files.  This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    #Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    #Include conf/extra/httpd-autoindex.conf
    # Language settings
    #Include conf/extra/httpd-languages.conf
    # User home directories
    #Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    #Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    #       starting without SSL on platforms with no /dev/random equivalent
    #       but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>Is there anything else I need to add to this file. As I am trying to install ALUI and for this I need to add the plugin as when I go to my portal page none of the
    images shows. Any help is appreciated.
    Thanks

    Hi,
    There is patch for the webserver(Apache Plugin),thats needs to be downloaded from Metalink,dont use the default plugin that comes with the weblogic 10.3 installtion.
    Regards,
    Dinesh

  • Auto-Deployment is not working in Eclipse - Weblogic

    I have created weblogic server instance in Eclipse.Then, I have added one project into weblogic server by using "Add/Remove Projects" menu.After I start the server , I logged into admin console and checked the deployments link. I am not finding the project listed in the list.I have selected option "Run stand alone web module directly from work space" in web logic server configuration window in eclipse.
    I am using Eclipse 3.3 and weblogic 10.0.
    I have no idea, why auto-deployment is not working.
    I would appreciate your help on this regard.I have contacted Eclipse Support, they have asked me to contact BEA team.
    Thanks,
    Prakash.A

    Hi Prakash,
    The "Run standalone web module from workspace" doesn't publish the application to the server (instead the app is deployed to a temp location).
    This is mainly to help test the app during the development stages. If your app is complete and would like to publish to the server then you might want to try the following option
    - In Server View, double click on the configuration to launch Overview
    - Select "Copy stand-alone web module into separate deployment folder"
    - Save the configuration
    - Start the server
    The application would be deployed to the server as a WAR file.

  • Navigation not working in Weblogic Server but working from JDeveloper.

    Hi
    I created a simple application with some page navigations (some declarative and some dynamic using Managed Bean).
    The navigation works fine when I run from JDeveloper. (Local System)
    So I deployed the application to the WebLogic server (Local system with a domain configured with ADF.)
    The pages are getting rendered correctly, bu on button clicks, the navigation is not happening from any of the pages.
    Could I have missed something or is there a way to track what the problem might be?
    JDev : 11.1.1.3
    Web Logic Server : 11gR1 (1.3) which comes with JDeveloper
    Thanks for any help.
    Sameer

    Hi John
    I am not using task flows. I just have some jspx pages defined in the unbounded task flow adfc-config.xml connected with navigation.
    I run from JDEveloper by right clicking on the jspx files.
    The URL when run from jdeveloper is as follows.
    http://127.0.0.1:7101/SessionsPOC-ViewController-context-root/faces/MainPage
    From Weblogic server I am using the link given in the Testing tab of the weblogic administration console.
    The URL is as follows.
    http://10.9.73.103:7001/SessionsPOC-ViewController-context-root (default)
    http://10.9.73.103:7001/SessionsPOC-ViewController-context-root/MainPage.jspx
    Actually, the URL given in the weblogic testing tab is not runnable. I am changing the link as follows to be able to run it.
    http://10.9.73.103:7001/SessionsPOC-ViewController-context-root/faces/MainPage.jspx
    I have defined the MainPage.jspx in the web.xml 's Welcome page. But it is not taking it I guess.
    Also, I am able to run the other page by giving the following url. But the navigation buttons are not working in that page also.
    http://10.9.73.103:7001/SessionsPOC-ViewController-context-root/faces/SecondPage.jspx
    Thanks
    Sameer

  • Debugging not working in weblogic portal

    When I am running my portal app built on weblogic portal 8.1, its throwing an error cannot start debugger. App might not be deployed properly.
    I have redeployed 2-3 times, and its running also fine, but debugger is not working.
    when the app domain starts few exceptions are thrown like,
    primary key voilated,
    jms connection pool could not connect
    Can this be the reason?

    well, from a debugging perspective, the application errors should not prevent a debugger from attaching to the VM. Can you be more specific about when you say the debugger is not starting?
    Thanks
    Mike

Maybe you are looking for