Is nw 2004s j2ee engine built with JDK 1.4?

i am currently running NetWeaver 2004 WAS 6.40 J2EE Engine SP14. from the version.txt file, i see this line:
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
i understand that during installation of j2ee engine i can specify jdk versions such as 142_09 etc. but i have a specific issue with the dbpool service provided by the j2ee engine. since the engine is itself built with jdk 1.3.1, it doesn't and couldn't support some of the jdbc apis introduced since jdk 1.4.
so i'd like to know which version of j2ee engine starts to be built with jdk 1.4?
if anyone has nw 2004s installed, could you pls check your version.txt file and let me know what the "Build java version" is?
kind regards,
wentao

Hi wentao
check the version from following.
http://host:j2eeport/sp
login with administrator user.
exand server node ->j2ee->version information click
under task click on run u get the current version .
regards,
kaushal

Similar Messages

[svn:bz-trunk] 20682: remove the tomcat 7 jar as now (built with JDK 1.6)

Revision: 20682
Revision: 20682
Author:   [email protected]
Date:     2011-03-08 09:19:53 -0800 (Tue, 08 Mar 2011)
Log Message:
remove the tomcat 7 jar as now (built with JDK 1.6)
Removed Paths:
    blazeds/trunk/modules/opt/lib/catalina-708.jar

One possibility is that the java path has different versions of java installed in the same place. So one part of java runs with version X and then that piece attempts to use a different piece but that piece is version Y.

J2EE engine restart with java.lang.OutOfMemoryError Java heap space

Hi
I hope someone can help me, I have an error on my J2EE engine.
My portal restarts only when I click on User - Administration - Identity Management.
Here is the log error.
Exception id: [000000000000005B0000001C0000098800045ACD637E87AB]#
#1.5^H#0000000000000059000000690000098800045ACD6EF06673#1225738282886#com.sap.engine.frame.Environment##com.sap.engine.frame.
Environment#J2EE_GUEST#0##host_SID_4130050#J2EE_ADMIN#40cf7230a9d811dda9f9000000000000#SAPEngine_Application_Thread[impl:3
]_13##0#0#Error#1#/System/Server/Critical#Plain###FATAL: Caught OutOfMemoryError! Node will exit with exit code 666#
#1.5^H#00000000000000590000006A0000098800045ACD6EF06833#1225738282886#com.sap.engine.frame.Environment##com.sap.engine.frame.
Environment#J2EE_GUEST#0##host_SID_4130050#J2EE_ADMIN#40cf7230a9d811dda9f9000000000000#SAPEngine_Application_Thread[impl:3
]_13##0#0#Fatal#1#/System#Java###FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
[EXCEPTION]
#1#java.lang.OutOfMemoryError: Java heap space
        at java.lang.ClassLoader.defineClass0(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
        at com.sap.engine.services.deploy.server.ApplicationLoader.defineClassWithInterception(ApplicationLoader.java:168)
        at com.sap.engine.services.deploy.server.ApplicationLoader.loadLocalClass(ApplicationLoader.java:140)
        at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:127)
        at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
        at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingComp.<init>(InternalAssignUserMappingComp.
java:173)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
        at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createInstanceIfDemanded(ComponentUsage.java:728)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getImplementingInterfaceViewInfo(ComponentUsage.java:403)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getViewManagerFor(ClientComponent.java:305)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:628)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:694)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
        at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
Thanks for your help

pretty obvious to me "java.lang.OutOfMemoryError: Java heap space"
Read,
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/(Kernel)OOM
or
java.lang.OutOfMemoryError: Java heap space
those links should give you a fairly good idea on how to solve the issue.
Regards
Juan

J2EE Engine Stopped with Error 11113

Hi All,
After I changed some values in the Portal UME to connect to ECC 6.0, after the restart of cluster the J2EE is not coming up and getting stopped with Error 11113.
I have changed the Datasource to ABAP and tried resetting the values in Configtool as per the previous threads in the forum but could not get my J2EE engine up.
Please find the last some last line of "std_server0.out" file:
stdout/stderr redirect
node name   : server0
pid         : 3456
system name : EP7
system nr. : 01
started at : Wed May 07 12:35:19 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 5340] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 7.00   PatchLevel is starting...
Loading: LogManager ... 562 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 203 ms.
Loading: ThreadManager ... 62 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 234 ms.
Loading: LockingManager ... 250 ms.
Loading: ConfigurationManager ... 2203 ms.
Loading: LicensingManager ... 31 ms.
Loading: CacheManager ... 172 ms.
Loading: ServiceManager ...
Loading services.:
Service memory started. (31 ms).
Service runtimeinfo started. (172 ms).
Service cafeucc~api started. (281 ms).
Service cross started. (219 ms).
Service timeout started. (156 ms).
Service file started. (500 ms).
Service userstore started. (78 ms).
Service jmx_notification started. (94 ms).
Service trex.service started. (156 ms).
Service p4 started. (282 ms).
Service classpath_resolver started. (46 ms).
Service log_configurator started. (7172 ms).
Service locking started. (0 ms).
Service naming started. (515 ms).
Service http started. (703 ms).
Service javamail started. (297 ms).
Service failover started. (219 ms).
Service appclient started. (203 ms).
Service ts started. (250 ms).
Service jmsconnector started. (297 ms).
Service licensing started. (32 ms).
Service cafeugpmailcf started. (281 ms).
Service connector started. (531 ms).
Service webservices started. (953 ms).
Service iiop started. (672 ms).
Service deploy started. (20344 ms).
Service MigrationService started. (47 ms).
Service bimmrdeployer started. (16 ms).
Service configuration started. (31 ms).
Service dbpool started. (2453 ms).
May 7, 2008 12:35:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'password' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
receiverid_guest=master
poolmaxwait=10000
client=800
user=sapuser
sysnr=02
poolmaxsize=10
ashost=SAP4
receiverid=master
May 7, 2008 12:35:57 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
May 7, 2008 12:35:57 PM   com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] Fatal:
May 7, 2008 12:35:57 PM   com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_78] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: 'password' missing
     at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
May 7, 2008 12:35:57 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Please take a look and help me in resolving this problem. Do let me know you need anymore other logs for analysis ?
Regards,
Srikar

Hi Karthik,
I have checked all the UME properties and are fine. I am trying to connect to ECC 6.0 Clnt 800 with Communication user I created called "portaluser" and the pwd along with system number and application host.
I tried giving all the details in Configtool > Ume properties but again the same problem J2EE is getting stopped with the same error.
About the SAPJSF user, it has been created while installation as a Dailog user in the EP system. I logged into the EP system and checked that in SU01. It there but not as a communication user but as a Dialog user.
Can you let me know what could be the issue ?
Regards,
Srikar
Edited by: Srikar Vankadaru on May 8, 2008 7:59 PM

How to logon the j2ee engine with logon group

hi everyone,
I have installed an HA j2ee engine system with MSCS.
But i donot know how to logon the DI&CI with logon group like ABAP system
Thanks very much
Regards
Peter

http://help.sap.com/saphelp_nw70/helpdata/EN/b5/e8239ef7bd494f896a84625d4b688f/frameset.htm

Local J2EE engine needed for NWDS

Hi Everybody,
I am new to NWDI. We want to use NWDI to make changes to ESS applications. The NWDI is installed with the Portal installation on the server.
I installed the Netweaver Developer studio on my Laptop. I didnu2019t install a local J2EE engine only the JDK. My question is do I need a local J2EE engine before I can start using the NWDI. I want to create a track and import the development into NWDS.
Edited by: Stoffel Erasmus on Aug 25, 2009 3:48 PM

Stoffel,
It's not necessary to have local j2ee engine.
to setup access to NWDI from NWDS go to windows-preferences - SAP J2EE Engine - select remote and give the host and port
go to widnows - preferences - java development infrastructure - development configuration - give the sld path
go to DTR perspective - create a DTR client by giving some name and DTR url and workspace
go to Development Configurations perspective - right click on Local Development- Import configuration
Thanks
Bala Duvvuri

What is the difference between J2EE Engine vs WAS in SAP

Hello All,
What are the differences between J2EE engine included with BW 3.0B and the WAS 6.20 ? what are the limitations of J2EE engine in terms of functionality.
Thanks in advance
Ravi

Hello Nitzan,
Thanks for the response. Just to clarify my question, There is a J2EE engine as part of BW 3.0B. What is the difference in terms of functionality of J2EE engine which comes bundled with BW 3.0B versus say WAS 6.20.
1. The J2EE engine which comes bundled with BW 3.0B, is it a run time or a full product where a java app can be developed and deployed to integrate with BW or do you need WAS for that purpose.
Thanks & regards
Ravi

J2EE engine Start ...Problem

I have Installeld SAP NetWeaver 04 SR1 successfully ..The Manual says
Start the J2EE engine by entering the following URL in your browser
http://<hostname>:5<J2EEinstance_number>00
The J2EE engine Start Page should appear.
But I am Not able to see the J2EEEngine StartPage .I have checked the Sap Management COnsole the SAP DB Instance,SCS as well as J2EE engine instance with dispatcher and server processes is running fine and is in green color.
Can anyone please suggest me as to how to proceed so as to get the J2EE engine Start Page.

Hi,
Check this.
Port No. is 50000+(100*instance_no)
regards
Anand.M

Issue in Communication of SAP R/3 6.4C with SAP J2EE Engine 6.40.

Hello,
We have an application deployed in SAP J2EE engine 6.20. From SAP R3 (SAP R/3 version is 6.4C), We are communicating to the application deployed in SAP J2EE Engine 6.20 using RFC protocol. EJB module (Deployed in SAP J2EE Engine 6.20) which is being invoked from a Function Module using RFC protocol has the same name as the Function Module name. We were able to communicate to SAP J2EE Engine 6.20 this way.
Currently, I have deployed the same application in SAP J2EE Engine 6.40. I have followed the same procedure which i have used while depolying and working with SAP J2EE Engine 6.20. But, it is not working, and i was not able to communicate to SAP J2EE 6.40, the same way i did in SAP J2EE Engine 6.20.
Please let me know whether the procedure for communicating to SAP J2EE Engine 6.40 has changed in comparison with SAP J2EE Engine 6.20.
Also,Any pointers regarding RFC and JCO implementation in SAP J2EE Engine 6.40 willl be helpful.
Thank you.
Regards,
-Shabir Rahim.

Hi,
compare to 4.7
1.New ABAP editor added like if u write code in abap editor ,using if coditions and select statments it automatically shows the link endif, like if .. endif,select ...endselect.
2.New abap debugger compare to the classic debugger.
3.DBACOCKPIT
Missing indexes of various database tablesu2019 and the transaction to reactivate all the missing indexes is u2018DBACOCKPITu2019. Below is the screenshot of the transaction DBACOCKPIT.
Regards,
Madhu

Port issue with j2ee engine, http service provider

hi gurus,
on two of our standalone j2ee servers, the j2ee engine is up and running fine. from the mmc everything shows green including messager server.
but when i connect to the j2ee page using browser either from the client machine or on the server it never gives me an error message but the status bar keeps processing. never throws any sort of dispatcher or 500 error messages.
There were some GRC-Virsa components deployed over the weekend not sure if that had changed something.
After intial research the port information in the HTTP service provider showed 80 for http and 443 for ssl (https)so i had manually changed it to 50000 and 50001 from config tool respectively , restarted the server.
After the restart the j2ee page came up and the very second http request it goes to the loop again with no error message, whats the reason behind this sort of behavior. i have made the port changes over the whole cluster and restarted.
surprising it works only for the first time after restart, the very second http request never accepted by dispatcher/server process , no error message though.
environment, nw04s with plain j2ee, windows 2003, sql2008
please assist.
-durga

thanks sean for responding, infact the issue is resolved yesterday.
Reason due to insufficient application threads and make sure the right port defined in HTTP service provider. So fixing these two things resolved the issue
Thanks,
Durga

Proper way to exit with a j2ee java app running in the NW70 j2ee engine

Hello,
I am working on migrating an app and it's ear from j2ee 6.20 to 7.0. It deploys okay, but when invoked, the j2ee server restarts. Looking at the part that fails, its trying to create a jco connection, which fails and then it catches the failure and does a stack dump and a System.exit(1). It shuts down and restarts at that point. Is System.exit(1) the proper way to exit a java app that is running within the j2ee engine? If it is, is it possible I am picking up the wrong System.exit and need to use an SAP specific one? I inherited the code, but not the IDE it was written with.
Thanks,
Paul D. Chamberlain

Hi,
Answered my own question. System.exit(1) should not be used. Return works.
Paul D. Chamberlain

Webdynpro application errors with SLD,J2EE Engine - JCOs probelem

Hi,
I have developed a small webdynpro application
1. Passing 2 values to RFC
2. Getting result contents from RFC and displayed in a table.
I am getting following errors:
u2022     SLD is not accessible. Check SLD Data Supplier service settings.
u2022     Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'.
u2022     ACCESS.ERROR: Authorization check for caller assignment to J2EE security role [SAP-J2EE-Engine : administrators].
u2022     application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: An attempt to write after the stream had been closed.
Exception id: [0002559A6FCB0077000000A0000CF0E8000460EC9406F721]
u2022     application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: An attempt to write after the stream had been closed.
at
Please suggest me.

Hi Kiran,
You need configure SLD and JCo destinations in your j2ee engine..
Check this [article |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5] to create the SLD and JCo destinations.
regards,
Siva

Class conflicts with third-party libraries on j2ee engine

Hi,
I am deploying a repository manager into EP. In my repository I referenced javax.xml.namespace.QName, which conflicts with the one declared in jaxrpc.jar in j2ee/cluster/server0/bin/ext/webservices_lib.
I am not very clear about how NW j2ee engine loads classes, but it seems that it loads classes in j2ee/cluster/server0/bin/ext/webservices_lib first. As a result, I got a class confliction error:
java.lang.NoSuchMethodError: javax.xml.namespace.QName.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
If I remove QName.class from the jar in webservices_lib, it works fine, but this not the right way. I have read Note 990854, but not clear about how to do. Could anyone give any help?
Thanks,
Ray

Close this thread as it makes little sense.

What J2EE engine for SAP NetWeaver 7.0 (2004s) Trial Version - Full Java Ed

Hi experts,
I am installing SAP NetWeaver 7.0 (2004s) Trial Version - Full Java Edition. For that
1.what J2EE engine sholud be installed?
2.where is it available?
3.give Installation procedure for this.
They have given it as trial version will it expire soon.
Regards,
karthik.

hi karthi,
This Section provides information on how to prepare the standard installation of the SAP System.
The below mentioned steps are to be done before going for a installation.
1.     Check the Resolution of the Screen - Screen resolution to be set to 1024 X 768.
2.     Check for Screen Saver Settings - Screensaver to be set to OFF
3.     Check for Installed OS and Service Pack.
4.     Check for all the Hardware related details Installation of drivers
5.      Check for Data Throughput for Network Adaptors.
Right Click the Local Area Connection -> Select Properties -> Select File & Printer Sharing for Microsoft Networks and click on Properties -> Click radio button for Maximize throughput for Network Connection
go to SAP market place web site u got more information about this
Regards,
P.Manivannan.

Problem with SAP PI7.0 J2ee Engine starting

Hi,
Problem with SAP PI7.0 Server
I am using AIX6.1 and p570
J2ee engine is not starting but I am able to login to ABAP engine.
When I am trying to long in through internet explorer it is not working.
How to check J2ee engine started or not.
If it is not started then how to start J2ee engine.
If J2ee engine problem is there then how to solve the issue and where to check to solve the issue.

Hi,
How to check J2ee engine started or not.
Check the url http://ipaddress:5xx00/index.html
If this url shows you the system info page then you j2ee engine is up.
If it is not started then how to start J2ee engine.
Check your server0.log file.
If J2ee engine problem is there then how to solve the issue and where to check to solve the issue.
Check for the problems in log file and do search in sdn or in the market place you will get plenty of info read them and try to resolve the errors.
Regards,
Vamshi.

Is nw 2004s j2ee engine built with JDK 1.4?

Similar Messages

Maybe you are looking for