Thanks for the reply,
the problem was not multithreading.
It was a program that wants to send a break message to the client.
the program has used the same communication port as the programcall so the
client receaved not the expected messageheader and was closing the port.

problem solved by not sending the message but put them into one of the
return parameter.
__________________________________________



"Gary L Peskin" <garyp@xxxxxxxxxxxx>
Gesendet von: java400-l-bounces@xxxxxxxxxxxx
15.09.2010 18:31
Bitte antworten an
Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>


An
"'Java Programming on and around the IBM i'" <java400-l@xxxxxxxxxxxx>
Kopie

Thema
RE: Problem with ProgramCall and Parameters






Hi, Andreas --

Do you get the same result if you invoke this same program from a small
standalone java program? I'm thinking that this error may be due to some
problems with your multithreaded environment.

Gary

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of A.Fritz@xxxxxxxxx
Sent: Wednesday, September 15, 2010 8:00 AM
To: java400-l@xxxxxxxxxxxx
Subject: Problem with ProgramCall and Parameters

Hi,

today I run into a problem with ProgramCall.
I am using ProgramCall for long time, but this week I got an Exception
I never had before and after 2 days research I couldn't get further.
I switched to jt400 7.1 After going back to 6.6 this error still
occurs.
It seems that some data is not correctly transfered back to the program
call.
the program which is called is running to the end. Also the output
parameters are set at the end of the program. but somehow my java
client does not get the correct data.

Is there anybody who can give me a hint to solve the problem?

, here ist the log:

Thread[AS400 Read Daemon
[system:192.168.2.250;job:833862/QUSER/QZRCSRVS],5,RMI Runtime] Mi Sep
15
16:09:10:921 CEST 2010 Incorrect data stream header detected.
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
40 40 40 40
java.lang.Throwable
at com.ibm.as400.access.Trace.log(Trace.java:1017)
at com.ibm.as400.access.ClientAccessDataStream.construct(
ClientAccessDataStream.java:95)
at com.ibm.as400.access.AS400ThreadedServer.run(
AS400ThreadedServer.java:347)
at java.lang.Thread.run(Thread.java:595)
Thread[AS400 Read Daemon
[system:192.168.2.250;job:833862/QUSER/QZRCSRVS],5,RMI Runtime] Mi Sep
15
16:09:10:921 CEST 2010 run(): Caught RuntimeException:
com.ibm.as400.access.InternalErrorException: Data stream is not known.
at com.ibm.as400.access.ClientAccessDataStream.construct(
ClientAccessDataStream.java:121)
at com.ibm.as400.access.AS400ThreadedServer.run(
AS400ThreadedServer.java:347)
at java.lang.Thread.run(Thread.java:595)
Thread[AS400 Read Daemon
[system:192.168.2.250;job:833862/QUSER/QZRCSRVS],5,RMI Runtime] Mi Sep
15
16:09:10:937 CEST 2010 run(): Notifying threads after
RuntimeException.
Thread[AS400 Read Daemon
[system:192.168.2.250;job:833862/QUSER/QZRCSRVS],5,RMI Runtime] Mi Sep
15
16:09:10:937 CEST 2010 run(): Threads notified after RuntimeException.


Code Snippet:

ProgramCall program = new ProgramCall(this.as400);
program.setProgram(caasObject.getPgmLib() +
parameters.get("ProgramLibrary") + caasObject.getProgramName());
program.setParameterList(this.createParameterList(parameterTypes,
parameters));

program.run();

thank you,
Andreas
--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.