Deploying 2 application of same context root

Recently I deployed 2 applications in weblogic7 and weblogic8
/usr2/applns_one --> dev
/usr3/applns_one --> staging
Here "applns_one" are the same in "/usr2 and /usr3" where "/usr2" is for dev and "/usr3" is for staging.
I deployed both on the same instance or managed server of weblogic.
first deployed app (/usr2) had a context root "/applns_one-1"
Second deplyed app (/usr3) had a context root "/applns_one"
After deployment I see 404 error for the URL which is accessing "/usr2" appln since its context root is "/applns_one-1".
My issue is how can I deploy "/usr2/applns_one" and /usr3/applns_two" on the same managed server.
Is there any workaround for this in weblogic.
Thanks,

If you're asking how can you deploy two applications to the same weblogic instance with the same context root, you just can't do that. There would be no point to that, as you'd only ever be able to access one of them. You'll need to change one of them.

Similar Messages

  • Deploying application with several web modules having the same context root

    Hi,
    I would like to be able to deploy an application in Weblogic 12c having one ejb module and several web modules with the same context root. Even though the web modules have the same context root, each of them is deployed to a different virtual host.
    Weblogic allows deploying the modules this way as long as their targets are different (i.e. each having a distinct virtual host). However this works only when I don't select a target for the .ear:
    Component Type Current Targets
    application.ear Enterprise Application (None specified)
    application.jar EJB AdminServer
    web1.war WEBAPP virtualHost1
    web2.war WEBAPP virtualHost2
    However if I select as target for the .ear to be AdminServer, the deployment doesn't work anymore, complaining that the context roots are in conflict.
    If I remove web2.war from the .ear and deploy the .ear and .jar to AdminServer and web1.war to virtualHost1, the deployment works but the strange thing is that the web application can be accessed also through the AdminServer's main network channel, even though I would expect that it should be accessible only through virtualHost1 network channel. I believe this is the reason why there are context root conflicts when specifying a target for the .ear, because both wars are made accessible to the main network channel.
    The reason why I want to keep the wars inside the same .ear is because I want to make them access the application's local EJBs (since as far as I know it's not possible to access a local EJB outside the application even if they belong to the same VM).
    Is there a way to deploy the web modules only to the virtual hosts without being targeted to the main network channel?
    Regards,
    Alexandru

    Murphy's Law: If anything can go wrong it will
    A corollary to Murphy's law: When everything fails, read the manual.
    Web application funda: Every web application must have its own context root. So, if wkfsocos is one
    web application then, wkfsocos1 is another web application -
    and hence must have its own context root.
    Hello Aman,
    If you are in E-Commerce version 4.0, then read this
    [ISA_Buildtool document |https://service.sap.com/~sapdownload/011000358700001920472003E/ISA_BuildTool_10.pdf]
    to create a copy of the application in its own context root.
    From your URL pattern I guess you are in E-Commerce version 4.0.
    If you are in E-Commerce 5.0 or above, then the
    [Extension Guide |http://service.sap.com/~sapdownload/011000358700006120622006E/]gives steps to create a copy with its own context root for use in modification.
    (See the chapter on - Creating a project specific Web Application with own context root )
    Both these links require access to SAP Service Marketplace. You can also find the
    documents through /instguides shortcut in Service Marketplace.
    Easwar Ram
    http://www.parxlns.com

  • How to configure multiple virtual hosts for the same context root /

    Hi,
    I am using Glassfish V1 U1 - b14 on Solaris.
    I am trying to configure two applications to be mapped to the / root context, each one in its own virtual host.
    Two things I have noticed:
    1. I have to manually add virtual-hosts="hostId" in domain.xml/application-ref ... looks like just simply deploying the app does not do that although the application is set as default for its particular virtual host. Is this a bug?
    2. Although I have set for each virtual host the default web-app correctly, and they both respond fine, I cannot map both of them to the / context. The second application (chronologically deployed) does not respond when called with the / context ....
    Any ideas? Is this a bug again?
    Regards,
    Rares
    Message was edited by:
    raresp

    Wow, that's a shame. All mighty Application Server and two different apps on two different virtual hosts are considered ambiguous to have the same context root definition.... Fair play to Tomcat and 90% of the rest of servlet containers!
    In my case I have the same EAR we are planning to deploy to many (up to 30) virtual hosts. Faking different context roots for each deployment will bring unnecessary overheads...
    Should I file a bug or feature request?
    Thanks again for your answer, although you're basically saying it is not possible I will wait and look a while for a possible solution before bringing this topic to a conclusion.

  • Same context root conflict.

    I'm try to run multiple instances of an application running on the same box (each on their own managed server) but use the same context root (/servlet)
    e.g.
    server1 -> /app -> /servlet
    server2 -> /app2 -> /servlet
    Currently how I do it is give each of them their own servlet name, e.g
    server1 -> /app -> /servlet
    server2 -> /app2 -> /servlet2
    I'm trying to make the urls for each instance as simple as possible. I can already see potential instances where the server#, app#, and servlet# would all be different numbers.
    If I set them to both servlet weblogic throws me this error:
    Exception:weblogic.management.ApplicationException: prepare failed for app2 Module: app2 Error: Context path '/servlet/' is already in use by the module: app application: app
    * [Deployer:149033]preparing application app2 on server2
    * [Deployer:149033]failed application app2 on server2
    * [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application app2 on server2.: Exception:weblogic.management.ApplicationException: prepare failed for app2 Module: app2 Error: Context path '/servlet/' is already in use by the module: app application: app.
    Any help that you can provide will be greatly appreciated.

    Hello,
    this is possible in IBM Websphere via custom extension: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tprs_sharing_data.html
    I don't know if it's possible somewhere else.
    k.

  • Multiple war with same context root

    Dear all,
    I would like to know if it's possible to have several war in an EAR file with a same context root?
    I know that it is possible to have several war but I don't know if it's possible to share the same context root.
    The problem here is that the application on which we work is provided by another company, hence we have an original EAR containing the company war as well as the company EJB. As new versions of the application are delivered to us quite frequently, it's impossible to store the code developped by us in the EAR, as it is replaced in each delivery.
    Concerning our custom code, it is not a problem as we develop this code in a separated project which is included as a jar in the APP-INF/lib directory of the EAR file.
    But concerning the war it's an other problem. Indeed, we develop custom JSFs pages or javascript. These files are placed in the application war file which changes for each delivery.
    Thus, we would like to create an other war file which will contain all our custom pages and javascripts in order to be able, in each delivery, to fully replace the other war containing the company pages and javascripts. This would allow us to save time each time a new delivery is done.
    The important thing would be to keep the same context root for the two wars, enabling transparency for the application.
    Thanks for your help,
    Citrouille57

    Hello,
    this is possible in IBM Websphere via custom extension: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tprs_sharing_data.html
    I don't know if it's possible somewhere else.
    k.

  • Iis and jboss using same context root

    I want to be able to run two instances of jboss, two iis web sites and have them both use the same context root "/". The will be used for different sites www.site1.com and www.site2.com.
    I have iis serving up my jsp from jetty using the apache redirector fine for one server. I can also get it running for two iis web servers and two jboss servers on different ip addresses (all on the same machine). But, I am unable to use the same context root in the uiworker.properties file. The only way they will serve up the pages separately is if thee workers are assigned different context roots. I want to use "/" for the context root on both sites in both jboss instances.
    Is there a way to do this?

    http://www.itshastra.com/know_bank/IIS_Jboss.pdf

  • Different application but with same context root

    hi all,
    I have two applications www.a.com and www.b.com deployed on two separate oc4j instances, both of the context root are also set to "/". But i found that only the www.b.com is correct, when i goto www.a.com, it will goto the page of www.b.com. How can i make the right cofiguration? I'm using oracle 10g AS (ver. 10.1.2.0.2).
    I have search around the forum and seems no one have similar question, can anyone answer me this newbie question. Thanks alot.

    thanks for your reply.....i'm a newbie on the oracle AS.. let me elaborate more on my situation...
    I'm using oracle http server, and i have setup 2 virtual hosts (one is for www.a.com, and the other is www.b.com) as following:
    <VirtualHost default:80>
    ServerName www.a.com
    DirectoryIndex index.html
    DocumentRoot "C:\OraHome_1\j2ee\test1\applications\App1"
    </VirtualHost>
    <VirtualHost default:80>
    ServerName www.b.com
    DirectoryIndex index.html
    DocumentRoot "C:\OraHome_1\j2ee\test2\applications\App2"
    </VirtualHost>
    At the AS, i created 2 oc4j instances which is testInstance1 and testInstance2. And then i deployed my two applications to the instance separately, but the context root are also set to "/". After that, i found that in the mod_oc4j.conf, it shows the following statement in it:
    Oc4jMount / testInstance1
    Oc4jMount /* testInstance1
    Oc4jMount / testInstance2
    Oc4jMount /* testInstance2
    i hope that is clear enough now for you to solve my problem. If not, please let me know... thanks.

  • Failed to deploy web application with same name twice

    Hello-
    On Oracle 10g Application server I deployed an WAR file called "anbadmin", then undeployed it. The undepoloyment failed from the OEM so I undeployed it manually via removing its entries from server.xml.
    When I tried to deploy it again with the same name I got this:
    Failed to deploy web application "anbadmin". Failed to deploy web application "anbadmin". . The evaluate phase failed. The Adapter used in the evaluate may have thrown an exception.
    Resolution:
    Please call Oracle support.
    Base Exception:
    java.lang.NoSuchMethodError
    null. java.lang.NoSuchMethodError
    Is there a solution for this?
    Regards

    I think I know the solution. We encountered exactly same message and no further deployment could be made. It appeared message in "dcmctl" utility was much more helpfull than the one in EM (though you still have to use "getError" command...)
    If you are using file-based repository, you have to issue command in dcmctl utility "resetFileTransaction". This closes repository and opens it again.
    Myrra

  • Deploy given EAR file having application.xml and change context-root

    hi
    Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
    For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
    Given documentation appendix B section "context-root" [3] saying
    "... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
    and documentation section "Typical Deployment Configuration Workflows" [4] saying
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
    Some observed behaviour:
    - scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
    - scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
    The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
    "Remove the META-INF/application.xml DD from the EAR"
    - scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
    - scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
    One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
    Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
    So ...
    - (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
    - (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
    Seems like a simple goal, but I must be missing something that is required to achieve it.
    - [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
    - [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
    many thanks
    Jan Vervecken

    Thanks for your reply René van Wijk.
    René van Wijk wrote:
    You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
    Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
    "/application/module/web[web-uri/text()="WebProject.war"]/context-root"
    But, that didn't work.
    Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
    "/application/module[id="WebProject"]/web/context-root"
    - scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
    So, it does not seem to work.
    ... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
    ... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
    Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
    "java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
    Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
    - [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
    regards
    Jan Vervecken

  • How do I change the context-root of a web app with a deployment plan?

    I've been trying to figure this out for several hours.
    I'm deploying a .ear file which sets the context root for the single web application it deploys in its application.xml deployment descriptor:
    <application>
    <display-name>MyApp</display-name>
    <module>
    <web>
    <web-uri>MyAppViewControler.war</web-uri>
    <context-root>MyApp</context-root>
    </web>
    </module>
    </application>
    I want to change the context-root from /MyApp to something else when deploying the ear file. It seemed to me that using a deployment plan was the way to do this. But when I use this plan:
    <deployment-plan>
    <application-name>MyApp<application-name>
    <variable-definition>
    <variable>
    <name>NEWCONTEXTROOT</name>
    <value>foobar</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>MyApp</module-name>
    <module-type>ear</module-type>
    <module-descriptor external="false">
    <root-element>application</root-element>
    <uri>META-INF/application.xml</uri>
    <variable-assignment>
    <name>NEWCONTEXTROOT</name>
    <xpath>/application/module/web/context-root</xpath>
    </variable-assignment>
    </module-descriptor>
    </module-override>
    </deployment-plan>
    I get an error:
    weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    /bea/user_projects/domains/devod1/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected element 'web-uri@http://java.sun.com/xml/ns/javaee' instead of 'context-root@http://java.sun.com/xml/ns/javaee' here in element web@http://java.sun.com/xml/ns/javaee:<nullplan.xml>
    I looked at http://e-docs.bea.com/wls/docs103/pdf/deployment.pdf which says:
    "You cannot use a deployment plan to change the context-root in an application.xml
    file. However, if an application is deployed as a library, you can either change the
    context-root through an weblogic-application.xml file or use the deployment plan
    to change the context-root in an weblogic-application.xml file."
    I don't understand what this means. I'm not deploying my application as a library.
    Does anyone know how to change the context-root for an application?
    Any help would be greatly appreciated!

    Hi James,
    I am quite new to Welogic if i am wrong please correct me.I have re-deployed my application (.war) with this Plan.xml
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false"&gt;
    &lt;application-name&gt;BrowserR08.003&lt;/application-name&gt;
    *&lt;variable-definition&gt;*
    * &lt;variable&gt;*
    * &lt;name&gt;CONTEXTROOT&lt;/name&gt;*
    * &lt;value&gt;BrowserWeb/servlet/BrowserServlet&lt;/value&gt;*
    * &lt;/variable&gt;*
    * &lt;/variable-definition&gt;*
    &lt;module-override&gt;
    &lt;module-name&gt;BrowserWeb.war&lt;/module-name&gt;
    &lt;module-type&gt;war&lt;/module-type&gt;
    &lt;module-descriptor external="true"&gt;
    &lt;root-element&gt;weblogic-web-app&lt;/root-element&gt;
    &lt;uri&gt;WEB-INF/weblogic.xml&lt;/uri&gt;
    &lt;hash-code&gt;1231953167814&lt;/hash-code&gt;
    *&lt;variable-assignment&gt;*
    * &lt;name&gt;CONTEXTROOT&lt;/name&gt;*
    * &lt;xpath&gt;/weblogic-web-app/context-root&lt;/xpath&gt;*
    * &lt;operation&gt;add&lt;/operation&gt;*
    * &lt;/variable-assignment&gt;*
    &lt;/module-descriptor&gt;
    &lt;module-descriptor external="false"&gt;
    &lt;root-element&gt;web-app&lt;/root-element&gt;
    &lt;uri&gt;WEB-INF/web.xml&lt;/uri&gt;
    &lt;/module-descriptor&gt;
    &lt;module-descriptor external="true"&gt;
    &lt;root-element&gt;wldf-resource&lt;/root-element&gt;
    &lt;uri&gt;META-INF/weblogic-diagnostics.xml&lt;/uri&gt;
    &lt;/module-descriptor&gt;
    &lt;/module-override&gt;
    &lt;config-root&gt;/export/home1/tecapp/BrowserR08.003/plan&lt;/config-root&gt;
    &lt;/deployment-plan&gt;
    I do not know wether i will require the other module descriptor definition in this Plzn.xml. Now when I go to following link.
    Deployments --&gt; MyApp --&gt; Testing
    It gives me following url as a test page:
    http://localhost:7001/BrowserWeb/servlet/BrowserServlet
    as soon as i click on to the above link it redirects me to following.
    http://localhost:7001/BrowserWeb/servlet/BrowserServlet/servlet/BrowserServlet
    Same if i remove these context-root part my normal Testing menu shows me following link as my webapp access path
    http://localhost:7001/BrowserWeb &lt;-- My war file name is BrowserWeb.war so it is default name of my deployed application if i am not wrong
    and as soon as i click on above link it redirects me to the following one.
    http://localhost:7001/BrowserWeb/servlet/BrowserServlet
    It means application server know that my full web access page is with '*servlet/BrowserServlet*' because its adding it in both the cases.
    What I want is a constant URL whcih does not change?
    Hope this helps :)

  • WebLogic 10.3 , ear file, application.xml only finds first context root

    I just can't find out what this is. I have two web service projects (JAX-WS) and am trying to put them in an .ear file to deploy to WebLogic 10. Normally, this is done by creating an .ear with both projects .war files in it and an application.xml file in the META-INF directory that defines the context-root for each .war file. However, nothing I do for WebLogic 10 seems to work, it only see's the first context-root and sets that same context-root for both web services. I have verified this by switching the order in the application.xml file. Also, this exact same .ear file deploys to the Sun Enterprise Server (Glassfish) and acts correctly. Using a weblogic.xml file in each .war and deploying them individually they end up having the correct context root, just not from an .ear using application.xml. I even tried deleting the application.xml file and just having the weblogic.xml files in each .war define the context root and it still only came up with one context root for both. It's as if only one context root is allowed in an .ear for WebLogic 10, which can't be correct as we are doing this on WebLogic 9.2 (JAX-RPC) with multiple .war files in an ear.

    Hi,
    Try to increase severity of the server logging to avoid more logging.
    Avoid Debugs and and info and better select the severity to notice which will avoid more logging.
    Regards,
    Kal

  • HowTo: deploy an j2ee app using "/" as context root on iAS 6.5

    Hi all iAS expert
    It is highly appreciated one can teach me how to get around below problem
    l deployed an app using "/" as context root. But the iAS could respond to any HTTP request.
    However, as l changed the context root to sth other than root. iAS responded properly.
    Can someone help me get around this problem ?
    thank you a lot
    fox

    I deployed the same EJB on WLS 6.1+sp3 and WLS 7.0.
    These both work. Looks like there is some problem with WLS6.0+sp2. I have opened
    a case with BEA customer support.
    --Latha

  • Change the integrated deployment context root

    How do I change the context root of applications deployed with the integrated WLS instance? I created my own application.xml and put it in project_root/META-INF but this gets overwritten when the application is deployed.

    Hi,
    Ok, we know that it is easy to change the context-root as you explained from within jdev.
    My question is if I want to set the context-root to default "/ how can I do?
    Jdev dosen't accept to set the context-root to "/" (context root invalid) and if there is a valid context root it overwrites my application.xml when I deploy to ear.
    Any solution other that this workarround:
    after deploying to ear unzip it and change the application.xml to <context-root>/</context-root>
    Thanks
    Jamil
    Edited by: Jamil Nour on Feb 23, 2010 12:19 AM

  • Unable to Run/Deploy the Application

    JDev 11.1.2.1.0 ADF BC
    I am unable to run my application and it gives the below log:
    *** Using HTTP port 7101 ***
    *** Using SSL port 7102 ***
    C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;D:\Sahar Hassan\sqljdbc4.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
    PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1112\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;D:\oracle\product\10.2.0\db_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
    *  To start WebLogic Server, use a username and   *
    *  password assigned to an admin-level user.  For *
    *  server administration, use the WebLogic Server *
    *  console at http:\\hostname:port\console        *
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
    Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Users\ADMINI~1\AppData\Local\Temp\trustStore4013408576188156013.jks -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true  -Xverify:none  -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server  -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\config\FMWCON~1  -Digf.arisidbeans.carmlloc=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\config\FMWCON~1\carml  -Digf.arisidstack.home=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol  -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.81\DEFAUL~1\oracle\store\gmds   -Dweblogic.management.discover=true  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1112\profiles\default\sysext_manifest_classpath  weblogic.Server
    <Jun 19, 2012 4:43:24 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jun 19, 2012 4:43:24 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jun 19, 2012 4:43:24 PM IST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\lib\sqljdbc4.jar>
    <Jun 19, 2012 4:43:25 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
    <Jun 19, 2012 4:43:27 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Jun 19, 2012 4:43:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 19, 2012 4:43:27 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jun 19, 2012 4:43:27 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 19, 2012 4:43:27 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00019. Log messages will continue to be logged in C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
    <Jun 19, 2012 4:43:27 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
    <Jun 19, 2012 4:43:31 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <MessageLocalizationHelper> <getLocalizedMessage> The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
    <Jun 19, 2012 4:43:36 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jun 19, 2012 4:43:36 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <CodebasePolicyHandler> <migrateDeploymentPolicies> Migration of codebase policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <AppPolicyHandler> <migrateAppPolicies> Migration of application policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <CodebasePolicyHandler> <migrateDeploymentPolicies> Migration of codebase policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <AppPolicyHandler> <migrateAppPolicies> Migration of application policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <WSEE:12>com.bea.core.repackaged.springframework.beans.factory.BeanCreationException: Error creating bean with name 'weblogic.wsee.jaxws.client.async.AsyncTransportProvider': Instantiation of bean failed; nested exception is com.bea.core.repackaged.springframework.beans.BeanInstantiationException: Could not instantiate bean class [weblogic.wsee.jaxws.client.async.AsyncTransportProvider]: No default constructor found; nested exception is java.lang.NoSuchMethodException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider.<init>()<WSEEComponentContributor.loadUsingSpring:83>
    <Jun 19, 2012 4:44:26 PM IST> <Error> <HTTP> <BEA-101216> <Servlet: "weblogic.wsee.jaxws.client.async.AsyncTransportProvider" failed to preload on startup in Web application: "SugarCRM-ViewController-context-root".
    javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:36)
         at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55)
         at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82)
         at com.sun.xml.ws.server.InvokerTube.setEndpoint(InvokerTube.java:85)
         at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:48)
         Truncated. see log file for complete stacktrace
    Caused By: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:37)
         at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:34)
         at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55)
         at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82)
         at com.sun.xml.ws.server.InvokerTube.setEndpoint(InvokerTube.java:85)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at java.lang.Class.newInstance0(Class.java:340)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:54)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:42)
         at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:35)
         Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 4:44:26 PM IST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'SugarCRM'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.jaxws.client.async.AsyncTransportProvider" failed to preload on startup in Web application: "SugarCRM-ViewController-context-root".
    javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:36)
         at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55)
         at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82)
         at com.sun.xml.ws.server.InvokerTube.setEndpoint(InvokerTube.java:85)
         at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:48)
         at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:150)
         at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
         at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
         at javax.servlet.GenericServlet.init(GenericServlet.java:241)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:37)
         at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:34)
         ... 49 more
    Caused by: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at java.lang.Class.newInstance0(Class.java:340)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:54)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:42)
         at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:35)
         ... 50 more
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider
         at java.lang.Class.newInstance0(Class.java:340)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:54)
         at weblogic.wsee.jaxws.injection.WSEEComponentContributor.newInstance(WSEEComponentContributor.java:42)
         at weblogic.wsee.jaxws.WLSServletInstanceResolver.create(WLSServletInstanceResolver.java:35)
         Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00019. Log messages will continue to be logged in C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\JDK160~1\jre\lib\security\cacerts.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on 127.0.0.1:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[6]" is now listening on 0:0:0:0:0:0:0:1:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Warning> <Server> <BEA-002611> <Hostname "path-mumbai7", maps to multiple IP addresses: 192.168.1.20, fe80:0:0:0:8ceb:756:d0e1:6176%11, fe80:0:0:0:3401:2477:3f57:feeb%13, 2001:0:5ef5:79fb:3401:2477:3f57:feeb>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:3401:2477:3f57:feeb:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 192.168.1.20:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:114:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on fe80:0:0:0:3401:2477:3f57:feeb:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.1.20:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on fe80:0:0:0:8ceb:756:d0e1:6176:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:8ceb:756:d0e1:6176:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 2001:0:5ef5:79fb:3401:2477:3f57:feeb:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 2001:0:5ef5:79fb:3401:2477:3f57:feeb:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:114:7102 for protocols iiops, t3s, ldaps, https.>
    <Jun 19, 2012 4:44:33 PM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
    <Jun 19, 2012 4:44:34 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 19, 2012 4:44:34 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    IntegratedWebLogicServer startup time: 98161 ms.
    IntegratedWebLogicServer started.
    [Running application SugarCRM on Server Instance IntegratedWebLogicServer...]
    [04:44:34 PM] **** Warning: Application SugarCRM may have been left deployed on the server.  Undeploy it from the admin console.
    [04:44:34 PM] Web Module ViewControllerWebApp.war recognized in project ViewController.jpr
    [04:44:34 PM] ----  Deployment started.  ----
    [04:44:34 PM] Target platform is  (Weblogic 10.3).
    [04:44:35 PM] Retrieving existing application information
    [04:44:35 PM] Running dependency analysis...
    [04:44:35 PM] Deploying 2 profiles...
    [04:44:35 PM] Wrote Web Application Module to C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\o.j2ee\drs\SugarCRM\ViewControllerWebApp.war
    [04:44:36 PM] Wrote Enterprise Application Module to C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\o.j2ee\drs\SugarCRM
    [04:44:36 PM] Redeploying Application...
    <CodebasePolicyHandler> <migrateDeploymentPolicies> Migration of codebase policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <AppPolicyHandler> <migrateAppPolicies> Migration of application policy failed. Reason: oracle.security.jps.JpsException: java.lang.reflect.InvocationTargetException.
    <Jun 19, 2012 4:44:37 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1340104476670' for task '0'. Error is: 'weblogic.application.ModuleException: Context path '/SugarCRM-ViewController-context-root' is already in use by the module: SugarCRM-ViewController-context-root application: SugarCRM_Project1_SugarCRM'
    weblogic.application.ModuleException: Context path '/SugarCRM-ViewController-context-root' is already in use by the module: SugarCRM-ViewController-context-root application: SugarCRM_Project1_SugarCRM
         at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1210)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:970)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
         at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:433)
         at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
         Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 4:44:37 PM IST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'SugarCRM'.>
    <Jun 19, 2012 4:44:37 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'SugarCRM'.>
    <Jun 19, 2012 4:44:37 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Context path '/SugarCRM-ViewController-context-root' is already in use by the module: SugarCRM-ViewController-context-root application: SugarCRM_Project1_SugarCRM
         at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1210)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:970)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
         at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:433)
         at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
         Truncated. see log file for complete stacktrace
    >
    [04:44:37 PM] Deployment cancelled.
    [04:44:37 PM] ----  Deployment incomplete  ----.
    [04:44:37 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application SugarCRM due to error deploying to IntegratedWebLogicServer.
    [Application SugarCRM stopped and undeployed from Server Instance IntegratedWebLogicServer]

    Context path '/SugarCRM-ViewController-context-root' is already in use by the module: SugarCRM-ViewController-context-root application: SugarCRM_Project1_SugarCRMLooks like the application (or another application which uses same context root) is already deployed to the server and could not be undeployed.
    Can you invoke the WLS console, navigate the deployment and undeploy it, then try deploying from JDev and see if it works fine?
    -Arun

  • Navigation and context root

    I have a web application that only has four pages. A login brings a user to a welcome page and then from the welcome page, the user should be able to access either of the other two pages. However, jsf is trying to direct to the other pages relative to the page it is currently on. For instance, in my WebContent folder I have an html folder which has otherTwo and welcome folders. welcome.jsp is in the welcome folder and the page I am trying to get to is in the otherTwo folder. When I click the link to get to the page, it says html/welcome/html/othertTwo/page.jsp is not found.
    Relevant code
    <navigation-rule>
    <navigation-case>
      <from-outcome>otherPage</from-outcome>
      <to-view-id>/html/otherTwo/page.jsp</from-outcome>
    </navigation-case>
    </navigation-rule>I have never had this problem before with jsf. I am using backbase for the first time in this application and was wondering if anyone knew if it is known for causing issues like this. Also, is there a way to set the context root explicitly in say web.xml or something like that?
    Thanks

    sl,
    Have you looked at the deployed applications in the OAS admin tool (GUI)? I'd be curious as t what you might find there with two applications using the same context root.
    -Michael

Maybe you are looking for

  • ITunes 64 setup won't complete on y Vista 64 bit OS

    Hope someone can help.... I've just purchased and set up a new Dell XPS running Vista Home Premium 64bit OS. Its a remarkable machine (lightning quick) however I wasn't aware that this 64 bit OS is an obstacle to some programs....I've worked out solu

  • ABAP runtime error / DDIC_STRUCLENG_INCONSISTENT

    Hi I got a ABAP runtime error DDIC_STRUCLENG_INCONSISTENT / short dump while creating a pricing condition record. The error is "accoring to the ABAP load, the structure should have been 1675 bytes long, according to information from ABAP dictionary a

  • When will I get my paid?

    I put my app in store on 12 Sept. and I still didn't get any paid from apple. I can see my earnings on financial reports page. When will Apple make payment?

  • FI: value of balance carryforward missing in fk10n

    Hi gurus, I have a problem with the customer balance carryforward. in transaction FK10N at the end of 2008 I have a balance carryforward value of 1.518.000 eur for customer wwwww. in the same transaction at the start of 2009 I have a balance carryfor

  • What Would You Guys Do?

    I make this summer video type thing for my friends and family every year. This year I wanted to have something at the beginning to really make it cool so this is what I was thinking... I wanted to do a 1 shot opening set in high speed from getting up