Default RMI port 1099

Hello,
Does anybody know how to change the default RMI port 1099 for
WebLogic implementation of RMI. Is there some config parameter
which will do it. I happened to have two RMI registry running
on one computer and I would like to run them on two different
ports (one of them is not WebLogic and not our application).
So I have control anly of one of them and do not want to connect
to the existing rmi registry.
Thanks, Lev

1099 is the port the java.rmi registry runs on. The WLS registry is a specialized namespace in the WLS JNDI name tree, so it is bound to the same port as the WLS instance. For example, a WLS instance started with
java.exe .... -Dweblogic.system.listenPort=7701 -Dweblogic.system.SSLListenPort=7702 weblogic.Server
will respond to
weblogic.rmi.Naming.lookup("rmi://localhost:7701/foo");
or
weblogic.rmi.Naming.lookup("rmi://localhost:7702/foo");
but not
weblogic.rmi.Naming.lookup("rmi://localhost:1099/foo");
Lev wrote:
Hello,
Does anybody know how to change the default RMI port 1099 for
WebLogic implementation of RMI. Is there some config parameter
which will do it. I happened to have two RMI registry running
on one computer and I would like to run them on two different
ports (one of them is not WebLogic and not our application).
So I have control anly of one of them and do not want to connect
to the existing rmi registry.
Thanks, Lev

Similar Messages

RMI port misuse

I'm getting really ticked off with clients having problems using my software because the RMI port 1099 (and often enough 1098) is being misused by another process. Does the IANA registered port list mean anything at all?
I guess I can't change the world :( so I'd like to know how other people deal with this problem. Thanks.

Two of the culprits are Microsoft (Outlook) and Google so I hope you have a big boot!
1098 and 1099 are also in the range of ephemeral ports --- allocated as the local end of connections which don't specify a port number.
http://support.microsoft.com/default.aspx?scid=kb;en-us;812873
"On Windows Vista and Server 2008 the default range of ephemeral ports is now 49152 to 65535"
For older versions of Windows the default range is 1025 - 4000 (and you can't change that lower limit). Finally a reason to use Vista!
Edited by: mthornton on 15-Nov-2008 20:35

RMI Port

Hi all,
Which is the default rmi port ?
Where is configured this port ?
How to configure this port ?
Thanks

"Jordi Pinyol" <[email protected]> writes:
Which is the default rmi port ?
Where is configured this port ?
How to configure this port ?The listen port for RMI is the same as all other protocols. The
default is 7001.
andy

Changed RMI port to 8010, but still looking for default 1099 port..

I have changed the rmi port to 8010 by using following command
rmiregistry 8010 & In linux server
when I run the serverImpl class to bind.. Its giving connection refused error..The Port is opened by network admin and telnet hostname 8010 is also working fine ( gets escape chaaracter..)
Please help.. do I have to something more in like change some configurations? :(

Hi I am doing following after your advise,
1. rmiregistry 8010&
in SampleServerImpl.java
import java.rmi.*;
import java.rmi.server.*;
import java.rmi.registry.*;
public class SampleServerImpl extends UnicastRemoteObject
implements SampleServer
SampleServerImpl() throws RemoteException
super();
public int sum(int a,int b) throws RemoteException
return a + b;
public static void main(String args[])
//set the security manager
try
System.setSecurityManager(new RMISecurityManager());
//create a local instance of the object
SampleServerImpl Server = new SampleServerImpl();
//put the local instance in the registry
Registry reg = LocateRegistry.getRegistry("10.252.26.6",8010);
if(reg != null) {
System.out.println("1port="+reg.REGISTRY_PORT);
reg.bind("SAMPLE-SERVER",Server);
System.out.println(" After reg binding server waiting.....");
catch (RemoteException re)
System.out.println("Remote exception: " + re.toString());
re.printStackTrace();
catch (Exception exp)
System.out.println("Other exception: " + exp.toString());
exp.printStackTrace();
I have compiled above class and also regenerated stub and skeleton..
After running this java im getting following error..
one more thing is System.out.println("1port="+reg.REGISTRY_PORT); always prints 1099 port..
1port=1099
Remote exception: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: SampleServerImpl_Stub
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: SampleServerImpl_Stub
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:352)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:207)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:534)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:350)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at SampleServerImpl.main(SampleServerImpl.java:39)
Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: SampleServerImpl_Stub
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:342)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:207)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.ClassNotFoundException: SampleServerImpl_Stub
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:430)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631)
at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257)
at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
... 9 more
Not sure how to fix this...Can you please help

Java.rmi.server.ExportException: Listen failed on port: 1099;

Hi All,
I am trying to run RMI tutorial from sun's java tutorial. It has 8 parts. The last two parts are "Compiling the Example Programs" and "Running the Example Programs".
Until "Compiling the Example Programs", I am okay.
But I am stuck in the last part, "Running the Example Programs". When I use the command "rmiregistry", it gives me a list of exceptions as follows.
c:\home\ann\src>rmiregistry
java.rmi.server.ExportException: Listen failed on port: 1099; nested exception is:
java.net.SocketException: Permission denied: listen failed
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:312)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
at sun.rmi.registry.RegistryImpl.main(RegistryImpl.java:322)
Caused by: java.net.SocketException: Permission denied: listen failed
at java.net.PlainSocketImpl.socketListen(Native Method)
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:380)
at java.net.ServerSocket.bind(ServerSocket.java:320)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
... 7 more
c:\home\ann\src>
Then, I try to use "start rmiregistry" command. At that time, a command window stating the above exception popup just for a while and closed automatically.
Now, I use jdk1.6.0_16 on Windows Vista.
Previously, I used j2sdk1.4.2_19. That time, I could run "start rmiregistry" properly and could try testing another RMI example application.
But if I use j2sdk1.4.2_19, compiling some statements in the sun's RMI tutorial gives me error. So, I change to use jdk1.6.0_16 for this tutorial. "jdk1.6.0_16" compiles all programs in the tutorial with no error. But I can't run the statement "start rmiregistry".
I use the command prompt from Vista's default Administrator account and already disable User Account Control too.
Any help, please!
Thanks a lot,
atzm111

Hi,
This is the result of netstat -an
c:\home\ann\src>netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2868 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3999 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 192.168.1.102:139 0.0.0.0:0 LISTENING
TCP 192.168.1.102:49475 64.233.189.17:80 ESTABLISHED
TCP 192.168.1.102:49620 64.233.189.83:80 ESTABLISHED
TCP 192.168.1.102:49625 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49626 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49627 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49628 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49629 72.5.124.102:80 ESTABLISHED
TCP 192.168.1.102:49631 72.5.124.61:80 TIME_WAIT
TCP 192.168.1.102:49634 124.155.222.16:80 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:51196 *:*
UDP 127.0.0.1:64757 *:*
UDP 192.168.1.102:137 *:*
UDP 192.168.1.102:138 *:*
UDP 192.168.1.102:1900 *:*
UDP 192.168.1.102:51195 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:5355 *:*
UDP [::1]:1900 *:*
UDP [::1]:51193 *:*
UDP [fe80::100:7f:fffe%16]:1900 *:*
UDP [fe80::100:7f:fffe%16]:51194 *:*
UDP [fe80::18c1:1fa4:382b:261%12]:1900 *:*
UDP [fe80::18c1:1fa4:382b:261%12]:51191 *:*
UDP [fe80::69bc:321e:5e99:dc7c%11]:1900 *:*
UDP [fe80::69bc:321e:5e99:dc7c%11]:51192 *:*
UDP [fe80::a0a0:89c2:b2fd:e4b9%13]:1900 *:*
UDP [fe80::a0a0:89c2:b2fd:e4b9%13]:51190 *:*
c:\home\ann\src>
So, port 1099 is not in use. I don't know how to check your second fact. I'll find it out coz I can't ask you. :D
Thanks!

Port 1099 being used by other processes ,need an alt port for RMI-Registry

I am using port 1099 for RMI and the o/s is windows 2003.
We want that the RMI registry shud automatically be started with the windows startup processes.But we found that some other processes are usoing the same port.
Is there any other port which can be used for the same?
or any method to make other processes release the port forcefully.

If you read the documentation or do a quick google search, you will discover the rmiregistry program can be assigned any port you wish. Simply invoke via:
rmiregistry -h from windows or "man rmiregistry" from mac or unix and you will be greeted with:
Usage: rmiregistry <options> <port>
In a nut shell just specify the port:
i.e.
rmiregistry 5000
etc...
Hope this helps.
-Lemont

RMI firewall issue - opening port 1099 is not enough

Hello,
We have a distributed java desktop app that uses RMI with callbacks to communicate amongst the clients. It all works really well at our dev site and at 2 trial sites.
We are about to deploy out to more customer sites - so I have been doing more testing with firewalls etc and discovered some issues. Our customers are small businesses and typically have between 1 and 10 desktop clients that connect to the server via RMI. These customers are "very NOT technical", so we need to give them set-and-forget firewalls etc.
This is all on a LAN, with RMI using port 1099. On the firewalls (of the various PCs) we open ports 1099 (RMI) and 5432 (for the Postgres DB).
Also, I was using "CurrPorts" and "SmartSniff" to monitor the traffic at each PC - so I had a reasonable view of proceedings.
Basically, opening port 1099 on the server is necessary, but it is NOT ENOUGH. The RMI moves off to ports other than 1099, and the server firewall does not allow the connection.
Procedure ...
(1) start the "server" app - which starts the RMI registry - the "localhost" desktop app also starts and it works well to both the database and the RMI.
(2) start another client - it connects to the DB Server, but NOT the RMI server.
(3) open the server firewall to all traffic for a few seconds - then the client connects successfully.
From CurrPort logging I could watch the RMI comms progress over those first few minutes ...
Initially the comms do include port 1099 on the initial call to the server, but there after there are always 2 or 3 "channels" open, but not to 1099.
I notice that the Postgres DB keeps using port 5432 for all of its active channels - so it does not have the same firewall issue.
After we have opened the firewall for a few seconds - to enable the link - then we can turn the client on and off and the client re-connects without issue - so it would seem to be only an issue with the initial connection.
I am sure that this is all completely standard and correct RMI behavior.
QUESTIONS:
1. Can RMI be "forced" to always use port 1099 for connections, and not move to other ports? (like the database uses 5432)
2. Are there any suggestions for getting around this seemingly standard RMI behaviour?
Other comments ...
The firewall lets me open individual ports (say 1099) - BUT I can not justify opening ALL ports.
The firewall lets me open all ports to an application, say "C:\Program Files\Java\jre6\bin\java.exe", but that app will occasionally change at a customer's site as they will update their java version and suddenly our app will stop working.
Any guidance is appreciated.
Many Thanks,
-Damian

1. Can RMI be "forced" to always use port 1099 for connectionsYes. Export all your servers on the same port. See UnicastRemoteObject constructor that takes an int, or UnicastRemoteObject.exportObject(int). If the RMI Registry is a separate process you can't re-use 1099 for this purpose, but see below.
2. Are there any suggestions for getting around this seemingly standard RMI behaviour?Yes. Start the RMI Registry in the same JVM as the code, then you only need to use 1099 for everything.
If you are using server socket factories, make sure they have an equals() method, or use the same instance for all remote objects.

Shutting down default JMX RMI port

I am starting up my JMX agent for remote access and it opens 2 ports, one which is set by the -Dcom.sun.management.jmxremote.port=XXXX and one randomly assigned port.
I know I can install a custom JMX agent to specify another RMI port that I can control, but what I really want to do is shut down the randomly assigned one. The problem is that weve a port monitoring app, so I can't open any ports open that I cannot control with causing IT to complain. Is there any way to disable this connector?
Thanks,
Mark

Hi,
Please have a look at these articles:
[http://blogs.sun.com/jmxetc/tags/firewall|http://blogs.sun.com/jmxetc/tags/firewall]
they should answer your questions.
Best regards,
-- daniel
JMX, SNMP, Java, etc...
[http://blogs.sun.com/jmxetc|http://blogs.sun.com/jmxetc]

Specifying RMI Port in JNDI Lookup

Hi,
I am using Silverstream 3.7.4 server for my J2EE development.
The host machine having multiple machine uses different RMI ports.
So I have 54893 as RMI port instead of default 54890. I cannot
create a InitialContext due to this Reason. Can anybody help me how to resolve this problem. The Code is
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sssw.rt.jndi.AgInitCtxFactory");
p.put(Context.PROVIDER_URL,"iiop://cds:15003");
Object sbobj = context.lookup("/RMI/ejb/ODRSessionFacade");
odrEJBHome = (ODRSessionFacadeHome)PortableRemoteObject.narrow(sbobj,ODRSessionFacadeHome.class);
odrEJB = odrEJBHome.create();
The Exception is:
javax.naming.ConfigurationException: Error finding 'RMI/ejb/ODRSessionFacade'. Resolution name is 'iiop://localhost:54890'.
javax.naming.ConfigurationException: Error finding 'RMI/ejb/ODRSessionFacade'. Resolution name is 'iiop://localhost:54890'.
     at com.sssw.rt.jndi.AgInitCtx.checkFederatedContext(AgInitCtx.java:436)
     at com.sssw.rt.jndi.AgInitCtx.checkFederatedName(AgInitCtx.java:98)
     at com.sssw.rt.ejb.AgInitClientCtx.lookup(AgInitClientCtx.java:66)
     at com.sssw.rt.jndi.AgBaseCtx.lookup(AgBaseCtx.java:218)
     at com.sssw.rt.jndi.AgInitCtx.lookup(AgInitCtx.java:492)
     at com.sssw.rt.ejb.AgInitClientCtx.lookup(AgInitClientCtx.java:70)
     at com.sssw.rt.jndi.AgBaseCtx.lookup(AgBaseCtx.java:241)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at com.sdm.pdr.ODR.ServerObject.<init>(ServerObject.java:39)
     at com.sdm.pdr.ODR.ODRMain.<init>(ODRMain.java:16)
     at com.sdm.pdr.ODR.ODRMain.main(ODRMain.java:48)

YOUR SYSTEM MAYBE HAS SOMETHING WRONG WITH THE FIREWALL
AND THE PORT CANNOT BE USED!YOU BE SURE:)

Why does the RMI port keep changing?

I have set up an RMI server process on a Sun server (SunOS 5.8) and I am running the client process from another Sun server (SunOS 5.9). I created a policy file on the client machine providing access to port 1099 on the server machine.
I kept getting connection refusals, and every time I did, it was on a different port. I changed the policy file to allow any port from 1099 on up in order to get around the problem. I tried to start up the rmiregistry with 1099 as an argument, and that did not help. What's going on?
Jim

(a) You will always get a different client side port, that's normal.
(b) the Registry port is 1099 but RMI servers are exported on a system-selected port unless you specify one. If your Registry and RMI servers are in the same JVM they can share ports

XP System process uses port 1099

XP process "System" with PID "4" uses port 1099 for
listening TCP connection. I need 1099 for RMI.
I don't want to kill "System" every time.
Any clue about asking "System" not to use port 1099?
Thanks in advance.

I'm not sure but I think this happens when I terminate a JBoss server process instead of shutting it down gracefully. Which would imply that ownership of the connection is transferred to the XP "System" process when this happens (?)

Could not connect to remote service [rmi://localhost:1099/

I have a large deployment with two filr appliances and one database and one search index.
I am running zen load balancer in front of the appliance which works great.
There are no config changes to the filr appliances in terms of port redirection.
I had an issue upgrading from 1.0.1 to 1.1 so I blew it away and started fresh.
After I installed and configured the appliances there were no issues . Now the :9443 configuration section will not work I get
(this is just the top lines)
HTTP ERROR 500
Problem accessing /. Reason:
Could not connect to remote service [rmi://localhost:1099/GangliaService]; nested exception is java.rmi.NoSuchObjectException: no such object in table
Caused by:
org.springframework.remoting.RemoteConnectFailureE xception: Could not connect to remote service [rmi://localhost:1099/GangliaService]; nested exception is java.rmi.NoSuchObjectException: no such object in table
at org.springframework.remoting.rmi.RmiClientIntercep torUtils.convertRmiAccessException(RmiClientInterc eptorUtils.java:190)
at org.springframework.remoting.rmi.RmiClientIntercep tor.doInvoke(RmiClientInterceptor.java:347)
This is on all appliances (search,data,filr1,filr2)
I restarted filr2 and the admin section 9443 comes back for a short time. Maybe 10 minutes then I get the same error. But now after the restart I get and authentication box asking for credentials on 8443. when I put in the admin or other creds it directs me to a page that says
HTTP Status 500 - Filter execution threw an exception
type Exception report
message Filter execution threw an exception
description The server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Filter execution threw an exception
org.kablink.teaming.webdav.servlet.filter.Resource DispatchFilter.doFilter(ResourceDispatchFilter.jav a:87)
root cause
java.lang.ExceptionInInitializerError
java.lang.J9VMInternals.initialize(J9VMInternals.j ava:259)
org.kablink.teaming.asmodule.spring.security.userd etails.DecryptedPasswordUserDetailsService.loadUse rByUsername(DecryptedPasswordUserDetailsService.ja va:51)
org.springframework.security.web.authentication.http://www.DigestAuthenticationFilte...lter.java:144)
org.springframework.security.web.FilterChainProxy$ VirtualFilterChain.doFilter(FilterChainProxy.java: 323)
org.springframework.security.web.context.SecurityC ontextPersistenceFilter.doFilter(SecurityContextPe rsistenceFilter.java:87)
org.springframework.security.web.FilterChainProxy$ VirtualFilterChain.doFilter(FilterChainProxy.java: 323)
org.springframework.security.web.FilterChainProxy. doFilter(FilterChainProxy.java:173)
org.springframework.web.filter.DelegatingFilterPro xy.invokeDelegate(DelegatingFilterProxy.java:346)
org.springframework.web.filter.DelegatingFilterPro xy.doFilter(DelegatingFilterProxy.java:259)
org.kablink.teaming.webdav.servlet.filter.Resource DispatchFilter.doFilter(ResourceDispatchFilter.jav a:87)
I have rebooted to no avail. If I restart the jetty service I do get the appliance login for 9443 but if I try to login I get the same message about [rmi://localhost:1099/
again if I reboot then 9443 works for 10 mins but 8443 gets hosed. Everything worked fine until I rebooted the appliance.
I am afraid to even reboot these appliances now in fear that the will cease to work.
I should also note that this was part of the upgrade issue I had after I rebooted all of the appliances.
Thanks in advance.

Originally Posted by bschilliger
The same issue here:
HTTP Status 500 - Filter execution threw an exception
type Exception report
message Filter execution threw an exception
description The server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Filter execution threw an exception
org.kablink.teaming.webdav.servlet.filter.Resource DispatchFilter.doFilter(ResourceDispatchFilter.jav a:87)
The password in the FILR appliance configuration 'Outbound E-Mail' was too complex (with special characaters). After changing the special characters with letters and/or numbers, the server starts without any troubles!
Regards from Switzerland,
Beat

RMIregistry: Port 1099 already in use

When I start rmiregistry, I get the following exception:
java.rmi.server.ExportException: Port already in use: 1099
What could be using Port 1099? How do I find out the mapping between ports and services? Thanks?

Alpha_Lord, I'm sorry I don't understand what you're talking about.
I don't remember posting the same question twice. If it was, it might've been because I refreshed the browser because the loading hang. And, if it wasn't, maybe someone else posted the same question.

RMI+Port+Naming+UnicastRemote

Hi,
My RMI client is behind a firewall. My naming service is being started at port 1099. The firewall will allow access only through a single port.
I want to know if I there is any issue invloved in exporting objects through UnicastRemoteObject at port 1099 and the running the naming service also at port 1099.
Is it possibe?

If you run the rmiregistry naming service on port 1099 you cannot export remote objects on that port.
Since both use TCP port 1099, you will recieve a SocketBoundException: port already in use or something similiar.

Cannot fix RMI port and wrong password

Hi, I have tried to fix the RMI port no. for my OC4J instance.
The port I specified sometimes may be taken by other OC4J instances and the server gives me the other one.
Can I set the rmi port outside the range 3101-3200?
Also I get the wrong password message if I try to remote access
the OC4J instance with user 'admin'. The default password is 'welcome' before, but now the password was changed by the server itself, since no server configuration has been made.
Any Ideas?
thanks in advance.

This post is just for reference.
For some reason, the OAS full install uses the ias_admin password for accessing JNDI over RMI. If you get authentication errors, try username = admin and password = the ias_admin password entered during the install.

Default RMI port 1099

Similar Messages

Maybe you are looking for