As a transitional step, this site will temporarily be made Read-Only from July 8th until the new community launch. During this time, you can still search and read articles and discussions.

While the community is read-only, if you have questions or issues requiring TIBCO review/response, please access the new TIBCO Community and select "Ask A Question."

You will need to register or log in or register to engage in the new community.

After yum update, in Centos7, Jasper Reports Server 6.4 Community Edition will not start. Any help appreciated.

JasperServer was running, but after Centos7 "yum update", I now get "HTTP Status 404 - /jasperserver/login.html" when trying to login.



I can browse the Tomcat root and run the Manager Application, but when I try to start the JasperServer webapp from within it, it fails with:



"FAIL - Application at context path /jasperserver could not be started".



Not being a Java Developer,  I see far,far more in my "localhost.YYYY-MM.DD.log" than I can make sense of, but "Port already in use: 10990" may be significant:



==========

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jMXregistry' defined in ServletContext resource [/WEB-INF/applicationContext-diagnostic.xml]: Invocation of init

 method failed; nested exception is java.rmi.server.ExportException: Port already in use: 10990; nested exception is:

        java.net.BindException: Permission denied (Bind failed)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1514)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:283)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)

        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)

        ... 49 more

Caused by: java.rmi.server.ExportException: Port already in use: 10990; nested exception is:

        java.net.BindException: Permission denied (Bind failed)

        at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:341)

        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249)

        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)

        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)

        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236)

        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213)

        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:198)

        at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203)

        at org.springframework.remoting.rmi.RmiRegistryFactoryBean.getRegistry(RmiRegistryFactoryBean.java:267)

        at org.springframework.remoting.rmi.RmiRegistryFactoryBean.getRegistry(RmiRegistryFactoryBean.java:236)

        at org.springframework.remoting.rmi.RmiRegistryFactoryBean.getRegistry(RmiRegistryFactoryBean.java:193)

        at org.springframework.remoting.rmi.RmiRegistryFactoryBean.afterPropertiesSet(RmiRegistryFactoryBean.java:164) was owned by 'root', so I ran

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1573)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1511)

        ... 58 more

==========

There is no other iteration of tomcat running, and httpd is not running. I did try changing 10990 to 10991 in ".../webapps/jasperserver/WEB-INF/js.diagnostic.properties", but then the logs say that port 10991 is already in use.



I noticed that, unlike all the other webapps in /var/lib/tomcat/webapps/, jasperserver was owned by root, so I ran "chown -R tomcat:tomcat jasperserver" to make it match the sample, manager, & other apps.



Again, this occurred as a result of a Centos7 "yum update", for the newly-discovered intel vulnerabilities among other reasons. I do have the js-export.sh backup, and if there is no other alternative I can reinstall jasperserver (the 6.4.2 security update) and try to restore our reports, but I'd like to have a working server in the meantime.



 

(1) Answer