j2se version="1.4.2*" ??

Is it not possible to use * character
<j2se version="1.4.2*" ??
So that my application uses only 1.4.2_xx version, I cannot use 1.4+ or 1.4.2+ or it will use 1.4.0 or 1.4.1_xx or 1.5

yes, you can use this but you must include the href parameter.
<j2se version="1.4.2*" href="http://java.sun.com/products/autodl/j2se"/>
without an href argument, a version indicates a java specification version, and so there is no such thing as 1.4.2
/Andy

Similar Messages

Using J2SE Version 5.0 with Oracle E-Business Suite 11i [ID 304099.1]

Hi hussein,
EBS 11i upgrade to Db 11gR2
RHEL 4.6
We are required to upgrade the J2SE to 5.0.
The notes said download it from
http://java.sun.com/j2se/1.5.0/download.jspBut when I click this site I only see
Download Java EE SDK 5.0 Update 1 for Linux Is this the one? is J2SE Version 5.0 the same with Java EE SDK 5.0?
Thanks a lot

Hi hussein,
I have finished downloading and installing the JRE 5.0
[root@oracletrng u04]# ./jre-6u22-linux-i586-rpm.bin
Unpacking...
Checksumming...
Extracting...
UnZipSFX 5.50 of 17 February 2002, by Info-ZIP ([email protected]).
inflating: jre-6u22-linux-i586.rpm
Preparing...                ########################################### [100%]
   1:jre                    ########################################### [100%]
Unpacking JAR files...
        rt.jar...
        jsse.jar...
        charsets.jar...
        localedata.jar...
        plugin.jar...
        javaws.jar...
        deploy.jar...
Done.
[root@oracletrng u04]#How do I check If my jre is updated? what is the JRE_TOP?

Try to use J2SE Version 6 with Oracle E-Business Suite 11i

Dears ,
i have an upgrade task from 11.5.10.2 to R12.1.1 and database from 9.2.0.8 to 11.2
so i apply patches :
1- 7429271
2- Upgrading Developer 6i with Oracle Applications 11i [ID 125767.1]
3- 9535311
4- 6241631
5-upgrade to JRE : Using J2SE Version 6 with Oracle E-Business Suite 11i [ID 401561.1]
when i run :
txkrun.pl -script=SetJDKCfg -contextfile=$CONTEXT_FILE -runautoconfig=Yes -appspass= <APPS_schema_passwd> -jdktop=[JDK60_TOP]
faced error :
java.lang.NoClassDefFoundError: java/util/HashMap
at
at oracle.apps.ad.tools.configuration.Customizer.getProdTopDrivers(Compiled Code)
at oracle.apps.ad.tools.configuration.Customizer.getAllDrivers(Compiled Code)
at oracle.apps.ad.tools.configuration.VersionConflictListGenerator.getAllConflicts(Compiled Code)
at oracle.apps.ad.tools.configuration.VersionConflictListGenerator.main(Compiled Code)
Exception in thread "main" Using Context file : /vol3/oracle/prdappl/admin/PRD_mcd-test.xml
Context Value Management will now update the Context file
and when try to run autoconfig on APPSTier i faced :
java.lang.NoClassDefFoundError: java/util/HashMap
at
at oracle.apps.ad.tools.configuration.Customizer.getProdTopDrivers(Compiled Code)
at oracle.apps.ad.tools.configuration.Customizer.getAllDrivers(Compiled Code)
at oracle.apps.ad.tools.configuration.VersionConflictListGenerator.getAllConflicts(Compiled Code)
at oracle.apps.ad.tools.configuration.VersionConflictListGenerator.main(Compiled Code)
Exception in thread "main" ERROR: Version Conflicts utility failed.
Terminate.
how can i solve it .
your response will be highly appreciated
Regards ,,,
Mohamed Mahgob

Please see these docs.
Creating "appsutl.zip" Failed On "java.lang.NoClassDefFoundError: java/util/HashMap", What is the Potential Solution ? [ID 1310838.1]
AdMKAppsUtil.pl Failing Can't Find Java HashMap [ID 1338399.1]
After Applying Patch 9535311 Get java.lang.NoClassDefFoundError: java/util/HashMap Error [ID 1188327.1]
Thanks,
Hussein

J2se version="1.6+" in JNLP not working on a client with Java 1.5

Hi all,
In my deployment scenario I have two jnlp files, one for the app and one for its installer extension. The deployment process works fine on a client with J2SE 1.6 but there are some problems when the client has an older Java installed.
I am trying to enforce a J2SE 1.6 version for my app deployed with WebStart and I have found that
<j2se version="1.6+" ...> has no effect.
The solution that I have found was to change "1.6+" into "1.6.***" and thus the JWS will download and install JRE 1.6 (however I was expecting it to download the latest JRE (update 16) but it installs 1.6 update 7).
Could anybody confirm that?
Thank you in advance.

Thanks for the reply. I think Sun should update the auto-downloaded jre from 6u7 to the latest one.
But this is a minor issue. The problem from my post is that you cannot impose a j2se version number 1.6 or greater. IOW <j2se version="1.6+" ... > has no effect. I have tested this on a clean win xp machine that had installed only j2se 1.5.
I think it is a bug in jws but I want to check this issue with others.

j2se version=1.4??? What comes here for 1.4.0. LP

What is the correct tag for the limited production version ??
<j2se version=1.4-beta" href="http://java.sun.com/products/autodl/j2se"/>
does unfortunately not work.

This worked for me:
<j2se version="1.4.0-rc"
rc" href="http://java.sun.com/products/autodl/j2se"/>
What OS are you using? Under linux I get the 'cannot download requested JRE' error when I use this tag.

JNLP j2se version tag - possible bug ?

Hi,
I would like to confirm if this is a bug and if so, I will place an official bug report;
I'm using Java 1.4.1, or at least Java Web Start 1.2...
In the .jnlp file of my application I have this tag:
<j2se version="1.4+" href="http://java.sun.com/products/autodl/j2se"/>
I'm sure it worked at some time in the past, but now my application is not started with the latest J2RE on my machine.
I have these Java Runtime Versions Enabled in my Java Web Start 1.2 configuration:
1.4.1_01 (Yes, it was just released)
1.4.0
1.4.0_01
1.4.1
From the JNLP Spec, using "1.4+" should tell jws to use 1.4.1_01 ...
By default, when a customer install a new JRE, I will have to tell him
to deactivate his old JRE in JWS if it was problematic with my app !?
Martin

hello Martin,
Am having trouble even having my application run with just one JRE!
Am using spring layout, so works fine normally with 1.4.1_01 (the one thats installed on my machine). But when I specify the same as:
<j2se version="1.4+"" href="http://java.sun.com/products/autodl/j2se"/>
or
<j2se version="1.4.1_01" href="http://java.sun.com/products/autodl/j2se"/>
java web start loads the application but looks like its downloading a wrong JRE.. my screens dont show up properly (painting issues)..
any ideas?
would really appreciate your hel[p
Thanks
Gokul

J2SE Version for SP12

We are suing XI3SR1 on J2SE14206. Per OSS note 716604, SAP tells us to use J2SE 142_08 SDK or higer 142 versions as and when theya re avaialble.
How do we upgrade from J2SE14206 to J2SE14208?
We tried to install J2SE14208 on the server but it is not overwriting J2SE14206. As a result integration builder will not start. We are not able to apply further patches related to WEB AS JAva part.
Please advise.
Thanks,
Bhaskar

This worked for me:
<j2se version="1.4.0-rc"
rc" href="http://java.sun.com/products/autodl/j2se"/>
What OS are you using? Under linux I get the 'cannot download requested JRE' error when I use this tag.

J2se version tag

Please tell me if I have missinterpreted the functionality of the j2se version tag.
I have in my jnlp file something like this:
<resources>
<j2se version="1.4.1_02+" href="http://myServer/asp/jreinstaller.asp"/>
<jar href="mySignedJar.jar" main="false" download="eager"/>
</resources>
where the asp-file will generate a jnlp file that download and install a JRE 1.4.1_02 version...
I believe(d) that if the client machine already had jre 1.4.1_02 (or a higher version) installed - it would just fetch the wanted jar file, and if the client machine only had earlier versions of jre installed - it would download my 1.4.1_02 version before fetching the jar.
But when I test this, jws will start downloading the jre regardless of which jre(s) are already available at the client machine (whether its older or newer, i.e. 1.3.something or 1.4.2_01) . Only if the 1.4.1_02 version is already downloaded once - jws will skip attempting to download it again...
Please tell me if I'm using the j2se version tag incorrectly or if you have any other idea of why it does not behave as I thought it would.
/Matt

Actually, it is because the href tag is overloaded.
First: it says where to go look for a jre if non is available on the client.
Second: it uniquely identifies the jre. On any client there may be a 1.4.1 from Sun, and other ones from IBM, or Blackdown, or any other licensee.
Without an href, the jre specification is a "platform version".
<j2se version="1.4"/> means "anyones jre you find that implements the Java 1.4 specification"
In practice, Java Web Start (on windows) searches the registry for sun registered jre's, and so assigns them all the sun href (java.sun.com/products/autodl/j2se) . Also, when you ask for a "product version" Java Web Start contacts the default sun site.
It would have been beter to use a differant arg for "product version" than fo the download location such as:
<j2se version="1.4.1_02+" product="sun.com" hfre="http://jreserver.com" />
then you could ask for either a product or a platform version, either with or without an href, and attempt to download only if their was an href.
/Dietz

Simple request: use whatever j2se version you can find

I've got an application that will work with any version of java >= 1.2.
I am trying to set up my JNLP file so that it will handle that. I happen to have java 1.4 beta3 which I suspect is causing problems. That's the only version of java that I have installed right now, and I cannot figure out a way to say this in the JNLP file.
I have tried
<j2se/>
-> complains about no version number
<j2se version=1.2+/>
-> tries to dl 1.2
<j2se version=1.3+/>
-> tries to dl 1.3
<j2se version=1.4+
-> says that 1.4 isn't at the sun site
1.4-beta*
1.4.0-beta3
1.4.0-beta*
-> same thing
<j2se version="1.4 1.2+"/>
-> tries to go to the website at sun 1.4 1.2+..
What can I put? Am I just out of luck since I am using 1.4 beta? I'm sure I could fix the problem by installing an older version of java, but I suspect that some customers will be in this situation and I'd like to be able to very simply say: whatever j2se you've got.... use it!
Thanks,
Kirby

There is something about this in the documentation. The problem is because 1.4 is still in beta, and not FCS. It says:
Java Web Start does not consider a non-FCS JRE to match a request for a particular platform version. For example, a request of the form <j2se
version="1.4+"> does not consider an installed "1.4.0-beta" JRE as a match for the request. An application wishing to run under any beta J2RE must explicitly specify a product version, i.e.,
also using the href attribute in the j2se element. For example, a proper request for a beta JRE:
<j2se version="1.4-beta" href="http://java.sun.com/products/autodl/j2se"/>
So for a non-FCS version of Java, you need the href. If you want only 1.3 or 1.2 platforms, you can do
<j2se version="1.3+ 1.2+"/>

Javaws doesn't launches the application if javaws & j2se version matches

Javaws is throwing not able to launch application, if javaws & j2se element under jnlp has same version of jre.
I have 1.6.0_14 installed in my machine & i am using to launch a java application which has j2se elemnt specified as 1.6.0_14 the javaws throwing exception to install jre 1.6.0_14 , even after it exists. & if i change j2se to 1.6.0_13 than everything works fine.
Please help me on this.

Hi ,
Below is the complete jnlp file that i am using for launching yes i thaught of redusing the jnlp, here is the full jnlp:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jnlp spec="6.0+" codebase="http://test.server.com/apps">
     <information>
          <title>Hydra v4.6.0.119</title>
          <vendor>UBS A.G.</vendor>
          <update check="background"/>
          <description/>
     </information>
     <security>
          <all-permissions/>
     </security>
     <resources>
          <j2se href="http://http://test.server.com:<port>/JNLPDispatcher/downloadJRE" java-vm-args="-Xmx1024m -XX:MaxPermSize=128m" version="1.6.0_14"/>
          <property name="sun.java2d.nodraw" value="true"/>
          <property name="jonah.queryTimeout" value="0"/>
          <property name="jonah.connectionWaitTimeout" value="0"/>
          <property name="sun.java2d.d3d" value="false"/>
          <jar download="eager" href="http://test.ap.com/myapp.jar"/>
          <jar download="eager" href="http://test.ap.com/antlr.jar"/>
          <jar download="eager" href="http://test.ap.com/browser.jar"/>
          <jar download="eager" href="http://test.ap.com/calendar.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-beanutils.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-codec-1.3.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-collections.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-dbcp.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-digester.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-discovery-0.2.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-fileupload.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-httpclient-3.0-rc3.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-lang-2.1.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-logging-1.0.4.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-pool-1.3.jar"/>
          <jar download="eager" href="http://test.ap.com/commons-pool.jar"/>
          <jar download="eager" href="http://test.ap.com/servercore.jar"/>
          <jar download="eager" href="http://test.ap.com/myapp-upload.jar"/>
          <jar download="eager" href="http://test.ap.com/myapp-client.jar" main="true"/>
          <jar download="eager" href="http://test.ap.com/samplelang.jar"/>
     </resources>
     <application-desc main-class="com.ubsw.eq.risk.hydra.ui.Main">
<argument>-ApplicationEnv</argument>
<argument>MyAPP/TEST</argument>
<argument>-ApplicationLaunch</argument>
<argument>silent</argument>
<argument>-ApplicationVersion</argument>
<argument>1.90</argument>
<argument>-CoreStub</argument>
<argument>true</argument>
</application-desc>
</jnlp>

J2SE version

Hello! I am new to Java programming and I was wondering which version of J2SE would be best to download v 1.3.1 or v 1.4 Beta 3? The only reason I am not downloading the newest version without asking is because it is a beta version. Could this be a problem? Would it be better to wait for a non-beta version? If I download the beta version (or the earlier 1.3.1 version) and want to upgrade later would I be able to do it just by installing the new version or would I have to do something more? Oh and one more thing: what are these icons next to versions 1.3.1 and before that look like ... CDs (that's what I thought anyway!) do they mean something?
Thank you very much in advance!

If you're new, it really doesn't matter. If your purpose is to develop an production app, then I'd stay with the non-beta. If you're hacking/learning, the beta is fine (worst risk is you find a bug and cannot determine if it's your code or the beta, rare though!)
As far as upgrading, the JDKs are very good about backwards compatitiblity, so if you went 1.3 and then upgraded, you'll be fine with a simply install. Of course, you can install more than one JDK, and many do, to run your code agaisnst multiple API sets..
bRi

J2se tag with differents versions ????

Hi,
I am new to jnlp,
in our jnlp file we have :
<resources>
<j2se version="1.4.2*" href="http://java.sun.com/products/autodl/j2se" initial-heap-size="100M" max-heap-size="200M"/>
the application work only with 1.4.2 and 1.5 but not with 1.6 ,
How can we controle the use of 1.4.2* and 1.5 but not 1.6 ??
Thanks
Edited by: abdelmajid on Dec 6, 2007 12:36 PM

The "JavaTM Network Launching Protocol & API Specification (JSR-56) - Version 6.0", in "appendix A.", suggests to me that this should work if both versions are mentioned in the version string, separated by a space.
<j2se version="1.4.2* 1.5*" href=... />
Though I suspect this form will tend to choose 1.5 in preference to 1.4.2.
<j2se version="1.5* 1.4.2*" href=... />
(The ordering is only a suggestion to the Plug-In - it might choose the 'smaller JRE' to download - if it comes to that.)
A side note about the use of the href attribute pointing to the autodl URL. Auto-download is effectively 'dead'. It only ever worked with combinations of Win/IE (notably not Win/FF), and does not work with the latest Vista OS. A comment in release notes for 1.6 added that the VMs would need to be ..rebuilt (or something) before it could possibly work, but did not indicate that anybody at Sun was about to rush in to do that. AFAIU - Sun has withdrawn all autodl VMs.
Does the application actually break in 1.6? Or is it just that it has not been tested using 1.6?

Unable to launch the application after upgrading Java to version 1.6.0_26

After upgrading Java to version 1.6.0_26 in Windows XP my web start throwing Exception. It works fine in Ubuntu with Java 1.6.0_24 and in Windows with older versions of Java 1.6.
Exception doesn't say anything:
java.lang.NullPointerException
       at com.sun.javaws.Launcher.executeApplication(Unknown Source)
       at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
       at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
       at com.sun.javaws.Launcher.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)Same as java console ouput
Java Web Start 1.6.0_26
Using JRE version 1.6.0_26-b03 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\esod
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
0-5: set trace level to <n>
#### Java Web Start Error:
#### nullMy Jnlp file looks like this
<jnlp spec="1.0+">
<information>
   <title>Editor</title>
   <vendor>Comapny name</vendor>
   <homepage href="http://company_urll" />
   <description>Editor/description>
</information>
<resources>
   <j2se version="1.6+" />
   <property value="true" name="javaws.cfg.jauthenticator" />
   <jar href="http://192.168.79.33:7070/resources/applet/formeditor.jar" />
</resources>
<security>
   <all-permissions />
</security>
<application-desc main-class="pl.rdata.formeditor.FormEditor">
   <argument>[email protected]</argument>
   <argument>rLq3347491</argument>
   <argument>17</argument>
   <argument>
   http://192.168.79.33:7070/formeditor/formManagerService.service</argument>
   <argument>
   http://192.168.79.33:7070/formeditor/customDataTypeManager.service</argument>
   <argument>
   http://192.168.79.33:7070/formeditor/authorizationService.service</argument>
   <argument>2</argument>
</application-desc>
</jnlp>This application is self signed.
When I download jar file to disk I can run it with command java -jar and it works fine.
After downloading jar I made some tests changing line <jar href="http://192.168.79.33:7070/resources/applet/formeditor.jar" /> in Jnlp file.
When I changed it to <jar href="formeditor.jar" />, and have jar in folder it works.
When I changed it to <jar href="file:///C:/formeditor.jar"> it is not working (same exception).
In every case jar is download correctly and it pass verifying.
can anyone help?
Regards
Michal

867322 wrote:
When I changed it to <jar href="formeditor.jar" />, and have jar in folder it works.Okay, so you at least have a workaround.
can anyone help?Search the bugs database to see if someone else already reported this; if not create a new bug entry. Whatever mistake you could make, you should not be getting a NullPointerException as a result so this is at the very least a bug in the error handling of webstart.
But just some observations to try and see if you can make a difference (which is added input for your bug report). If I check JNLP examples, I see that the url specified is usually without a protocol, so it could be like this:
<jar href="/resources/applet/formeditor.jar" />The JNLP should be on the host that you service the jar from, so Webstart can fill in the host information for itself.
Also you provide a main-class; if the jar manifest specifies a main-class (and it should) you don't need to specify it in your JNLP file.

Can Web Start call earlier installed versions on client machine?

Can Web Start invoke earlier installed versions of the
JRE on a client machine, without invoking a download?
I ask because I have tried to so, unsuccessfully,
using the versions attribute of the j2se element.
In the usenet thread 'Jar test, with 1.4 VM?',
Usenet Message ID:
[email protected]
http://groups.google.com/groups?selm=1170640609.025666.236030@s48g2000cws.googlegroups.com
(follow the Google link at the top, to the thread)
I was attempting to confirm that a Jar file I
was deploying, was 1.4 compatible.
The test failed, because despite that the (1)
user who attempted it had a working 1.4.2 install,
the JNLP file (which declared version='1.4'),
was prompting for a download. The user was
not prepared to do that, understandably -
that was exactly what I was trying to avoid
doing, myself.
Since then, I did further testing locally -
trying to get a 1.5 launch when my current
Java is 1.6 - I have a number of 1.5 versions.
No request for '1.5', '1.5.0_08' or '1.5*' worked
(OK - that last one was just a WAG*), every time
I was prompted for download (which also failed,
as an aside!).
What am I getting wrong?
Do I misunderstand the intent of the j2se element
finding earlier verions? Is it only versions that
were installed by web start?
Is my understanding of how to use the version
attribute, incorrect?
* Where are the detailed instructions on the
allowable forms of the version attribute?
Neither the spec. nor developers guide seem
to go into it in any detail. Some of the forms
I have seen around the forum were (AFAIR)..

version="1.4 1.5+"

version="1.4"

version="1.4.2_13+ 1.5+"FWIW - here is the JNLP I am currently using
for the test, it is 'live and public'..
<?xml version='1.0' encoding='UTF-8' ?>

<jnlp spec='1.0'
    codebase='http://www.athompson.info/family/'
    href='thompson-1.4.jnlp'>
<information>
    <title>Thompson Family Genealogy</title>
    <vendor>Andrew Thompson</vendor>
    <description kind='one-line'>
      The ancestors of William Robert Ramshaw Thompson
    </description>
    <offline-allowed />
    <shortcut online='false'>
      <desktop/>
    </shortcut>
</information>
<resources>
    <j2se
      version="1.4"
      href="http://java.sun.com/products/autodl/j2se" />
    <jar href='genj-applet.jar' main='true' />
</resources>
<applet-desc
    main-class='genj.applet.Applet'
    name='genealogy'
    codebase='./index.html'
    width='300'
    height='170'
    >
      <param name='GEDCOM' value='thompson.ged' />
      <param name='ZIP' value='thompson.zip' />
</applet-desc>
</jnlp>

Using your tips, I was able to find the 1.5
JRE's listed in the Java control panel
(of an XP Pro box) and see they had no
checkmark for 'enabled'.
After enabling 1.5.0_08, I was successfully
able to launch the application (OK - applet
really) using the 1.5.0_08 JRE.
Thanks.
As an aside, I had to specify '1.5.0_08'
exactly to get that JRE. This is fine for
local testing, but sometimes it is handy
to ask others to help test via the web,
and it would be nice if I could make it less
specific (e.g. '1.5', to get any installed
and enabled JRE that is a 1.5 variant)
Do I understand wrong? Should that work,
to specify '1.5' and get a '1.5.0_08' JRE that
is installed and enabled?

How to stop version check that happens in the background after timeout?

Hi all,
I have a problem that seriously makes my swing application (installed using webstart) very slow for some time.
Steps to reproduce my problem :
1. Deploy the jars of application in the web server running on Machine A( either in LAN or running on public IP).
2. Download the application on Machine B using the link.
3. Shutdown Machine A.
4. Now try to start the application on Machine B. The starting of the application has become very slow.
After some time(long enough) the application is started. Even now, the application is slow for first few minutes.
Below is the part of jnlp that we used.:
+<?xml version="1.0" encoding="utf-8"?>+
+<jnlp spec="1.0" codebase="$$codebase" href="LaunchMyApplication.jnlp">+
+<information>+
+<title>My Application</title>+
+<vendor>XYZ</vendor>+
+<description kind="short">XXXXXXXX</description>+
+<icon href="../../../../images/myapp_splash2009.gif" kind="splash"/>+
+<icon href="../../../../images/myapp_logo.jpg"/>+
+<offline-allowed/>+
+</information>+
+<security>+
+<all-permissions/>+
+</security>+
+<resources>+
+<property name="abc.type" value="client"/>+
+<j2se version="1.5" initial-heap-size="48m" max-heap-size="256m"/>+
+     +
+     +
+     ...........+
+     ..........+
+     +
+</resources>     +
+<application-desc main-class="com.abc.xyz.Login">+
+     <argument>..........</argument>+
+</application-desc>+
+</jnlp>+
My assumsion is
When I start my application, version checking will happen. But the cache server system(machine A) is not available. Due to this initial slowdown has occurred.
After the timeout has occured, my application has started. Since the version checking continuous in the background, my application is again slow.(Even when my application server and database system are in the same LAN of my client machine).
This slowdown is certainly not desirable.
This slowness isn't there when there Machine A( in which my webserver is installed) is running and my webserver (Tomcat 5.0 in my case) is not started.
Is my assumsion is correct?
If correct, how do I stop version checking process that happens in the background after initial timeout?
I think update check and policy attribute may not help me as I wanted to stop this background version check altogether. Also, my java sersion is 1.5_0_14.
Please help me out in this.
Thanks in advance..,
Chakri.

Talk to Apple here...
http://www.apple.com/feedback/

j2se version="1.4.2*" ??

Similar Messages

Maybe you are looking for