|
Patrick, We were thinking along the same lines and implemented your suggestion late last week. The Host table did have an entry for the local system, but the search order was set to use *REMOTE. Plus, there were no DNS entries. We set the search order to *LOCAL and added 2 valid DNS server IP addresses. The response time did improve, but strangely enough, the program still goes into a SELW status but for 10 seconds rather than 30. We opened a conversation with the Support Line on Friday as well, and they gave us some things to try to see if we can narrow the possible causes. Kendall -----Original Message----- From: java400-l-admin@midrange.com [mailto:java400-l-admin@midrange.com] On Behalf Of Patrick Townsend Sent: Monday, February 18, 2002 1:54 AM To: java400-l@midrange.com Subject: Re: Java program waits 30 seconds in SELW status The GetHostName API may be doing a DNS query to find your host name. Use CFGTCP to define a local host name and domain. Then add this to the host table. Lastly, make sure the seach order is for *LOCAL first. You might find this helps. Patrick ----- Original Message ----- From: "Kendall Coolidge" <kendall.coolidge@ccbai.com> To: <java400-l@midrange.com> Sent: Thursday, February 14, 2002 11:33 AM Subject: RE: Java program waits 30 seconds in SELW status > Thanks for your reply, David. We have done some further investigation and > have found the following: The customer AS/400 is actually more up to date > with PTF's than we are. Is there a specific licensed program that I can > check for PTF level? > > The job that hangs at SELW is the QJVACMDSRV job. The first time data is > sent to the port, the program begins to execute immediately, processes the > data, and returns to wait on the port. The second and subsequent times data > is sent to the port we see the 30 second SELW status. We examined the call > stack of QJVACMDSRV while it was in SELW and found the following procedure > name at the end of the stack: > Java-net-InetAddress-getHostName()Ljava-lang-String; > > Does this give you any clues? > > Best regards, > Kendall Coolidge > > -----Original Message----- > From: java400-l-admin@midrange.com [mailto:java400-l-admin@midrange.com] On > Behalf Of Dave Wall > Sent: Wednesday, February 13, 2002 5:17 PM > To: java400-l@midrange.com > Subject: Re: Java program waits 30 seconds in SELW status > > > From the developer who works on the command/program call server ... > > SELW is a Select Wait - our daemon jobs go into that all the time while > sitting on a select(), waiting for a connection. If the customer > program is using a select() in order to check sockets for something to > read or write, that would explain the SELW. Then the question becomes > why is it waiting for 30 seconds when the same program doesn't wait on a > different system. Are they up to date on PTFs, particularly for the > sockets components? Does the program use select()? If so, I would look > at the code around that area. > > David Wall > AS/400 Toolbox for Java > > > > > "Kendall > Coolidge" To: > <JAVA400-L@midrange.com> > <kendall.coolidge cc: > @ccbai.com> Subject: Java program waits > 30 seconds in SELW status > Sent by: > java400-l-admin@m > idrange.com > > > 02/12/2002 05:20 > PM > Please respond to > java400-l > > > > > > Hello All, > > We have an AS/400 Java program that binds to a TCP port and waits for data > to come through. When running on our AS/400, when the data is received, > the > program immediately executes the next lines of code, processes the data, > and > returns to wait on that port. However, on a customer's AS/400, the program > goes into a SELW status after it receives the data and waits there (using > no > CPU) for 30 seconds before processing the data successfully. > > Can anyone suggest why the two machines would act so differently? Both are > V4R5, using Toolbox 4.5 Mod 0.3, and JDK 1.1.8. Our older model 40S does > not exhibit this behavior while the customer's 270 does. > > Thanks in advance for any suggestions! > > Kendall Coolidge > > > _______________________________________________ > This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/java400-l. > > > > > > _______________________________________________ > This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/java400-l. > > > _______________________________________________ > This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/java400-l. > > _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com 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 mailing list archive is Copyright 1997-2024 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.