• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 281
  • Last Modified:

JBoss + postgresql + SQLException - Different results on Windows and Linux

Does JBoss for Linux need to be configured differently than JBoss for Windows for SQLException handling?

I installed the latest 3.2.5 JBoss on Windows and Linux and didn't configure anything. I'm using Eclipse 3.0 with MyEclipse 3.8.1 (+ update packs) to create a deploy directory for my application for JBoss on Windows. I then zip up this directory and move it to the same diretcory on the Linux both and unzip it and test the application there.

Here is my situation: I am creating a Struts 1.1 based application that runs fine under Tomcat 5 and JBoss 3.2.5 on Windows. During login, I am validating the user against their PostgreSQL database login. If they enter a bad username/password, PostgreSQL generates an exception. On Windows the following code works:

try
{
    // Code to attempt login with username/password entered
}
catch (SQLException e)
{
    log.error("Error in validating user.");
    log.error("\tSQL statement = " + sQuery);
    log.error("\terror code = " + e.getErrorCode());
    log.error("\tstate = " + e.getSQLState());

    if (e.getSQLState().equals("08004"))
    {
        // have a password/userid error, return null user
    }

the 'state' is '08004' on userid/password errors.

I packaged up my exploded war directory on Windows and moved it over to Linux and unzipped it into jboss-3.2.5/servers/default/deploy -- same location as on Windows. However when I run the same code on Windows and enter in an invalid user id/passowrd combination, when the exception is thrown and caught and my code is run, the 'state' returned is NULL.

If a proper userid/password are entered they are logged into the system and everything runs fine.

Thanks in advance for any corrections or suggestions.

Brian
0
Brian Bezanson
Asked:
Brian Bezanson
1 Solution
 
Brian BezansonSoftware Architect/DeveloperAuthor Commented:
The solution to the above issue was to update the versions of JBoss, PostgreSQL, and especially the Java JRE to their respective current versions. Once the JRE was updated to 1.4.2_05 the result code came back as expected.

Brian
0
 
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now