HTTP Status 500 - Internal Server Error


type Exception report

messageInternal Server Error

descriptionThe server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: WELD-000049: Unable to invoke public void br.com.eddydata.bean.servicosonline.PrincipalFace.init() on br.com.eddydata.bean.servicosonline.PrincipalFace@76a2d52b

root cause

org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void br.com.eddydata.bean.servicosonline.PrincipalFace.init() on br.com.eddydata.bean.servicosonline.PrincipalFace@76a2d52b

root cause

java.lang.reflect.InvocationTargetException

root cause

javax.ejb.EJBException

root cause

javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Error Code: 0

root cause

Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Error Code: 0

root cause

java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

javax.resource.spi.ResourceAllocationException: Connection could not be allocated because: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

root cause

java.net.ConnectException: Connection refused (Connection refused)

note The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.1 logs.


GlassFish Server Open Source Edition 4.1