topic Re: Invalid state, the PreparedStatement object is closed. in Talend Studio

Invalid state, the PreparedStatement object is closed.

Anonymous — Fri, 23 Mar 2018 14:38:43 GMT

Hi,

I am facing an issue with the below flow -

tMap --> tJavaFlex-->tMSSQLOutput_1

tMSSQLOutput_2

through tJavaFlex I could have multiple rows for one row. When I am executing the job. It is throwing the below error.

Exception in component tMSSqlOutput_2
java.sql.SQLException: Invalid state, the PreparedStatement object is closed.

Does anyone faced that issue or have a solution for that ?

Re: Invalid state, the PreparedStatement object is closed.

vboppudi — Fri, 23 Mar 2018 16:40:27 GMT

Hi,

tMSSQLOutput_1 and tMSSQLOutput_2 using same DB object or different DB objects?

Regards,

Re: Invalid state, the PreparedStatement object is closed.

Anonymous — Mon, 26 Mar 2018 07:50:02 GMT

Hello,

We will appreciate it a lot if you can upload your current job design screenshots on forum.

Best regards

Sabrina

Re: Invalid state, the PreparedStatement object is closed.

Anonymous — Mon, 26 Mar 2018 08:04:12 GMT

Hi vbopuddi,

I have tried both the case - Same and different connection. What I have found - the problem is with tJavaFlex. If I remove the tJavaFlex, its executing fine.

As everytime I am getting two flows out of one through tJavaFlex. So for now to resolve the issue I have removed tJavaFlex and created one more flow out of tMap.

But in case if there are multiple flows, there must be a permanent solution.

Best Regards,
Abhishek

Re: Invalid state, the PreparedStatement object is closed.

Anonymous — Mon, 26 Mar 2018 08:08:04 GMT

Hi xdishi,
Sorry, due to some security issues, I can not share the complete document. But the flow is like below-

tfilterRow -> tJavaRow -> tMap -> tJavaFlex->tMSSQLOutput_1
|
tMSSQLOutput_2

Best Regards,
Abhishek

Re: Invalid state, the PreparedStatement object is closed.

vboppudi — Mon, 26 Mar 2018 15:03:01 GMT

Hi,

What are you doing in tJavaFlex component?

Regards,