Naming Service Error(could not start on port 1099)| JBoss.org Content Archive (Read Only)

1. Re: Naming Service Error(could not start on port 1099)

jaikiran Aug 26, 2008 10:27 AM (in response to jagsysadmin)

"jagsysadmin" wrote:
Hi,
I am new to this Jboss software and i am using jboss 2.4.3\tomcat 3.2

Do you really mean 2.4.3 version of JBoss(which is very old)?

"jagsysadmin" wrote:

and when i start jboss i get this error naming serive could not start on port
1099 and i am using windows xp with sp3.Please help

Please post the entire exception stacktrace and the console log.

While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted

2. Re: Naming Service Error(could not start on port 1099)

peterj Aug 26, 2008 11:35 AM (in response to jagsysadmin)

Also see the http://wiki.jboss.org/wiki/DebugBindException

3. Re: Naming Service Error(could not start on port 1099)

jagsysadmin Aug 27, 2008 12:27 AM (in response to jagsysadmin)

Thanks For The Reply Peter j and Jaikiran.I will try it and reply u with the screen shot of the error.

Jaikiran we have developed one application which uses jboss 2.4.3 and we have yet to upgarde it to new jboss version.Thanks for ur reply.

4. Re: Naming Service Error(could not start on port 1099)

jagsysadmin Aug 27, 2008 6:37 AM (in response to jagsysadmin)

Hi Peter j,
I did use tcpview by sysinternal nothing running on the port 1099 and i am posting the error

JBOSS_CLASSPATH=;C:\jdk1.3.1_01/lib/tools.jar;run.jar;../lib/crimson.jar
jboss.home = E:\CIM_Appl\CIM_Appl\jBoss_tomcat\jboss
Using JAAS LoginConfig: file:/E:/CIM_Appl/CIM_Appl/jBoss_tomcat/jboss/conf/tomca
t/auth.conf
Using configuration "tomcat"
[root] Started Log4jService, config=file:/E:/CIM_Appl/CIM_Appl/jBoss_tomcat/jbos
s/conf/tomcat/log4j.properties
[Info] Java version: 1.3.1_01,Sun Microsystems Inc.
[Info] Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc.
[Info] System: Windows 2000 5.1,x86
[Shutdown] Shutdown hook added
[Service Control] Initializing 47 MBeans
[WebService] Initializing
[WebService] Initialized
[NamingService] Initializing
[NamingService] Initialized
[JNDIView] Initializing
[JNDIView] Initialized
[TransactionManagerService] Initializing
[TransactionManagerService] Initialized
[ClientUserTransactionService] Initializing
[ClientUserTransactionService] Initialized
[JaasSecurityManagerService] Initializing
[JaasSecurityManagerService] Initialized
[JdbcProvider] Initializing
[JdbcProvider] Loaded JDBC-driver:org.hsqldb.jdbcDriver
[JdbcProvider] Initialized
[HypersonicDatabase] Initializing
[HypersonicDatabase] Initialized
[XADataSourceLoader] Initializing
[XADataSourceLoader] Initialized
[ServerDataCollector] Initializing
[ServerDataCollector] Initialized
[ContainerFactory] Initializing
[ContainerFactory] Initialized
[EmbeddedTomcatServiceSX] Initializing
[EmbeddedTomcatServiceSX] Initialized
[JBossMQService] Initializing
[JBossMQService] Initialized
[StateManager] Initializing
[StateManager] Initialized
[PersistenceManager] Initializing
[PersistenceManager] Initialized
[JVMServerILService] Initializing
[JVMServerILService] Initialized
[RMIServerILService] Initializing
[RMIServerILService] Initialized
[OILServerILService] Initializing
[OILServerILService] Initialized
[UILServerILService] Initializing
[UILServerILService] Initialized
[TopicManager] Initializing
[TopicManager] Initialized
[TopicManager] Initializing
[TopicManager] Initialized
[TopicManager] Initializing
[TopicManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[QueueManager] Initializing
[QueueManager] Initialized
[NamingAlias] Initializing
[NamingAlias] Initialized
[NamingAlias] Initializing
[NamingAlias] Initialized
[JMSProviderLoader] Initializing
[JMSProviderLoader] Initialized
[ServerSessionPoolLoader] Initializing
[ServerSessionPoolLoader] Initialized
[J2eeDeployer] Initializing
[J2eeDeployer] Initialized
[RARDeployer] Initializing
[RARDeployer] Initialized
[ConnectionManagerFactoryLoader] Initializing
[MinervaNoTransCMFactory] Initialized
[ConnectionManagerFactoryLoader] Initializing
[MinervaSharedLocalCMFactory] Initialized
[ConnectionManagerFactoryLoader] Initializing
[MinervaXACMFactory] Initialized
[ConnectionFactoryLoader] Initializing
[MinervaDS] Initialized
[ConnectionFactoryLoader] Initializing
[JmsXA] Initialized
[AutoDeployer] Initializing
[AutoDeployer] Initialized
[JMXAdaptorService] Initializing
[JMXAdaptorService] Initialized
[RMIConnectorService] Initializing
[RMIConnectorService] Initialized
[MailService] Initializing
[MailService] Initialized
[Service Control] Initialized 47 services
[Service Control] Starting 47 MBeans
[WebService] Starting
[WebService] Started webserver with address: null port: 8083
[WebService] Codebase set to: http://unilog-113:8083/
[WebService] Started
[NamingService] Starting
[NamingService] Starting jnp server
[NamingService] Could not start on port 1099
java.net.BindException: Address in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at org.jnp.server.Main.start(Main.java:200)
at org.jboss.naming.NamingService.startService(NamingService.java:149)
at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107
)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16
28)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(Conf
igurationService.java:836)
at $Proxy0.start(Unknown Source)
at org.jboss.util.ServiceControl.start(ServiceControl.java:81)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16
28)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at org.jboss.Main.(Main.java:221)
at org.jboss.Main$1.run(Main.java:127)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:123)
[NamingService] InitialContext Environment:
[NamingService] key=java.naming.factory.initial, value=org.jnp.interfaces.Naming
ContextFactory
[NamingService] key=java.naming.factory.url.pkgs, value=org.jboss.naming:org.jnp
.interfaces:org.jboss.naming:org.jnp.interfaces
[NamingService] Naming started on port 1099
[NamingService] Started
[JNDIView] Starting
[JNDIView] Started
[TransactionManagerService] Starting
[TransactionManagerService] Started
[ClientUserTransactionService] Starting
[ClientUserTransactionService] Started
[JaasSecurityManagerService] Starting
[JaasSecurityManagerService] startService, cachePolicy=null
[JaasSecurityManagerService] startService, SecurityProxyFactory=org.jboss.securi
ty.SubjectSecurityProxyFactory@6f0be8
[JaasSecurityManagerService] Started
[JdbcProvider] Starting
[JdbcProvider] Started
[HypersonicDatabase] Starting
[Default] Server.run/init: java.net.BindException: Address in use: JVM_Bind
[HypersonicDatabase] Database started
[HypersonicDatabase] Started
[XADataSourceLoader] Starting
[DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS

and we are using oracle 8i database.Please help me with this.

also i saw the registry location no reserverd ports value.Thanking u

5. Re: Naming Service Error(could not start on port 1099)

peterj Aug 27, 2008 11:30 AM (in response to jagsysadmin)

Some possibilities:

1) Port 1099 is in use but tcpview is not showing it (there was a while on XP where tcpview did not show all opened ports - a later XP patch fixed this). Try using netstat, see if that helps. Oh, another way to tell of a port is open it to use telnet to test it:

telnet localhost 1099

If the port is not open, you will get a connection error. If the port is open, you will see text+gibberish, and possibly a screen refresh (like using the 'cls' command)

2) You have a firewall and it is preventing the port from being opened.

3) The JVM is unable to open the port for some reason. JDK 1.3.1_01 is a very old version of 1.3.1, perhaps you should try using the latest patch for 1.3.1. (Looks like 1.3.1_19 is the latest for Windows)