Wls 6.1 :deployng war error

hi all,
during deploying war, return this execption:
<Error> <HTTP> <sapmop31> <tata0Server1> <ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <> <101046> <[WebAppServletContext] Error loading servlet: 'ConfigServlet'>
java.lang.VerifyError: (class:XMLUtil, method: toDocument signature: Incompatible argument to function
     at AbstractXMLObject.toXML(AbstractXMLObject.java:57)
     at InitializerManager.init(InitializerManager.java:46)
     at configuration.ConfigServlet.init(ConfigServlet.java:48)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:731)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:658)
have you any ideas?
thanks
Marco

Keith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith

Similar Messages

  • Start Weblogic Server gives missing module b2b.war error

    I am getting the following error when I downloaded the BEA Workshop and platform
    8.1 and tried starting the WLS domain under evalguide. Any clues on how I can
    fix this missing b2b.war error is highly appreciated
    Thanks
    Raman
    <Mar 24, 2004 10:49:14 AM PST> <Notice> <WebLogicServer> <BEA-000327> <Starting
    WebLogic Admin Server "cgServer" for domain "evalguide">
    <Mar 24, 2004 10:49:16 AM PST> <Warning> <Management> <BEA-149317> <Application
    WLI-B2B is configured with a deprecated deployment protocol and will be deployed
    as such.>
    <Mar 24, 2004 10:49:19 AM PST> <Error> <Management> <BEA-141049> <An error occur
    red while initializing module b2b.war of application evalguide:Name=WLI-B2B,Type
    =Application from path C:\bea81\weblogic81\integration\lib: b2b.war does not exi
    st. Other modules in this application targeted to the same server will not be
    de
    ployed.>
    <Mar 24, 2004 10:49:19 AM PST> <Error> <Management> <BEA-141000> <Error occurred
    while initializing module b2b.war of application evalguide:Name=WLI-B2B,Type=Ap
    plication from path C:\bea81\weblogic81\integration\lib: weblogic.management.Dep
    loymentException: Missing module: b2b.war.>

    The file b2b.war is missing from the build 8.1 sp2.
    Go back to the original build 8.1 as found in the orange box "BEA WebLogic Workshop and Platform 8.1 - Evaluation and Resource Kit" Once you install this version you will have the file b2b.war

  • WLS 9.2 using XmlBeans error

    Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean called from a JSP.
              Using XmlBeans v2.3.0.
              Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
              JSP version is 2.0
              Servlet API is 2.4
              An exception is thrown :
                        javax.servlet.jsp.el.ELException
                   at javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
                   at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
                   at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
                   at javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
                   at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
                   at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
                   at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
                   at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
                   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
                   at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
                   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
                   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
                   at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
                   at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
                   at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                        This corresponds to the declaration of the root document within the bean e.g.
              ======== JSP code extract ===========
                        <%@ include file="/html/doctypes/StrictDoctype.html" %>
              <%@ taglib uri="utilTLD" prefix="util" %>
              <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
              <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
              <%@ page import="com.web.order.*" %>
              <%@ page language="java" session="false" %>
              <jsp:useBean id="composeXmlBean" scope="request" class="com.web.order.composeXmlBean">
              <jsp:setProperty name="composeXmlBean" property="*"/>
              </jsp:useBean>
              <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                        ============End Jsp code =======
              ========Java code extract =======
                        public class ComposeXmlBean {
                   public Document getMyXmlString() {
                             // Use XML Beans to construct the XML String
                         DDServiceDocument rootDoc = DDServiceDocument.Factory.newInstance();
                        ========End Java code ===========
              Anyone have any ideas about what could be causing this error. I have used XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by Javelin ?
              regards,
              Chris

    Chris,
              Firstly, I think your pasted jsp's line below is not correct:
              <jsp:useBean id="composeXmlBean" scope="request"
              class="com.web.order.composeXmlBean">
              Should it be <jsp:useBean id="composeXmlBean" scope="request"
              class="com.web.order.ComposeXmlBean"> ?
              I tried to reprodcue your issues locally, but fails (my testcase works fine)
              since I have not your customerized classes.
              My codes are listed below:
              1) Bean codes:
              package com.web.order;
              public class ComposeXmlBean {
              public String getMyXmlString() {
              return "100";
              public void setMyXmlString(String setV) {
              return;
              2) JSP codes:
              <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
              <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
              <%@ page import="com.web.order.*" %>
              <%@ page language="java" session="false" %>
              <jsp:useBean id="composeXmlBean" scope="request"
              class="com.web.order.ComposeXmlBean">
              <jsp:setProperty name="composeXmlBean" property="*"/>
              </jsp:useBean>
              <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
              My sugegstions:
              1) is it a XML bean related issue?
              can you remove XML releated logic to verify whether JSP compiler could
              support this kind of EL ( "${composeXmlBean.myXmlString}") correctly?
              2) If possible, can you pasted a reproducer here(a .war)?
              3) As for WLS8.1, which only support JSP1.2 and dose not support JSP2.0's
              EL, while your failed points is at EL: "${composeXmlBean.myXmlString}" in
              fact, I think your testcases are different during these two tests(WLS 8.1
              and WLS 9.2), Or that EL dose not work at all in WLS8.1. Can you help to
              clarify this?
              Regards
              Leon
              <Chris Thorp> wrote in message news:[email protected]...
              Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean
              called from a JSP.
              Using XmlBeans v2.3.0.
              Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
              JSP version is 2.0
              Servlet API is 2.4
              An exception is thrown :
                        javax.servlet.jsp.el.ELException
              at
              javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
              at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
              at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
              at
              javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
              at
              javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
              at
              javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
              at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
              at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
              at
              weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
              at
              weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
              at
              weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
              at
              weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
              at
              weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
              at
              weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
              at
              weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
              at
              weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
              at
              weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                        This corresponds to the declaration of the root document within the bean
              e.g.
              ======== JSP code extract ===========
                        <%@ include file="/html/doctypes/StrictDoctype.html" %>
              <%@ taglib uri="utilTLD" prefix="util" %>
              <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
              <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
              <%@ page import="com.web.order.*" %>
              <%@ page language="java" session="false" %>
              <jsp:useBean id="composeXmlBean" scope="request"
              class="com.web.order.composeXmlBean">
              <jsp:setProperty name="composeXmlBean" property="*"/>
              </jsp:useBean>
              <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                        ============End Jsp code =======
              ========Java code extract =======
                        public class ComposeXmlBean {
              public Document getMyXmlString() {
                             // Use XML Beans to construct the XML String
                    DDServiceDocument rootDoc =
              DDServiceDocument.Factory.newInstance();
                        ========End Java code ===========
              Anyone have any ideas about what could be causing this error. I have used
              XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by
              Javelin ?
              regards,
              Chris

  • Wls 10.0 - intermittent 401 errors

    I have a simple HelloWorld servlet that is configured to use CLIENT-CERT as the authentication mechanism.
    I am attempting to deploy this to a WLS 10.0 instance (though the problem I'm seeing also occurs under 9.2)
    When I access the servlet once from my web browser everything works fine, the 2-way SSL handshake takes place and I get the output from my servlet.
    However, if I attempt to access the servlet from multiple tabs concurrently, I get 401 errors intermittently. I can pick any one of the tabs that has a 401 error, hit 'reload' and get the correct output from the servlet.
    I'm concluding that this problem shows up when too many concurrent authentication attempts are made I get the 401 errors.
    This problem disappears if I remove the <security-contraint> section from the web.xml. This leads to the following questions:
    1) If the <security-constraint> configures the servlet to allow any authenticated user (i.e the role specified maps to <principal-name>users</principal-name> in weblogic.xml) AND my WebLogic server is configured to require client certificates (and only listen on the SSL port), is the <security-constraint> serving any purpose?
    2) How do I go about debugging this? Is this some sort of thread/resource issue that can be tweaked through WebLogic server settings somewhere?
    Thanks in advance,
    Bruce

    Probably too late for an answer but I try,
    We are not able to build our J2EE 1.4 application with weblo 10, we have to build them with weblo 8 which contains the xdoclet. then we deploy it in WL10. then sometimes we have to fix some build constraints that WL10 doesn't allow anymore.

  • WLS 6.1 SP4 Recompilation Error

    Hi,
    We run version WLS 6.1 SP4 (I never noticed this when we were using
    WLS 6.1) on each of development, system test, and production machines.
    When I compile and deploy my web app to our devlopment machine
    everything is fine. It is always compiled on our devlopment machine.
    However when I deploy the same web app to our system test machine it
    gives the following error:
    ####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
    <myserver> <main> <system> <> <010004
    <The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
    This has always happened on our development machine but not on our
    production machine, so it has never really been a problem because it
    just recompiles it and everything is fine.
    But now I have added some EJBs to the web app and now when I
    recompiles it at startup it never compiles the new EJBs, and thus
    never deployes them.
    I have check the following on each machine to compare WLS versions.
    wlgenerated file in the app jar file
    java weblogic.ejbc -version
    java weblogic.version
    and java -version
    They all report to be the exactly the same version.
    Are there any suggestions to stop the WLS recompiling my app or to
    make it compile my new EJBs when the server starts up.
    Any suggestions would be very much appricited.
    Cheers
    Keith

    Keith,
    This message gives you exact reason. Double-check classpaths
    used the start weblogic and to run ejbc. There may be something
    left from previous installations.
    Regards,
    Slava Imeshev
    "Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
    >
    Hi,
    We run version WLS 6.1 SP4 (I never noticed this when we were using
    WLS 6.1) on each of development, system test, and production machines.
    When I compile and deploy my web app to our devlopment machine
    everything is fine. It is always compiled on our devlopment machine.
    However when I deploy the same web app to our system test machine it
    gives the following error:
    ####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
    <myserver> <main> <system> <> <010004
    <The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
    This has always happened on our development machine but not on our
    production machine, so it has never really been a problem because it
    just recompiles it and everything is fine.
    But now I have added some EJBs to the web app and now when I
    recompiles it at startup it never compiles the new EJBs, and thus
    never deployes them.
    I have check the following on each machine to compare WLS versions.
    wlgenerated file in the app jar file
    java weblogic.ejbc -version
    java weblogic.version
    and java -version
    They all report to be the exactly the same version.
    Are there any suggestions to stop the WLS recompiling my app or to
    make it compile my new EJBs when the server starts up.
    Any suggestions would be very much appricited.
    Cheers
    Keith

  • WLS 7.0 SP2 - deploy error using security-permission in weblogic.xml on Win NT (jdk1.3.1)

    I am trying to use this in my weblogic.xml and this is the error that I get:
    weblogic-web-app>
    <description>Test Web App</description>
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jdbc/TestDSRef</res-ref-name>
    <jndi-name>TestJdbc</jndi-name>
    </resource-description>
    </reference-descriptor>
    <security-permission>
    <security-permission-spec>
         // grant ability to read any file
         grant codeBase "http://server/virtual_directory/-"
         permission java.io.FilePermission "<<ALL FILES>>", "read";
         </security-permission-spec>
    </security-permission>
    </weblogic-web-app>
    Error parsing descriptor in Web appplication "e:\bea7_2\user_projects\mydomain\.\applications\.wlnotdelete\wl_comp15697.war"
    [Path="e:\bea7_2\user_projects\mydomain\.\myserver\upload\ourpeople", URI="ourpeople.war"]
    Any ideas on what I might be doing wrong? When I remove the security-permissions,
    the application deploys fine.

    I am trying to use this in my weblogic.xml and this is the error that I get:
    weblogic-web-app>
    <description>Test Web App</description>
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jdbc/TestDSRef</res-ref-name>
    <jndi-name>TestJdbc</jndi-name>
    </resource-description>
    </reference-descriptor>
    <security-permission>
    <security-permission-spec>
         // grant ability to read any file
         grant codeBase "http://server/virtual_directory/-"
         permission java.io.FilePermission "<<ALL FILES>>", "read";
         </security-permission-spec>
    </security-permission>
    </weblogic-web-app>
    Error parsing descriptor in Web appplication "e:\bea7_2\user_projects\mydomain\.\applications\.wlnotdelete\wl_comp15697.war"
    [Path="e:\bea7_2\user_projects\mydomain\.\myserver\upload\ourpeople", URI="ourpeople.war"]
    Any ideas on what I might be doing wrong? When I remove the security-permissions,
    the application deploys fine.

  • WLS 10.3: Node Manager  error while starting managed server

    Hi,
    I get the following error when trying to start a managed server using Node Manager from the Admin console on WLS 10.3
    Error:
    <27/11/2009 3:21:34 PM> <Info> <NodeManager> <Server output log file is "/opt/osb/osb_env/domains/DevVVDomain/servers/dev_osb_server1/logs/dev_osb_server1.out">
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : grepuname: : not foundnot found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : not foundgrep
    : not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: expr: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: test: argument expected
    <27/11/2009 3:21:35 PM> <Debug> <NodeManager> <Waiting for the process to die: null>
    <27/11/2009 3:21:35 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <27/11/2009 3:21:35 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>My nodemanager.properties file looks like this:
    DomainsFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.domains
    LogLimit=0
    PropertiesVersion=10.3
    javaHome=/opt/osb/osb1031/jrockitR27.6.5-32
    AuthenticationEnabled=true
    NodeManagerHome=/opt/osb/osb1031/wlserver_10.3/common/nodemanager
    JavaHome=/opt/osb/osb1031/jrockitR27.6.5-32/jre
    LogLevel=INFO
    DomainsFileEnabled=true
    StartScriptName=startWebLogic.sh
    ListenAddress=mcsdev3
    NativeVersionEnabled=false
    ListenPort=5556
    LogToStderr=true
    SecureListener=false
    LogCount=1
    StopScriptEnabled=true
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=false
    StartScriptEnabled=true
    LogFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.log
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    StopScriptName=stopWeblogic.shPlease let me know what additional configuration is required to get the server started properly
    Regards
    Vikas

    Found a workaround:
    Manually, add PATH (and probably the other environment variables also) to
    ${WLS_HOME}/common/bin/commEnv.sh.

  • Undeploying war error

    Using wl 7.0 sp2 on solaris , deployed on a 2 instance wide cluster
    I have this application called test.war
    When i deploy this after server startup , there is no problem, application deploys
    fine and i can
    access it to via the browser.
    Now when we try to undeploy it , i keep getting this:
    " Unprepare application test2 on aseq103a Status-Running, Begin testing - Sun
    Mar 23 19:06:10 EST 2003", there is no End Time and pressing the cancel button
    does not cancel it
    if i try to undeploy again samething and the same error keeps repeating, seems
    there are threads out there that do not get cancelled
    Looking at the logs i get this:
    "Exception caught for task Unprepare application test2 on aseq103a: Unprepare
    task for application, test2, with id, 29, cancelled for target aseq103a"
    weblogic.management.ManagementException: Unprepare task for application, test2,
    with id, 29, cancelled for target aseq103a
         at weblogic.management.deploy.MasterDeployer.cancelTask(MasterDeployer.java:967)
         at weblogic.management.deploy.DeploymentTaskRuntime.cancel(DeploymentTaskRuntime.java:970)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
         at $Proxy84.cancel(Unknown Source)
         at weblogic.management.console.actions.mbean.CancelTaskAction.perform(CancelTaskAction.java:85)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5445)
         at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)

    Are you using kregedit or iASAT to verify the existence of the modules? My
    experience is that for kregedit, you need to "collapse" and then "expand"
    the J2EE Modules branch to see the latest changes after you remove the
    modules. For iASAT, you need to perfrom a "refresh" action (an option from
    the menu) to see the latest changes. BTW, I can remove module by using the
    command just like what you did.
    Keith
    Bryan Field <[email protected]> wrote in message
    news:[email protected]..
    I am trying to undeploy a war file using the iasdeploy removemodule
    -verbose csa.war command. It says that it finishing deploying, which is
    odd, and then it still shows up in the IAS registry under the j2ee
    modules. Is this the correct way to undeploy a war file? Is there
    something else I have to do?
    Thanks,
    Bryan

  • WLS 9.2:  Interpreting the error - This RJVM has already been shutdown

    Hi,
    I have encountered the error message (stacktrace below) in one of the managed servers of my Weblogic 9.2 cluster (containing 4 managed servers). There are ALSB proxies consuming and producing to JMS distributed queues on the cluster.
    The server reporting this error (server01_01) is complaining about the Remote JVM of the other servers (server01_02, 02_01, 02_02) being shutdown, but what I have observed is that server01_01 was killed by the Nodemanager(may be due to failure or being unavailable).
    I would like to know:
    1) When does this error occur usually?
    2) How is it different from "weblogic.jms.common.LostServerException: [JMSClientExceptions:055169]Network connection to server was lost."?
    3) Why did I get an error complaining about the other healthy servers when actually the problem is with the server reporting the error?
    Any hints are appreciated.
    +####<Mar 26, 2009 11:44:08 AM EST> <Warning> <RMI> <ifappd111d-v04t> <+server01_01+> <[ACTIVE] ExecuteThread: '37' for queue:+
    +'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238028248453> <BEA-080006> <Failed to associate the transaction context with the response while marshalling an exception to the client:+
    java.rmi.ConnectException: This RJVM has already been shutdown -3786093667493708317S:ifappd112d-v04t:[8003,8003,-1,-1,-1,-1,-1]:ifappd111d-v04t:8003,ifappd112d-v04t:8003,ifappd111d-v04t:8005,ifappd112d-v04t:8005:domServiceBus:server02_01.
    java.rmi.ConnectException: This RJVM has already been shutdown -3786093667493708317S:ifappd112d-v04t:[8003,8003,-1,-1,-1,-1,-1]:ifappd111d-v04t:8003,ifappd112d-v04t:8003,ifappd111d-v04t:8005,ifappd112d-v04t:8005:domServiceBus:*server02_01*+
         at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:336)
         at weblogic.rjvm.RJVMImpl.getResponseStream(RJVMImpl.java:679)
         at weblogic.rjvm.MsgAbbrevInputStream.getMsgAbbrevOutputStream(MsgAbbrevInputStream.java:275)
         at weblogic.rjvm.MsgAbbrevInputStream.getOutboundResponse(MsgAbbrevInputStream.java:534)
         at weblogic.rmi.internal.BasicServerRef.postInvoke(BasicServerRef.java:599)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:453)
         at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
         at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    EJB keep traks of Bea CLUSTER using JVMID as an identifier of each manged server's JVM. When this JVMID is no longer valid, you can see "JVM is already been shutdowm" as client exception. This issue happen when, on client side, EJB can't recognize server side JVM shutdown. In WLS 8.1 there was a PATCH to solve this problem. Ask to Bea support if you need a patch also for WLS 9.2.
    Regards

  • Jaxrpc HelloWorld process-war error

    for the helloworld example, I successfully finished:
    ant compile-server
    ant setup-web-inf
    ant package
    However I got following error with ant process-war:
    ===========================================================================
    Buildfile: build.xml
    set-ws-scripts:
    process-war:
    [echo] Running wsdeploy....
    BUILD FAILED
    file:C:/Java/jwsdp-1.1/docs/tutorial/examples/jaxrpc/common/targets.xml:123: Exe
    cute failed: java.io.IOException: CreateProcess: C:\jwsdp-1.1\jaxrpc-1.0.3\bin\w
    sdeploy.bat -tmpdir build/wsdeploy-generated -o dist/hello-jaxrpc.war dist/hello
    -portable.war -verbose error=3
    Total time: 1 second
    ===========================================================================
    any idea what the error means? thanx

    Hi,
    Check the errors in the output file specified by -o option of wsdeploy.
    That might help you in knowing the reason

  • Napoleon Total War Error 403 Macbook Air

    I've been downloading Napoleon Total War for my Macbook Air and the last few times I have recieved a 403 forbidden error. It has not completed download, and is not in my application folder so Feral's answer to several other users will not work for me. 

    Disable anti virus software if installed.
    If you have Little Snitch installed, that can prevent apps from downloading.
    Mac App Store: How to resume interrupted downloads
    Make sure Mac App Store is selected in:  System Preferences > Security & Privacy > General
    message edited by:   cs

  • Deploying war error

    Dear all,
    When we are deploying a war file in Soa 10.1.3.4 . we are getting the following error :
    Exception Creating EntityManagerFactory using PersistenceProvider class oracle.toplink.essentials.PersistenceProvider
    Did any one faced this error before ?
    Please advise
    Kai

    Reeya -- In general, deployment / EM problems associated with 9iAS will probably get better responses on the General iAS forum at:
    http://forums.oracle.com/forums/forum.jsp?id=466592
    You might want to post your query there.
    Thanks -- Jeff

  • Makefile.war error

    Hi,
    I am trying to run the Makefile.war provided by the AM in /opt/SUNWam. We get an error in the majkefile, unexpected else line 21.
    I am trying to look at the script code and resolve it, but has anybody else come across this? Since this makefile comes with the JES 7 installation.
    Also, I am slightly confused about the use of this makefile. If we install AM and chose "configure now" option, then do we still need to run the makefile? With AM install and configure now option (SUN web server is container), when I try to access http://incognitus.dbi.udel.edu/amconsole, I get an object not found. Am I missing something here? Directory Server and Web Server installation appears to be fine.
    All the AM packages are installed. In the installation, I set the cookie domain to .dbi.udel.edu
    Thanks,
    Giriprasad

    You shouldn't need to do anything if you choose "configure now" with the installer. Since you chose the webserver, you may need to log into the admin and select "apply changes" then restart after an initial install. Other than that, everything should be up and running, assuming all components installed correctly. The docs on docs.sun.com do have a section for what you need to do with various components in both the "configure now" and "configure later" cases.
    Also, I'll note that with AM7, if you chose realm mode, you won't have the old AM Console. In AM7, the correct URL would be http://server.domain.edu/amserver/console to access the new console. If you'd chosen legacy mode, that new console is still preferred, but the old amconsole is still supported (in case you have custom extensions or are using other components like portal 6.3 that require it).
    My guess is you chose realm mode, so you're really just trying to access something that doesn't exist.
    I hope that helps,
    - Matt

  • WLS 9.2.03 Startup errors

    Hi,
    can anyone explain what may be causing these two errors on startup. Both seem related to Web Services; all of which use SOAP/HTTP bindings so mention of JMS seems spurious.
    1. Data Binding Error
    <WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
    <WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.
    2. JMS queue warning
    <WSEE>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.c
    onnect:227>
    Thanks.

    The first error might be thrown by WLS JAX-RPC client. Which API did you use to create javax.xml.rpc.Service? If your client can't invoke your service, you can try ServiceFactory.loadService(Class serviceInterface), or Service loadService(URL wsdl, Class serviceInterface, Properties p) to create the Service instance.
    'weblogic.wsee.DefaultQueue' is used by the internal async webservice to receiving async response message over JMS transport.The second warning just tries to remind that async request-reply webservice and callback webservice over JMS transport doesn't work if no JMS queue is configured to receiving async messages. You can ignore this warning message if all your services use SOAP/HTTP bindings.

  • WLS 6.0 - SSL Setup error

    We have configured a managed server to be SSL enableb but the admin
    server is not SSL enable. We get the following error when starting
    the managed server that is SSL enabled.
    <Mar 23, 2001 6:10:06 PM PST> <Alert> <WebLogicServer> <Inconsistent
    security co
    nfiguration, java.lang.Exception: Unable to open url: http://192.168.10.6:7001/w
    l_management java.io.FileNotFoundException: Response: '500' for
    url: 'http://192
    .168.10.6:7001/wl_management'>
    java.lang.Exception: Unable to open url: http://192.168.10.6:7001/wl_management
    java.io.FileNotFoundException: Response: '500' for url: 'http://192.168.10.6:700
    1/wl_management'
    at weblogic.t3.srvr.SSLListenThread.resolvePropertyFromAdminServer(SSLLi
    stenThread.java:198)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:425)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:939)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Thanks
    Viren

    Have you verified that your managed server has a valid
    ServerCertificateFileName as well as a ServerCertificateChainFileName? The
    first certificate in the ServerCertificateChainFileName must be the signer
    of the cert in the ServerCertificateFileName file. The last certificate (may
    also be the first) in the ServerCertificateChainFileName must be
    self-signed. From the stack trace it looks as though the code may be trying
    to get a property or file from the admin server. Does the admin server's
    log have any errors in it that contain info about a certificate?
    Paul
    I think that the
    "Viren" <[email protected]> wrote in message
    news:3abf8a9f$[email protected]..
    >
    We have configured a managed server to be SSL enableb but the admin
    server is not SSL enable. We get the following error when starting
    the managed server that is SSL enabled.
    <Mar 23, 2001 6:10:06 PM PST> <Alert> <WebLogicServer> <Inconsistent
    security co
    nfiguration, java.lang.Exception: Unable to open url:http://192.168.10.6:7001/w
    l_management java.io.FileNotFoundException: Response: '500' for
    url: 'http://192
    168.10.6:7001/wl_management'>
    java.lang.Exception: Unable to open url:http://192.168.10.6:7001/wl_management
    >
    java.io.FileNotFoundException: Response: '500' for url:'http://192.168.10.6:700
    1/wl_management'
    atweblogic.t3.srvr.SSLListenThread.resolvePropertyFromAdminServer(SSLLi
    stenThread.java:198)
    atweblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:425)
    atweblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
    atweblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:939)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Thanks
    Viren

Maybe you are looking for

  • Ipod shuffle randomly freezes....please help!!!!

    My Ipod shuffle seems to randomly freeze after certain songs, or spots on the shuffle. I dont recall exactly when this first started, but it seems like ive tried everything. I have tried scandisk, defrag, resetting the ipod, updating it to latest fir

  • How do I display on-the-fly generated XML on a web page using DW CS4 Spry regions?

    On a main web page I'm trying to display formatted data from an ASP page that generates XML on-the-fly from a query. When I run the ASP page from the browser, the XML formatting of the data works. But when I run the main web page, the data doesn't di

  • Ipod nano in ipod sock...no scratches

    I seem to read nothing but complaints everywhere about the nano and scratches. What a lame deal to have a scratched up ipod! However I personally have not had this trouble at all. I have been carrying my nano half the time (I have had it for weeks no

  • Why my IllustratorCC can not found compatible GPU???

    I can't open and place jpg files in IllustratorCC I guess GPU performance causing trouble... Could you fix my GPU setting? Thanks! This is my System Info Components: ACE 2014/04/14-23:42:44 79.554120 79.554120 Adobe APE 2013/02/04-09:52:32 0.1160850

  • FRM-92100 : Connection was interrupted

    I wonder if someone can help us with this problem. We tried our own forms application running on the web - calling a java bean and got it. Then we tried Oracle example: GetClientInfo and got it to work on one machine. We checked all the paths on our