java error

[Bob Manocchia]

We have a data warehouse server running Informatica. We are seeing errors logged which we know next to nothing about. Please see the attached extraction from the log.

Any help would be appreciated.

[Steven E. Protter]

Shalom,

This looks like bad application code. You probably didn't write the code so it should be reported to those who did provide the code.

It would be helpful to know what your current level of java is. Bringing it up to date might help so long as informatica doesn't have a problem with that.

http://www.hp.com/go/java

swlist -l product | grep jre
or
swlist -l product | grep jdk

SEP

[Matti_Kurkela]

I agree with SEP.

There might be an underlying connectivity problem, but the application definitely isn't making the diagnosis easy.

Some wild guessing follows:

It might be that it does not check whether the setup of the XAConnectionFactory (whatever that is) succeeds or not, and just proceeds forward until the connection is needed, and then blows apart when the assumed connectivity isn't there. Sadly, this lack of error checking is far too common.

At this point, a good program should output an error message detailing where it was trying to connect and what kind of error there was.

To even begin to solve this problem, you would need to know what the "XAConnectionFactory" and "dlq connection" are and where they're supposed to connect to in this part of the program. Armed with this information, you could check whether there are any network or firewall problems. Or maybe the target system simply isn't responding.

With only the error message, I think this problem is not solvable without access to the java source code or a lot more documentation about this specific application.