Is JDK 5.0 support RMI?

Hi,
Is JDK5.0 support RMI(remote method invocation)?
Thanks,

I'm not sure I understand the question, but RMI has been part of J2SE for years now.
See this chart: http://java.sun.com/j2se/1.5.0/docs/images/j2se5.gif
hth,
-Alexis

Similar Messages

JDK is NOT supported for 7.1 anymore?

I get the info that for whatever 7.1 (e.g. PI7.1, BI7.1, etc.), JDK is NOT supported anymore.
SAP JVM is installed during the upgrade to 7.1 .
Is that true? Thanks!!

Hi Ashley,
This is true. You can refer the same in product availability matrix (PAM) under https://service.sap.com/pam
Cheers........,
Raghu

Doesn't iWS support rmi?

Hello!!!
I am trying to use rmi on iWS7.0, but I hava met the message like this
"Exception in thread "main" java.rmi.MarshalException: Transport protocol
not supported by server?
Does iWS support rmi?
Thandks advanced!!!

Hi Park.
How exactly are you trying to use RMI? Are you working it as a client or a
server? Need more info here.
Thx,
- deepak
Park wrote:
Hello!!!
I am trying to use rmi on iWS7.0, but I hava met the message like this
"Exception in thread "main" java.rmi.MarshalException: Transport protocol
not supported by server?
Does iWS support rmi?
Thandks advanced!!!--
Deepak Balakrishna
Senior Technical Manager
Product Management
Sun|Netscape Alliance

JDK/JRE Version support for Oracle Lite

Hi,
We have developed an application using jdk 1.4.x which also using Oracle9i Lite 5.0.2 release as a database. Application behaves normal except while closing it throws java exception (Exceptio Guard Page Exception) error.
Is it because of the JDK Version we are using? What is the JDK/JRE version level supported by Oracle Lite.
Thanks
Krishna

Right
I got the same problem too.
When my program and oracle 9i lite is running under JRE1.3.1, everything is ok.
However, when i migrate the jre to 1.4.x, the program must fail and report DLL exception after closing.
So trouble~!

Does JDK 1.5 support hugepages on Linux

JRockit JVM has the facility by which it uses hugepages if available to store its heap within the Linux kernel. I am trying to find a similar facility within Sun's JDK 1.5. Any clues?
Thanks
rh

The JDK has had large page support on Solaris for many releases but it is relatively new on Linux. There are a few issues with some older kernels and the feature is disabled by default. The -XX:+UseLargePage option is used to enable it. To use this option you need to be using 5.0u5 (just released), or a mustang (Java SE 6.0) build.

Does OC4J support RMI/IIOP connections ?

Hi,
I have only one question :
Does OC4J support IIOP connections ?
I'd like to connect as EJB client to OLAPService on Oracle9i server (CORBA object), but I can't.
Thanks in advance

Thanks for your timely post Debu.
I would like to state that I read and followed the guides (same files as those ponted by the links you just provided) and tried this:
1. Sample J2EE Application using ORMI in OC4J Standalone (this works ok)
2. Same but now using ORMIS (this also works fine)
3. Tried same J2EE App using IIOP; took these steps:
3.1 commented out the rmi.xml security lines,
3.2 enabled ports in internal-settings.xml,
3.3 changed the jndi.properties - now using corbaname URL,
3.4 enabled the IIOP stub generation in the JVM settings at oc4j startup, and finally
3.5 deployed the EAR using the generateIIOP flag.
The result: the exception I posted above
4. Tried with IIOP/SSL, did these steps:
4.1 configured the keystore settings in both internal-settings.xml and ejb_sec.properties
4.2 and added <ior-security-config> config elements to orion-ejb-jar.xml.
The exception here is a little bit different:
client started...
In IIOPInitialContextFactory ..
In IIOPInitialContextFactory getInitialContext..
1/08/2006 07:07:10 PM com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl <init>
ADVERTENCIA: ORBUTIL.connectFailure
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:1739)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:1757)
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.<init>(SocketFactoryConnectionImpl.java:74)
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl.createConnection(SocketFactoryContactInfoImpl.java:77)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:121)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:214)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:345)
at com.sun.jndi.cosnaming.CNCtx.initUsingCorbanameUrl(CNCtx.java:321)
at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:247)
at com.sun.jndi.cosnaming.CNCtx.createUsingURL(CNCtx.java:85)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURLIgnoreRest(iiopURLContextFactory.java:56)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURL(iiopURLContextFactory.java:61)
at com.sun.jndi.url.iiop.iiopURLContextFactory.getObjectInstance(iiopURLContextFactory.java:34)
at oracle.j2ee.iiop.IIOPInitialContextFactory.getInitialContext(IIOPInitialContextFactory.java:76)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at hello.HelloClient.main(HelloClient.java:31)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
at oracle.oc4j.corba.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:398)
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.<init>(SocketFactoryConnectionImpl.java:58)
... 19 more
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:460)
at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
at oracle.oc4j.corba.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:389)
... 20 more
javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 20
      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:362)
      at com.sun.jndi.cosnaming.CNCtx.initUsingCorbanameUrl(CNCtx.java:321)
      at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:247)
      at com.sun.jndi.cosnaming.CNCtx.createUsingURL(CNCtx.java:85)
      at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURLIgnoreRest(iiopURLContextFactory.java:56)
      at com.sun.jndi.url.iiop.iiopURLContextFactory.getUsingURL(iiopURLContextFactory.java:61)
      at com.sun.jndi.url.iiop.iiopURLContextFactory.getObjectInstance(iiopURLContextFactory.java:34)
      at oracle.j2ee.iiop.IIOPInitialContextFactory.getInitialContext(IIOPInitialContextFactory.java:76)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
      at javax.naming.InitialContext.init(InitialContext.java:219)
      at javax.naming.InitialContext.<init>(InitialContext.java:175)
      at hello.HelloClient.main(HelloClient.java:31)
Caused by: org.omg.CORBA.COMM_FAILURE:   vmcid: SUN minor code: 201 completed: No
      at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:1739)
      at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:1757)
      at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.<init>(SocketFactoryConnectionImpl.java:74)
      at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl.createConnection(SocketFactoryContactInfoImpl.java:77)
      at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
      at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:121)
      at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:214)
      at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
      at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:345)
      ... 12 more
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
      at oracle.oc4j.corba.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:398)
      at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.<init>(SocketFactoryConnectionImpl.java:58)
      ... 19 more
Caused by: java.net.ConnectException: Connection refused: connect
      at sun.nio.ch.Net.connect(Native Method)
      at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:460)
      at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
      at oracle.oc4j.corba.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:389)
      ... 20 more
NamingException: Cannot connect to ORB

JDeveloper 10.1.2.0.0 JDK 1.5 support

Hi all!<br>
Does JDeveloper 10.1.2.0.0 support projects using JDK 1.5?<br>
Regards,<br>
Matthias

Hi all,
I've tried setting up Jdeveloper 10.1.2 to use JDK 1.5 but keep getting the following error when building.
Error: initialization error: class file has wrong version 49.0, should be 45.3 or 46.0 or 47.0 or 48.0 ....
Does anyone have a workaround for this kind of issue?

Which JDK is JSF supported for?

Is JSF Supported for JDK 1.3.1_03?

I think it's more of a J2EE SDK support issue and I think (but am not sure) you need J2EE1.4.
You may want to try this question on the Sun Java Studio Creator forum:
http://swforum.sun.com/jive/forum.jspa?forumID=123
Probably not the most appropriate forum, but more correct than this forum which is focused on the Sun Web Application Framework (JATO).
craig

JDK 1.6 Supported Regular Expression Optimizations

Hi all,
Thanks in advance for your help.
I'm reading Mastering Regular Expressions my Jeffrey Friedl. In Chapter6, the author discusses many regex engine optimizations that are out there. Is there a complete list of these optimizations that are supported by the latest version of JDK 1.6?
Thanks.

Hi
Check this Note 716604 - Access to Sun J2SE and recommended J2SE options
http://java.sun.com/products/archive/
Regards
Uday

JDK 1.3 support and US DST tz db updates

Sun support,
Please point me to your official statement on whether or not you support JDK 1.3 any more - last I remember you said JDK 1.3 was going to be end-of-life'ed once Java 6 is released - well, you've done it - please supply us with your official word.
Regarding US DST changes for 2007 (as described here http://java.sun.com/developer/technicalArticles/Intl/USDST/) - can you clarify which JDKs can be updated with the tzupdater tool - does this apply to ALL 1.4 and later JDK releases ? What is the target file that is updated by this tool and is it possible to share this file among JDK/JRE distributions (eg via a symlink to a common location) ?
Many thanks
Bernard Cena

what about the special forums for JDK or JRE questions?
Or a simple search of the site would have provided you with the information you need inside the space of a few minutes, rather than needing days to wait for answers to forum questions which will likely just tell you to look on the site.
There was an article about this on the frontpage just a short while ago as well, listing every release that's compatible.

Jdk 1.4 support for websphere studio 5.1

I am using Websphere application studio version 5.1 which uses jdk1.3 and not 1.4. My project requirement forces me to use jdk 1.4 swing components as 1.4 swing version has lot more than that of 1.3 (for e.g. masking for input field and lot more). Does anyone have an idea how can i use 1.4 (at least swing) into websphere application studio 5.1 (which uses jdk 1.3)?? or does anyone know how can i point/force websphere studio to use jdk version 1.4?
I would highly appreciate any pointers/reference material or anything like that.
Thanks,
Vicky

mriyer,
The Windows binaries in 2.3.10 were built using JDK 1.5 and did not use a -target 1.4 flag. You did the right thing by rebuilding.
Regards,
George

Which version of OC4J 9.0.2 or 9.0.3 supports jdk 1.4

does anybody know which version of OC4J 9.0.2 or 9.0.3 supports jdk 1.4??
thanks

OC4J v9.0.3 support JDK 1.4. By default OC4J standalone come with JDK 1.3.1.
Below are instructions to enable JDK 1.4 support in OC4J v9.0.3 standalone.
- Download JDK 1.4 from http://java.sun.com/
- Rename existing [OC4J_HOME]/jdk to [OC4J_HOME]//jdk131
[OC4J_HOME] - is the directory where oc4j_extended.zip was extracted
mv jdk jdk131
- copy JDK 1.4 with all the sub-directories into [OC4J_HOME]
cp -r <a jdk1.4> OR install JDK 1.4 into [OC4J_HOME]/jdk
Note: remember to name the directory jdk under [OC4J_HOME]
- The file jdk/jre/lib/security/java.security needs to be edited to include the following:
# Oracle specific definitions
auth.policy.provider=oracle.security.jazn.spi.PolicyProvider
login.configuration.provider=oracle.security.jazn.spi.LoginConfigProvider
The above steps will enable you to use OC4J under JDK 1.4.0
-Prasad

XSLT version supported in JDK 6 Transformer

Hi! This is a simple question: Does JDK 6 Transformer Class support XSLT 2.0?
My problem raise when I use the <xsl:character-map> tag. A Example:
template.xslt
<xsl:stylesheet version="2.0">
<xsl:output method="xml" version="1.0" encoding="UTF-8" use-character-maps="vxml"/>
<xsl:character-map name="vxml">
   <xsl:output-character character="«" string='&lt'/>
   <xsl:output-character character="»" string='&gt'/>
   <xsl:output-character character="¨" string='"'/>
</xsl:character-map>
<xsl:template match="/">
   «vxml version=¨2.0¨»
   {xslt operations...}
   «/vxml»
</xsl:template>
{code}
*someXML.xml*
{code}
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="template.xslt"?>
{code}
Well, when I use external software (Altova XMLSpy), the result is exactly that I want... but, when I use a simple java class with Transformer (in java 6), the result contains alternative char and no the correct character that character-map is supposed to change.
Then, in this forum all people only use XSLT with version="1.0"... and appear my question... Transformer Class in JDK 6 really support XSLT version 2.0? I can't find information of this...
Edited by: MIrribarra on 20-03-2009 05:51 PM
Edited by: MIrribarra on 20-03-2009 05:53 PM
Deleted intensionally semi-colon in "&lt" and "&gt" because editor change string code

Simple answer: No.
Less simple answer: you can plug in any transformer you like. The process for doing that is described in the documentation for javax.transform.TransformerFactory, method newInstance.

RMI Applet error

I'm programming a RMI based messenger system. I tested the server and a java console client... all worked very well!
After that, I programmed a very simple test applet (source below).
import java.awt.*;
import java.awt.event.*;
import java.applet.*;
import java.rmi.*;
import java.rmi.server.*;
public class MessageApplet extends Applet {
     private MessageDaemon messaged;
     public MessageApplet() {}
     public void init() {
          try {
               // connect RMI Server
               messaged = (MessageDaemon)Naming.lookup("rmi://myhost.net/messaged");
// RMI test
               System.out.println(messaged.whois("username").getName());
          catch (Exception e) {
               e.printStackTrace();
I start the applet under Windows 98 (JDK 1.3.1) with the following command:
appletviewer MessageApplet.html
and all I get is the following exception:
java.security.AccessControlException: access denied (java.net.SocketPermission myhost.net resolve)
at java.security.AccessControlContext.checkPermission(Compiled Code)
at java.security.AccessController.checkPermission(Compiled Code)
at java.lang.SecurityManager.checkPermission(Compiled Code)
at java.lang.SecurityManager.checkConnect(SecurityManager.java:1004)
at java.net.InetAddress.getAllByName0(Compiled Code)
at java.net.InetAddress.getAllByName0(InetAddress.java:544)
at java.net.InetAddress.getByName(Compiled Code)
at java.net.Socket.<init>(Socket.java:98)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect SocketFactory.java:29)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Compiled Code)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:462)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:194)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Compiled Code)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:89)
at MessageApplet.init(MessageApplet.java:27)
at sun.applet.AppletPanel.run(Compiled Code)
at java.lang.Thread.run(Thread.java:479)
If I run the same applet unter MRJ (Mac OS Runtime for Java, JDK 1.1.8, Apple Applet Runner) on my Mac, I get another exception:
java.rmi.UnmarshalException: Return value class not found; nested exception is: java.lang.ClassNotFoundException: MessageDaemonImpl_Stub
at sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java)
at java.rmi.Naming.lookup(Naming.java)
at MessageApplet.init(MessageApplet.java:27)
at com.apple.mrj.JManager.JMAppletViewer_OLD.doAppletInit(JMAppletViewerOld.java)
at com.apple.mrj.JManager.JMAppletViewer_OLD.setState(JMAppletViewerOld.java)
at com.apple.mrj.JManager.JMViewerEvent.post(JMAppletViewerOld.java)
at com.apple.mrj.JManager.AVDispatcherThread.run(JMAppletViewerOld.java)
What could be the problem? Do I have to add some permissions? The client could load the MessageDaemonImpl_Stub class without any problems, so there is surely no problem with the server/rmiregistry.
Thank you very much.
Best Regards,
Adrian R.

some additional information:
I started the applet with appletviewer (1.3.1) under Windows...
appletviewer http://192.168.0.1/msg/MessageApplet.html
(no problems)
appletviewer http://myhost.net/msg/MessageApplet.html
(security exception allthough myhost.net is the same host as 192.168.0.1!)
The server ist running on a linux system with 2 network interfaces: LAN: 192.168.0.1 and WAN: (DHCP, dynamically linked to a DNS). I'm testing the applet from a host in the LAN and only the url http://192.168.0.1/msg/MessageApplet.html did work.
I also tested the applet with MS IE 6 and all I got is the following exception:
java.lang.ClassNotFoundException: java.rmi.Naming
on my Mac I tested the applet in MS IE 5 and it worked with the URL: http://192.168.0.1/msg/MessageApplet.html but http://myhost.net/msg/MessageApplet.html didn't work.
What about IE 6? Is it possible that IE doesn't support RMI?!?! But what to do? And how can I solve the problem regarding "IP vs. DNS"?
Best Regards
Adrian R.

RMI from client browser?

I heard somebodies are developing solutions to do RMI from client browser,
is this a good idea?

The Limitations of RMI Applets on the Internet
Although using RMI in Internet-based applets seems like a good idea, in practice, the instability of Internet connections and a lack of client support make it impractical. Among the obstacles to deploying RMI applets on the Internet are the following:
* Despite supporting the majority of the Java 1.1 specification, the most popular web browsers -- Netscape Navigator and Microsoft Internet Explorer -- do not adequately support RMI. Navigator supports RMI on most platforms but does not support HTTP tunneling, so Netscape users connected to the web through a proxy server can't use an RMI applet. Meanwhile, Netscape for the Macintosh does not support RMI at all. Internet Explorer 4.0-5.0 also lacks RMI support, although a patch is supposedly available to add the missing classes (the RMI classes are available from Microsoft's web site, but instructions for installing them is not provided). As a result, a large percentage of Internet surfers can't use RMI applets in their current browser.
* The RMI registry can experience problems when handling connections via the Internet. A bug that causes the registry to stop accepting new connections occurs all too frequently with web-based RMI clients, requiring that the registry be shut down and restarted. Also, in Java runtime environments prior to JDK 1.2.2, server sockets created to handle connections from Internet-based RMI clients can live on indefinitely (consuming server resources) even after those clients are shut down.
* The RMI registry is not as flexible as most server applications, answering only to client connections made to one specific hostname. This means that your RMI server application cannot support multiple domains on a single web server, which limits your deployment options.
* Many applications may require that data exchanged between client and server be encrypted, compressed, or handled in some other fashion. Doing this with RMI is simple enough, requiring only that you implement your own socket classes and an RMI socket factory that creates your special sockets. However, overriding the default socket factory disables RMI's ability to do HTTP tunneling, thereby preventing access by proxy server users.
* Deploying an RMI server application requires additional network firewall configuration. By default, RMI objects are bound to random, "anonymous" server port numbers, making it impossible to predict the ports that must be available to Internet clients. RMI functionality new to Java 2 allows you to specify a port number when creating a remote object, but deployment still requires that firewalls allow access to ports not typically used by web-based applications.
quoted from :
http://developer.java.sun.com/developer/technicalArticles/RMI/rmi/
AND when u get the sample code working, tell me how u did it. okay? :) thx! mail me at [email protected].

Is JDK 5.0 support RMI?

Similar Messages

Maybe you are looking for