Dom Incollingo

Greenhorn
+ Follow
since Dec 04, 2002
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Dom Incollingo

Jeanne,

Thanks very much for the info. I checked our Ant installation a few weeks ago, and we're running version 1.6.5. So I don't think that there is a more stable version for us go upgrade to.

I've since found a couple other people that had the same problem when trying to run a build script from WebSphere Studio, but one of them was able to run the same ant script on Eclipse. So I'm guessing that there is some WebSphere-specific setting that I need.

For now, I'm happily running the build script from the command line on one of our Linux servers.

Thanks again for your time and suggestions.

Dom
18 years ago
Jeanne,

Thanks for the response. Do you recall which version of Ant you had to upgrade to? Since the ant build works file when it is run from the command line, I figured (perhaps incorrectly) that the problem was with WSAD. But when I get to work tomorrow, I will check our version of Ant and try upgrading to a newer version.

Dom
18 years ago
Hello,

I am trying to run a couple ant build scripts to build and deploy java applications. The ant scripts run successfully when I execute them from the command line. However, if I try to run the same ant scripts from WebSphere Studio (version 5.1), the compile step fails with the message: "Modern compiler not found - looking for classic compiler".

I googled for this error, and found some IBM documentation that says I need to supply the following argument when executing the ant script from WebSphere Studio: -Dbuild.compiler=org.eclipse.jdt.core.JDTCompilerAdapter

Well I tried supplying the above argument, but I still get the exact same error.

Has anyone encountered and found a solution to this problem?

Thanks very much!

Dom
18 years ago
Thanks for the reply. I didn't see your reply until today (April 4). Last night, I made a few functional changes (unrelated, I thought), and one of them seems to have solved the problem.

There were a couple work fields stored in the form bean (ActionForm), called
userAction and systemAction, that were being used to determine which
buttons to display based on what the user was trying to do. I removed
the field called systemAction..... And when I ran the next test, the
system did a doPost but did not follow that with a doGet. How this could have solved the problem, I can't even begin to imagine....

When I get home from work tonight, I'll check the code rendered by the validator framework, as you suggested. I am using html:submit for my buttons; perhaps changing them to html:buttons would also have solved the problem (and a better solution as well).

Thanks for your help.
18 years ago
Hello,

I'm using Struts 1.2.4 (along with the validator framework), and I've noticed that for my forms that do a Post, the action class is executed twice. I put log statements in my code to try to figure out what is happening. The sequence of events is as follows:

- User presses Update button on a JSP
- doPost method invoked (ActionServlet)
- Struts validation methods invoked
- execute method (Action class) entered
- execute method (Action class) returns forward action of Success
- processing returns to the same JSP
.........................................................................
- doGet method invoked (ActionServlet)
- Struts validation methods invoked
- execute method (Action class) entered
- processing returns to the same JSP
- web page is displayed on browser

Everything prior to the doGet looks normal. I can't understand why the JSP submits a Get request when it should display. The method specified in the JSP's form (there is only one form in the JSP) is a Post, not a Get. The JSP does not contain any JavaScript.

Has anyone seen this problem or know what is happening here? Thanks very much for your assistance.

Dom
18 years ago
Nothing is being closed on the client side (the java application). Someone I work with suggested that we may be having a problem on the server side(UNIX legacy system) - that perhaps UNIKIX is locking the socket.
Hello everyone,
I am working on a java application (JDK 1.3.1 running on Windows NT) that does a TCP/IP connection to a backend legacy system running on UNIX. This java application has been running successfully for over a year, using Sockets to send data to and receive data from the backend legacy system. A new Socket was instantiated for each transmission of data.
We are now trying to pool our sockets in order to improve efficiency. Each time the java application re-uses a Socket from the pool to communicate with the backend legacy system, a SocketException is thrown. We are able to send data from the java application to the legacy system. But when we try to receive data by invoking the 'read' method of the Socket's InputStream, we get a SocketException with the message "Connection shutdown: JVM_recv in socket input stream read." I have verified that the Socket's 'close' method is not being called.
Does anyone have any ideas about what may be causing this exception or how I can resolve it? Thanks very much for your help.
Dom