DSXchange

Hello All, I am at a client place with 9.1.2 version. Client is considering moving to a managed Grid env with 11.5 version and at the enterprise level, modernization initiative is pushing all the teams to look for alternatives that work with/within BigData eco system. Since the migration(effort/cost...

Kondeti,
I appreciate your response. I will keep that in mind.

I found a resolution to force the Integration stage to use TLS1.2. Now the Debug logs shows "*** ClientHello, TLSv1.2" and my job goes though without any issues.

-Dhttps.protocols=TLSv1.1,TLSv1.2.

Craig, Still looking to see if JAVA1.6 even supports TLS1.2 or not. Few google search reads say yes and some don't. The target is allowing us through a different port but i need to be able to get a resolution to use TLS1.2. From your perspective, time to reach IBM, since the properties are not being...

I tried with those options. It didn't work, I switched on the debug mode and it still says "*** ClientHello, TLSv1" . Please the fill DEBUG log below -Dcom.ibm.jsse2.overrideDefaultTLS=true -Dcom.ibm.jsse2.overrideDefaultProtocol=TLSv12 -Djavax.net.debug=all -------------------------------...

I have a java program that is being called from JAVA Integration stage to invoke a REST API. It has been working fine with the end points using a port num 8443. see the java version below java -version java version "1.6.0_30" OpenJDK Runtime Environment (IcedTea6 1.13.3) (rhel-5.1.13.3.el6...

I tried to implement the same with in a transformer and looks like I am running into same issue. The restructuring I am grouping on has 25k iterations to go though and failing with this error below.
waitForWriteSignal(): Premature EOF on node "nodename" Socket operation on non-socket

Thanks for your Input. yes the job runs fine till 13.5 M records and it fails after that. even if we bump up the heap it didn't help. We are raising a ticket to IBM and see if they can help. Speaking of doing the restructure and Hjoins outside of that stage, taking a alternate approach to avoid usin...

I looked down the log and these are additional ones I see. node_node2: Player 1 terminated unexpectedly. seq_pfsComp,0: Failure during execution of operator logic. seq_pfsComp,0: Output 0 produced 9581094 records. seq_pfsComp,0: Fatal Error: Unable to allocate communication resources main_program: A...

To make the job fail, I took the files to lower env with a 256MB value for heap and it failed with clear error as you expected, but when I increase the heap and reran it fails with no specific error like before.

Thanks for the response.
1. The data that is coming in for restructuring is pre sorted.
2. The heap size has been set to 2.5 GB

Speaking of splitting the data, is there a way for me to find out we are running out of Heap or any other setting that is causing the job to blow up?

Thanks.

We have a job that creates Json file using the hierarchical stage for XML transformation. The stage is connected from 3 sequential stages and the XML stage assembly does Restructure and Hjoins. The job is failing after reading 13.5 M records. Is there a setting or environment variable for the stage ...

Thanks for the reply. If the above was the case, the error should have been consistent across all the env, which is not the case. we are able to run parallel jobs successfully without any issues in the other env.

I appreciate all of your inputs. coming back here to update. We have setup this up. created JSONs in datastage and invoking a JAVA program/class from Java Integration stage and persist API response to a DB. we tested this in Lower Env and getting 24 Rows/sec. which is expected due to target end poin...

I had to add the required .jars explicitly in the class path, even after bundling them in the main class .jar file. This is fixed now.

Thanks for your reply. i tested from ../branded_odbc/samples/example/example utility as well as ./uvsh ds_connect utility. both work just fine. but when i run the job it fails. like you said in the log the error shows up as information at the beginning and i see the same as fatal and job failure aft...