pruebas carga - copia
pruebas carga - copia
The internal connection pool has reached its maximum size and no connection is currently
available!
Session 2
Opradicar
15-May-2024 16:00:33.009 SEVERE [http-nio-8080-exec-673]
com.co.ugpp.ws.jpa.AdminStoreProcedures.generarNumeroRadicado ERROR en
generarNumeroRadicado
at
org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:147)
at
org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:155)
at
org.hibernate.procedure.internal.ProcedureCallImpl.execute(ProcedureCallImpl.java:653)
at
com.co.ugpp.ws.jpa.AdminStoreProcedures.generarNumeroRadicado(AdminStoreProcedures.java:
763)
at
com.dacartec.ugpp.svcDocumento.impl.DocumentoServiceImpl.generacionNumeroRadicado(Docu
mentoServiceImpl.java:2499)
at sun.reflect.GeneratedMethodAccessor412.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.xml.ws.util.Trampoline.invoke(MethodUtil.java:52)
at sun.reflect.GeneratedMethodAccessor408.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.xml.ws.util.MethodUtil.invoke(MethodUtil.java:77)
at com.sun.xml.ws.api.server.MethodUtil.invoke(MethodUtil.java:34)
at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:220)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:119)
at
com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:58)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1106)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:1020)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:989)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:847)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:389)
at
com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:838)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:392)
at
com.sun.xml.ws.transport.http.servlet.ServletAdapter.invokeAsync(ServletAdapter.java:195)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:131)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:167)
at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:681)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.hibernate.HibernateException: The internal connection pool has reached its
maximum size and no connection is currently available!
at
org.hibernate.engine.jdbc.connections.internal.PooledConnections.poll(PooledConnections.java:8
2)
at
org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnec
tion(DriverManagerConnectionProviderImpl.java:186)
at
org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbc
ConnectionAccess.java:35)
at
org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(
LogicalConnectionManagedImpl.java:99)
at
org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getPhysicalConnection(Logic
alConnectionManagedImpl.java:129)
at
org.hibernate.engine.jdbc.internal.StatementPreparerImpl.connection(StatementPreparerImpl.jav
a:47)
at
org.hibernate.engine.jdbc.internal.StatementPreparerImpl$1.doPrepare(StatementPreparerImpl.ja
va:86)
at
org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepar
eStatement(StatementPreparerImpl.java:172)
at
org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerI
mpl.java:78)
at
org.hibernate.procedure.internal.ProcedureCallImpl.buildOutputs(ProcedureCallImpl.java:437)
at
org.hibernate.procedure.internal.ProcedureCallImpl.getOutputs(ProcedureCallImpl.java:404)
at
org.hibernate.procedure.internal.ProcedureCallImpl.outputs(ProcedureCallImpl.java:663)
at
org.hibernate.procedure.internal.ProcedureCallImpl.execute(ProcedureCallImpl.java:646)
... 49 more
Firmar
según los resultados obtenidos en los escenarios configurados en las pruebas de estrés de los
servicios web se puede concluir:
Los servicios respondieron a casos que estaban muy por encima del promedio de los
radicados producidos en un día por UGPP. Ya que se realizaron pruebas donde en poco
tiempo (promedio 5 minutos), se obtenían exitosamente todos los radicados de un día de
producción documental de UGPP.
El servidor Tomcat y los servicios respondieron efectivamente ante las peticiones y se
realizaron las configuraciones adicionales propuestas por UGPP como el aumento de la
memoria, aumento en el pool de conexiones y ajustes a los servicios, para obtener mejores
resultados de estas.
Sesión 22/05/2024