JNLPDownload servlet issue when deployed in iPlanet server

Hi all,
I am doing a POC to check how JWS works to launch an applet on a workstation having two different JRE versions (14.2_06 and 1.6.0_01 installed in lower to higher version order)
I deployed the sample application files in iPlanet server 6.0. In the JNLP file, under resources tag, I included a jar file with some version. However JWS is failing to download the file, with an exception (as seen from JNLP servle log file)
JnlpDownloadServlet(4): JnlpResource: JnlpResource[WAR Path: /lib/SampleApplet__V1.1.jar versionId=1.1 name=SampleApplet.jar lastModified=Thu Jan 01 05:30:00 GMT+05:30 1970] returnVersionId=1.1]
JnlpDownloadServlet(3): Resource returned: /lib/SampleApplet__V1.1.jar
Error in processing request
JnlpDownloadServlet(1): Internal error:
java.lang.NullPointerException
     at com.sun.javaws.servlet.DownloadResponse$ResourceFileDownloadResponse.getContentLength(DownloadResponse.java:178)
     at com.sun.javaws.servlet.DownloadResponse$FileDownloadResponse.sendRespond(DownloadResponse.java:117)
     at com.sun.javaws.servlet.JnlpDownloadServlet.handleRequest(JnlpDownloadServlet.java:115)
     at com.sun.javaws.servlet.JnlpDownloadServlet.doGet(JnlpDownloadServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:919)
     at com.iplanet.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:483)
The same application when deployed in tomcat server 4.1.32 is working fine.
All the jar file is available in the correct location and I have verified it. After some investigation with JNLP servlet source code, I found that iplanet 6.0 is throwing nullpointer excepton due to null return from following line from com.sun.javaws.servlet.JNLPResource.java file.
_resource = context.getResource(path); // here context is ServletContext and path input is relative path.
Has any one come across this problem in iplanet server? Does getResourcePath always return null in iPlanet server?
I don't want to change code in jnlp-servlet.jar, and it's the best case. Your inputs on this are appreciated.
Thanks & Regards,
Sudhakar

Below is our reuirment.
1. We will route the request based on urlprefix, these url prefix can be added and removed at runtime. We want to handle this situation automatically(not by obj conf changes). Also we will chnage the destination of request.
2. We want insert string in the url for our internal purpose.
So we opted for plugin.
BTW: I built the plugin for 32-bit environment.
$ file archMini-90.0.0.1.so
archMini-90.0.0.1.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
Below is my cc options.
CC_CMD=/usr/bin/gcc -m32 -fpic -DNET_SSL -DLinux -DLINUX -D_REENTRANT
LD_SHAREDCMD=/usr/bin/gcc -m32 -shared

Similar Messages

  • Whether java component (Not ejb, not servlet) can be deployed in App Server and get the services provided by App Server

    As I mentioned in subject, I am just wondering Whether the java component (Not
    ejb, not servlet) can be deployed in App Server and get the services provided
    by App Server or not?

    Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

  • App Insights for web application not working when deployed to Dev server

    App Insights is not sending telemetry data for ASP.NET MVC web *requests* (page views from the JS instrumentation are fine) when the app is deployed to the Dev or Test IIS servers.  On local IIS express it works perfectly fine.    I have
    no idea how to troubleshoot this problem.
    Bert Jackson

    - the AI.config file is both in the root of the site, and the /bin folder (which was confusing the other day).  Both are correct.
    - it looks like a local browser can go to https://dc.services.visualstudio.com (it results in a 403 since its just a GET to the root).  During this test, I found that this server did NOT have the Root trust certificate (Baltimore cybertrust), which
    would cause problems when using IE locally to browse the app; the javascript AI logging was not working, because it couldnt fetch the ai.0.js file).  I got the proper root certificate installed on the server, but request logging still not working.  I
    dont believe the firewall is a problem.
    - I've verified that all binaries are indeed deployed in to the bin folder on the server
    - web.config does have the AI http module; I've verified via logging that the ApplicationInsightsWebTracking is loaded.  However, I have custom Context/Telemetry initializers, and their Initialize() methods are *NOT* being called when deployed on the
    server.  I've tried both ways of registering the initializers; via code in the Application_Start() event and also in the ApplicationInsights.config file.
    I don't know how to troubleshoot any further, to figure out if AppInsights is actually *trying* to send telemetry out and failing, or if its not actually even trying.
    Bert Jackson

  • Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager

    Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
    when I check on Microsoft site it says
    Reports are not upgraded when you upload a report definition file directly to the report server
    or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
    created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
    This is the only way you can upgrade a report definition file.
    Now here is another confusing statement which says
    You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
    2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
    unchanged.
    All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
    2012?
    <o:p>
    </o:p>
    Mudassar

    I have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
    No Migration is required .
    I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
    "You
    can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
    Microsoft needs to correct this the documentation is misleading
    Mudassar

  • Application does not load correctly when deploying to standalone server

    All,
    I have created simple application implementing fusion theme. Applicaiton works fine when I run on integrated server but when deployed on standalone server it does not load any images or the theme itself. afrloop keep incrementing in status bar and ends up with java script error while later.
    I deployed another test application on standalone server and that works fine i.e. theme gets loaded correctly. Also, how should I include images on the page? I have a images folder in web content folder but they dont get loaded.
    Any help will be appreciated.
    Thanks,
    Dipal

    LabVIEW now uses the Microsoft installer. It's possible that you need to upgrade the version that's on the Win2K box. I think the latest service packs from Microsoft include it.

  • Servlet exception when deploying a WAR to WebLogic 10.3.5

    Hello,
    I've got a web application in a war file that I am attempting to deploy to a test environment which runs WebLogic 10.3.5. I've got a couple of developer environments that run WebLogic 12.1.1 and 10.3.4. The application can be deployed and started on 10.3.4 and 12.1.1 without any problems. It will deploy to the server running 10.3.5, but when I attempt to start the application (Start > Servicing All Requests) then I'm getting an error.
    javax.servlet.ServletException: [HTTP:101249][ServletContext@21871606[app:HelloWeb module:HelloWeb.war path:/HelloWeb spec-version:2.5]]: Servlet class for servlet helloweb could not be loaded because the requested class was not found in the classpath . java.lang.ClassNotFoundException
    The error log doesn't offer me any additional information about the cause of the error, just this error message and a stack trace of weblogic APIs that I'm not familiar with. Upgrading from 10.3.5 to a newer version of WebLogic isn't an option -- I don't own the test environment and I'm not allowed to make changes to the application server version. I've spent a the last two days trolling for help on this error message and I'm out of ideas. Any help would be welcome.

    Sure. Right now I was trying this on just the AdminServer, but it will give the exact same problem when it's run on a managed server as well.
    ####<Feb 6, 2013 8:25:14 AM EST> <Error> <Deployer> <LOCALSERVER> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1360157114674> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1360157109162' for task '2'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "helloweb" failed to preload on startup in Web application: "HelloWeb.war".
    javax.servlet.ServletException: [HTTP:101249][ServletContext@18469014[app:HelloWeb module:HelloWeb.war path:/HelloWeb spec-version:2.5]]: Servlet class for servlet helloweb could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: .
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         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.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "helloweb" failed to preload on startup in Web application: "HelloWeb.war".
    javax.servlet.ServletException: [HTTP:101249][ServletContext@18469014[app:HelloWeb module:HelloWeb.war path:/HelloWeb spec-version:2.5]]: Servlet class for servlet helloweb could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: .
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         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.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         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)
         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.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.servlet.ServletException: [HTTP:101249][ServletContext@18469014[app:HelloWeb module:HelloWeb.war path:/HelloWeb spec-version:2.5]]: Servlet class for servlet helloweb could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: .
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         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.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >

  • Images do not show when deployed on remote server

    We are using jdeveloper 11.1.2.1, adf and integrated weblogic and remote server has weblogic where we deploy the application for testing.
    We have a login.html page. when deployed and running the image in login.html does not show in FF or IE 8. It shows on IE9. when deployed on the remote server.
    When deployed on the integrated server only fire fox shows the image. None of the other web browsers show the image in login,html
    Here is my login.html
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html>
    <head>
    <!--meta http-equiv="Content-Type" content="text/html;CHARSET=iso-8859-1" /-->
    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>
    <title>Application Login</title>
    </head>
    <body>
    <div class="header">
    <div class="head_logo"><img src="images/imageLogo.JPG" alt="DASIS Logo" height="73" width="862"/></div>
    </div>
    <div class="navigation"></div>
    <div class="content">
    <div class="contentTitle">
    Welcome to ISATS online.
    <hr/>
    </div>
    <div class="contentArea">
    <p class="Arial">To login, enter your user ID and password, then click the Login button.
    </p>
    <form method="POST" action="j_security_check">
    <TABLE CELLPADDING="5"
    SUMMARY="This table contains a web form
    with fields for ID and password entry." >
    <TBODY>
    <TR>
    <TD ALIGN="right" VALIGN="top">
    <span class="Arial">User ID:</span>
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="text" value="" alt="Enter User ID" name="j_username"></input>
    </TD>
    </TR>
    <TR>
    <TD ALIGN="right" VALIGN="top">
    <span class="Arial">Password:</span>
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="password" name="j_password" value="" alt="Password"></input>
    </TD>
    </TR>
    <TR>
    <TD ALIGN="right" VALIGN="top" width="85">
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="submit" name="submit" value="Submit"></input>
    </TD>
    </TR>
    </TBODY>
    </TABLE>
    </form>
    <span class="Arial">
    Please contact Help Desk for assistance with the User ID and Password.
    <br>
    The Help Desk number is XXX) XXX-2300.
    </span>
    </div>
    </div>
    </body>
    </html>
    Any help is appreciated
    Edited by: user597294 on Jan 11, 2012 3:58 PM
    Edited by: user597294 on Jan 11, 2012 4:01 PM

    The problem does not seem to be with TopLink or JPA, so you may want to post this question to a different forum, such as the JDeveloper/ADF forum at:
    JDeveloper and ADF
    If the image itself is being sent but not loaded, you might check that it is a display issue with the browser being used.
    Best Regards,
    Chris

  • Org.eclipse.virgo.util.io.FatalIOException when deploying to local server

    Hi,
    i get the following error a lot when deploying an app to a local test server. (Neo SDK 2.3.1)
    [2013-03-15 10:37:04.439] fs-watcher                   <DE0017E> Failed to update web bundle 'shall-we' version '0.0.0'. See the logs for more information. org.eclipse.virgo.util.io.FatalIOException: Content of destination path '.\webapps\shall-we' cannot be removed
              at org.eclipse.virgo.util.io.ZipUtils.determineFinalUnzipDestination(ZipUtils.java:243)
              at org.eclipse.virgo.util.io.ZipUtils.unzipToFolder(ZipUtils.java:159)
              at org.eclipse.virgo.util.io.ZipUtils.unzipToDestructive(ZipUtils.java:81)
              at org.eclipse.virgo.util.io.JarUtils.unpackToDestructive(JarUtils.java:58)
              at org.eclipse.virgo.web.war.deployer.WARDeployer.update(WARDeployer.java:352)
              at org.eclipse.virgo.nano.deployer.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:98)
              at org.eclipse.virgo.nano.deployer.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:191)
              at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)
              at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:82)
              at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:373)
              at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:282)
              at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:48)
              at java.lang.Thread.run(Thread.java:722)
    My current workaround is to restart the server. However this is really annoying.... Is this a known issue?
    Best regards,
    Fabian

    Hi Vlado,
    thanks for your support.
    From a first test it looks like this new version solves the problem along with JDK7
    Just let me add, for those using maven, in order to exclude jaxb-impl from deployment, you just need to add the following dependency to you pom.xml
    <dependency>
         <groupId>com.sun.xml.bind</groupId> 
         <artifactId>jaxb-impl</artifactId> 
         <version>2.2.6</version> 
         <scope>provided</scope> 
    </dependency>
    This will tell maven to not bundle jaxb-impl into the lib folder as it's offered by JDK7
    Of course you have JAVA_HOME set to JDK7 home so that the local cloud server picks up the JDK7 libs
    Thanks a lot
    Vincenzo

  • When deploying to Weblogic Server, JDeveloper is unable to list servers

    I have created a BPEL project using JDeveloper 11.1.1.6.
    Have created an Integration Server in the JDeveloper Application Server tab. While deploying the project using this Integration Server profile, JDeveloper is unable to list out servers. As a result, the NEXT button is grayed-out and the deployment prematurely halts and cannot continue any further.
    When deploying to Integrated Weblogic Server, JDeveloper is unable to list servers.
    I have taken the following actions:
    In JDeveloper, the proxy setting was initially turned off. So, I have turned it on and given it a try too.
    I have also gone through the proxy settings in my JDeveloper, proxy connection test was successful. I still dont see servers during development.
    I have also followed all steps on JDeveloper Help Tutorial on "41 Deploying SOA Composite Applications" and no success.
    Issue can be reproduced as below:
    The issue can be reproduced at will with the following steps:
    1. Create a SOA BPEL Composite
    2. Try Deploying the Composite
    3. In the JDeveloper Deploy Wizard, notice the SOA server is not listed.
    Please advice.
    Thanks in advance.

    Hi,
    I am having the same issue, were you able to resolve this, would you be so kind to let me know what was the fix?
    I have JDEV 11.1.1.6, both my admin servers and managed servers are up and running, I can create Application Server connection with no problem, but I don't see any servers under SOA servers list when trying to deploy a composite.
    Thank you,
    Anatoliy

  • Page Break does not work in PDF report when deployed to App Server

    I have a report with a PAGE Break before on a repeating frame that holds a matrix report. In reports designer on the PC, the report correctly shows the page break. When deployed to the app server, the report shows the page after the break superimposed on top of the page before the break.
    The report has a repeating frame that spans both pages and holds the header information (page 1), and the matrix report (page 2).
    Any suggestions on how to fix this would be greatly appreciated.
    Deb

    Crystal Reports Designer 2008 and Business Objects Enterprise XI release 2 are not in the same suite release. You should use Crystal Reports Designer XI release 2 to connect BOE XIr2.

  • Servlet error after deploy to app server

    Hi,
    When I run my jheadstart app from local pc then everything is fine. When I deploy the same app to the app server it starts correctly, and works somehow. But, when I click the new button in any kind of jsp, I get the following error:
    05/05/18 09:58:19 Started
    05/05/18 09:58:27 ilbi: jsp: init
    05/05/18 09:58:28 ilbi: action: init
    05/05/18 09:58:29 ilbi: uix: init
    05/05/18 09:58:31 ilbi: 9.0.4.1.0 Started
    05/05/18 09:59:06 ilbi: Servlet error
    java.lang.ClassCastException
         at oracle.jheadstart.util.ReportingUtils.processException(ReportingUtils.java:274)
         at oracle.jheadstart.util.ReportingUtils.translateExceptionToStrutsErrors(ReportingUtils.java:149)
         at oracle.jheadstart.util.ReportingUtils.reportErrors(ReportingUtils.java:131)
         at oracle.jheadstart.controller.strutsadf.action.JhsStrutsJspLifecycle.reportErrors(JhsStrutsJspLifecycle.java:263)
         at oracle.adf.controller.struts.actions.DataAction.reportErrors(DataAction.java:269)
         at oracle.adf.controller.struts.actions.DataAction.reportErrors(DataAction.java:463)
         at oracle.adf.controller.lifecycle.PageLifecycle.handleLifecycle(PageLifecycle.java:150)
         at oracle.adf.controller.struts.actions.DataAction.handleLifecycle(DataAction.java:222)
         at oracle.jheadstart.controller.strutsadf.action.JhsDataAction.handleLifecycle(JhsDataAction.java:389)
         at oracle.adf.controller.struts.actions.DataAction.execute(DataAction.java:153)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
         at oracle.jheadstart.controller.strutsadf.JhsActionServlet.process(JhsActionServlet.java:127)
         at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:239)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:239)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
         at oracle.jheadstart.controller.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:172)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
         at khb.ilbi.controller.SSOAuthenticationFilter.doFilter(SSOAuthenticationFilter.java:113)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:600)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
         at java.lang.Thread.run(Thread.java:534)
    I think this is a deployment problem and I tried to resolve used the deployment issue on this forum (I made the ADF Runtime manual installation steps), but at this moment I have no idea.
    Could anybody help me, please?
    thanks
    Gyula

    Hi,
    Here are the codes:
    OLD CODE:
    protected void create(AttributeList attributeList)
    super.create(attributeList);
    setOwnerId(AdfbcUtils.getValueFromSequence("ILB_OWNERS_S", getDBTransaction()));
    NEW CODE
    protected void create(AttributeList attributeList)
    super.create(attributeList);
    setOwnerId(getSeqNum("ILB_OWNERS_S", getDBTransaction()));
    getSeqNum:
    PUBLIC NUMBER getSeqNum(String sequenceName, DBTransaction tr) {
    STATEMENT st = NULL;
    ResultSet rset = NULL;
    NUMBER retVal = NULL;
    try {
    String stmt = "select to_char(" + sequenceName + ".nextval) from dual" ;
    st = tr.createStatement(1);
    rset = st.executeQuery ( stmt );
    WHILE (rset.NEXT())
    retVal = NEW NUMBER(rset.getString(1));
    logger.DEBUG("Sequence captured");
    RETURN retVal;
    } catch (SQLException s) {
    logger.DEBUG("Sequence not captured because error occured");
    throw NEW JboException(s);
    } finally {
    try {
    IF (st != NULL) st.CLOSE();
    } catch (SQLException s) { /* ignore */ }
    Gyula

  • PL/SQL  Web Service fails when deployed to WebLogic server

    I have a web service generated via JDeveloper from a PL/SQL package. It runs fine both when tested in JDeveloper and when the WAR file is manually deployed to the Integrated WebLogic Server. However, when the WAR file is deployed to our actual WebLogic server, it fails. Other existing web services that were not generated with the JDeveloper wizard work correctly. I am having trouble finding any references to this type of issue to solve it. Are there any ideas what might be causing the WSDL to fail?
    References:
    * JDeveloper 11.1.1.6.
    * No proxies are involved.
    * The PLSQL package is a basic function that returns varchar2 input fed in by one parameter:
    create or replace package body pkg_ws_test as
    function test_me (p_anything_in varchar2)
    return varchar2 is
    begin
    return p_anything_in;
    end test_me;
    end pkg_ws_test;
    * Top of error stack is as follows:
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
    ...

    Hi,
    The below error trace you've provided doesn't confirm that Weblogic server has thrown the error.
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://svr:8892/wsTest2-getSame-context-root/TestMePort?wsdl: HTTP connection error code is 500 at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:325) at
    Please paste complete stacktrace of the error to check and also include the caused by section in the error.
    Thanks,
    Vijaya

  • Issue when deploying a Jersey RESTful WS (Standalone Vs Intg WLS)

    Hi All,
    I wrote a simple RESTful Web Service using the Jersey API. I downloaded the three files jersey-core, jersey-server and asm and bundled them with the deploying WAR file. I deployed the Web Service using JDeveloper to the Integrated Web Logic and everything went fine.
    I Deployed the same web app to another standalone Web Logic Instance and it gave me the below error
    Has anyone faced and resolved this issue?
    [04:36:54 PM] Weblogic Server Exception: weblogic.application.ModuleException: [HTTP:101216]Servlet: "jersey" failed to preload on startup in Web application: "MultiPartTester.war".
    java.lang.NoSuchMethodError: com/sun/jersey/core/spi/factory/ContextResolverFactory.<init>(Lcom/sun/jersey/core/spi/component/ProviderServices;Lcom/sun/jersey/core/spi/factory/InjectableProviderFactory;)V
         at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:804)
         at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:589)
         at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:403)
         at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:252)
         at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:550)
         at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:201)
         at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:307)
         at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:470)
         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:121)
         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:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         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:41)
         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:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [04:36:54 PM] Caused by: java.lang.NoSuchMethodError: com/sun/jersey/core/spi/factory/ContextResolverFactory.<init>(Lcom/sun/jersey/core/spi/component/ProviderServices;Lcom/sun/jersey/core/spi/factory/InjectableProviderFactory;)V
    [04:36:54 PM]   See server logs or server console for more details.Edited by: Codean on Mar 28, 2011 4:53 PM

    I found the issue. The jersey core and jersey server jar were of different revisions and that is why it was failing. Did not understand why JDeveloper worked fine with the integrated server.
    In any case i downloaded the same version of all the jersey jars and it is now working

  • Issue when deploying web service

    Hi,
    I'm new to web services. Im currently using netbeans 6.0 beta 1 to create my web services. After creating and deploying it on the bundled tomcat 6 server, i get this error that says that requested resource not found. What could be the cause of it as it works in netbeans 5.5? Could it be that the error is caused by the difference in the JAX WS 2.0 and 2.1 libraries?
    note: netbeans 5.5 uses JAX WS 2.0. netbeans 6.0 beta 1 uses JAX WS 2.1.
    much help would be appreciated. Thank you...
    coderDuck

    here's the log
    Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:511)
    at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1220)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1458)
    at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:820)
    at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:348)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
    at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
    ... 36 more
    Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
    at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1237)
    at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:373)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)
    **************************************WARNING***************************************
    To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
    before rt.jar. To do this you can use Java endorsed mechanism to override what is in
    Java platform. The easiest way to do so is to copy all jars from the
    C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
    Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
    at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
    at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
    at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
    ... 22 more

  • Error in Logging using log4j When deployed in weblogic server

    I have deployed an SOAP based web service application as an war file and used log4j propertiers to do application logging .When i tested the application through a JAVA client the log4j log file has all the application log information but when i deployed it in the weblogic server 10.3.3 and tested it through SOAP UI it gives me just "Run time error exception" in the log4j log file(which is returned in the SOAP response) as against the application logs which i need. I have also added <wls:package-name>org.apache.log4j.*</wls:package-name> in the weblogic.xml and also changwed the logging to the log4j logging in the server ( which was perviously JDK logging) .But still it is not returning the complete application error stack trace in the log4j log file(and also in the weblogic command console) I need to get the application error stack trace in the log4j log file ( and also in the console) so it would be easy to debug the code.
    Please help me out in doing the same.
    thanks in advance

    Noman,
    have you checked that the folder D:\OracleJeveloper\Middleware\jdk160_14_R27.6.5-32 contains the jre?
    Timo

Maybe you are looking for

  • Looking for a solution to simply drop outliers

    I have created an application to measure a Helium concentration, using an Alcatel ASM-102 Leak Detector.  The problem is that occasionally, the device sends out a bogus value, perhaps 0.00x10^0 or perhaps 2 x 10^-2, reather than 2 x 10^-7.  I am look

  • Problem to import IBM .XSD in SAP PI 7.11

    I can't impot the follow .XSD in SAP PI, the system shows Name of element codigo-ISO-4217-Alfabetico contains errors: <?xml version="1.0" encoding="UTF-8"?> <xsd:schema attributeFormDefault="unqualified"      elementFormDefault="unqualified"      tar

  • Consuming Web Services in SSIS Script Task

    Hello Sorry for my English, I' ll try to explain my problem. I am new to SSIS. Using this article http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/01/28/consuming-web-services-in-ssis-script-task.aspx I have tried to consume web service. 1

  • Electronic Signature based approval

    Hello Experts, Does OIM support electronic signature based approval? Instead of simply cliking "Approve" button , the approver has also to verify his electronic signature to approve a resource request. Thanks INIYA

  • Acrobat X PDF Won't Print

    I installed Acrobat X the other day. Today, I tried printing a PDF document, but it won't print. When I click OK, I get an error message that reads: document cannot print, then another message that reads no pages were selected. If I click on printer,