JApplet debugging problem

Hi there all:
I'm having a problem with debugging a JApplet. I created a new workspace, project and applet and didn't make any changes to anything. When I try to debug the applet, I get these messages:
System Error: java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup )
System Error: java.lang.Object java.lang.Class.newInstance0()
System Error: java.lang.Object java.lang.Class.newInstance()
System Error: java.applet.Applet sun.applet.AppletPanel.createApplet(sun.applet.AppletClassLoader)
System Error: void sun.applet.AppletPanel.runLoader()
System Error: void sun.applet.AppletPa
System Error: nel.run()
System Error: void java.lang.Thread.run()
If I change the object from a JApplet class to an Applet class, I can debug just fine.
Anyone know what's going on here?
Thanks
Jeff

Me again. Was doing some searching on the net about this one since I've gotten no response.
Found this at Inprise (Borland) about a debugging problem with JBuilder3 (I assume that the base of jdev is still JBuilder).
http://community.borland.com/article/0,1410,19739,00.html
To quote from their document--------
Question:
I can't seem to debug Applets with JBuilder3 Standard. If I attempt to debug my Applet
I recieve the following error:
java.security.AccessControlException: access denied (java.lang.RuntimePermission
modifyThreadGroup )
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:195)
at java.security.AccessController.checkPermission(AccessController.java:403)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
Why?
Answer:
In a nutshell this is an installation problem with JBuilder3 Standard edition.
The install for JBuilder3 Standard did not provide the file 'DebugApplet.policy'.
To resolve this problem download the file from the following URL:
http://www.borland.com/devsupport/jbuilder/downloads/DebugApplet.policy
After you have downloaded the file, copy the file to your JBuilder3\bin directory.
This will fix the problem.
You can also cut and paste the following:
(NOTE: create the file DebugApplet.policy in your JBuilder3\bin directory)
//DebugApplet.policy
// These policy permissions are needed for the AppletViewer used by sun.tools.debug.
grant {
permission java.lang.RuntimePermission "accessClassInPackage.*";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.net.SocketPermission "*", "accept, connect, listen, resolve";
permission java.util.PropertyPermission "appletviewer.version", "read";
permission java.io.FilePermission "<>", "read";
permission java.security.AllPermission;
Could this be a problem in JDev3 too?
Jeff
null

Similar Messages

Sun Studio Debugging problem

Hello
I need help configuring the Sun studio debugger to work in fedora 8. The project is loaded from a make file, compiles fine, and runs fine. However, I can not place break points, and when I start the visual debugger, it gives a message box titled progress, and hangs on saying: starting debugger: /lib/libc.so.6
Running from the command line gives me:
$dbx <my program>
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
Reading <my program>
Reading ld-linux.so.2
Reading libm.so.6
Reading libmpich.so.1.1
Reading libpthread.so.0
Reading librt.so.1
Reading libc.so.6
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
I have another problem in debugging an mpi problem in another installation of Sun Studio on Solaris 10 on a Sun machine. The visual debugger is working fine there, however, I need to debug with mpirun
to decide the number of processors, because by default it loads the application on one processor. Iwill need to do this as well later on the linux machine I am using now, which doesn't even start the debugger on a sequential code so far.
I appreciate your help a lot.
Thank you very much in advance.
Manal

mhelal wrote:
Hi
Thank you for your reply. you said 2 problems,Yes, basically I meant these two:
1. dbx: warning: unknown location expression code (0xe0)
2. dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
First one should be fixed in dbx itself, but the second looks like an incompatibility between Fedora's libc and dbx; unless distros in "supported" list upgrade to the same version of libc, dbx can't be changed to match it.
In other words, I'm sorry to say that you will probably not succeed in using dbx on Fedora 8 for the time being.

Debug problem using JDK 1.2.2

Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks

I had this problem earlier today. I deleted the old workspace, created a new one, added my projects in again, recompiled and things were fine. Every now and then my workspaces seem to corrupt and I have to do this, although I don't always get the "can't debug class message"
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Bill:
Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks <HR></BLOCKQUOTE>
null

Debug problem in JDeveloper 3.0

Has anybody come across a problem when debugging an application that causes JDeveloper to go into an infinite loop (until my machine runs out of memory) when a breakpoint is hit.
This only seems to happen on certain files
I've removed JDeveloper 2.0. I've reinstalled JDeveloper 3.0. I've recreated my workspace and project from scratch but I still get the problem.
My project has ~1200 files.
I've also noticed that sometimes the breakpoint is hit and the application being debugged will be paused but JDeveloper does not gain control (i.e. the 'step', 'step into' etc. buttons are still disabled). This is possibly related to the above problem.

Has anybody come across a problem when >debugging an application that causes >JDeveloper to go into an infinite loop >>(until my machine runs out of memory) when a >breakpoint is hit.This is not a known issue but if anyone has a reproducable test case then we'll be happy to follow it up.
Thanks,
Arun

Java debugging - problems with standard input

Hi
I hope somebody can help me with this problem.
I'm developing a Java app that reads from the standard input. I use System.in.read() to do that. When I debug it, I use the Standard I/O window instead of the Run Log window to pass in values, but nothing happens (i.e. the line following the read() is never reached). I also tried to run the app and then attach the debugger to use the Run Log window as standard input, with the same result. If I add a breakpoint before the call to read(), the debugger pauses the execution, so I suppose the breakpoints are OK.
In the executable Info window, Debugging tab, I use the pseudo terminal with the Java debugger.
So my question is: how can I enter values from the standard input in debugging mode?

I believe that you are seeing these problems because we have found the
current versions of RMI found in the JDK to be inherently unscalable -- we
do not listen for them. As you noticed, we recommend that you use our
packages for now, and then do the simple change that you found if you decide
that you do not like WLS. (If you do decide that you do not like us, please
definitely let us know why you chose the way you did!)
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Tim Dawson" <[email protected]> wrote in message
news:397b8cc2$[email protected]..
We're developing a J2EE application on NT using WLS 5.1, SP3, but we don't
want to be tied to any particular J2EE server, so we're making sure that
none of our code is weblogic specific.
In keeping with this philosophy, I created an RMI service that used the
standard java.rmi.* imports instead of weblogic.rmi.* and used thestandard
RMIC compiler rather than the weblogic.rmic compiler.
Unfortunately, I couldn't get the system to work. I kept getting
"java.rmi.MarshalException: Error marshaling transport header; nested
exception is: java.io.EOFException" whenever I'd call Naming.lookup().
Of course, when I did the search & replace with java.rmi.* with
weblogic.rmi.*, and switched from the standard rmic to weblogic.rmic,
everything started working just fine. This is the ONLY change I made!
Has anyone else run into similar problems?
Tim Dawson
Sr. Software Architect
is.com

Debugging problem, in inbound function module.

Hi Experts,
              R/3 system is receiving data through an IDOC called WPUUMS[sales data]. It has been seen that when this data is posted in R/3 through XI the data gets reflected in WE02 / WE05, and is similar to when a manual entry is done the transaction WPUK. But the difference is , when manual idoc generation is done, it is updating correct data in database, but when same data is posted from XI, it is updating data base with in correct data!
   what I cant get to understand is in both the cases, IDOC is posted, and same data is there in the DATA records, but database is getting upated with diff data.
    Also , when I am putting a break point on the inbound function module IDOC_INPUT_POS_SALES_ACCOUNT, it is not hitting the break-point but idoc gets generated successfully with status records like
53 Application Document posted
62 Idoc Passed to application
64 Idoc ready to be transferred to application
50 Idoc added.
Also , i want to know, wether these messeges come step by step or randomly, because, why is the messege 62, before messege 64.
Lastly when I am taking the same IDOC and trying the same in WE19, then it hits the break-point function module IDOC_INPUT_POS_SALES_ACCOUNT successfully.
Experts, comments pls.!
Regards,
Arnab.

Hi,
You are supposed to read the ststus messages from bottom to top. So the actual sequence is:
50 Idoc added.
64 Idoc ready to be transferred to application
62 Idoc Passed to application
53 Application Document posted
Which is correct.
And it is correct that the system bypasses any breakpoint in the background mode. So when the IDoc is coming from XI the posting FM IDOC_INPUT_POS_SALES_ACCOUNT is called in background and so the breakpoint is not called.
Only way to debug the problem is via transaction WE19 in Debug mode.
Regards,
Prakash Pandey

Debugging problems on iPad

I have two applications, and 4.7 installed in two different PCs (64 bits one and 32 bits the other one).
In one PC (32 bits) both apps can be tested with no problem at all. In the other one (64 bits) I debugged one of them once, but now I can't debug any of them.
Problem description: device is there and connected, debug begins, says it's installing and seems to finish it well. It waits for me to initiate the app, but the app is not there. No app for debugging in the iPad.

Hi,
A similar issue has been logged and is being tracked. Please refer to below bug for more description.
http://bugs.adobe.com/jira/browse/FB-33478
Workaround: Even though ipa is not installed on the device, ipa will be generated in the specified output folder(bin-debug).Using iTunes install the ipa on the device and launch the app to make a debugger session.
Let me know if you require more information.
Thanks,
Sanjay

Debug problem

I installed the sneak preview Enterprise portal on my machine. Yesterday i was able to debug my portal application. But today i wasn't. This problem was after the moment I deleted the old portal application.
Can someone tell my how i can fix this problem
Message was edited by: Edward Kust

It could be that your IP address has changed?! In this case, the Developer Studio/Eclipse might not be able to find the portal anymore. I had the same problem, and the strange thing about it is that IE still connects to the portal.

Smartform debugging problem

Hi Experts,
How to debug smartform in quality. can anybody explain me....
Thanks
rajesh

dear
Do one thing apply the breakpoint in smartform where u r getting the problem and execute directly u will come to that point .
Else execute u will get long string name in function module screen :
Goto to the display mode and then put the break point
this will also do
thanx
-ankit

Debugging problems...

New to PSCS5 is the loss of the 'Hold-the-ALT-key-during-script-launch-to-run-in-ESTK' feature.
This has screwed up my workflow somewhat.
What's worse is that I have now have several PS scripts that won't launch from ESTK at all. They just hang. No error message or anything.
Photoshop pops forward, the ESTK spinner spins, and nothing happens. I have to hit the Stop button and return focus to PS before I can
do anything again with ESTK.
I'll file a bug report now that I'm able to reproduce this with a script I can share with them. But if anybody wants to try to replicate this, download the latest rev of CSX and try and launch it from ESTK. It may be a little sluggish since CSX is flattened out to 25KLOC, but I see the same problem in my dev version that uses //@includes.
As it stands, when ever I want to debug stuff, I have to use "$.level =1; debugger;". I'd really be screwed if that ever went away. Again.

New to PSCS5 is the loss of the 'Hold-the-ALT-key-during-script-launch-to-run-in-ESTK' feature.
This has screwed up my workflow somewhat.
What's worse is that I have now have several PS scripts that won't launch from ESTK at all. They just hang. No error message or anything.
Photoshop pops forward, the ESTK spinner spins, and nothing happens. I have to hit the Stop button and return focus to PS before I can
do anything again with ESTK.
I'll file a bug report now that I'm able to reproduce this with a script I can share with them. But if anybody wants to try to replicate this, download the latest rev of CSX and try and launch it from ESTK. It may be a little sluggish since CSX is flattened out to 25KLOC, but I see the same problem in my dev version that uses //@includes.
As it stands, when ever I want to debug stuff, I have to use "$.level =1; debugger;". I'd really be screwed if that ever went away. Again.

JDev Debugging problem

Dear sirs,
I would like to be able to debug my JDeveloper project and trace into the J2SE source files, but JDeveloper will not let me.
The project JVM is currently set to "Java 1.3.1"
with the path : "E:\java\jdk1.3.1\jre\bin\java.exe"
and with the classpath:
E:\java\jdk1.3.1\lib\dt.jar;E:\java\jdk1.3.1\jre\lib\rt.jar;E:\java\jdk1.3.1\jre\lib\i18n.jar
I have tried to set the path to
"E:\java\jdk1.3.1\bin\java.exe" instead, but JDeveloper switches the path back to "E:\java\jdk1.3.1\jre\bin\java.exe" for no apparent reason.
I have tried to uncompress the src.jar and set the
source path: E:\java\jdk1.3.1\src\ but to no avail.
I have tried to set the classpath to
E:\java\jdk1.3.1\lib\dt.jar;
E:\java\jdk1.3.1\src.jar;
E:\java\jdk1.3.1\jre\lib\i18n.jar;
E:\java\jdk1.3.1\jre\lib\rt.jar
to try and force it to use the source files instead of the runtime files, but then I get a System Error when trying to run my compiled project and execution is halted :
System Error:     java version "1.3.1"
System Error:     Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
System Error:     Java HotSpot(TM) Client VM (build 1.3.1-b24, interpreted mode)
System Error:
Please help me, as I am running out of ideas on how to trace into the Java source code.
Best regards,
Christian Loft
"E:\java\jdk1.3.1\jre\bin\java" -mx50m -showversion -classpath "E:\Program Files\Oracle\JDeveloper 3.2\myprojects\RMI2\myclasses;E:\Program Files\Oracle\JDeveloper 3.2\jdbc\lib\oracle8.1.7\classes12.zip;E:\Program Files\Oracle\JDeveloper 3.2\lib\connectionmanager.zip;E:\Program Files\Oracle\JDeveloper 3.2\lib\jdev-rt.zip;E:\java\jdk1.3.1\lib\dt.jar;E:\java\jdk1.3.1\src.jar;E:\java\jdk1.3.1\jre\lib\i18n.jar;E:\java\jdk1.3.1\jre\lib\rt.jar" -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=2103 RMI_Client_Application

Dear Christophe,
thank you for your reply. I have included the src.jar in the source path. But there is no "tracing classes and packages to Exclude" under the "Run/Debug" tab (I use JDeveloper 3.2.2 (Build 915)), but under the "Compiler" tab I have made sure that there is no files mentioned in the "Exlude class" and the "Exclude Sources".
The problem remains. I can run the application, but when I try to debug, the application window never appears.
Do you have any other things I can try?
Best regards,
Christian
You need to make sure sure of a couple of things:
- have src.jar added to your java source path (Project settings Input path)
- also you need to go into the debugger pane of project Settings and remove from "tracing classes and packages to Exclude" all the classes you want to trace into. For example if you want to trace into java.lang.String remove the java package.
Hope it helps, Christophe [JDeveloper team]

Premiere Debug Problems

hi there,
I have just tried to export via the Adobe Media Encoder to a Quicktime Format.
After a while, the endocing stopped and a Debug Event window popped up and said
something about "SRC\PPixHandleUtilites.cpp-114
I wasn't able to continue the Encoding Process.
has anyone got an idea of what to do and what the problem is?
Best,

Please provide
these details to help us help you.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Idoc debugging problem

Hi Experts,
I have created FM "Z_OV_GIS_UPDATE", which is having only 3 table parameters of type EDIDC, EDIDD and BDIDOCSTAT.
I found some of idocs in WE05. I made use of one Idoc and try to debug by tcode WE19 and by the FM Z_OV_GIS_UPDATE, tcode is throwing error like "Interface for function Z_OV_GIS_UPDATE is incorrect".
Please advice to avoid this problem,
solution will be Appreciated.
Thanks,
bhasha

Hi,
The function module interface should be the same for all the IDOC processing FMs..
Check the function module IDOC_INPUT_ORDERS for the sample interface..And modify your FM accordingly..
Thanks,
Naren

XCode debugging problems

For some reason, when I try to debug or run my application within XCode, my Application menu does not appear, and keys pressed go to the runlog window, not my application controls.
Any Idea what's going on, or how I should start troubleshooting this problem?

It sounds like your Info.plist file is messed up. I used to get that problem when I was first using Xcode. The best way to fix it is to create a new Cocoa application with nothing in it. Compile and run it to make sure it works correctly. Then, inspect the Project and Target settings. I don't remember precisely where the problem was. Usually, it was something related to a mismatch involving the name of the application. I had renamed my app something different than MyApp and didn't use the new name everywhere.
Anyway, inspect those settings. Your GUI has become disconnected from your application. Sorry I can't provide more help. It has been several years since I had this problem. I have since learned to pick a good application name when I create the project and stick with it.

Debugging problem

hi,
I want to debug my AIR app built with Flash Builder on the iPad. I followed the instructions on
http://renaun.com/blog/2010/11/debugging-air-apps-on-idevices-with-flash-builder-4-or-burr ito/
I compiled my application using the -debug option. While creating a debug version of the IPA using the -target ipa-debug option , I get the following error
Exception in thread "main" java.lang.Error: Unable to find named traits: mx.collections.errors::ItemPendingError
        at adobe.abc.Domain.resolveTypeName(Domain.java:195)
        at adobe.abc.Domain.resolveTypeName(Domain.java:112)
        at adobe.abc.GlobalOptimizer$InputAbc.resolveTypeName(GlobalOptimizer.java:274)
        at adobe.abc.GlobalOptimizer$InputAbc.readCode(GlobalOptimizer.java:983)
        at adobe.abc.GlobalOptimizer$InputAbc.readBody(GlobalOptimizer.java:531)
        at adobe.abc.GlobalOptimizer$InputAbc.readAbc(GlobalOptimizer.java:404)
        at adobe.abc.GlobalOptimizer$InputAbc.readAbc(GlobalOptimizer.java:280)
        at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:160)
        at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcode(AOTCompiler.java:329)
        at com.adobe.air.ipa.AOTCompiler.GenerateMacBinary(AOTCompiler.java:600)
        at com.adobe.air.ipa.IPAOutputStream.compileRootSwf(IPAOutputStream.java:196)
        at com.adobe.air.ipa.IPAOutputStream.finalizeSig(IPAOutputStream.java:366)
        at com.adobe.air.ADTPackager.createPackage(ADTPackager.java:65)
        at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:165)
        at com.adobe.air.ADTEntrypoint.parseArgsAndGo(ADTEntrypoint.java:132)
        at com.adobe.air.ipa.PFI.parseArgsAndGo(PFI.java:152)
        at com.adobe.air.ADTEntrypoint.run(ADTEntrypoint.java:68)
        at com.adobe.air.ipa.PFI.main(PFI.java:112)
I am using the following command for creating the ipa
"pfi -package -target ipa-debug -connect -provisioning-profile myProvisioningProfile.mobileprovision -storetype pkcs12 -keystore ipad_dev.p12 -storepass pass "SampleIPadApp.ipa" "SampleIPadApp-app.xml" "SampleIPadApp.swf"
I have tried all options for connect(with ip etc. as mentioned in the developer guide) but getting the same error.
On googling for the problem, the only thing I deduced was that you get this error when you use the debug version of .swf file. But in this case I do want the debug version. Second problem could be if you are using referencing a swc via RSL. I am not using any and moreover i am able to succesfully create ipa with the -target ipa-test option.
In the blog post mentioned above there's a note by the author that - "I used ActionScript 3 project in this post because currently Flex has issues when packaging an ipa with a debug SWF."   Is this still true? Has anybody been able to succesfully debug their app(developed in Flex) on iDevice?
Regards,
Vrushali

hi,
I managed to solve the problem by using the compiler from Flex SDK 3.6. Earlier I was using Flex SDK 4.1. Don't know what problems I'll face later on. I wonder if developing iPhone app in Flex is advisable or not. Mabe its better to have a pure ActionScript project.
-Vrushali

JApplet debugging problem

Similar Messages

Maybe you are looking for