Jump to content
We've recently updated our Privacy Statement, available here ×
  • NameAlreadyBoundException 10990


    Jim W
    • Features: JasperReports Server Version: v5.5, v5.2, v5.1, v5.0 Product: JasperReports® Server

    Issue Description:

    If you are running multiple instances of JasperReports Server  v5.x on Linux and encountered this exception.

    [toc]
    Caused by: java.io.IOException: Cannot bind to URL
    [rmi://localhost:10990/jasperserver]:
    javax.naming.NameAlreadyBoundException: jasperserver [Root exception is
    java.rmi.AlreadyBoundException: jasperserver]
    at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:826)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
    at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:187)
    at
    
    org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)
    at
    
    org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452)
    ... 26 more
    Caused by: javax.naming.NameAlreadyBoundException: jasperserver [Root exception is java.rmi.AlreadyBoundException: jasperserver]
    at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:139)
    at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:226)
    at javax.naming.InitialContext.bind(InitialContext.java:419)
    at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
    ... 29 more
    Caused by: java.rmi.AlreadyBoundException: jasperserver
    at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:153)
    at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
    at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:409)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:267)
    at sun.rmi.transport.Transport$1.run(Transport.java:177)
    at sun.rmi.transport.Transport$1.run(Transport.java:174)
    at java.security.AccessController.doPrivileged(Native Method)
    

      See solution below.


    Resolution:

    On one of the instances,

    Change the port number in the file,

    ../jasperserver-pro/WEB-INF/js.diagnostic.properties

    Change the default diagnostic port 10990 to 10991.

    Now you have one instance running on port 10990 and another running on port 10991.


    Ref. Case #00038471


    User Feedback

    Recommended Comments

    There are no comments to display.



    Guest
    This is now closed for further comments

×
×
  • Create New...