JBuilder debugging & 6.0

I'm using JBuilder 4 on win2k to debug a weblogic 6.0 applications.
Everything functions ok except the environment takes almost 20 minutes to
start off.
This is on a 700Mhz 256MByte machine.
I noticed 6.0 spends a lot of time copying and setting up its
.wl_temp_do_not_delete
directories.
It there away of switching off all the unnecessary bits of 6.0 for
development?
Ideally I would like startup time under 5 minutes!
Regards
Paul Savage
PS
Startup time for 4.5.1 & 5.1 when using Kawa was only a minute or so on the
same machine.

Hi there,
I've been experiencing the same problem...have you gotten any clue?
Personally, I do not think that it's taking so long because JBuilder's debugger
I think it's something with the WLS 6.0 (SP1), it is not due JVM neither since
I have WLS 5.1 in the same box and running with the same JVM...and, I agree, it
just take a minute or so
Thanks
- Aldo
"Paul Savage" <[email protected]> wrote:
I'm using JBuilder 4 on win2k to debug a weblogic 6.0 applications.
Everything functions ok except the environment takes almost 20 minutes
to
start off.
This is on a 700Mhz 256MByte machine.
I noticed 6.0 spends a lot of time copying and setting up its
..wl_temp_do_not_delete
directories.
It there away of switching off all the unnecessary bits of 6.0 for
development?
Ideally I would like startup time under 5 minutes!
Regards
Paul Savage
PS
Startup time for 4.5.1 & 5.1 when using Kawa was only a minute or so
on the
same machine.

Similar Messages

JBuilder debug problem

Hi,
I'm using JBuilder 4 ( I know its pretty old but we can't afford to keep upgrading...) and I've just reached a problem with the debugger.
My project has dozens of included libraries and as such the command line created by JBuilder has got longer and longer until now, when I get:
-- IOException starting Java runtime process --
java.io.IOException: CreateProcess: C:\JBuilder4\jdk1.3\bin\javaw -classic -classpath "long piece of text containing all the classpaths, which is then cut off, presumably because the process has run out of environment spac"
Oh yes, and I'm running on Windows 2000.
I'm guessing that either Windows or JBuilder have run out of environment space for this process. Has anyone else had this? If so, was there a workaround - I couldn't see anything on JBuilder and the Borland site isn't particularly informative.
Also, JBuilder puts in some of its own jars:
C:\JBuilder4\jdk1.3\demo\jfc\Java2D\Java2Demo.jar;C:\JBuilder4\jdk1.3\jre\lib\i18n.jar;C:\JBuilder4\jdk1.3\jre\lib\jaws.jar;C:\JBuilder4\jdk1.3\jre\lib\rt.jar;C:\JBuilder4\jdk1.3\jre\lib\sunrsasign.jar;C:\JBuilder4\jdk1.3\lib\dt.jar;C:\JBuilder4\jdk1.3\lib\tools.jar
which help to take up the environment space. I'm pretty sure that Java2Demo is not essential to my project, not sure about the others. Does anyone know how I can remove these from my debugger command line?

To remove libraries from your command-line, in JBuilder 4, do the following:
With your project open, click on the Project menu, then Project Properties (2nd from bottom). In the dialog, there's a tabbed pane, click on the 3rd option ('Required Libraries'), then select the libraries you want to remove and click on Remove. (Try removing all, then rebuild the project. If it complains, you have to add some back)
Removing the libs from the project doesn't remove the libs from disk, it just tells the compiler that for the given project it doesn't need to add those libs to the classpath.

Deployment and debugging from JBuilder

Hi,
i build a JATO application that deployed as a war file and run
perfectly on an external Tomcat.
But running this app on the integrated Tomcat of the JBuilder tool
results in the following error :
Application Error - javax.servlet.ServletException: Invalid reqest -
request handler "Login" not found
On that way, debugging the application is not possible.
Any idea what's wrong ?
I've heard there is a deployment tool document ? Where is it ?
thanks for your help

Hi--
None of our team has experience running JATO apps in JBuilder. The main
thing to check when running in an IDE is that the web.xml is properly
registered. Because you've received a JATO error, I assume it is in your
case. Therefore, it must be something else.
The error you sent means that the lookup for the LoginViewBean class failed.
This is probably a silly question, but are all of your classes compiled and
under the /WEB-INF/classes directory? Any other reason your application
classes might not be found?
Todd
Todd Fast
Senior Engineer
Sun Microsystems, Inc.
todd.fast@s...
----- Original Message -----
From: <donnetmonay@y...>
Sent: Tuesday, November 20, 2001 1:26 AM
Subject: [iPlanet-JATO] deployment and debugging from JBuilder
Hi,
i build a JATO application that deployed as a war file and run
perfectly on an external Tomcat.
But running this app on the integrated Tomcat of the JBuilder tool
results in the following error :
Application Error - javax.servlet.ServletException: Invalid reqest -
request handler "Login" not found
On that way, debugging the application is not possible.
Any idea what's wrong ?
I've heard there is a deployment tool document ? Where is it ?
thanks for your help
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp

Can't debug with jbuilder on a remote s1as

Hi,
I'm trying to run or debug an application on a remote sun one application server from a jbuilder 8 ee. The thing is that the ide deploys the web application without any problem, but when it doesn't run it, and if you try to debug it, you get this error:
-- Cannot start Java debug process VM --
com.sun.jdi.connect.VMStartException: VM initialization failed for: D:\JBuilder8\jdk1.4\bin\java.exe -classpath "D:\Sun\AppServer7\lib\appserv-admin.jar;D:\Sun\AppServer7\lib\appserv-cmp.jar;D:\Sun\AppServer7\lib\appserv-ext.jar;D:\Sun\AppServer7\lib\appserv-jstl.jar;D:\Sun\AppServer7\lib\appserv-rt.jar;D:\Sun\AppServer7\lib\appserv-tags.jar;D:\Sun\AppServer7\lib\jhall.jar;D:\Sun\AppServer7\lib\sun-appserv-ant.jar;d:\JBuilder8\lib\ext\appsrvSUNJB8.jar" -DFILETODEPLOY="D:/pruebas/jbuilder8/pruebasS1AS7/pruebasS1AS.war" com.sun.appserv.jbuilder.server.Main Debug
In the manual says that this could be caused by the admin server not running, but it is not the case, because it is running, and has just been used to deploy the application.
If i do the same operation on tomcat, there are no problems.
Thanks for the help and regards,
Juan

In case you need to debug an application on a remote Sun ONE Server Instance. Go to Admin Tool of Sun ONE Application Server 7 and Start Default Server Instance in the Debug Mode. You need to look for port at which Sun ONE debugger has started. For this find the following Entry in server.xml of Default Server instance.
server.xml is located in config folder in the default server instance folder in that particular domain under the domains directory in <INSTALL_DIR> of Sun ONE Application 7 e.g. if default server instance is server1 in domain1 then server.xml will be located in <INSTALL_DIR>/domains/domain1/server1/config
<java-config java-home="C:/Appservers/Sun/AppServer7/jdk" server-classpath="C:/Appservers/Sun/AppServer7/lib/appserv-rt.jar; " env-classpath-ignored="true" debug-enabled="true" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1186 -Xnoagent -Djava.compiler=NONE">
Note the value of address in the debug-options attribute value
specification. In this example the address is 1186.
Now in JBuilder Go To Run->
Configurations and edit Run Time Configuration for your JSP. Go To Debug Tab and Enable Remote Debugging and check Attach Option. In the Host name text field enter the hostname of the Default Server Instance. In the transport select dt_socket from the Type List and in the Address field enter the value of address from the debug-options attribute specified in the server.xml file.
Now try to Debug the application.
For more information on Remote Debugging, check out section 5.8.2 Remote Debugging in User Documentation of the Plugin.

Using debug mode with jbuilder 4 (or other tool) and wl 6.0

Hello,
I would like to know if there is a way to use jbuilder environnement to
debug ejb deployed on WL. I would like to be able to set break points into
my source code and be able to display variables values.
If it is not possible with jbuilder, is it possible with an other tool ?
If not, how can you debug ejb ? For exemple if I want to be sure a specific
line has been callde, do I need to stop my server, insert a system.out,
redeploy my ejb and restart my WL or is there a more simple way to do it ?
Thank's.
Nicolas.

Hello,
I would like to know if there is a way to use jbuilder environnement to
debug ejb deployed on WL. I would like to be able to set break points into
my source code and be able to display variables values.
If it is not possible with jbuilder, is it possible with an other tool ?
If not, how can you debug ejb ? For exemple if I want to be sure a specific
line has been callde, do I need to stop my server, insert a system.out,
redeploy my ejb and restart my WL or is there a more simple way to do it ?
Thank's.
Nicolas.

Does WLS support Debugging Servlets with JBuilder 3 ?

I have read all the news groups and it appears that WLS 4.5.1 does not
support debugging Servlets with Jbuilder 3.0.
I am using the trial version, does this matter ?
Or should I just buy another web server ?
Joe

I think below documents will be helpful to you.
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/webservices/webservicesecurity/CreateDefaultWSSConfig.html
This document tell you that you can attach a weblogic webservice configuration using weblogic admin console.
After creating this configuration you need to updated this configuration as per the steps given under :
Use X.509 certificates to establish identity
Thanks,
sandeep

Debugging Servlet with JBuilder 6

Does anyone know how to debug a servlet with JBuilder version 6?
I have created the servlet without the wizard.
Thanks.
-Amar

You can use ServletExecDebugger from NewAtlanta.
You can download ServletExecDebugger at
http://www.newatlanta.com/products/servletexec/download.jsp
1. Extract ServletExecDebugger files to your local folder
2. Import ServletExecDebugger.jar file into you JBuilder
workspace
3. There will be ServletExecDebuggerMain.java file
Import that also.
4. Set ClassPath, Project Path , etc and off you go.
ServletExecDebugger comes with good documentation
for a free debugger.
I have been using it for sometime now (in both JBuilder and Visual Age) and find it relatively simple to setup and good for debugging servlets.
You cannot debug JSPs that much easier though !
Hope this helps..
KD

Debugging with JBuilder...

Hi,
When I use the Step Into or Step Over functions of the debugger in JBuilder, it gets into all kinds of "strange" methods implemented by the Java Standard Library. How can I make it pass through my implementations only?
Thank You,
Maya.

Run -> View clases with tracing disabled, in that window you can tell JB which classes shoul be ignored when debugging.
Abraham

Debugging session EJBs in WLS 6.1 with JBuilder 5

Hello,
I'm trying to debug my code by attaching my JBuilder 5 to a WLS 6.1 running on
my pc. This works fine up to the moment I try to debug code in a EJB session bean.
If I try to debug "step by step" I get a message:
Can not locate <my ejb>fquimtELOIml.java from project source/class path.
and when I try to evaluate the value of an object inside the EJB I get a message
"unable to evaluate"...
Does somebody have an idea what I did wrong?
Thanks,
Roland

"Roland Pennings" <[email protected]> wrote in message
news:3e671a7f$[email protected]..
I'm trying to debug my code by attaching my JBuilder 5 to a WLS 6.1running on
my pc. This works fine up to the moment I try to debug code in a EJBsession bean.
>
If I try to debug "step by step" I get a message:
Can not locate <my ejb>fquimtELOIml.java from project source/class path.
and when I try to evaluate the value of an object inside the EJB I get amessage
"unable to evaluate"...
Does somebody have an idea what I did wrong?Sure. Use System.out.println. It's ten times more
efficient that IDE debugging.
Regards,
Slava Imeshev

JBuilder 3.2 crashes on remote debug of EJB

Error message says:
"....access violation...rdbk.dll..."
Also when you type:
call dbms_java.grant_permission('WEROWE',
','SYS:oracle.security.JServerPermission', ','Debug', null);
into the database to grant debug permission on the 8.1.7 database SQL*Plus says:
SP2-0552: Bind variable "ORACLE" not declared.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Walker Rowe ([email protected]):
Error message says:
"....access violation...rdbk.dll..."
Also when you type:
call dbms_java.grant_permission('WEROWE',
','SYS:oracle.security.JServerPermission', ','Debug', null);
This one is dfinitly misspelled in the help file, according to the online help it should be:
call dbms_java.grant_permission( 'WEROWE',
'oracle.security.JServerPermission', 'Debug', null);
or:
grant javadebugpriv to werowe;
both should do!!
Pretty annoying isnt it - wrong helpfiles
cost a lot of time!!
into the database to grant debug permission on the 8.1.7 database SQL*Plus says:
SP2-0552: Bind variable "ORACLE" not declared.<HR></BLOCKQUOTE>
null

How to debug JavaDoc from JBuilder

Does anybody know a way to debug the Doclet? Because right now I am facing problems changing the existant com.sun.tools.doclets.Standard class written by sun to my required output.
Thanks

Hi this is not what I meant. may be my question wasn't obvious because i wrote it in a hurry. I just wanted to debug my doclet. and I just found a way by using the com.sun.tools.javadoc.Main.main() function.
Thanks for ur response.

Library debugging and jbuilder

hi,
i am using jbuilder 2006 and working on a J2EE appln.
i have a main library in a separate package which takes care of database
connection etc. i have added this as a required library in my appln.
i possess the library code. i have run into some jdbc related issues linked
to the main library.
now my qns are ---
how can i step thru the main library code?
can i launch a debugger from my appln and step into the library code?
plz guide me.
thx

Here's a screen shot of the GreenBox''s properties. If I remove the var line in my AS file. I don't get an error, but if I check "Export in frame 1" in the Symbol Proberties box, I get the error.

How Can I debug a Wle CORBA Server Program by JBuilder 5 Or other Java develop tool.

Finally, I find a way to solve this problem although I still can not make it work by using a servlet to invoke ipsadmin or AddComponent class. The easiest way to solve this question is to access Ldap directly. I used ipsadmin to add a new domain and role first and then checked all their attributes in the Ldap. I wrote a program to insert the domain and role entry with the same attributes as using ipsadmin and it works just fine. I really can just add domain and role entry even though there are no webtopdomain and webtoprole objectclasee in the schema.

Deploy web application in jbuilder 9 with weblogic 7 problem

when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
where options include:
-help Print this help message.
-version Print version information.
-adminurl <https://<server>:<port>> The URL of the administration server: default
http://localhost:7001
-user <user> A user other than the default of
"installadministrator"
-password <password> Specifies the password on the command line.
If this option is absent the user is
prompted.
-verbose Displays additional status during the
deployment process, including notifications
when the application is prepared and
activated on each target.
-debug Displays debug level messages to the standard
output.
-examples Display example usage of this tool.
-upload Causes the specified source file(s) to be
transferred to the adminstration server. This
is used when the Deployer tools is not being
used on the same machine as the adminstration
server and the user does not otherwise have
access to place the targeted files on the
adminstration server.
-delete_files Causes the server to remove the files that
are specified in the file list and leave the
application activated. This option is valid
only for unarchived web applications.
-remote Signals that the tools is not runnning on the
same machine as the adminstration server and
that the source path should be made passed
through unchanged as it represents the path
on the remote server.
-nostage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged and the
original source is be used.
-external_stage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged but the
value of the staging path will be used when
preparing the application.
-stage Sets the stagingMethod staging attribute on
the application when it is created so that
the application will always be staged. This
value will override the stagingMethod
attribute on any targeted servers.
-nowait Once the action is initiated the tool will
print the task id and exit. This is used to
initiate multiple tasks and then monitor them
later using the -list action.
-timeout <seconds> The maximum time in seconds to wait for the
completion of the deployment task. When the
time expires the current status is printed
and the program exits.
-source <archive file or directory> Location of the file or directory that
represents the enterprise component or
application tha is being (re)activated. If
the source file is relative it is relative to
the current directory, unless the -remote
option is used. To specify individual files
within an application for reployment or
addition list them at the end of the command
line.
-name <application name> The name of the application being deployed.
-targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
cluster names. Each target may be qualified
with a J2EE component name. This enables
different components of the archive to
deployed on different servers.
-id <task identifier> Optional client supplied unique identifier
for the deployment task. The id is first
specified to -activate, -deactivate,
-unprepare or -remove. It is then used later
as an argument to -cancel or -list.
-activate (Re)activates the <source> application on the
<targets> with the <name>.
-deactivate Deactivates the application <name> on the
<targets> leaving an staged application files
in a state where the may be quickly
reactivated.
-unprepare Deactivates and unloads classes for the
application <name> on the <targets> leaving
an staged application files in a state where
the may be quickly reloaded.
-remove Deactivates the application <name> on the
<target> and removes any files that were
staged for this application. If there are no
longer any targets for the application, the
associated configuration is completely
removed.
-cancel Atempts to cancel the task <id> if it is has
not yet completed.
-list Lists the target status of each task <id>
-deploy a convenient alias for activate.
-undeploy a convenient alias for unprepare.
Optionally a list of the specific files in the archive that are to be
redeployed may be specified. If a directory is specified the entire subtree is
redeployed.
Full documentation on this tool is available at:
http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
No actions was specified. Please specify one and only one of:
-activate, -deactivate, -cancel, -remove, -unprepare, or -list.
Type java weblogic.Deployer -examples for example usage.

you use "deploy" under DOS-Mode to deploy your web application?
i found some differences between "deploy" and "redeploy" function in jbuilder 9.
when i choose "deploy" ,jbuilder shows me the commond below:
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility

Missing version field in response...( Tomcat, JBuilder )

Hello,
(Sorry for a long message, but I saw several times messages with the only
response like "write more details...")
I'm trying to execute a simple Web Start application using version-based download.
I'm constantly receiving the following error:
Missing version field in response from server when accessing resource:
(http://localhost:8083/checkboxcontrol/CheckBoxControl.jar, 1.1)
Is it possible that there is a bug somewhere within Web Start ?
The download is working in a basic version - the problem starts to occur when
I'm changing JNLP to:
<jar href="CheckBoxControl.jar" version="1.1"/>
Is there anybody that can help me ?
(I've read all past messages about "Missing version field in response...")
Below is all information about the case.
URL:
===================
http://localhost:8083/checkboxcontrol/CheckBoxControlLauncher.jnlp
Software configuration:
======================================
JBuilder 9 Enterprise Trial
Java Web Start 1.4.2
Tomcat 4.1 (included for debugging inside the JBuilder)
Windows NT 4.0 SP6a
Mozilla Firebird 0.6.1
Please note that I've tried also with IBM Websphere 4 - the same result.
JNLP file:
===================
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="http://localhost:8083/checkboxcontrol">
<information>
<title>CheckBox Example</title>
<vendor>Borland</vendor>
<homepage href="CheckBoxControlLauncher.html" />
<description>Web Start Example for CheckBoxControl</description>
</information>
<resources>
<j2se version="1.3+" />
<jar href="CheckBoxControl.jar" version="1.1"/>
</resources>
<application-desc main-class="com.borland.samples.swing.checkboxcontrol.Application1" />
</jnlp>
File directory contents:
========================
.\Lib (empty)
.\WEB-INF
->\classes
->->\checkboxcontrol
->->->\WEB-INF
->->->->\Lib
->->->->->\jardiff.jar
->->->->->\jnlp-servlet.jar
->->->->->\jnlp.jar
->->\classes\com\borland\samples\swing\checkboxcontrol\
->->->\Application1.class
->->->\Frame1$1.class
->->->\Frame1$2.class
->->->\Frame1$3.class
->->->\Frame1$4.class
->->->\Frame1$5.class
->->->\Frame1.class
->\lib
->->\jardiff.jar
->->\jnlp-servlet.jar
->->\jnlp.jar
->\web.xml
CheckBoxControl.jar
CheckBoxControlLauncher.html
CheckBoxControlLauncher.jnlp
CheckBoxControl__V1.1.jar
version.xml
web.xml contents:
===================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<servlet>
<servlet-name>JnlpDownloadServlet</servlet-name>
<servlet-class>com.sun.javaws.servlet.JnlpDownloadServlet</servlet-class>
</servlet>
[... cut ....]
<servlet-mapping>
<servlet-name>JnlpDownloadServlet</servlet-name>
<url-pattern>*.jnlp</url-pattern>
</servlet-mapping>
<mime-mapping>
<extension>jar</extension>
<mime-type>application/x-java-archive</mime-type>
</mime-mapping>
<mime-mapping>
<extension>jnlp</extension>
<mime-type>application/x-java-jnlp-file</mime-type>
</mime-mapping>
</web-app>
version.xml contents:
======================================
<jnlp-versions>
<resource>
<pattern>
<name>CheckBoxControl.jar</name>
<version-id>1.1</version-id>
</pattern>
<file>CheckBoxControl.jar</file>
</resource>
</jnlp-versions>
Stack trace:
===================
JNLPException[category: Download Error : Exception: null : LaunchDesc: null ]
     at com.sun.javaws.cache.DownloadProtocol.doDownload(DownloadProtocol.java:566)
     at com.sun.javaws.cache.DownloadProtocol.getDownloadSize(DownloadProtocol.java:850)
     at com.sun.javaws.LaunchDownload.downloadJarFiles(LaunchDownload.java:580)
     at com.sun.javaws.LaunchDownload.downloadEagerorAll(LaunchDownload.java:544)
     at com.sun.javaws.Launcher.downloadResources(Launcher.java:735)
     at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:291)
     at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:199)
     at com.sun.javaws.Launcher.run(Launcher.java:167)
     at java.lang.Thread.run(Thread.java:534)

I took a scan through what you posted and it looked OK - it has to be something simple. Sometimes it helps to compare against a working system - try looking at ScheduleWorld's jnlp.

JBuilder debugging & 6.0

Similar Messages

Maybe you are looking for