Error in deploying Work list - urgent
Hi all,
i'm trying to deploy the sample worklist given in {bpel_home}/samples/hw/worklistapp.
i had a problem previously, which i've described in the following link:
Problem in work list deployment
I have changed <project default="default" basedir="."> to <project default="" basedir=".">
BUILD IS SUCCESSFUL
next step described in README.txe of {bpel_home}/samples/hw/worklistapp is
(ii) java -jar admin.jar ormi://localhost/ oc4jadmin welcome1 -deploy -file $SRC_HOME/pcbpel/lib/hw_services.ear -deploymentName hw_services -parent orabpel
ormi://localhost/ ---> ormi://MyMachine:23791
$SRC_HOME ---> D:\product\10.1.3.1\OracleAS_1\bpel\samples\hw\worklistapp
now i'm getting the following error:
Error: Could not connect to the remote server. Please check if the server is down or the client is using invalid host, ORMI port or password to connect: Connection refused: connect
What could be the reason for this?
My SOA Suite is running.
Thanks.
Can you see them if you are using Oracle Enterprise Manager from your installation?
Marc
Similar Messages
-
Oracle.bpel.services.datacontrol.data.DataCollection error in BPM work-list
Hi,
I am working with Human task form. I Have created one form using create auto-generate option from task options. The form is fetching and displaying data properly in BPM work-list, but when i click on approve/reject button in form, it gives the error oracle.bpel.services.datacontrol.data.DataCollection error . Not sure, from where this error is coming.
Please reply if anyone is having idea why this error is coming. I am working with Jdev 11.1.1.5 and SOA suite 11g and this project is part of new development. ( no migration issue, i guess)
thanks,
rpswas this issue resolved?
I am facing the same issue and when I click on Approve/Reject in the form I receive a pop up saying
oracle.bpel.services.datacontrol.data.DataCollection cannot be cast to oracle.bpel.services.datacontrol.data.DataObject. -
Error in Initiating work list application
Hi I developed my BPEL code in SOA basic installation it was runnig fine but when I deployed the jar in Advanced SOA worklist is not getting initiated.
jazn.jar is available in j2ee/home but there is no jazn.jar in j2ee/oc4j_soa
When i run the command java -jar /software/product/10.1.3.3.0/j2ee/home/jazn.jar -user oc4jadmin -password addmin123 -listusers
I am getting a response
jazn.com/oc4jadmin
jazn.com/JtaAdmin
jazn.com/anonymous
It is not listing any BPM roles.
Kindly help me how to make sure that default worklist application users are created in oc4j_soa. Will jazn.jar be present in oc4j_soa ?Can you see them if you are using Oracle Enterprise Manager from your installation?
Marc -
500 Internal Server Error at HFM work space,Urgent;;;;;
Hi,
Can any one give me solution for this.
When I try to open Work space it is giving the error "500 Internal Server Error"
And I am using Apache Tomcat.\
Thanks in advance.Hi 807662 ,
Hope this helps...
Can you post the errors from the BI+ error log?
You say that you can't log into the client applications? What client apps are you trying to log into?
If Planning can you post the the errors from Planning? If HFM can you post the errors from HFM?
Can you post the errors from the Event Viewer log on the server?
-David
Web server returns the message "Internal Server Error (HTTP 500)"
DETAILS:
This message usually indicates an error on the Web server. This message is too generic to provide the actual cause of the error, but a careful examination of the Web server logs, can provide clues which may point you in the right direction.
There are a few of things you can infer from an "Internal Server Error" message.
1. The web server is NOT down, i.e it is responding to an HTTP request, since the error is being generated and returned by the web server. Unlike a "Page cannot be displayed" error which is a default message generated by a browser if it cannot contact the web server. The "Internal server error" message is caused by the web server actually returning an HTTP 500 code.
2. If all users are getting this error, its might indicate a problem with the web server itself, perhaps a lack of system resource, a system-wide failure, or a configuration or installation issue. If only one user gets the error, its probably just tied to the session of the user, and even may be specific to the current activity
3. The root cause is the web server, and not the application server or database, even though its possible that an application server or database response might trigger an error on the web server. For example, SQL returning a large result set might cause an OutOfMemory condition on the web server. If the application server errors out, the PIA servlet traps it and returns a generic message saying "An error has occurred on the application server", it does not return an HTTP 500 error.
The Internal Server Error message is generated by the web server, when the sub-process it called to process the browser's request, did not complete successfully. The sub-process may be a CGI program, ( Verity search in PeopleBooks for example), it may be another web server ( Apache proxying to WebLogic), or it may be a servlet (Weblogic HTTP handing off request to PIA). If the sub-process errors out, or returns an invalid error code, the web server will return an HTTP 500 error code to the browser.
The key therefore in troubleshooting HTTP 500 errors is to find out what sub-process was invoked, and what was the error encountered by the sub-process. Start by checking the access log on the web server. It will have the URL with the GET or POST request, and the return code. Here
Note though, that not all java exceptions translate to HTTP 500 errors, and not all HTTP 500 errors caused by servlets correspond to java errors. Sometimes a servlet may recover or ignore an exception and manage to return a valid response to the calling web server, mitigating an HTTP 500 code response to the browser.
Some of the common causes of servlet failures are:
- Invalid web server configuration ( these errors should be consistently reproducible)
- Errors from the Application Server that are not captured and translated into a meaningful message for the user.
- Network I/O errors while communicating with Application Server, or to a proxy plugin.
- Out of memory conditions on the web server.
- Problems with the Java runtime.
- System errors, like running out of disk space, insufficient permissions, running out of threads, etc.
- Errors in the servlet code itself. Example: NullPointerException
- Invalid or corrupted Session information, perhaps caused by Proxies, Load Balancers, Timeouts.
- Incorrect web server, JRE, OS patches and or versions.
G'Luck,
David
Edited by: David Debish on Feb 4, 2011 3:12 PM
Edited by: David Debish on Feb 4, 2011 5:09 PM -
Error while deploying VS Workflow to SharePoint List
Hi all,
I am getting error while deploying the WF to SharePoint 2013 list
Error 1 Error occurred in deployment step 'Activate Features': Microsoft.Workflow.Client.ActivityNotFoundException: The activity named 'WorkflowXaml_782198e9_fd42_4862_bdc0_d4a966f97c29' from scope '/SharePoint/default/36804029-858c-48cc-af57-4264730767a6/0068758c-be16-420e-a97e-46ab58b67daf'
was not found. HTTP headers received from the server - ActivityId: 0599b125-8148-4dd5-87bb-c90356bd00c6. NodeId: ServerName. Scope: /SharePoint/default/36804029-858c-48cc-af57-4264730767a6/0068758c-be16-420e-a97e-46ab58b67daf. Client ActivityId : e265df0a-03ea-40dc-98
0 0 ReportReqWF
I tried Powershell as
Register-SPWorkflowService -SpSite 'http://servername/site/' -WorkflowHostUri 'http://servername:12291' -AllowOAuthHttp -Force -ScopeName 'SharePoint' Command executes but error remains same.
Please help meHi Sunita,
Firstly, I recommend to debug your workflow in Visual Studio to see if there is anything incorrect in the code about Activating the feature.
Then I recommend to deploy the project as wsp solutions and then deploy it to SharePoint. After that use Install-SPFeature command to install the feature, then activate the feature to how it works.
Here are some similar threads for you to take a look:
http://social.technet.microsoft.com/Forums/en-US/251a7977-13ba-4568-932d-eed55d5c2bfc/missing-workflow-xaml-feature-error-during-site-creation-from-custom-template?forum=sharepointadmin
http://social.technet.microsoft.com/Forums/en-US/0c470b4b-8e32-47ab-bc29-409db01dce81/unable-to-activate-the-workflow-feature-in-sharepoint-2013?forum=sharepointcustomization
More information:
Develop SharePoint 2013 workflows using Visual Studio
http://msdn.microsoft.com/en-us/library/jj163199%28v=office.15%29
Walkthrough: Creating and Debugging a SharePoint Workflow Solution
http://msdn.microsoft.com/en-us/library/ee231573(v=vs.110).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support -
Illegal dependency error on deploying GP Web Dynpro application
Hello All,
We have created a GP application (FamilyStatusChange) on NWDS 7.0.11. We are using EP. 7.0 SP11.
On deploying and running this application via NWDS
java.lang.NoClassDefFoundError: com/sap/caf/eu/gp/co/api/EngineException
When I try to checkin and activate the activity corresponding to FamilyStatusChange, the activation fails and I get the following error:
Development Component Build (2007-06-29 03:27:08)
Component name: FamilyStatusChange
Component vendor: xyz.com
SC compartment: xyz.com_SC_XYZ_PORTAL_SP11_1
Configuration: JD2_XYZSP11_D
Location: JD2_XYZSP11_D
Source code location: http://dads:51900/dtr/ws/XYZSP11/adobe.com_SC_XYZ_PORTAL_SP11/dev/active/DCs/xyz.com/FamilyStatusChange/_comp/
DC root folder: /usr/sap/JD2/JC19/j2ee/CBS/85/.B/13602/DCs/xyz.com/FamilyStatusChange/_comp/
DC type: Web Dynpro
Host: dads
DC Model check:
All used DCs are available locally
validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
validating dependency to public part "default" of DC "sap.com/tc/cmi"
validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
validating dependency to public part "default" of DC "sap.com/tc/logging"
validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
validating dependency to public part "default" of DC "sap.com/com.sap.exception"
validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
validating dependency to public part "default" of DC "sap.com/caf/eu/gp/api"
validating dependency to public part "default" of DC "sap.com/caf/eu/gp/api/wd"
ERROR: Illegal dependency: Access list does not allow use of sap.com/caf/eu/gp/api for xyz.com/FamilyStatusChange(xyz.com_SC_XYZ_PORTAL_SP11_1) with respect to public part default.
Build failed with errors.
Also when I try to add used DCs (public part "default" of DC "sap.com/caf/eu/gp/api" and public part "default" of DC "sap.com/caf/eu/gp/api/wd") to this application, I get the illegal dependency error.
Please let me know if there is any settings / access that need to be in place so that this application runs fine. Also let me know the Jar files that need to be added to make this app work.
Regards,
VibhaHi Romain,
I am still working on the issue. But here are my findings. I am stuck up with Basis team to deploy the missing Jar files.
I had created a GP webdynpro application in EP7 SP6. When we moved to SP11, I copied the same application from SP6 track to SP11 track. Then I got the error upon deployment. Now the catch here is the way GP related Interfaces and classes are used in SP7 and above.
The changes can be summarized as follows:
1. You need to reference to DC caf/eu/gp/api but instead of using the Public Part
default you need to use Public Part external
2. All published Interfaces now start with the prefix IGP
3. All published Classes now start with the prefix GP
Please go through the document "Implementing a Web Dynpro Callable Object which Implements the GP Interface" on SDN.
For illegal dependency issue, if the DC has already been added then you get this error. If required, remove the used DC and add it again.
Also ensure that the DCs that you are adding as Used DC in your application are deployed on the J2EE engine.If not deploy them through SDM.
My development configuration contains the following DCs:
- caf/eu/gp/api(PP - External)
- caf/eu/gp/api/wd(PP - GPWebDynproCO)
- com.sap.exception
- com.sap.security.api.sda
- tc/logging
Hope this solves your issue.
Regards,
Vibha Singhal
Message was edited by:
Armin Reichert -
Error While Deploying A Web Service
Hello All,
I am trying to deploy a Web Service however when I am doing so I keeping getting this exception any idea what could be wrong:
5056bf5661#SAPEngine_Application_Thread[impl:3]_130##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation update with application sap.com/reg~equip.#2#update#sap.com/reg~equip#
#1.5#005056BF5661006E000009A100000F5000043492CC869AC9#1183705008343#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#93423####0d48d6a02b8e11dcba6b005056bf5661#SAPEngine_Application_Thread[impl:3]_130##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation update with application sap.com/reg~equip.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3155)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:667)
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:309)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:194)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
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.exceptions.ServerDeploymentException: Cannot deploy application sap.com/reg~equip.
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:328)
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)
... 13 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/reg~equip. . Additional info: none
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:274)
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:319)
... 15 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The reason is: Error occurred, trying to generate web services deployment files for application sap.com/reg~equip. . The error refers to application: none, jar: {2}, web service: {3}.
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, parsing com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application sap.com/reg~equip, web service EmmServiceWS, location message: type: jar file, location: D:\\usr\\sap\\ERP\\DVEBMGS10\\j2ee\\cluster\\server0\\.\\temp\\deploy\\work\\deploying\\reader1183705000828\\sap.com~reg~equip~ejbmodule.jar . . Additional info: {1}
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to parse source type: zip entry, zip file location: D:\\usr\\sap\\ERP\\DVEBMGS10\\j2ee\\cluster\\server0\\.\\temp\\deploy\\work\\deploying\\reader1183705000828\\sap.com~reg~equip~ejbmodule.jar, entry: com/sap/reg/equip/appsrv/emmservice/EmmServiceWSVi.videf . Additional info: {1}
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:925)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:817)
... 26 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
... 27 moreHi,
Could not diagonise from this stack trace alone. But what doubt is that there is something wrong with cardinality in your web service. Otherwise something may have gone wrong like you mishandling a list or some mismatch like that.
Regards,
Srinivasan Subbiah -
Error while deploying entity javabean (CMP)
Hello,
I have a problem while I'm trying to deploy an entity javabean (with container managed persistance). I'm using JDeveloper 3.2.3 and 8.1.7.2 database.
Here is the error I get:
*** Executing deployment profile E:\Xaris\JDeveloper\General\EJBs\EmpCmp\EmpCmp.prf ***
*** Generating archive file E:\Xaris\JDeveloper\General\EJBs\EmpCmp\empcmp.jar ***
Compiling the project...done
Validating the profile...done
Initializing deployment...done
Scanning project files...done
Generating classpath dependencies...done
Generating archive entries table...done
*** Archive generation completed ***
*** Deploying the EJB to 8i JVM ***
EJB deployment argument list:
"E:\Program Files\Oracle\JDeveloper 3.2.3\java1.2\jre\bin\javaw"
"-DPATH=E:\Program Files\Oracle\JDeveloper 3.2.3\bin;E:\Program Files\Oracle\JDeveloper 3.2.3\java1.2\bin"
-classpath
"E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\aurora_client.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\lib\javax-ssl-1_2.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\jasper.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\vbjorb.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\vbjapp.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\vbjtools.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\vbj30ssl.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\aurora.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\sqlj\lib\translator.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\sqlj\lib\runtime.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\aurora\lib\mts.jar;E:\Xaris\JDeveloper\General\EJBs\EmpCmp\classes;E:\Program Files\Oracle\JDeveloper 3.2.3\lib\jdev-rt.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\jdbc\lib\oracle8.1.7\classes12.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\lib\connectionmanager.zip;E:\Program Files\Oracle\JDeveloper 3.2.3\lib\javax_ejb.zip;C:\Program Fil
s\JavaSoft\JRE\1.3.1\lib\i18n.jar;C:\Program Files\JavaSoft\JRE\1.3.1\lib\jaws.jar;C:\Program Files\JavaSoft\JRE\1.3.1\lib\rt.jar;C:\Program Files\JavaSoft\JRE\1.3.1\lib\sunrsasign.jar;E:\Program Files\Oracle\JDeveloper 3.2.3\lib\xmlparserv2.jar"
oracle.aurora.ejb.deployment.GenerateEjb
-u
harris
-p
harris
-s
sess_iiop://192.168.10.218:2481:WORK
-keep
-temp
TEMP
-descriptor
"E:\Xaris\JDeveloper\General\EJBs\EmpCmp\EmpCmp.xml"
-oracledescriptor
E:\Xaris\JDeveloper\General\EJBs\EmpCmp\EmpCmp_oracle.xml
-generated
"E:\Xaris\JDeveloper\General\EJBs\EmpCmp\EmpCmpClient.jar"
"E:\Xaris\JDeveloper\General\EJBs\EmpCmp\empcmp.jar"
Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Processing container managed persistence bean...done
Generating Comm Stubs.............................................done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...done
Generating EJBHome and EJBObject on the server...
An exception occurred during code generation: null
*** Errors occurred while deploying the EJB to 8i JVM ***
*** Deployment completed ***
Can anyone help me understand where is the error?
Thanks in advance,
CharalamposVolker,
Let me try again (in the hope that this time you will understand
what I am saying).
"database embedded EJB container" and "EJB" are not the same thing.We are a little bit further in technology, so that we have no single Engine, single
Processor Systems any more.
Distribution over many computers (RAC) is done by Visigenic ORB (9i) or OC4J.
EJB Framework is for distribution of Business Logic or in your words of
Database Logic.
Oracle is abandoning the "database embedded EJB container".
Oracle is not abandoning EJB.Please step into technology and make a comparison of Java Stored
Procedures, look at the native compiler ncomp and try to figure out which
classes are important for Server Side software development.
Oracle recommends using OC4J as the EJB container.
Here is a recent post (from an Oracle employee and regular forum
participant) from the J2EE forum:
High number of http 404 errors from webcache
Here is a quote from that post:
starting from Oracle9i Release 2 Database EJBs are going to be desupported from database. EJBs can only be deployed in OC4J component of Oracle9iASAs far as I can see, it makes no sense to do that step.
I beleave, that this decision is very very short lived.
Unfortunately, my German is very poor -- I can only try to explainYou are right, I am a German.
things to you in English. Hopefully (if you are still not comprehending
what I am saying), some kind soul (who must have a better levelAmerican english is for everyone.
of reading and comprehension in English than you) will explain it
to you in your native tongue.I have understood, what you said!
So let me summarize:
Oracle is abandoning the database embedded EJB container.I don't beleave that! Is that OK!
By the way, something may have gotten lost in the translation, or
this may be just another example of your comprehension problem, but
what is the connection between the TowerJ JVM and the Oracle databasencomp has the same architecture as TowerJ native Compiler.
Ok?
embedded EJB container?
The very best of luck to you,Thanks a lot!
Avi +Volker! -
Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4
Hi,
I am migrating EJB2.x code from JBoss to Weblogic 10.3.4. As a first step, I am tyring to deploy just Entity beans. I get following error when deploying to server.
'weblogic.application.ModuleException: Exception preparing module: EJBModule(myEJB.jar)
Unable to deploy EJB: CollMetaData from myEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
There are 1 nested errors:
java.lang.NullPointerException
at weblogic.ejb.container.cmp.rdbms.finders.EjbqlFinder.setMethods(EjbqlFinder.java:288)
at weblogic.ejb.container.cmp.rdbms.Deployer.processFinders(Deployer.java:744)
at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:446)
at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:506)
at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:455)
at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:118)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1214)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can someone help me fixing the issue?
I changed schema locations of descriptor files as suggested at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13706/overview.htm#i1074199 (see the third category for '*Enterprise Bean 2.1*' in the listing Table 1-1). Alternatively, you may see the schema locations for EJB2.0 directly at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13719/dd_reference.htm#EJBPG481JRE version in JBoss is 1.6.0_16. JVM in web logic is pointing to jrockit_160_22_D1.1.1-3 which is come in the package. It doesn't seem to be related to JVM version mismatch.
I think it is an issue with definitions in weblogic-cmp-rdbms-jar.xml file. How should be the definition of entity-descriptor appear for entity bean which has finder methods in ejb-jar.xml?
Please see the snippets from corresponding descriptor files below.
ejb-jar.xml
=========
<entity>
<display-name>EmpBean</display-name>
<ejb-name>EmpBean</ejb-name>
<local-home>LocalEmpBeanHome</local-home>
<local>LocalEmpBean</local>
<ejb-class>EmpBeanBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>EmpBean</abstract-schema-name>
<cmp-field>
<field-name>firstName</field-name>
</cmp-field>
<cmp-field>
<field-name>lastName</field-name>
</cmp-field>
<cmp-field>
<field-name>phone</field-name>
</cmp-field>
<cmp-field>
<field-name>address</field-name>
</cmp-field>
<primkey-field>lastName</primkey-field>
<query>
<query-method>
<method-name>findByPrimaryKey</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql>SELECT Object(o) FROM EmpBean o WHERE o.lastName= ?1</ejb-ql>
</query>
</entity>
weblogic-jar.xml
============
<weblogic-enterprise-bean>
<ejb-name>EmpBean</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>20</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>meta-inf/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
<finders-load-bean>true</finders-load-bean>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/EmpBean</local-jndi-name>
</weblogic-enterprise-bean>
weblogic-cmp-rdbms-jar.xml
====================
<weblogic-rdbms-bean>
<ejb-name>EmpBean</ejb-name>
<data-source-jndi-name>mysqlDS</data-source-jndi-name>
<table-map>
<table-name>emp</table-name>
<field-map>
<cmp-field>firstName</cmp-field>
<dbms-column>first_namel</dbms-column>
</field-map>
<field-map>
<cmp-field>lastName</cmp-field>
<dbms-column>last_name</dbms-column>
</field-map>
<field-map>
<cmp-field>phone</cmp-field>
<dbms-column>phone</dbms-column>
</field-map>
<field-map>
<cmp-field>address</cmp-field>
<dbms-column>address</dbms-column>
</field-map>
</table-map>
<weblogic-rdbms-bean>
Please ignore any typos that you may notice in above sample descriptions (because I just typed it here changing original names).
When I try to deploy the application, I get error message as posted in my first post above in this thread. Please correct me if I am making any erros in descriptor files.
Edited by: 839281 on Feb 25, 2011 10:55 AM
Edited by: venkatp on Mar 1, 2011 9:31 AM -
Error after deploying backup PAR
Hello guys,
we updated a PAR-File in our Portal. The PAR-File that was changed is com.sap.portal.appintegrator.sap.par. And now iViews with Codelink
com.sap.portal.appintegrator.sap.bwc.BSP show Message:
"SAPApplication Backward Compatibility Component".
After reverting back to old Par-File (was backed up local before
changing) and reloading it (even after restarting the whole server) the
Problem still persists.
When executing a iView of that type following errors are located in log-File:
Time , Category , Date , Message , Severity , Location , Application , User
11:36:23:272 , /System/Server , 11/21/2006 , Failed to get application
IPropertyContentProvider:
pcd:com.sap.portal.system/applications/com.sap.portal.appintegrator.sap/components/BSP
, Error , com.sap.portal.ivs.semantic.iViewService , sap.com/irj , horn
11:36:23:270 , /System/Server , 11/21/2006 , Failed to get application
IPropertyContentProvider: com.sap.portal.appintegrator.sap.BSP , Error ,com.sap.portal.ivs.semantic.iViewService , sap.com/irj , horn
I further saw, that portalapp.xml in pcd (browse over pcd-browser) after deploying, only has 409 bytes.
"portalapp.xml view, download 409 Tue Nov 21 17:54:08 CET 2006"
The content of this file is:
" <?xml version="1.0" encoding="iso-8859-1" ?>
- <application>
- <!-- THIS FILE IS A COPY OF THE ORIGINAL VERSION STORED IN THE PCD. PLEASE DO NOT CHANGE IT!
-->
- <application-config>
<property name="ClassLoadingPolicy" value="5.0" />
<property name="DeploymentPolicy" value="5.0" />
<property name="AuthenticationPolicy" value="5.0" />
</application-config>
<components />
<services />
</application>"
So there must be an error when I deploy the backup-PAR to server. But after deploying I get the message:
"Messages:
INFO: Detected Portal Archive File: com.sap.portal.appintegrator.sap.parINFO: Application successfully stored in the PCD
Messages from Server ID 7805250
INFO: com.sap.portal.appintegrator.sap has been successfully updated. "
additionally it seems that services that are defined in portalapp.xml aren't deployed, if I redeploy the backup of com.sap.portal.appintegrator.sap.par. The names of this services are IViewURLGenerator and Transaction_Configuration under com.sap.portal.appintegrator.sap in service tree.
The portalapp.xml component aren't attached to the corresponding security zones, too. For example in Portal Content Browser I see:
ara:/security/sap.com/NetWeaver.Portal/low_safety/com.sap.portal.appintegrator.sap/components/BSP
If I select Where-Used on this Element, there is the message:
"No component is bound to this security zone"
and
"No service is bound to this security zone"
I have no further idea how I can deploy this par-File that it works correctly. Hope you can help me!
Thanks in advance.
Best regards,
DanielHi,
now I searched the directories again and I found under ROOT/WEB-INF/deployment/pcd
three files with name "com.sap.portal.appintegrator.sap.par" but three file-extensions:
-log
-err
-bak
In log-File there is shown an error while deploying...perhaps that helps analysing.
Here I list the content of the log-File:
2006-11-21_10-22-16
Application upload failed: com.sap.portal.appintegrator.sap.par
java.lang.InternalError: jzentry == 0,
jzfile = 4333072224,
total = 94,
name = /usr/sap/TEP/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.sap.portal.appintegrator.sap.par,
i = 1,
message = invalid LOC header (bad signature)
at java.util.zip.ZipFile$2.nextElement(ZipFile.java:322)
at com.sapportals.portal.prt.deployment.ArchiveIterator.iterate(ArchiveIterator.java:46)
at com.sapportals.portal.prt.deployment.UploadProcess.upload(UploadProcess.java:60)
at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:835)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
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:324)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Best regards,
Daniel -
EPMLCM-37009: Error parsing application artifact listing metadata. ....
This is a freshly installed 11.1.2.2
Foundation services (including CalcMgr and EPMA), RA (framework, FR and WA), Planning and Essbase are installed
Only Foundation services (including CalcMgr and EPMA), RA (framework, FR and WA) are configured.
OHS is the web server.
Everything seems fine except when I click "EPM Architect" in the SS console, I have got the error below.
EPMLCM-37009: Error parsing application artifact listing metadata. An Invalid listing or listing having empty tags
Also under workspace, when I attempted to open "Dimension Library" and "Application Library" the following error pops up.
;nested exception is:
HTTP transport error: javax.xml.soap.SOAPException:
javax.xml.soap.SOAPException: Message send failed:
Connection refused: Connect
Executed the diagnostic programme, got a red in almost anything related to EPMA.
Question. Do I need to configure any of the application (e.g. Ess, Planning, etc) together with EPMA to make it work?Seems like a EPMA is not configured properly. Can you open a status-60 bug, then attach the deployment report and Shared Services logs, especially the LCM log?
-
"Recycle IIS Application Pool" error while deploying solution using Visual Studio
Hi All,
I am getting below error while deploying solution from Visual Studio. I have verified the URL and its okay and site is also up and running and accessible.
Error 1 Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site:
http://portal/sites/site1/. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since
you created the project, update the Site URL property of the project.
Suggest some solution.
Thanks in advance.Hi,
Please do/Validate the below things..
1.Current logged in user is in Administrator group
of SharePoint server.
2.Current logged user has db_owner permission for Content
Database of the site you are trying to deploy .
http://www.sharemuch.com/2010/03/19/resolving-vs-2010-solution-deployment-issues-for-sharepoint-2010-projects/
and also
Do a IIS reset
Check if IIS is resetting.
If it is not, then disable UAC from control panel and IIS reset will work.
Go to Central Administration site
Navigate to the Manage Web Applications page
Click on the web application that hosts the site you are trying to deploy to
Click the User Policy ribbon item.
Add your windows account to the list of users with the Full Control permission.
Don't forget to mark it as an Answer if it resolves your issue and Vote Me as helpful if it useful.
Mahesh -
Error while deploying composite in EM console
Error while deploying jar files directly from EM console.Please find the below error message and let us know how to deploy the composite.
Deploying on partition "mooa_businessservices" of "/Farm_SOADomain/SOADomain/SOAServer" ...
Deploying on "/Farm_SOADomain/SOADomain/SOAServer" failed!
Error during deployment: Deployment Failed: Unable to find a WSDL that has a definition for service {http://xmlns.oracle.com/xxxxxxx}xxxxxxx and port xxxxxxx. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace service name and port name. In addition check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally validate the HTTP proxy settings for the server..Thanks for the input.
We Tried to set ListenAddress to hostname,ipaddress and localhost, still composites are not accessible with localhost for any of the three options. It seems like some network or weblogic configuration which is blocking local host 9711 port but same is accessible with hostname and ip address.
Do you have any idea on this ?
1. Host Name hostname.com
Managed Server HelloSOAServer Set the "Listen Address" to the hostname hostname.com
a. http://hostname.com:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Accessible) - Working Fine
b. http://10.10.x.x:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Accessible) - Working Fine
c. http://localhost:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://localhost:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL", caused by: java.net.ConnectException. : java.net.ConnectException: Connection refused
d. http://hostname.com:8011/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
Error 500--Internal Server Error
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '9711'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:327)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:419)
at weblogic.net.http.HttpClient.New(HttpClient.java:246)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:176)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:361)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
Pasted from <http://hostname.com:8011/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL>
2. IP Address 10.10.x.x
Managed Server HelloSOAServer Set the "Listen Address" to the ipaddress 10.10.x.x
a. http://hostname.com:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Accessible) - Working Fine
b. http://10.10.x.x:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Accessible) - Working Fine
c. http://localhost:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://localhost:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL", caused by: java.net.ConnectException. : java.net.ConnectException: Connection refused
3. Local Address localhost
Managed Server HelloSOAServer Set the "Listen Address" to the localhost 127.0.0.1
a. http://hostname.com:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
b. http://10.10.x.x:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
c. http://localhost:9711/soa-infra/services/default/HelloWorld/helloworldprocess_client_ep?WSDL (Not Accessible)
Unable to retrieve composite details.
The composite HelloWorld (1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this -
Error while deploying EJB 1.1 on Weblogic 10.3.0.0
I am trying to deploy an EJB (1.1) jar which is succesfully running on JBoss5.0 on WebLogic 10.3.0.0; I am getting following Error while deploying the jar on weblogic;
Exception preparing module: EJBModule(ejb_RemoteServicesEjb) Unable to deploy EJB: RemoteServicesEjb.jar from RemoteServicesEjb.jar: There are 1 nested errors: weblogic.ejb.container.compliance.ComplianceException: In EJB com.package.ejbimpl.RemoteServicesEjb, the throws clause for ejbCreate method ejbCreate() contains exceptions that are NOT in the throws clause of the corresponding home interface method. at weblogic.ejb.container.compliance.HomeInterfaceChecker.checkCreateMethodsMatchBeanCreates(HomeInterfaceChecker.java:365) 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 weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:337) at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:286) at weblogic.ejb.container.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:952) at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:920) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:246) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:552) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:519) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:393) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:715) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:618) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1154) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Does anybody knows what must be going wrong?
Can't I deploy EJB 1.1 jar directly on Weblogic 10.3.0.0 or I need to change or configure something before doing it?Does the ejbCreate() method of the com.package.ejbimpl.RemoteServicesEjb class have an exception on it's throws clause that is not present on the ejbCreate() method of your home interface? If so, does the error go away if you add the exception to the home's ejbCreate() method? In general, you want checked exceptions in a throws clause to match between the interface declaration of the method and the implementation of the method on the bean class.
- Matt -
Error while deploying web service in Netweaver application
Hi,
In my group, two members working in the development of a WebDynpro based application. We have created a track and are using the same for development. For our application
the team member 1 created a Dc say DC1 for EJBS(both
entity and session) and another DC say DC2 for the application archieve 'ear'
and activated the two DCS. When another member of
the team is trying to create a webservice in the checked out DC, the
webservice was created successfully but while deploying the
application archive DC it gives an error (details furnished below).
Error:
:Caught exception during application deployment from SAP J2EE Engine's
deploy service:java.rmi.RemoteException: Cannot deploy
application asianpaints.com/pe_mgt_ear.. Reason: Webservices common
deployment exception! The reason is: Error occurred,
trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, trying to update web services
for application asianpaints.com/pe_mgt_ear.
WSDeploymentException: Webservices common deployment exception! The
reason is: Error occurred, trying to parse documentation
for web service NewPEProcessorService. .
So we created one more DC3(referring the entity beans of DC1) and
created the required session bean and webservice in that
DC. It got deployed successfully. Again when we are trying to create
new webservice it got created but the deployment got
aborted with the same error as mentioned above:
The detailed error description we got in both the cases is given below:
Mar 30, 2006 1:07:39 PM /userOut/deploy
(com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy
Thread,5,main]] INFO:
[005]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[/usr/sap/J2E/JC00/SDM/program/log/sdmcl20060330074205.log]/>
<!PATTERN[sdmcl20060330074205.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[ISO8859_1]/>
<!LOGHEADER[END]/>
Mar 30, 2006 1:12:07 PM Info: -
Starting deployment -
Mar 30, 2006 1:12:07 PM Info: Loading selected archives...
Mar 30, 2006 1:12:07 PM Info: Loading
archive '/usr/sap/J2E/JC00/SDM/program/temp/temp35515asianpaints.com~pe_mgt_ear.ear'
Mar 30, 2006 1:12:17 PM Info: Selected archives successfully loaded.
Mar 30, 2006 1:12:17 PM Info: Actions per selected component:
Mar 30, 2006 1:12:17 PM Info: Update: Selected development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
currently deployed development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
Mar 30, 2006 1:12:17 PM Info: The deployment prerequisites finished
without any errors. All items are correct.
Mar 30, 2006 1:12:17 PM Info: Saved current Engine state.
Mar 30, 2006 1:12:17 PM Info: Error handling strategy: OnErrorStop
Mar 30, 2006 1:12:17 PM Info: Update strategy: UpdateAllVersions
Mar 30, 2006 1:12:17 PM Info: Starting: Update: Selected development
component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
currently deployed development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
Mar 30, 2006 1:12:17 PM Info: SDA to be deployed:
/usr/sap/J2E/JC00/SDM/root/origin/asianpaints.com/pe_mgt_ear/J2E_HSSPNEW_D/20060330130420/temp35515asianpaints.com~pe_mgt_ear
.ear
Mar 30, 2006 1:12:17 PM Info: Software type of SDA: J2EE
Mar 30, 2006 1:12:17 PM Info: ***** Begin of SAP J2EE Engine
Deployment (J2EE Application) *****
Mar 30, 2006 1:15:07 PM Info: Begin of log messages of the target
system:
06/03/30 13:12:17 -
06/03/30 13:12:20 - Start updating EAR file...
06/03/30 13:12:20 - start-up mode is lazy
06/03/30 13:12:23 - EAR file updated successfully for 3161ms.
06/03/30 13:12:23 - Start updating...
06/03/30 13:12:24 - EAR file uploaded to server for 525ms.
06/03/30 13:15:07 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy
application asianpaints.com/pe_mgt_ear..
Reason: Webservices common deployment exception!
The reason is: Error occurred, trying to update web
services for application asianpaints.com/pe_mgt_ear. . Additional info:
none; nested exception is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException:
Webservices common deployment exception! The reason is: Error occurred,
trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
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:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.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:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
deployment exception! The reason is: Error occurred, trying to generate
web services deployment files for application
asianpaints.com/pe_mgt_ear. . The error refers to application: none,
jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to parse
documentation for web service NewPEProcessorService. .
Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:596)
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:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.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:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The
reason is: Error occurred, trying to update web services for
application asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
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:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.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:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
deployment exception! The reason is: Error occurred, trying to generate
web services deployment files for application
asianpaints.com/pe_mgt_ear. . The error refers to application: none,
jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to parse
documentation for web service NewPEProcessorService. .
Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
at
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:64)
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:324)
at java.io.ObjectStreamClass.invokeWriteReplace
(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0
(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields
(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData
(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject
(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0
(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject
(ObjectOutputStream.java:278)
at
com.sap.engine.services.rmi_p4.DispatchImpl.throwException
(DispatchImpl.java:135)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:296)
... 8 more
For detailed information see the log file of the
Deploy Service.
06/03/30 13:15:07 -
Mar 30, 2006 1:15:07 PM Info: End of log messages of the target
system.Mar 30, 2006 1:15:07 PM Info: ***** End of SAP J2EE Engine
Deployment
(J2EE Application) *****
Mar 30, 2006 1:15:07 PM Error: Aborted: development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot deploy application
asianpaints.com/pe_mgt_ear..
Reason: Webservices common deployment exception! The reason is: Error
occurred, trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to update
web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
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:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run
(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160)
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The
reason is: Error occurred, trying to generate web services deployment
files for application asianpaints.com/pe_mgt_ear. . The
error refers to application: none, jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, trying to parse documentation
for web service NewPEProcessorService. . Additional
info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
(message ID:
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Mar 30, 2006 1:15:17 PM Info: J2EE Engine is in same state
(online/offline) as it has been before this deployment process.
Mar 30, 2006 1:15:17 PM Error: -
At least one of the Deployments
failed -
Deployment failure happens only when the DC contains a web service; else, it goes through properly.
Can anyone of you indicate where we are going wrong and what should be done to resolve this issue?
Thanks a lot in advance.
Regards,
RaviHi,
You can go to the Visual Administrator -> <SID> -> Server -> Services -> Deploy -> Runtime tab -> option Container at the bottom and see if everything is correct and running in the webservices_container.
If something necessary to the deployment is not started you can select it and click in start.
I hope it helps.
Thanks,
Anderson
Maybe you are looking for
-
Current date in date range formula
I have a report where I only want to see records if the current date is between 2 dates on the report ( {@ Eff From} and {@Eff To} ) I will try to show example below: Part A - Eff From 06-04-2007 Eff To 12-31-2020 Part B - Eff From 06-04-2007 Eff
-
I have installed Leopard 10.5.1 and apart from some annoying Keychain issues I seem to have lost my entire iTunes library. Any ideas?
-
I am working with tracking problem. I am somewhat new to VC++. I have to take several data from the position sensor and read in the PLC and feed the data to the motor to run. That is fine. But the problem arises when I receive the data from position
-
Error when installing latest GM45 integrated graphics drivers
I have a T400 64-bit Windows 7 machine with switchable graphics, model CTO 2764 . Current integrated graphic driver version is 8.15.10.1892. I'm trying to update to latest driver version 8.15.10.1968, released 11/13/2009. Following the installati
-
Hi Experts, I have a multi-threaded app that connects to a RAC DB using OCI. Flow: 1.) Get an expired resource 2.) Assigned it to a user Each thread executes the following sequence of queries: 1.) SELECT id, data FROM table_name WHERE date_expiry = :