Error in deploying a WebDynpro application

Hi All,
I created a WebDynpro application and was unable to deploy it from NWDS. I had made all possible configurations like
1. setting the host name and IP address in the hosts file
2. Stating the server name instead of local host in the J2EE preferences of NWDS
But, still was unable to deploy it from NWDS. As I went through some of the workaround solutions stated on sdn I followed them and tried deploying via sdm and that deployment worked.
Later, I got the port 500018 opened so that I would be able to deploy from remote system using NWDS.
But, now when I try deployment I just realise that the WebDynpro Runtime in Visual Admin is inactive and am not in a position to even deploy the application via sdm.
The error thrown is stated below:
===========================================================================
Deployment started Fri Jun 24 15:28:23 IST 2005
===========================================================================
Starting Deployment of FirstWebDynPro
Aborted: development component 'FirstWebDynPro'/'local'/'LOKAL'/'0.2005.06.10.14.23.22':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/FirstWebDynPro.ear. Reason: None of the available containers recognized the components of application local/FirstWebDynPro; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of FirstWebDynPro finished with Error (Duration 2703 ms)
Can someone please help me and let me know as to how I could get the WebDynpro back to active status.
Thanks for all your help in advance,
Best regards,
Divya Rao

Hi Divya,
You could try with the Console Administrator. Open a command prompt and execute:
telnet localhost 50008
[login]
> jump 0
> startservice webdynpro
Now you can check the status like this:
> lss | grep webdynpro
If it is still stopped check /usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log/defaultTrace.trc and /usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log/system/server.log for errors.
HTH,
Vladimir
PS: Please consider rewarding points for helpful answers.

Similar Messages

  • Error while deploying a webdynpro application

    Hi,
    Iam getting an error while deploying the application in nwds the error is like this
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.labprocess.LabProcess1
    what is the remedy for this and due to what reason it is displaying. plz reply me ASAP.
    Regards,
    Shilpa.N
    Edited by: pasumarthi shilpa on Apr 17, 2008 7:01 AM

    Hi,
    Iam having one doubt regarding ECATT  in case of this at front end any changes we need to make is it necessary.....
    actually ECATT means recording the nwds applications at backend browser when we click on start recording it will start recording and what ever values we r entering at front end we can view from backend...  Plz suggest me ASAP.... waiting for u r response........
    Regards,
    Shilpa.N

  • Deployment aborted while deploying a webdynpro application

    Hi SDNers,
    While deploying a webdynpro application deployment aborted and shown the following error.
    Aug 8, 2006 4:51:38 PM /userOut/deploy
    (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]]
    ERROR:
    [010]Deployment aborted
    Settings
    SDM host : incata90
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/veer/LOCALS1/Temp/temp9590TutWD_DynamicForm.ear
    Deployment exception : Server incata90 did not accept login request as apiadmin on port
    50018 - Cannot log in. There are already active sessions:
    Session id 8 / An administrator logged in via API /
    Inner exception was :
    Server incata90 did not accept login request as apiadmin on port 50018 - Cannot log in.
    There are already active sessions:
    Session id 8 / An administrator logged in via API /
    can somebody help me in resolving this problem?
    Regards
    Veeru

    Hi,
    Sometimes I get this error. It is usually solved by restarting the SDM server.
    Switch to the J2EE Engine view in NWDS and right click the SDM server. Restart process.
    Good luck,
    Roelof

  • Error in deploying Web Dynpro application

    Hi
    I have created (in Net weaver developer studio) and deployed a webdynpro application on the portal. I have created a SAP WebDynpro iView for the web Dynpro application that I have deployed on the portal. When I execute the WebDynpro iView in the portal,
    1) I get a popup message "Session Management will not work! Please check the DSM log file for details" I checked for the DSM log file under System Administration>Support>Support Desk>Portal RuntimeLogViewer and I browse to irj/root/WEB-INF/portal/logs. There is no file in the logs folder.
    2) After clicking ok on the popup message, I get an  error message in the portal saying
    Service cannot be reached
    What has happened
    URL http://svc1uer.<companyname.net>:8038/webdynpro/dispatcher/com.postdk.flights/FlightsApp call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system UER with error code 404 and for the reason Not found.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If you do not yet have a user ID, contact your system administrator.
    ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:K-i:svc1uer_UER_38-v:0-s:404-r:Notfound
    HTTP 404 - Not found
    Your SAP Internet Communication Framework Team
    Thanks in advance
    Jay

    Hi..
    Thank u boss, ur reply was very helpfull to sort out our requirment.
    Regrads
    Rajesh

  • Getting an error while deploying the Quiz application in NWDEV

    Hi,
    I am getting an error while deploying the Quiz application in NWDEV.
    Please check this error log.
    It looks that it is not getting the Question.properties file but the file is already specified
    in the desired location.
    Error log:
    Detailed Error Information
    Detailed Exception Chain
    java.util.MissingResourceException: Can't find bundle for base name com.sap.tc.webdynpro.tutorials.quiz.resources.Questions, locale en_US
         at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:839)
         at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:808)
         at java.util.ResourceBundle.getBundle(ResourceBundle.java:702)
         at com.sap.tc.webdynpro.serverimpl.core.localization.AbstractResourceHandler.initResourceBundle(AbstractResourceHandler.java:485)
         at com.sap.tc.webdynpro.serverimpl.core.localization.AbstractResourceHandler.loadResourceBundle(AbstractResourceHandler.java:162)
         at com.sap.tc.webdynpro.tutorials.quiz.QuizComp.wdDoInit(QuizComp.java:108)
         at com.sap.tc.webdynpro.tutorials.quiz.wdp.InternalQuizComp.wdDoInit(InternalQuizComp.java:122)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Regards
    Kaushik Banerjee

    Hi,
    I think it is talking the default browser language as US and seraching for the properties file of that language.
    I think the sol for this prob is change the
    Question.properties -
    >Question_en.properties
    Thanks & Regards,
    Lokesh

  • Deployment of WebDynpro Application failed

    I get the following error when I try to deploy by WebDynpro application:
    Oct 18, 2006 12:05:38 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
    [008]Deployment finished with warning
    Settings
    SDM host : EIX-Blade-001
    SDM port : 50118
    URL to deploy : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp46898sap.comcafnpidemowdmass.ear
    Result
    => deployed with warning : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp46898sap.comcafnpidemowdmass.ear
    Finished with warnings: development component 'caf/npi/demo/wd/mass'/'sap.com'/'LOKAL'/'0.2006.10.18.12.05.27'/'0':
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application sap.com/caf/npi/demo/wd/mass and wait. Reason: Clusterwide exception: server ID 16576650:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/cafnpidemowdmass'' for startup. Reason=Clusterwide exception: Failed to start dependent interface ''caf/eu/gp/api'' of application ''sap.com/cafnpidemowdmass''. Status of dependent component:  STATUS_MISSING. Hint: Is the component deployed correctly on the engine?
         at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : Got problems during deployment

    Hi
    It seems to be some problem with your application start up. The component is deployed in the server, but however its not able to start automatically.
    Do you have a cluster setup on the server, like a central instance and dialogue instance kind of set up. If yes, pl ensure that the application is started from the central and (also check with the dialogue servers also).
    Better delete the application /component from all the nodes and you must deploy to the central /main instance server.
    For you to run the current deployed applciation, navigate to the appropriate server node and to the application and start it manually ( a simple tick) will start it.
    Hope this helps
    thanks

  • Error while deploying a composite application

    Hi
    I have an error while deploying my composite application.
    It says
    java.lang.NoClassDefFoundError: com/sap/caf/ui/utils/cool/CoolConnectionProperties
    The versions of my NWDS and WAS are 7.0.Please help.
    Thanks,
    ms.

    Hi
    I have added references to libraries with hard reference type.I also added the dc
    tc/conn/connectorframework.
    I still have errors
    => deployment aborted : file:/C:/DOCUME1/pr46715/Local Settings/Temp/temp28823sap.comcarpool~permissions.sda
    Aborted: development component 'carpool/permissions'/'sap.com'/'local'/'20070702161445':
    Caught exception during access of archive "E:\usr\sap\NWS\DVEBMGS01\SDM\root\origin\sap.com\carpool\permissions\local\20070702161445\temp28823sap.comcarpoolpermissions.sda":
    java.lang.RuntimeException: ERROR: Cannot initialize EARReader: Error while initializing Extended Ear Reader using file: E:\usr\sap\NWS\DVEBMGS01\SDM\root\origin\sap.com\carpool\permissions\local\20070702161445\temp28823sap.comcarpoolpermissions.sda. Reason: Exception occurred while reading ear descriptor xml. Reason: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(META-INF/application-j2ee-engine.xml, row:10, col:25)Exception is:
    => deployment aborted : file:/C:/DOCUME1/pr46715/Local Settings/Temp/temp28822sap.comcarpool.ear
    Aborted: development component 'carpool'/'sap.com'/'local'/'20070702165134':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/carpool.. Reason: Exception during generation of components of application sap.com/carpool in container EJBContainer.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/carpool in container EJBContainer.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Regards
    ms.

  • Flex error while deploying a VC application

    Hi Experts,
    Though I have rarely worked on VC developments, I have to troubleshoot an issue wherein we are getting following error while deploying a VC Application.
    Error: Error in compiling flex application. Consult log file for details.
    I have got a log file and it has written out 100s of lines of log, however, following is the important part from the log file:
    #00145E9635CE0060000016940015E0C60004A07BE7C55172#1302353936732#/System/Server/VCServer
    #sap.com/VisualComposerServerEar04
    #com.sap.portal.vc.server#ganeshb#35216##n/a##b1528d4062a811e0aedc00145e9635ce
    #SAPEngine_Application_Thread[impl:3]_12##0#0#Debug#1#/System/Server/VCServer#Plain###
    Server Error:Failed to import model - attribute is missing in imported file bytes are <?xml version="1.0" encoding="UTF-8"?>
    Any help on how to resolve this?
    Thanks in advance,
    Ameya
    Edited by: Ameya Pimpalgaonkar on Nov 16, 2011 7:31 AM

    Hi Ameya,
         If its VC 7.0 then you must be using Flash Compiler.Try changing the compiler to Flash at this path
    Tools->Options->Compiler->Change 'Runtime filed to Flash'.I hope this should solve your problem.
    Naga

  • Runtime Error While executing the WebDynpro Application

    I am getting the Runtime Error While executing the WebDynpro Application. The error message is "TSV_TNEW_OCCURS_NO_ROLL_MEMORY".
    It says like "
    Short text
        No roll storage space of length 9728 available for OCCURS area.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    But while executing some other Web Dynpro Applications, i am not facing this problem.

    Generally this error is a result of an infinite loop on internal table or select endselect statement where by severs  temporary memory gets full. With no memory to insert new records in temporary memory system generates the dump.
    Check your application or ask basis consultant to look at the memory parameters in instance profile.
    Regards
    Rohit Chowdhary

  • Error while deploying a WebDynpro from NWDS

    Hi,
    I'm trying to deploy a simple WebDynpro application. I'm deveoping on a local machine, the J2EE Engine is on the remote host.
    While developing I'm getting the following deployment exception:
    Deployment exception: Cannot determine sdm host (is empty). Please configure your engine/sdm correctly!
    I have read a lot of postings about the same problem, but none could realy solve my problem.
    I don't have access to the remote machine, but the  admistrator checked the J2EE Engine and the SDM and they should be running correctly.
    I'm also sure that I have correctly specified the Message Server Host and the Message Server Port under Windows-Preferances-SAP J2EE Engine.
    Strange is that in the J2EE Engine Tab the Remote engine node is not marked green like people told it should be, instead under the Remote engine node I only see another node marked with N/A and something like an error icon.
    I would appreciate any help.
    Thanks,
    Mladen

    hi ,
    select window> Preferences>SAP J2EE Engine-->Choose SAP J2EE Engine
    and select FIRST radio button and enter the host address and port as 3601.
    even it is not deploying..
    Try adding this to solve ur problem,
    in following location
    C:\WINDOWS\system32\drivers\etc
    u will find one file names "hosts" open that in notepad and add at the end of file..
    <ur system ip address> <servername>
    example:
    202.2.3.45 <any name>
    hope this will sovle ur deployment problem
    regards
    sunil
    Message was edited by: sunil chiluveru

  • Deploying a WebDynpro application from NWDS 7.0 on NWCE 7.1

    Hi,
    I am trying to deploy a simple WebDynpro application in NWDS 7.0. On the server there is NWCE 7.1 installed. When I try that, I always get this error:
    Deploymenty Exception: Cannot determine the sdm host (is empty). Please configure your engine/sdm correctly.
    I checked the settings in Window->Preferences->SAP J2EE Engine. Everything is set up and seems to work. When I check it either in SAP Management console or in NWDS at J2EE Engine View everything is lighting green.
    I've already found about 5 or more threads, where people seem to have the same problem, but in none of them was any solution. And further more everybody was writing about SDM configuration, but in NWCE 7.1 there is no longer any SDM (as it is written in SAP Installation Manual for NWCE 7.1).
    Did anyone solve this issue?
    Thanks

    Filip,
    Never worked with NW CE. But my guess is that it is a issue with your NWDS which is at a lower version than the server.
    As you know NW04's has a SDM.
    Thanks & Regards,
    Vijith

  • SDM Error when Deploying Web Dynpro Application

    Hi,
    My SAP SDM server gives error while, I deploy any .ear file through NWDS. Error is as below:
    Jul 29, 2008 4:22:29 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [ThreadDeploy Thread,5,main] ERROR:
    003Deployment aborted
    Settings
    SDM host : server2
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/gyan/LOCALS1/Temp/temp16971gyan.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/gyan/LOCALS1/Temp/temp16971gyan.ear
    Aborted: development component 'gyan'/'local'/'LOKAL'/'0.2008.07.29.16.22.26':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: server2 with user name: J2EE_ADMIN Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted.
    i have same password for SDM and J2ee_admin.
    Regards
    Gyan

    Hi Gyan Prakash,
    I Faced Similar when iam working on NWDS, nothing to worry about it just Delete the Application which you have created for your Project
    you find your application as follows:
    proj_sample --> webDynpro --> Applications --> proj_sampleApp.
    Delete the proj_sampleApp.
    save all metadata. Rebuild your Project. Restart your NWDS.
    create your New Application for your WebDynpro Project, rebuild your project and Now Deploy and Run your Project.
    This will solve your Problem.
    Regards,
    Sharma.

  • Error in deploying the Quiz Application

    hi
    i made the quiz application refering the Sample application given in sdn .
    when i deployed it in the WAS 6.4 server , the application was deployed successfully and ran without any issue
    however , when i deployed it in WAS 7.0 server , deployment was aborted and i faced the following error
    *Jun 30, 2008 2:23:53 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:*
    *[023]Deployment aborted*
    *Settings*
    *SDM host : cgnsap29*
    *SDM port : 50118*
    *URL to deploy : file:/C:/DOCUME~1/ss72883/Local Settings/Temp/temp5563WebDynpro_Quiz.ear*
    *Result*
    *=> deployment aborted : file:/C:/DOCUME~1/ss72883/Local Settings/Temp/temp5563WebDynpro_Quiz.ear*
    *Aborted: development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2008.06.30.14.22.43'/'0':*
    *Caught exception during application deployment from SAP J2EE Engine's deploy service:*
    *java.rmi.RemoteException: Cannot deploy application local/WebDynpro_Quiz.. Reason: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?*
    *(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)*
    *Deployment exception : The deployment of at least one item aborted*
    the additional information about the deployment
    *Jun 30, 2008 2:23:54 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:*
    *[023]Additional log information about the deployment*
    *<!LOGHEADER[START]/>*
    *<!HELP[Manual modification of the header may cause parsing problem!]/>*
    *<!LOGGINGVERSION[1.5.3.7185 - 630]/>*
    *<!NAME[F:\usr\sap\EC2\DVEBMGS01\SDM\program\log\sdmcl20080630085256.log]/>*
    *<!PATTERN[sdmcl20080630085256.log]/>*
    *<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>*
    *<!ENCODING[UTF8]/>*
    *<!LOGHEADER[END]/>*
    *Jun 30, 2008 2:22:57 PM  Info: - Starting deployment -*
    *Jun 30, 2008 2:22:57 PM  Info: Error handling strategy: OnErrorStop*
    *Jun 30, 2008 2:22:57 PM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop*
    *Jun 30, 2008 2:22:57 PM  Info: Update strategy: UpdateAllVersions*
    *Jun 30, 2008 2:22:57 PM  Info: Starting deployment prerequisites:*
    *Jun 30, 2008 2:23:14 PM  Info: Loading selected archives...*
    *Jun 30, 2008 2:23:14 PM  Info: Loading archive 'F:\usr\sap\EC2\DVEBMGS01\SDM\program\temp\temp5563WebDynpro_Quiz.ear'*
    *Jun 30, 2008 2:23:21 PM  Info: Selected archives successfully loaded.*
    *Jun 30, 2008 2:23:21 PM  Info: Actions per selected component:*
    *Jun 30, 2008 2:23:21 PM  Info: Update: Selected development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2008.06.30.14.22.43'/'0' updates currently deployed development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2007.08.13.16.02.48'/'0'.*
    *Jun 30, 2008 2:23:21 PM  Info: Ending deployment prerequisites. All items are correct.*
    *Jun 30, 2008 2:23:22 PM  Info: Saved current Engine state.*
    *Jun 30, 2008 2:23:22 PM  Info: Starting: Update: Selected development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2008.06.30.14.22.43'/'0' updates currently deployed development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2007.08.13.16.02.48'/'0'.*
    *Jun 30, 2008 2:23:22 PM  Info: SDA to be deployed: F:\usr\sap\EC2\DVEBMGS01\SDM\root\origin\local\webdynpro_quiz\LOKAL\0\0.2008.06.30.14.22.43\temp5563WebDynpro_Quiz.ear*
    *Jun 30, 2008 2:23:22 PM  Info: Software type of SDA: J2EE*
    **Jun 30, 2008 2:23:22 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *******
    *Jun 30, 2008 2:23:47 PM  Info: Begin of log messages of the target system:*
    **08/06/30 14:23:22 -  *************************************************************
    *08/06/30 14:23:26 -  Start updating EAR file...*
    *08/06/30 14:23:26 -  start-up mode is lazy*
    *08/06/30 14:23:26 -  EAR file updated successfully for 172ms.*
    *08/06/30 14:23:26 -  Start updating...*
    *08/06/30 14:23:28 -  EAR file uploaded to server for 500ms.*
    *08/06/30 14:23:47 -  ERROR: Not updated. Deploy Service returned ERROR:*
                         *java.rmi.RemoteException: Cannot deploy application local/WebDynpro_Quiz..*
                         *Reason: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:*
                         **     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?**
                         **     at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)**
                         **     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)**
                         **     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)**
                         **     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)**
                         **     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)**
                         **     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)**
                         **     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)**
                         **     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)**
                         **     at java.security.AccessController.doPrivileged(Native Method)**
                         **     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)**
                         **     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)**
                         *Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?*
                         **     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)**
                         **     at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1259)**
                         **     at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)**
                         **     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)**
                         **     at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)**
                         **     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)**
                         **     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)**
                         **     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)**
                         **     at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)**
                         **     ... 10 more**
                         *For detailed information see the log file of the Deploy Service.*
    **08/06/30 14:23:47 -  *************************************************************
    *Jun 30, 2008 2:23:47 PM  Info: End of log messages of the target system.*
    **Jun 30, 2008 2:23:47 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *******
    *Jun 30, 2008 2:23:48 PM  Error: Aborted: development component 'WebDynpro_Quiz'/'local'/'LOKAL'/'0.2008.06.30.14.22.43'/'0':*
    *Caught exception during application deployment from SAP J2EE Engine's deploy service:*
    *java.rmi.RemoteException: Cannot deploy application local/WebDynpro_Quiz..*
    *Reason: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:*
    **     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/WebDynpro_Quiz. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?**
    *(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)*
    *Jun 30, 2008 2:23:48 PM  Info: Starting to save the repository*
    *Jun 30, 2008 2:23:49 PM  Info: Finished saving the repository*
    *Jun 30, 2008 2:23:49 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.*
    *Jun 30, 2008 2:23:49 PM  Error: - At least one of the Deployments failed -*
    please site me the reason
    thanks and regards
    Viswas

    Hi,
    Is this DC, if so check that all used DCs are deployed.
    One more reason of this exception is when there is name conflict between two projects deployed on the same server , eg say projects A & B have same application name, component name.
    When I get this exception, I go to nwa, see logs to find out two conflicting projects and rename one of them and deploy again. It solves my problem.
    from Re: deployment getting aborted
    regards,
    Pradeep

  • Error while deploying the Composite Application ERROR: (SOAPBC_START_1)

    Hi,
    I have a EJB web service created and deployed in GlassFish. I have created a BPEL which will recieve from the web service and then insert into a SQL table. To track the messages I have also created to File WSDLs to save the WS message and the DB message.
    While deploying the Composite application I am recieving this error. "Component: sun-http-binding
    ERROR: (SOAPBC_START_1) HTTPBC-E00205: Start failed. java.lang.Exception: LifecycleException: PWC3985: Protocol handler initialization failed: java.net.BindException: Already bound: 8080
    Can anyone tell me what this is error is all about ??
    Regards,
    Jai

    This is the Glassfish Server log
    Nov 8, 2008 4:01:16 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand
    INFO:
    C:/Program Files/Java/jdk1.6.0_06\bin\java
    -Dcom.sun.aas.instanceRoot=C:/Program Files/glassfish-v2ur2/domains/domain1
    -Dcom.sun.aas.ClassPathPrefix=
    -Dcom.sun.aas.ClassPathSuffix=
    -Dcom.sun.aas.ServerClassPath=
    -Dcom.sun.aas.classloader.appserverChainJars.ee=
    -Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,j2ee-svc.jar
    -Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun-appserv-ant.jar
    -Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
    -Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar
    -Dcom.sun.aas.classloader.serverClassPath.ee=/lib/hadbjdbc4.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/lib/dbstate.jar,/lib/hadbm.jar,/lib/hadbmgt.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Dcom.sun.aas.classloader.serverClassPath=C:/Program Files/glassfish-v2ur2/lib/install/applications/jmsra/imqjmsra.jar,C:/Program Files/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/Program Files/glassfish-v2ur2/imq/lib/fscontext.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/lib/ant/lib/ant.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
    -Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,jesmf-plugin.jar,/lib/dbstate.jar,/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Program Files/Java/jdk1.6.0_06/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-launcher.jar,com-sun-commons-logging.jar,C:/Program Files/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/Program Files/glassfish-v2ur2/imq/lib/fscontext.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqxm.jar,webservices-rt.jar,webservices-tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar,C:/Program Files/glassfish-v2ur2/updatecenter/lib/updatecenter.jar,C:/Program Files/glassfish-v2ur2/jbi/lib/jbi.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/lib/ant/lib/ant.jar,dbschema.jar
    -Dcom.sun.aas.configName=server-config
    -Dcom.sun.aas.configRoot=C:/Program Files/glassfish-v2ur2/config
    -Dcom.sun.aas.defaultLogFile=C:/Program Files/glassfish-v2ur2/domains/domain1/logs/server.log
    -Dcom.sun.aas.domainName=domain1
    -Dcom.sun.aas.installRoot=C:/Program Files/glassfish-v2ur2
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -Dcom.sun.aas.promptForIdentity=true
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Dcom.sun.updatecenter.home=C:/Program Files/glassfish-v2ur2/updatecenter
    -Ddomain.name=domain1
    -Dhttp.nonProxyHosts=localhost|127.0.0.1|jnambiar2
    -Dhttp.proxyHost=web-proxy.atl.hp.com
    -Dhttp.proxyPort=8088
    -Dhttps.proxyHost=web-proxy.atl.hp.com
    -Dhttps.proxyPort=8088
    -Djava.endorsed.dirs=C:/Program Files/glassfish-v2ur2/lib/endorsed
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.6.0_06/lib/ext;C:/Program Files/Java/jdk1.6.0_06/jre/lib/ext;C:/Program Files/glassfish-v2ur2/domains/domain1/lib/ext;C:/Program Files/glassfish-v2ur2/javadb/lib
    -Djava.library.path=C:\Program Files\glassfish-v2ur2\lib;C:\Program Files\glassfish-v2ur2\lib;C:\Program Files\glassfish-v2ur2\bin;C:\Program Files\glassfish-v2ur2\lib
    -Djava.security.auth.login.config=C:/Program Files/glassfish-v2ur2/domains/domain1/config/login.conf
    -Djava.security.policy=C:/Program Files/glassfish-v2ur2/domains/domain1/config/server.policy
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Djavax.net.ssl.keyStore=C:/Program Files/glassfish-v2ur2/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Program Files/glassfish-v2ur2/domains/domain1/config/cacerts.jks
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djmx.invoke.getters=true
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -client
    -XX:+UnlockDiagnosticVMOptions
    -XX:MaxPermSize=192m
    -Xmx512m
    -XX:NewRatio=2
    -XX:+LogVMOutput
    -XX:LogFile=C:/Program Files/glassfish-v2ur2/domains/domain1/logs/jvm.log
    -cp
    C:/Program Files/glassfish-v2ur2/lib/jhall.jar;C:\Program Files\glassfish-v2ur2\lib\appserv-launch.jar
    com.sun.enterprise.server.PELaunch
    start
    Starting Sun Java System Application Server 9.1_02 (build b04-fcs) ...
    MBeanServer started: com.sun.enterprise.interceptor.DynamicInterceptor
    CORE5098: AS Socket Service Initialization has been completed.
    CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_06] from [Sun Microsystems Inc.]
    SEC1002: Security Manager is OFF.
    C:/Program Files/glassfish-v2ur2/domains/domain1/config/.__com_sun_appserv_pid
    ADM0001:SunoneInterceptor is now enabled
    SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
    WEB0114: SSO is disabled in virtual server [server]
    WEB0114: SSO is disabled in virtual server [__asadmin]
    ADM1079: Initialization of AMX MBeans started
    ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://jnambiar2.asiapacific.hpqcorp.net:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
    ADM1506: Status of Standard JMX Connector: Active = [true]
    JBIFW0010: JBI framework ready to accept requests.
    WEB0302: Starting Sun-Java-System/Application-Server.
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
    SMGT0007: Self Management Rules service is enabled
    Application server startup complete.
    Registered Status Provider MBean for sun-jdbc-binding.
    Registered Status Provider MBean for sun-sql-engine.
    JBISE6013: JavaEEServiceEngine : Java EE Service Engine started successfully.
    JBIFW1146: Engine sun-javaee-engine has been started.
    Registered runtime configuration MBean for sun-jdbc-binding.
    Registered runtime configuration MBean for sun-sql-engine.
    HTTPBC-R00100: sun-http-binding starting
    FILBC-LCY0006: Component sun-file-binding started (outbound).
    FILBC-LCY0005: Component sun-file-binding started (inbound).
    Started outbound.
    SQLSE started.
    JBIFW1146: Engine sun-sql-engine has been started.
    Started outbound receiver.
    Receiver started.
    Receiver started.
    FILBC-LCY0003: Component sun-file-binding started with the following configuration:
    specification-version: 1.0
    build-number: 080408_1
    Threads: 10
    JBIFW1146: Binding sun-file-binding has been started.
    Started inbound receiver.
    JDBC Binding component started.
    JBIFW1146: Binding sun-jdbc-binding has been started.
    PWC3982: Cannot register MBean for the Protocol
    grizzlyHttpProtocol.selectorRegisterProtocol
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 9080
    XSLTSE-5001:Initialized XSLT service engine successfully!
    XSLTSE-5002:Started XSLT service engine successfully!
    JBIFW1146: Engine sun-xslt-engine has been started.
    HTTPBC-E00153: Failed to read the descriptor file for identity information; descriptor file is 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\components\sun-http-binding\install_root/META-INF/jbi.xml'
    java.net.MalformedURLException: unknown protocol: c
    at java.net.URL.<init>(URL.java:574)
    at java.net.URL.<init>(URL.java:464)
    at java.net.URL.<init>(URL.java:413)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650)
    at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.identity(HttpSoapBindingLifeCycle.java:1103)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.logComponentInfo(HttpSoapBindingLifeCycle.java:1075)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.start(HttpSoapBindingLifeCycle.java:476)
    at com.sun.jbi.framework.ComponentFramework.startComponent(ComponentFramework.java:1846)
    at com.sun.jbi.framework.ComponentFramework.startComponent(ComponentFramework.java:1792)
    at com.sun.jbi.framework.ComponentOperation.process(ComponentOperation.java:233)
    at com.sun.jbi.framework.Operation.run(Operation.java:104)
    at java.lang.Thread.run(Thread.java:619)
    HTTPBC-R00101: sun-http-binding started with the following configuration:
    specification-version: unknown
    build-number: unknown
    OutboundThreads (max outbound threads): 10
    HttpDefaultPort: 9080
    HttpsDefaultPort: 9181
    AMConfigDir:
    ProxyType: DIRECT
    ProxyHost:
    ProxyPort: 0
    NonProxyHosts: localhost|127.0.0.1
    ProxyUserName:
    UseJVMProxySettings: false
    ApplicationVariables: {  }
    ApplicationConfigurations: {  }
    JBIFW1146: Binding sun-http-binding has been started.
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    JTS5014: Recoverable JTS instance, serverId = [3700]
    About to load the system app: MEjbApp
    POARemoteRefFactory checking if SFSBVersionPolicy need to be added
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    POARemoteRefFactory addSFSBVersionPolicy? false
    POARemoteRefFactory checking if SFSBVersionPolicy need to be added
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    POARemoteRefFactory addSFSBVersionPolicy? false
    LDR5010: All ejb(s) of [MEjbApp] loaded successfully!
    About to load the system app: __ejb_container_timer_app
    EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]
    LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!
    BPJBI-5001:BPEL service engine initialized
    BPJBI-5002:Starting BPEL service engine
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    I18N:
    BPJBI-5003: BPEL service engine started with following configurations:
    Persistence Enabled : false
    Monitor Enabled : false
    Persistence Database NonXA JNDI ResourceName : jdbc/bpelseNonXA
    Persistence Database XA JNDI Resource Name : jdbc/bpelseXA
    Engine Expiry Interval (failover setting) : 60 seconds
    Debug Enabled : false
    Debug Port : 3,343
    Thread Count 10
    Engine Installed on Application Server Cluster : false
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    JBIFW1146: Engine sun-bpel-engine has been started.
    JBIMA0452: Successfully processed 0 Service Assemblies during startup.
    JBIFW0012: JBI framework startup complete.
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "domain.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.security.config"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.security.config"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.dynamic.username.password"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.dynamic.username.password"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.signature.key.alias"
    wsgen successful
    DPL5306:EJB Web Service Endpoint [HPAdaptorWS] listening at address [http://jnambiar2.asiapacific.hpqcorp.net:8080/HPAdaptorWSDLService/HPAdaptorWS]
    deployed with moduleid = HPAdaptorWSEJB
    Container com.sun.enterprise.webservice.JAXWSContainer@1fae7b1 doesn't support class com.sun.xml.ws.api.server.Module
    LDR5010: All ejb(s) of [HPAdaptorWSEJB] loaded successfully!
    The log message is null.
    javax.ejb.EJBException
    at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:3869)
    at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3769)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3571)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:200)
    at $Proxy62.hpAdaptorWSDLOperation(Unknown Source)
    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 com.sun.enterprise.webservice.InvokerImpl.invoke(InvokerImpl.java:81)
    at com.sun.enterprise.webservice.EjbInvokerImpl.invoke(EjbInvokerImpl.java:82)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:113)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:226)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:155)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:114)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:87)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    Caused by: java.lang.UnsupportedOperationException: Message Recieved Successfully
    at hp.adaptor.gateway.HPAdaptorWS.hpAdaptorWSDLOperation(HPAdaptorWS.java:22)
    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 com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
    at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
    at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
    at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3986)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:189)
    ... 63 more
    EJB5018: An exception was thrown during an ejb invocation on [HPAdaptorWS]
    javax.ejb.EJBException
    at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:3869)
    at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3769)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3571)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:200)
    at $Proxy62.hpAdaptorWSDLOperation(Unknown Source)
    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 com.sun.enterprise.webservice.InvokerImpl.invoke(InvokerImpl.java:81)
    at com.sun.enterprise.webservice.EjbInvokerImpl.invoke(EjbInvokerImpl.java:82)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:113)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:226)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:155)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:114)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:87)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    Caused by: java.lang.UnsupportedOperationException: Message Recieved Successfully
    at hp.adaptor.gateway.HPAdaptorWS.hpAdaptorWSDLOperation(HPAdaptorWS.java:22)
    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 com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
    at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
    at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
    at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3986)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:189)
    ... 63 more
    Deploying service assembly HPAdapatorInboundCAwithFault to target server.
    Cannot find CatalogManager.properties
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\DBMessageFile.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\MsgInbound_DB.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\Partners\HPAdaptorWSDLService\HPAdaptorWS.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCA

  • Error upon deploying a dataservices application

    I'm getting a strange error upon deploying a data service project.
    The data service project is very simple, I import a single webservice from a port via a URI reference. This import happens fine.
    I then choose to build a dataservice from this webservice. I build and compile the project.
    When I choose test view, I paste a preformatted xml request which works fine in SoapUI. However, when I try to execute, I get an error (after the bea workshop builds and deploys the application)
    I get a java.lang.noClassDefFoundError: com/bea/ld/sql/api/SQLQueryRequest
    I'm running ALDSP 2.5 on Weblogic 8.1.5
    Please see the full attached error message, which is a screenshot from my BEA Workshop for Weblogic Platform IDE.

    Thank you mreiche. My workshop IDE set the Aqualogic Data Service Platform Application home to be the workshop home, not the liquiddata home!!
    Now I get the following error:
    weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027 [{bea-err}XQ0027b]: Element "{http://schemas.xmlsoap.org/soap/envelope/}Envelope" not found for validation
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.setValidationType(XMLValidatorForXMLBeans.java:233)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processTokensOnHold(XMLValidatorForXMLBeans.java:1345)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.gotBeginElementToken(XMLValidatorForXMLBeans.java:772)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:100)
         at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.core.RTVariable.fetchNext(RTVariable.java:49)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.exec(JAXRPCWebserviceIterator.java:165)
         at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:103)
         at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
         at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:56)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:161)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
         at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
         at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:142)
         at com.bea.ld.server.QueryInvocation.getResult(QueryInvocation.java:461)
         at com.bea.ld.EJBRequestHandler.executeFunction(EJBRequestHandler.java:346)
         at com.bea.ld.ServerBean.executeFunction(ServerBean.java:108)
         at com.bea.ld.Server_ydm4ie_EOImpl.executeFunction(Server_ydm4ie_EOImpl.java:208)
         at com.bea.ld.Server_ydm4ie_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
    This is what my request looks like:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:purisma-pcr:CEXP_0305_local">
    <soapenv:Header/>
    <soapenv:Body>
    <urn:FuzzySearchLocationRequest searchConfigurationName="Location_CompanyReq" maxNumberOfResults="0" scoreThreshold="0" startIndex="0" pageSize="0">
    <!--1 or more repetitions:-->
    <fuzzyCriterion fieldName="Customer_Name">columbus</fuzzyCriterion>
    <!--Zero or more repetitions:-->
    <fieldName>all</fieldName>
    </urn:FuzzySearchLocationRequest>
    </soapenv:Body>
    </soapenv:Envelope>
    All I really want to do is be able to import my startup's generated .wsdl into an ALDSP data service, and then call that data service. This is turning out a lot more difficult than I thought.

Maybe you are looking for