We Keep Coding

Spring: Sporadically getting No handler found for portlet request

I've been having some issues with NoHandlerException's in a multi server configuration. I've been trying to figure out exactly when I get this exception but
I can not find any good description on what it actually means that no handler was found.
The thing here is that everything actually seems to work fine, we are not receiving any error reports on this from our production system, and we are not able
to reproduce the error in our test systems. But we can clearly see a big amount of no handler found errors in our production logs.
So my question is, could this error be due to some bad load-balancing? Like that we send our users between
different servers and the server receiving server does not have an updated state for this user/session? Or should it be some configuration error on the Spring-application
that can not be affected by the load balancing?
When I have searched for other people with the same error they seem to get it all the time, but I get it only sporadically
The error we receive:
Uncaught service() exception root cause AppName: javax.servlet.ServletException: org.springframework.web.portlet.NoHandlerFoundException: No handler found for portlet request: mode 'view', phase 'ACTION_PHASE', parameters map['action' -> array<String>['myController.parameter']]

Try to check xml somewhere contains portlet. Normally every handler stage error cased by configuration.

Occasionally Getting java.lang.NoClassDefFoundError

I have a very unusual error condition that I can't seem to find the solution to. I'm hoping someone out here in StackOverflowland can help. Before you just look at the title and say "your CLASSPATH is wrong," read on!
I work with a server-based Java application that utilizes a number of third-party libraries. The particular library that I'm getting the error with is a file transfer library. Part of the functionality of the application allows the user to connect to remote servers (FTP, SFTP and FTPS) and send/receive files.
One of our customers is using the application and occasionally gets a "Class Not Found Exception" (or more specifically, "No Class Definition Found") when attempting to connect to a remote host. What's weird is that they don't get it all the time. They have sent me logs that show a successful connection and then another one which shows this error. There was no restart of the server between the two and both connections are to the same host using the same connection settings.
What would cause a "Class Not Found Exception" to occur occasionally within a Java application on a class that has already been successfully used? I've contacted the third-party vendor and they are just as puzzled.
I wasn't able to determine anything from the stack trace, but since it was requested, here it is:
java.lang.NoClassDefFoundError: com.enterprisedt.net.j2ssh.configuration.ConfigurationLoader (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:139)
at com.enterprisedt.net.j2ssh.SshThread.a(SshThread.java:93)
at com.enterprisedt.net.j2ssh.SshThread.<init>(SshThread.java:73)
at com.enterprisedt.net.j2ssh.transport.TransportProtocolCommon.startTransportProtocol(TransportProtocolCommon.java:515)
at com.enterprisedt.net.j2ssh.SshClient.connect(SshClient.java:593)
at com.enterprisedt.net.ftp.ssh.SCPClient.connectSSH(SCPClient.java:1137)
at com.enterprisedt.net.ftp.ssh.SSHFTPClient.connect(SSHFTPClient.java:920)
at com.enterprisedt.net.ftp.async.internal.ConnectTask.connect(ConnectTask.java:154)
at com.enterprisedt.net.ftp.async.internal.ConnectTask.run(ConnectTask.java:216)
at com.enterprisedt.net.ftp.async.internal.FTPTaskProcessor$b.run(FTPTaskProcessor.java:590)

How to fix error: [BEA][SQLServer JDBC Driver]No more data available to read

My java application does use DB Connection pooling. One of the functionality started failing today with this error:
[BEA][SQLServer JDBC Driver]No more data available to read
This doesn't occur daily. Once I restart my application server things look fine for some days and this error comes back again.
Anyone encountered this error? Reasons might vary, but I would like to know those various reasons to mitigate my issue.

Is it possible that the database or network connection has briefly had an outage? You might expect any currently open result sets then to become invalid with resulting errors.
I've never seen this particular error, but then I don't work with BEA or SQL Server, but a quick google does show other folks suggesting such a cause.
When you're using a connection pool, if you do get such a glitch, then all connections in teh pool become "stale" or invalid. My application server (WebSphere) has the option to discard the entire connection pool after particular errors are detected. The result then is that one unlucky request sees the error, but then subsequent requests get a new connection and recover. If you don't discard the whole pool then you get a failure as each stale connection is used and discarded.
I suggest you investigate to see a). whether your app server has such a capability b). how you application responds if the database is bounced, if this replicates the error then maybe you've found the cause.

Jboss Server Exception

Jboss server was throwing an Exception all of a sudden "You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null". No changes made to the datasources, prior to this. Everything got normal after a server bounce...
What are all the possibilities for this?

After digging into this issue further, we found there was a dependency which was not responding, that increased the thread count.There was also memory leak. Due to this server got restarted by itself... From the logs it was clear the server got restarted and that could be the reason this exception. As mentioned in the above comments the search pages from the google shows that this exception could be thrown when there is issue loading the datasources... Everything was fine after bouncing the server... Thanks all...

What is causing a JVMTI_ERROR_NULL_POINTER?

I'm getting an error when my application starts. It appears to be after it's initialized its connection to the database. It also may be when it starts to spawn threads, but I haven't been able to cause it to happen on purpose.
The entire error message is:
FATAL ERROR in native method: JDWP NewGlobalRef, jvmtiError=JVMTI_ERROR_NULL_POINTER(100)
JDWP exit error JVMTI_ERROR_NULL_POINTER(100): NewGlobalRef
erickson:
I'm not very familiar with the DB code, but hopefully this string is helpful:
jdbc:sqlserver://localhost;databasename=FOO
Tom Hawtin:
It's likely I was only getting this error when debugging, but it wasn't consistent enough for me to notice.
Also, I fixed a bug that was causing multiple threads to attempt to update the same row in DB and I haven't gotten the JVMTI... error since.

JVMTI is the debugging and profiling protocol. So, I'm guessint it's something peculiar to the environment you are attempting to run your application in.

I'm guessing you are using a native-code–based database driver (JDBC driver type 1 or 2). And I'm guessing that driver is buggy. If you could provide more information about the driver and your datasource configuration or connection string, it might help determine some answers.