Error while debugging in NWDS

Hi,
I am getting a "source not found" error while debugging in NWDS.
I put a break point in a particular class, but it never gets hit, instead I get an error saying "source is not found".
I have tried rebuilding, deploying and even starting the IDE but nothing works.
Can anybody help me here.
Regards
Arvind

Hi Arvind,
1) Have you set debug on in the server?
If not you need to on debug on SAP-J2EE engine(For web applications).
2) If that is a pure java class then it will work.
Regards,
Devender V

Similar Messages

Error While Debugging the Application

Hello,
I am developing applications using WebDynpro for JAVA.
I am using NWDI 7.0.
I am getting an error while debugging the application. When I click on debug mode in debug perspective, I am getting error message as :
"Failed to connect to remote VM. Connection refused"
Could any one of you help in resolving this error?
Thanks and regards,
Pradnya

Hi,
I think NWDI has nothing to do with debugging the application.
Probably you will get some answers in WebDynpro java forum
-Ashutosh

Source Not Found Error while Debugging

Hello,
I get annoying Errors while debugging a midlet. I reinstalled all programms an created a new midlet suite + midlet but the error is still there and the Midlet doesnt start.
i got Eclipse Version: 3.2.2, Eclipse ME 1.6.6, the newest WTK 2.5 and java.vm.version=1.6.0-b105.
I configured everything like www.eclipseme.org says it would be correct.
Running a Midlet works fine.
The bug opens an Helper.class file which says:
Class File Editor: Source not found: "The Jar of this classfile belongs to the container J2ME library [ Sun Java (TM) Wireless Toolkit 2.5 for CLDC/MediaControl]. To configure the source attachment, go directly to the corresponding configuration page (For example for JRE go to 'Installed JRE#s page in references).
Any clou how to fix this?? I need to debug my midlet :-/
THANKS!
Byby
pako

Hi,
I just had the same problem and navigated to this page here in hope for a solution...
However I've solved the problem now. On Eclipse, do the following.
1) Right-click on the added Jar-file (which is producing the problem)
2) On the popup-menu choose "Build Path" and "Configure Build Path..."
3) On the opening preference window, click the checkbox of the Jar
This is probably necessary because the jar has to be exported such that the simulator is able to execute it.
Greets,
Juri
http://juri-strumpflohner.blogspot.com

Error while deploying from NWDS

Hi,
i am getting the following error while trying to deploy a PAR file from NWDS through export.
PAR upload failed:C:\Documents and settings\Trials\Trials.par
Please check the userid and password.
i cross checked the userid and password.both are correct. the same par file is deployed successfully in other servers.
this error occurs only for PAR file deployment. other applications like webdynpro and all are deploying successfully.please help.
/* useful inputs will be rewarded*/
Regards,
Art Tech.

Hi All,
Thanks for ur responses.
To Sahu:
     Yes the user id has system admin role.
To Ramani:
     I know that we can upload the PAR from portal itself as u said but i want to know the cause of my problem. why i am not able to do it from NWDS.
To Vinoth:
     As i said i want to upload it from NWDS only.
i want to inform onething to all of u . we thought that it may be problem in SDM. so we checked SDM also. in that a process (deployment) is still going on. so we r not able to enter into it. it is like a infinitive for loop. so, that may be the cause which doesnt allow other deployments.
Can any one tell me how to kill that process. it is something relevent to J2ee engine administration i hope.
What i mentioned above is only our decision , we are not sure that whether it is the exact reason or not. so if anyone encountered the same problem and solved please guide me or any docs related to this also will be helpful.
Regards,
Art Tech.

ERROR while debugging a SELECT..ENDSELECT

Hello All,
We get an error while we go into the select..endselect loop during debugging. Because of this if we try to do some research on existing program with Select-endselect..it fails in the second pass of this loop.
This problem was not there earlier, but after we upgraded from 4.6 to 4.7 this problem is bugging us..every day. Does any one have a clue why ?
Thanks!!
Regards,
Vishal

Hi,
debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.
See OSS notes 675, 2104.
From OSS note 675 **********************************
Cause and prerequisites
Chain of causes:
      1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).
      2. A database Commit causes the database to lose the cursor.
      3. The system cannot automatically continue within Select loop after loss of cursor.
Following statements lead to a database Commit:
    * All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)
    * BREAK-POINT/ Debugging
      . if no debug process free
      . always after regeneration (in order to release generation lock).
    * WAIT Here a work process is released and a Commit is executed.
    * COMMIT WORK/ROLLBACK WORK
From OSS note 2104 **********************************
Solution
The "COMMITWORK" message appears in the ABAP debugger when programs
orscreensrequireregeneration,or when not enough free capacity
is available inthesystem (or else the debugger blocks a system
process).
Normallyonly one work process is released for debugging. This
isgenerally insufficient ina developmentsystem, as processes
can be blocked for other reasonstoo(background processing,
CPI-C connections,andso on).
The number of work processes made available for debugging can
be configured using the profileparameter
                  rdisp/wpdbug_max_no
Forexample:
                rdisp/wpdbug_max_no = 10
setsthe maximum number of work processes made available for
debuggingto 10. It may be necessary to generally increase the
numberofwork processesatthis time (parameter rdisp/wp_no_dia).
In all other known cases, an error in the application program is
involved.
Regards, Manuel

Error while deplying from NWDS 7.0 to PI 7.1

Hello Frenz,
I am trying to deply an webdynpro application developed with NWDS 7.0 on PI 7.1 server. But i am getting the following error. Any idea about this. Please help.
Description:'1. [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application com.tsi/xyz.
No one of the [com.sap.security.login-modules] containers, which processed it, returned deployed component names.
The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
     1.An AS Java service, which is providing a container, is stopped or not deployed.
     2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.'.
Regards,
Shweta

HI,
1. structure of WD in 7.1 is totally diff from 7.0 WD. so if you tried to deploy them directly after developing in NWDS 7.0 it wont work.
2. and also you have to consider the compiler versions too
so
Either open your project in NWDS 7.1 and migrate it...or atleast try to build it in NWDS7.1.
if you r application successfully built then you will be able to deploy it.
7.1 have a downward compatibilty for 7.0 but the major problem is the environment and compiler where it is developed.

Error while debuging form

Dear All,
I tried to debug some forms 10g that has been created in 6i,but i got the following error message while debuging...
FRM-30454: Unsupported item type.
Item: OLE_CONTROL51
Block: B2
Form: STRMAIN
FRM-30085: Unable to adjust form for output.
Please provide me with some solution...
Thanks and regards
Monoj

Hi
apparently u r using but this item type is considered is considered obsolete item no longer supported in forms 10.
You would need to use CLIENT_OLE in the webutil package to launch e.g. Word and etc.
It is documented in oracle regarding Migrating Client-Server Applications to the Web
Instead, use JavaBeans to duplicate functionality in the user interface. Any other Microsoft Windows user interface dependencies should also be replaced with JavaBeans. You can also use WebUtil to restore some of these functions.
Hope this helps...
Regards,
Amatu Allah

Error while debugging a FM to get pricing condition details

Hi,
when debugging the FM PRC_PD_HEAD_SHOW ( SPC_GET_PRICING_CONDITIONS ) to get the pricing condition details i am getting an error java debugging back end on sapdevsystem is waiting for port 8003.
Is this bcoz java not properly installed in my system. Can anybody pls tell me how to solve this issue.
Thanks,
Leena

Did not get any answer.. so found all the dates by particular tables a*** from pricing.

Error when debugging in NWDS

Hi there,
I am trying to debug in the NWDS. When i run the program using the java application, i encounter this error message
Error javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Can anyone tell me wad error is this?
Thanks Loads
Quatre

Hi Quatre,
You check whether are you set the Main Class Name in the Java Application --> Run Option.
You will be follow this steps to set the Main Class in the Run Option on Java Application in NWDS.
In NWDS --> Select Run --> Again Run --> In that Window having the Java application --> select the java program, what you are created --> Right side of the window having the tab for Main --> In tab, you fill the Project Name, Main Class. And also you will check whether the JRE is set in the NWDS.In the same window having that option.
After that you can run the java application..
I think its help to you.
Regards
Prakash T

Error while debugging an application

Hi all,
I am facing this issue in jdeveloper 11.1.1.6 when I am trying to run in a debug mode. The page does'nt even show up and in the jdeveloper log I can see the below error message.
]] Root cause of ServletException.
java.lang.InternalError: name is too long to represent
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
     at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
     at weblogic.servlet.jsp.JspClassLoader.findClass(JspClassLoader.java:48)
     at weblogic.servlet.jsp.JspClassLoader.loadClass(JspClassLoader.java:33)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:281)
     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
     at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:416)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:326)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:523)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
     at oracle.adfinternal.view.faces.config.rich.RecordRequestAttributesDuringDispatch.dispatch(RecordRequestAttributesDuringDispatch.java:44)
     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
     at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)
     at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:469)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
     at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
     at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:911)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:367)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:222)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = arti-HP TXID = CONTEXTID = f6ef983f54a76485:7483abb2:13876769704:-8000-0000000000000084 TIMESTAMP = 1342017390348
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
Can someone please let me know what might be wrong? I checked the managed beans method names and also the VO,EO names they are not too long.

There are a couple of reasons why you get this error. Not enough memory is one of them, as there are a couple of other possibilities (like a bug).
google for 'java.lang.InternalError: name is too long to represent' and you find some possible solutions...
Timo

Unable to connect to Services Registry(error) while connecting from NWDS

Hi SDN friends,
I am trying to do WSDL import from NWDS (Developer Studio SAP NetWeaver 7.1 Composition Environment SP03 PAT0000 Build id: 200710302120 ) and i am getting following error
"Unable to connect to Services Registry"
Below are the service regsitry details i am passing
window --> Preferences
Service Registry (UDDI Service)
Server Name:sr.esworkplace.sap.com
Server Port:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
Classification Service
Server Name:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Classification Path:ClassificationService/CS?style=document
I am using the following credentials for login to UDDI Service http://sr.esworkplace.sap.com
login/pwd: sruser
password: esword123
I tried with two different systems (office and Home) , bit still not connecting.
Waiting for experts answer.
Thanks
Aravinda

Hi,
You wrote that you connect to the SAP uddi:
Service Registry (UDDI Service)
Server Name:sr.esworkplace.sap.com
Server Port:sr.esworkplace.sap.com
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
sr.esworkplace.sap.com is not on your home pc. Its a SAP public uddi.
If you want to connect to your own pc than your configuration would be sompething like this:
Server Name:localhost
Server Port:50000
Server HTTPS Port:50043
Inquiry Path:uddi/api/inquiry
Publish Path:uddi/api/publish
Security Path:uddi/api/security
And you shouldn't use this login data
login/pwd: sruser
password: eswork123
regards,
v s
Edited by: v s on Jul 2, 2008 9:31 AM
Edited by: v s on Jul 2, 2008 9:34 AM

WebdynproJava Components giving error while migrating from NWDS SP03 toSP09

Hi,
The original DC's were developed in lower NWDS patch level, currently i have upgraded the patch level of NWDS to 09 and importing the Wed Dynpro components from NWDI; but some of the DC's are proper but some are giving error.
I tried Project build, DC build and Repairing the DC's but nothing worked.

Hi Siarhei,
Error:
The constructor WSTypedModel(String, String, QName, String, Map, String, IWSTypedModelInfo, Map<String,QName>) is undefined
Warnings:
Versions of 'com.sap.dictionary.runtime' are different.
Versions of 'com.sap.dictionary.services' are different.
Versions of 'com.sap.tc_.wd_.rtgen' are different.
Forgot to mention i am working on CE7.1
Regards
Jagan

Error while deploy from NWDS 7.1

When I am trying to deploy a web dynpro to our J2EE server using:
SAP NetWeaver Developer Studio 7.1 SP07 PAT0003 Build id: 200902281924
I receive the following error:
Message:
An internal error occurred during: "Deploying project(s)
Exception StacK Trace:
java.lang.NoClassDefFoundError: com/sap/ide/dii05/util/api/diilog/Severity
at com.sap.ide.eclipse.sdm.threading.OptionalDiiLogImpl.diiLog(OptionalDiiLogImpl.java:31)
at com.sap.ide.eclipse.sdm.threading.OptionalDiiLog.diiLog(OptionalDiiLog.java:38)
at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:258)
at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:149)
at com.sap.ide.webdynpro.archivebuilder.ActionDeployArchive$DeployJob.run(ActionDeployArchive.java:214)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Does anyone know how to resolve this problem?
Stephan

HI,
1. structure of WD in 7.1 is totally diff from 7.0 WD. so if you tried to deploy them directly after developing in NWDS 7.0 it wont work.
2. and also you have to consider the compiler versions too
so
Either open your project in NWDS 7.1 and migrate it...or atleast try to build it in NWDS7.1.
if you r application successfully built then you will be able to deploy it.
7.1 have a downward compatibilty for 7.0 but the major problem is the environment and compiler where it is developed.

Error while debugging the Oracle Stored Proc Body

I am trying to debug a standalone Oracle Stored Proc. I keep a break point on the Package body, and JDeveloper doesn't seem to pick it up at all. I have made sure that are the prerequisites are met and all the instructions have been followed diligently, but still i keep getting this error message:
Unable to set breakpoint (C:\Program Files\JDeveloper\jdev\mywork\ADReports\ADReportsProject\packagebody staging.staging_reports.sql 57), unable to resolve Java package.
The Debugger doesn't seem to stop at the specified break point in the package body. Though it does connect to the DB, and shows all the data values inside the procs, and other stuff as mentioned in the debug tutorial/manual.
Some replied to my previous post saying that it was a bug with the JDeveloper itself and it has been fixed, so if this is the case, can someone point me to the right place where we can download the bug free version.
Thanks in advance

Hi,
Please see:
PL/SQL Debugging does not stop on breakpoint
- Mark

Error while debugging AIR for IOS app

I get the following error when attempting to debug my AIR-IOS app on an IPad 2.
The weird thing is that the logfile mentioned does not exist.
Any ideas?
- Abey
# A fatal error has been detected by the Java Runtime Environment:
# EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x764db9bc, pid=5400, tid=9024
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) Client VM (20.4-b02 mixed mode windows-x86 )
# Problematic frame:
# C [KERNELBASE.dll+0xb9bc]
# An error report file with more information is saved as:
# C:\Users\ABEY~1.LEX\AppData\Local\Temp\AOT1326388929076\hs_err_pid5400.log

I have the same error.
The wierd is that the log file doesn't exists.
Anyway I try everything... to reinstal my Flash Builder, reinstall all versions of java. I even try to make Xmx and Xms bigger size.. but nothing... still got the error.
If I create new project... then everything works fine... Export Release Build work very well,
but if I try to Export Release Build for my large project... then this error comes up.
I look at my code and no find any errors...
Build for android works as well, the error comes up when I try to build for iOS.
Please Adobe - give us help how to fix this.
Thank you

Error while debugging in NWDS

Similar Messages

Maybe you are looking for