Web service deployment issue

On my WinXP laptop using Jdeveloper10g I can wrap a PL/SQL stored proc (10g database) as a web service - test it and deploy it to Oracle 10g AS also running on my laptop.
However, if I do the same thing using the same version of JDeveloper, database and Application server on a Win2003 server (the service tests ok within embedded OC4J container) it returns the error below when I try to deploy it. (curiously enough I can deploy the service back onto my laptops App server which tells me the service and it's deployment file is ok).
any clues?
Here is the deployment error...
Target platform is Oracle Application Server 10g (Local10gAS).
Wrote WAR file to C:\JDev_10g\jdev\mywork\POC\Project\WebServices.war
Wrote EAR file to C:\JDev_10g\jdev\mywork\POC\Project\POC-Project-WS.ear
Invoking DCM servlet client...
C:\j2sdk1.4.2_08\bin\javaw.exe -Djava.protocol.handler.pkgs=HTTPClient -jar C:\JDev_10g\jdev\lib\oc4j_remote_deploy.jar http://127.0.0.1:1810/Oc4jDcmServletAPI/ ias_admin **** redeploy C:\OraHome_1 C:\JDev_10g\jdev\mywork\POC\Project\POC-Project-WS.ear POC-Project-WS C:\OraHome_1\j2ee\home
Initializing log
Servlet interface for OC4J DCM commands
Command timeout defined at 600 seconds
Executing DCM command...
Executing command redeploy C:\OraHome_1 C:\JDev_10g\jdev\mywork\POC\Project\POC-Project-WS.ear POC-Project-WS C:\OraHome_1\j2ee\home
Command = REDEPLOY
Reading application's ear file
Ear file was successfully read
Opening connection to Oc4jDcmServlet
Setting userName to ias_admin
Sending command to DCM servlet
HTTP response code = 200, HTTP response msg = OK
Command was successfully sent to Oc4jDcmServlet
Receiving session id from servlet to check command status
Session id = 0a096002712cef0355c6b42483e83cd8dc3454d821f
Please, wait for command to finish...
Checking command status...
Setting userName to ias_admin
Setting Cookie to JSESSIONID=0a096002712cef0355c6b42483e83cd8dc3454d821f
Checking command status
HTTP response code = 200, HTTP response msg = OK
Command has finished
Receiving command exit value
Receiving command output
**** No output was received from command
Closing connection to Oc4jDcmServlet
#### DCM command did not complete successfully (-1)
#### HTTP return code was -1
Exit status of DCM servlet client: -1
Elapsed time for deployment: 11 seconds
#### Deployment incomplete. #### 01-Jul-2005 14:38:48

Make sure the webservice endpoint is the correct one. You have to change this one if you deploy the webservice to another machine.

Similar Messages

Web Service: Deploy: Issues

Hi, I am trying out the basic tutorial 'Developing, Deploying and Managing Web Services Using JDeveloper and Oracle Application Server' located at http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm#t4
I am getting a weird error when I try to deploy the WebService.Deploy to oc4jconn.
This web service does not use any db connection. myjdev is configured to jdev and I can run other applications connecting to mysql. Any pointers will be great I am stuck with this error.
Here is the full error stack:
---- Deployment started. ---- Oct 7, 2006 11:08:50 PM
Target platform is Standalone OC4J 10g 10.1.3 (oc4jconn).
Wrote WAR file to D:\jdevhome\mywork\TopDownContractDevelopment\GetDates\deploy\WebServices.war
Wrote EAR file to D:\jdevhome\mywork\TopDownContractDevelopment\GetDates\deploy\TopDownContractDevelopment-GetDates-WS.ear
Uploading file TopDownContractDevelopment-GetDates-WS.ear ...
Application Deployer for TopDownContractDevelopment-GetDates-WS STARTS.
Copy the archive to D:\Jdev10_1_3\j2ee\home\applications\TopDownContractDevelopment-GetDates-WS.ear
Initialize D:\Jdev10_1_3\j2ee\home\applications\TopDownContractDevelopment-GetDates-WS.ear begins...
Unpacking TopDownContractDevelopment-GetDates-WS.ear
Done unpacking TopDownContractDevelopment-GetDates-WS.ear
Unpacking WebServices.war
Done unpacking WebServices.war
Initialize D:\Jdev10_1_3\j2ee\home\applications\TopDownContractDevelopment-GetDates-WS.ear ends...
Starting application : TopDownContractDevelopment-GetDates-WS
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Warning. Unable to set up connection factory to location TopDownContractDevelopment-GetDates-WS for a resource adapter in {1}
application : TopDownContractDevelopment-GetDates-WS is in failed state
Operation failed with error:
Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
Deployment failed
Elapsed time for deployment: 3 seconds
#### Deployment incomplete. #### Oct 7, 2006 11:08:53 PM

I had the same problem and found the issue. This post is to help anyone else that runs across it.
If you get to this point you probably did the following:
Set up a deployable proxy DC.
Added all the entries to the various xml files.
Had a problem with deployment of the ear due to the reference type being set to 'hard'.
Changed the reference type to 'weak' to get the deployment to work.
The Reference type really needs to be set to 'hard'.
The issue is that the Reference target name needs to be set to the deployable proxy name. For example, if the proxy DC is named 'testprxy' then the Reference target needs to have this name. If you are using NWDI tracks (not a local DC), then the name will include the SC name (ex. abc~testprxy where abc is the SC name).
Also, the provider name should be the same as the vendor name used for the DC.
If the proxy DC full path name is: com.myco.abc.proxies.TestProxy -
Summary of names and paths to use for the various entries:
In ejb-j2ee-engine.xml - Server component JNDI name
/wsclients/proxies/myco.com/abc~testprxy/com.myco.abc.proxies.TestProxy
In application-j2ee-engine.xml - Reference target
abc~testprxy (or just testprxy if it is a local DC)
Use any name for the Application local JNDI name in the ejb-j2ee-engine.xml. But this is the only place in the xml files where this name is used.
If you use MyTestProxy as the Application local JNDI name, then the reference in code for the context lookup would be 'java:comp/env/MyTestProxy'.
Just remember local DCs don't have an SC name to include (which was 'abc~' in the examples above).
When in doubt about the JNDI name (full path), use Visual Administrator to look at the JNDI registry (start at wsclients which is at the bottom of the list).
Hope this helps.
-Cindy

Web services deployment issue.

Hello,
I have created a new weblogic domain using wlst, and all the services and applications appear to have deployed correctly. However when testing any of the web services they do not work at all, going to the test pages or wsdl gives a 404 error. Under the monitoring tab only 5 servlets are listed, the equivalent deployment on an old non-wlst domain lists 8 servlets.
Can anybody advise why 3 of the servlets have not been automatically created, no errors are in the logs. The missing servlets are ClasspathServlet, GetIORServlet and WebServiceServlet.
Thanks

I have finally managed to fix the problem, I'll post this solution in case any one else has the same problem and comes to this page.
Our scripts set a few default properties for server mbeans one of which is defaultInternalServletsDisabled = 1, removing this and recreating the domain meant that all the necessary servlets were created and our web services worked fine.

Jdeveloper WS proxy error while invoking web service deployed on weblogic

Hello experts, can you please help me. I have web service deployed on weblogic server.
I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
java.lang.SecurityException: keyStoreFilename is either null or empty string
     at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
     at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
     at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
     at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
Process exited with exit code 0.
Here is my client class :
public static void main(String[] args) {
try {
contactWSService = new ContactWSService();
ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
// QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
System.out.println("Inside the client class");
} catch (Exception ex) {
ex.printStackTrace();
Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
Appreciate your quick response.
thanks a lot
jyothi

Hello experts, can you please help me. I have web service deployed on weblogic server.
I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
java.lang.SecurityException: keyStoreFilename is either null or empty string
     at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
     at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
     at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
     at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
Process exited with exit code 0.
Here is my client class :
public static void main(String[] args) {
try {
contactWSService = new ContactWSService();
ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
// QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
System.out.println("Inside the client class");
} catch (Exception ex) {
ex.printStackTrace();
Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
Appreciate your quick response.
thanks a lot
jyothi

External web services deployment

Hi,
I am facing a situation of web services deployment. I am using Jdeveloper 10g and oracle bpel process manager 10.1.3.1.0. I am not able to deploy web services. The following are the steps that I followed to consume that web service called web service called WeatherByCity from xmethods.net.
Create new Application---> create new empty project( I named it 'projectgt') ----> new 'java web service from wsdl' from wsdl document url (http://ws.strikeiron.com/InnerGears/WeatherByCity2?WSDL ------------->
--> In the default mapping options for Package Name I put 'projectgt' and root package for generated types I put 'projectgt.types'. All the other options are default. When I right click Webservices.deploy under resources and deploy to the application server, it says failed to deploy with the following message.
---- Deployment started. ---- Apr 21, 2006 5:00:07 AM
Target platform is Standalone OC4J 10g 10.1.3 (AppServerConnection1).
Wrote WAR file to D:\Application24\Projectgt\deploy\WebServices.war
Wrote EAR file to D:\Application24\Projectgt\deploy\Application24-Projectgt-WS.ear
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Uploading file Application24-Projectgt-WS.ear ...
Application Deployer for Application24-Projectgt-WS STARTS.
Copy the archive to D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear
Initialize D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear begins...
Unpacking Application24-Projectgt-WS.ear
Done unpacking Application24-Projectgt-WS.ear
Unpacking WebServices.war
Done unpacking WebServices.war
Initialize D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS.ear ends...
Starting application : Application24-Projectgt-WS
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Initializing EJB sessions
Committing ClassLoader(s)
Initialize WebServices begins...
Initialize WebServices ends...
Started application : Application24-Projectgt-WS
Binding web application(s) to site default-web-site begins...
Binding WebServices web-module for application Application24-Projectgt-WS to site default-web-site under context root Application24-Projectgt-context-root
Operation failed with error:
Error compiling :D:\product\10.1.3.1\OraBPEL_1\bpel\system\appserver\oc4j\j2ee\home\applications\Application24-Projectgt-WS\WebServices: Error instantiating compiler: Web service artifact generation failed:java.lang.NoClassDefFoundError: projectgt/types/com/strikeiron/ws/SubscriptionInfo
Deployment failed
Elapsed time for deployment: 26 seconds
#### Deployment incomplete. #### Apr 21, 2006 5:00:32 AM
I will be grateful for any response on this issue.
Thankyou,
Sagar

As a matter of fact, I receiving a similar error for all other web services. Please let me know the error in my method of deployment

Web Service Deployment Exception

Hi All,
I have created a Stateless session bean in which i am accessing JPA entities.
In my session bean I have two methodes and i exposed those methodes as web services. I deployed this ejb project into server and search for my web service in Web Service Navigator. I didn't find my web service. Then I observer server logs. It is throwing a Web Service Deployment exception.
Code:
@WebMethod(operationName="readChannel", exclude=false)
     public ReadChannelResMsg readChannel(@WebParam(name="readChannelReqMsg")
     ReadChannelReqMsg readChannelReqMsg) {
          ReadChannelResMsg readChannelResMsg=new ReadChannelResMsg();
          readChannelResMsg.setChannel(channelDao.findById(readChannelReqMsg.getChannelId()));
          return readChannelResMsg;
Exception:
[ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 3324150:Exception occured during web services deployment. Unable to generate serialization framework for web service ProgramPlanWS, application hcl.com/longterm_plan_ear.
-> class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20 [email protected] alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20 [email protected] alive
server ID 3324150:com.sap.engine.services.deploy.container.DeploymentException:
Why this exception is coming and how can i resolve this issue?
Thanks
Sampath G

Hi,
the initial exception suggest
After an upgrade from SAP NetWeaver release 2004 to SAP NetWeaver release 7.0, according to the new SAP security policy, the J2EE Engine administrator user may be prompted to change his or her password. The password is changed in the User Management Engine (UME).
According to SAP security policy, the J2EE Engine administrator password must be changed every 90 days. The password is changed in the UME.
However, SDM reads the J2EE Engine administrator password not from the UME, but from the secure storage instead. The J2EE Engine administrator password is not changed in the secure storage. For more information, see SAP Note 870445.
and the possible Solution could be
Change the J2EE Engine administrator password in the secure storage
Regards
Manohar

Question concerning Web Service Deployment

I have a question on web service deployment as it pertains to multi-client SAP systems.
I created and deployed a web service in the client that is used for the development of client-independent objects. There are no issues when calling the web service following deployment.
I am trying to use the same web service on the same SAP system, but on a different client. What is the proper way for accomplishing this? As of right now, the only way I've been able to do this is to open up the desired client and deploy the service again. I tried to take a transport and copy it to the other client using SCC1, but it failed since all the objects referred to client-independent objects.
Below is the URL of the WSDL that was generated via SOAMANAGER.
http://svr-sap05-dev.xxx.com:8010/sap/bc/srt/wsdl/bndg_DF2B9EDC2EA40CF1A9B7001CC4459012/wsdl11/allinone/ws_policy/document?sap-client=120
Client 120 is the client used for development and is where the web service was created and deployed. I would like to use the same web service, but in a different client.
I tried in changing the logon parameters of the web service using SICF, but the invocation failed. It only works if the client mentioned in the logon data matches the client specified in the URL.
I am assuming that SAP builds the namespace of the web service using the client specified in the above URL. If this is the case, then I will have no choice but to deploy this service manually in the other client.
Is something wrong being done or do I have to do the same deployment in the other client?
Regards,
Vince Castello

In Netweaver 7.01 (with SOAMANAGER) you can no longer deploy webservices via STMS.
You have to login in each client and create endpoints in each one.
It's a pain, but SAP says it's too risky to implement the solution via STMS or something like that.
There is a SAP note about this.

Rt web services deployment failed

I have a sbrio 9612 that I setup with an executable and web services. I can get it to run great. I then took an image of that one (using RAD) and deployed it to another sbrio 9612. The web services don't work. I then tried to deploy webservices the second sbrio with my project, and I came up with the error in the attached picture: Web Services Deployment Failed. The NI Application Web Server is still loading.
All I can find about that is issues when deploying to a laptop with a wifi card, but nothing about that with a RT unit.
Any thoughts?
Thanks,
Eric.
Attachments:
error.jpg ‏83 KB

I have redeployed the firmware several times and it still doesn't work. It works on the original unit I took the image from, but not on the unit I'm deploying the image to. Using max is not an option because these are basically in an OEM environment and if I distribute an image to a customer they will not have national instruments installed.
Besides, that defeats the purpose of taking an image, if it works correctly in one place, you should be able to take an image of that and deploy it on another unit.

Error invoking web service deployed in SOA Suite

I have implemented a stateful web service in Jdeveloper 10.1.3.2.
I can test succesfully an operation of the web service from the embedeed oc4j of jdeveloper, but i can not succes when i try do the same from the application server control of soa suite.
The response of the web service in the second case, is the xml of the request.I can not understand.
I implemented a web service proxy in jdeveloper that invokes the web service deployed in soa suite.When i run it, it gives me an exception like this:
unexpected element name: expected={http://orclproject/types/}doLoginResponseElement, actual={http://orclproject/types/}doLoginElement
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:231)
     at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:159)
     at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._deserialize_doLogin(OrclLoginWSSoapHttp_Stub.java:1022)
     at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._readFirstBodyElement(OrclLoginWSSoapHttp_Stub.java:891)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:333)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
     at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub.doLogin(OrclLoginWSSoapHttp_Stub.java:484)
     at orclproject.OrclLoginWSSoapHttpPortClient.doLogin(OrclLoginWSSoapHttpPortClient.java:65)
     at orclproject.OrclLoginWSSoapHttpPortClient.main(OrclLoginWSSoapHttpPortClient.java:28)
where doLogin is the operation of the web service.
any idea?
thanks in advance...

Hi,
almost 8 months passed since this post, but if still actual then look at BUG: Request XML returned as response when result too large thread. It may be the same problem with large data sets.
Regards,
Patrik

Problem generating stubs for Java EJB web service deployed in OAS

I created an EJB web service and I've successfully deployed it in my Oracle App Server. Some of the methods work fine but others produce the ff error:
org.apache.soap.SOAPException - java.lang.IllegalArgumentException: No Serializer found to serialize [classname] using encoding style [encoding]It seems that the objects specified as parameters in the web service methods exposed are the only ones that had stubs generated for them. Other objects I use, which are usually wrapped inside a Vector, did not have generated stubs.
Example:
public String loginUser(UserDTO userDTO) throws RemoteException, NamingException, SQLException;
public String addItems (Vector vecItems) throws RemoteException, NamingException, SQLException; // where vecItems is a collection of ItemDTO objects In this scenario, stubs were generated for the UserDTO class, but not for the ItemDTO class. In effect, calling the addItems method resulted to the exception I mentioned above.
I did a workaround wherein I declared a dummy method which accepted all the types of objects I needed as parameters so all the necessary stubs can be generated, but this fix doesn't feel like it's the proper solution to my problem.
If anyone can help me, it would be greatly appreciated. Thanks!

Crossposted:
Problem generating stubs for Java EJB web service deployed in OAS

BPM Studio call web service deployed by R12 Intergration Repository error

Hi, I encountered a problem when calling a web service deployed by R12 Intergration Repository (SOA Gateway) w/ username/password authentication.
It seems that the BPM Studio can not pass the security information to the web service. But using SoapUI it's quite easy to call the service with no error, just set the username and password, and set the password type to PasswordText.
Under the External Resources catalog, I've set fileds in the Security tab with "Plain" Username Token, "sysadmin" Username and "sysadmin" Password, then changed the Authentication Type to "Username Token Profile". Then create a participant named sysadmin, and use this participant to run the process, but it just can't work.
Anybody can help? My colleague also posted a topic here: processRemoteException when invoke webservice from Oracle E-Business Suite but nobody answered. It would be very appreciated if sb. can fix this.

I've encounter something similar to you're problem and it was resolved by manually creating the object using the web service constructor and inputting user credentials. If you manually instantiate your web service wrapper object and set a a security profile token, it may solve your problem. You can also pass in the web service endPoint URL, if you want.
Fuego.WebServices.UsernameTokenProfileSecurityPolicy
I'm not sure how to use UsernameTokenProfileSecurityPolicy, but try something like this:
Fuego.WebServices.UsernameTokenProfileSecurityPolicy policy = UsernameTokenProfileSecurityPolicy();
policy.username ="mark";
policy.password = "password";
tws = YourWebService();
response = tws.callWebServiceMethod();
I realize the security profile isn't tied anywhere to the web service, but try it anyway.
There is also some fields on the webservice, tws.setRequestHeader() that may allow you to set the username and password on the request, but this doesn't make sense to me. It shouldn't be that hard.
Edited by: Mark Peterson on Mar 19, 2010 9:14 AM
Edited by: Mark Peterson on Mar 19, 2010 9:20 AM

Web Service deployed with admin_client is not working

Hi,
I'm usung SOA Suite 10.1.3.1 and Eclipse WTP 3.2.2.
The thing is that I developed a Web Service with Eclipse using the plugin for generating web services. Then I exported my project to a .war file from eclipse as well.
For deploy my web service in oc4j, I tried from the oc4j console in Applications --> Deploy and Next-Next wizard and using the .war file generated by Eclipse. I got the application deployed and I can check that the wsdl is working in http://localhost:8888/Hello_Web2/services/Hello?wsdl
But the main problem is when I try to deploy using the admin_client command tool running the command: java -jar admin_client.jar deployer:oc4j:opmn://localhost/home oc4jadmin welcome1 -deploy -file d:\TEMP\Hello_Web.war -deploymentName Web5 -contextRoot "/". Everything seems right, I can see the application created in the console, but when I try to access to the web service using "http://localhost:8888/Hello_Web2/services/Hello?wsdl" I get and Http 404.
What is wrong with the command method?
Many thanks in Advance,
Alberto

Hi,
As the custom web part works well in other browsers, the issue may be related to the IE itself.
Have you tried the methods below?
Use compatibility mode to check whether it works.
Open IE->Tools->Compatibility View Settings
Add the site into Trusted sites to check whether it works.
Open the IE->Internet Options->Security->Trusted Sites->add the site into the zone
What’s more, you can also switch the Document mode to IE 10 or lower to check whether it works.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Error [TOPLINK-6007] while calling a web service deployed on external oc4j

hello everybody,
Actually, I'm working on a project using oracle soa suite.
I developped a web service that works fine when I deploy it using the embeded oc4j but when I deploy it on an external oc4j, I get the followed error:
Internal Server Error (Caught exception while handling request: Exception [TOPLINK-6007] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.QueryException Description de l'exception : Descripteur absent pour [class riad.commun.bean.rh.agents.Agents]. Interrogation : ReadObjectQuery(riad.commun.bean.rh.agents.Agents))
Can anyone help me? please it's urgent.........

Hello,
The error is stating there isn't a descriptor for the Agent class the app is trying to execute a query on. This could be due to improper mappings, but assuming Agent is mapped, is more likely due to a classloader issue. TopLink uses the classloader at login to initialize the descriptors and hash them on the Class objects. If the application uses a different classloader, descriptors will not be found for classes loaded from the new classloader. How are you obtaining sessions, and where is the session being used?
Best Regards,
Chris

Connection reset error while calling web service deployed on tomcat

Hello Friends,
I am trying to invoke a web service from web dynpro application. The web service is deployed on tomcat 5.5 server.
I am creating an adaptive web service model using wsdl file. The model gets created without any error.
But when application is deployed and run it is giving following exception:
java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:168)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
    ... 102 more
I tried to call the service from a simple java application. There the service works fine.
Also, in the web services navigator, if I specify the wsdl url for testing it gives the same error of "Connection reset".
I don't think this is a proxy server issue as the tomcat is within the local network.
Can someone please help me with this?
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 27, 2008 7:03 PM

Hi Sumit,
Thanks for the reply.
Here is the stack trace:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<host>:<port>/WebServicesTest/DummyWebService?wsdl' and service factory configuration 'null'
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
     at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
     at com.tcs.vis.Vishy.<init>(Vishy.java:73)
     at com.tcs.app.AppView.wdDoInit(AppView.java:101)
     at com.tcs.app.wdp.InternalAppView.wdDoInit(InternalAppView.java:143)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     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:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
     ... 45 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
     ... 49 more
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Connection reset -> java.net.SocketException: Connection reset
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
     ... 50 more
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at com.sap.engine.services.webservices.jaxm.soap.LimitedInputStream.read(LimitedInputStream.java:61)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:269)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:332)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:165)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:220)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
     ... 52 more
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 28, 2008 1:10 PM

P6 R8.1 Web Service installation issue on Linux

We are trying to install P6R8.1 web services on weblogic in linux. We have the following setup:
1. Oracle 11g standard database in CentOS-5.4 64-bit
2. P6R8.1/ Weblogic 10.3.3.4 installed on CentOS 5.4 64-bit (separate server).
We have installed as per the oracle installation guide without any warning/ failure. After deploying the .war file (p6ws.war), it also showing Active in Weblogic admin console. But while trying to access the application (http://localhost:7001/p6ws) we are getting error: 403 Forbidden.
We have tested the weblogic by deplyoing some sample .war file and it works fine
After examining, we have found that there is no index.jsp file in the root of the p6ws.war file and it is only 29 mb compare to primaveraweb.ear file which is 194 mb of our existing installation (P6V7 with similar environment).
Is our .war file is not properly generated or we are missing some steps? Or there is any other issue?
Any help will be highly appreciated.
Best Regards,
Sandip

In previous versions the following was sufficient:
http://HOST:PORT/p6ws/
The correct URL as of version 8.0 of P6 Web Services is the following:
http://HOST:PORT/p6ws/services
See the following: "Error 403--Forbidden" When Attempting To View Available Services For P6 Web Services (Doc ID 1293112.1)

Web service deployment issue

Similar Messages

Maybe you are looking for