Lucee 6.0.0.313-SNAPSHOT Error (java.util.NoSuchElementException) - java

lucee.runtime.exp.NativeException: Pool exhausted
Getting this error every two hours on lucee server.
Message: Pool exhausted

Related

WFLYEJB0467: The request was rejected as the container is suspended

When I am starting/restarting Wildfly 21 server, I am getting the following error
05:18:12,412 ERROR [stderr] (ServerService Thread Pool -- 96) javax.naming.NamingException: WFLYNAM0062: Failed to lookup mss-3.3.0-SNAPSHOT/ejbModule-3.3.0-SNAPSHOT/CompleteCallSessionBean!com.xim.mss.ejb.sessionbeans.completecall.CompleteCallRemoteInterface [Root exception is java.lang.RuntimeException: **org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended**]
But I am not getting this error when I am deploying the EAR ?
Can anyone tell me why this is happening?
Is this expected error or does this need to be resolved ?
This is an expected error, you are performing an EJB call before the EJB container is started and it is in suspended state (I reproduced the issue with a similar situation).
I have found a similar explanation for the error when the server is in shutdown (when the EJB container is also suspended).
https://issues.redhat.com/browse/JBEAP-444
The best solution is to delay this ejb call with a timer to wait the application to be fully started.

JBoss eap-6 boundPort and boundAddress MBean

We are trying to get the boundAddress and boundPort for JBoss server at the time of the Jvm startup. We have a jvm agent which starts with JBoss server and while trying to get the boundPort and boundAddress through MBean we are getting exception as,
^[[0m^[[31m16:03:34,066 ERROR [stderr] (ServerService Thread Pool -- 54) javax.management.InstanceNotFoundException: jboss.as.expr:socket-binding-group=full-sockets,socket-binding=http
^[[0m^[[31m16:03:34,067 ERROR [stderr] (ServerService Thread Pool -- 54) at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:94)
^[[0m^[[31m16:03:34,067 ERROR [stderr] (ServerService Thread Pool -- 54) at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:171)
....
....
Same piece of code works if we deploy our agent after the server has initialized. I tried loop around the try-catch block where the exception is coming, assuming MBean server might be waiting for initialization but that also did not work.
I would like to know if there is any better way to get these values at the time of startup.
Thanks,
Rupesh

Restarting the app server getting error?

we are getting error when restarting the app server.
generally when we restart the app server it will create connections itself.
but it was throwing below error.
2013-11-05 04:06:00,029 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] (pool-11-thread-1) Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: null, message from server: "Host 'jade2.ftdi.com' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'")
Observed below log also:
2013-11-05 04:07:18,074 INFO [STDOUT] (pool-11-thread-1) DEBUG 2013-11-05 04:07:18,074 [pool-11-thread-1] com.ftd.core.datasource.model.DataSourceHealthMonitor: doDBServerMaintenance path to db server maintenance files jboss.server.data.dir
2013-11-05 04:07:18,074 ERROR [STDERR] (Thread-12) java.lang.OutOfMemoryError: Java heap space
2013-11-05 04:07:20,844 INFO [STDOUT] (http-0.0.0.0-8713-2) ERROR 2013-11-05 04:07:16,673 [http-0.0.0.0-8713-2] com.ftd.core.datasource.exceptionhandlers.NormalExecutionHandler: Caught TransactionException.org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.ftd.core.datasource.exceptions.ConnectionException: nested exception is com.ftd.core.datasource.exceptions.DataSourceException: All Databases are down!!!
After this error Our DBA'S issued flush hosts; in DB side but no luck still we are getting same error.how fix it
java.lang.OutOfMemoryError: Java heap space
Maybe you should try to increase the heap size of VM

jboss OutOfMemory

We have a java application which use JBoss 4.2.0, EJB, Hibernate.
In one of our production server, getting OutOfMemory error at regular interval.
We are seeing user defined exceptions in the jboss and server log files. we intentionally throwing this user defined exception from our code when the user hit the particular piece of code. But the number of users and usage is more for this customer. so it throws 400-500 exceptions. After that we are getting a
WARN org.jboss.mq.SpyJMSException: No pong received;
We have already implemented the ExceptionListener to reconnect the topicConnection in case of failure. And also some of the socketexception as below.
2012-10-12 10:33:57,824 ERROR [org.apache.tomcat.util.net.PoolTcpEndpoint] (http-0.0.0.0-8880-Processor1436) Socket error caused by remote host /125.236.40.205 java.net.SocketException: Connection reset
Have analysed the heap dump generated. 4.5 GB memory is occupied by jmsspyobject exception.
We have got the thread dump from jmx console. Do we need to load the copied thread dump to TDA(Thread Dump Analyzer) tool?
Is OOM because of user defined exception in so many numbers? do we need to reduce it ? or user defined exceptions are not cause for the OOM error?
Please find the attached thread log. I am very new to analyze the jboss thread logs. Could anyone help me to do this?
http://www.4shared.com/file/toRiqF1n/perf-info.html
Thanks.

SalesForce connection throwing java.lang.OutOfMemoryError in vFabric

OK, somehow in the log of the server I was not getting the proper error, but after trying different things I got an OutOfMemory:PermGenSpace error, and for that one stackoverflow already has a solution.
Dealing with "java.lang.OutOfMemoryError: PermGen space" error
I use the solution there and my problem is solved :)
Thanks #maximdim for your help
I've been struggling with an issue for two weeks.
I am connecting to test.salesforce.com through a web service in a Java web application using jdk7.
I generated the stubs with JAX-WS wsimport.
I am using STS with VMWare vFabric tc Server v2.6 in my local environment, here connection works fine.
The problem is when I deploy to the test server which is SpringSource tc Runtime 7.0 with jdk 7 I get the following exception after doing the web service call:
Exception in thread "RMI TCP Connection(idle)"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "RMI TCP Connection(idle)"
Exception in thread "RMI TCP Connection(idle)"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "RMI TCP Connection(idle)"
Exception in thread "RMI TCP Connection(idle)" Exception in thread "ContainerBackgroundProcessor[StandardEngine[Catalina]]"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "RMI TCP Connection(idle)"
I have already incremented the memory parameters in the test server. It is starting with 1 GB or memory. I am giving more detail on the way memory has been increased:
vFabric server has a console, so we have the following configuration there:
Min Heap Size: 1,000MB
Max Heap Size: 16,000 MB
Thread Stack Sie: 192 KB.
I also found the file where these parameters are set (setenv.sh) and they are like this:
JVM_OPTS="-Xms1000m -Xmx16000m -Xss192k -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"
I also know that is not a connectivity issue because sometimes the connection is made successfully but after that I get the error.
I also got a dump of the memory after the OutOfMemoryError and analyze it with Eclipse plug in and the memory leak is in:
com.sun.xml.internal.ws.client.sei.SEIStub
$Proxy51
Tried to post the image here but as I am a new user stackoverflow didn't allow me.
Please HELP!! Any help will be appreciated.
Alan Robles
How exactly did you 'incremented the memory parameters'? There are few different memory regions in JVM so you might increment one of them but the problem is in another - e.g. PermGen vs. Heap.
OK, somehow in the log of the server I was not getting the proper error, but after trying different things I got an OutOfMemory:PermGenSpace error, and for that one stackoverflow already has a solution.
Dealing with "java.lang.OutOfMemoryError: PermGen space" error
I use the solution there and my problem is solved :)
Thanks #maximdim for your help.

Categories

Resources