Link to home
Start Free TrialLog in
Avatar of raghavanm1978
raghavanm1978

asked on

SQLLDr stops at 60 secs when called from websphere

1. our application runs on websphere, on linux.
2. The application calls SQLLDr
3. SQLLdr opens up, processes some records and stops and after some time websphere process is hung (obviously!)
4.  When SQlLdr is opened directly from command prompt and the same .ctl file and .param files are used with the same text data, SQLLdr prefectly loads all the records.

Question is where is the problem. This is a highly critical issue and any help is greatly appreciated!
Avatar of Gary Patterson, CISSP
Gary Patterson, CISSP
Flag of United States of America image

This really isn't the place for "highly critical issues".  If it is critical, I suggest you get a paid professional in who knows how to troubleshoot this kind of problem.  We don't have access to your system, and you've provided very little information to help with troubleshooting.

1) How is SQLLDR invoked?  Show the code.
2) What error, if any are you getting?  Provide a stacktrace.  

Finally, look at this:

http://www.coderanch.com/t/549118/java/java/Trouble-executing-sqlldr-java

- Gary Patterson
Avatar of raghavanm1978
raghavanm1978

ASKER

@dvz why would your solution help?
@gary , I am trying out what has been said in the article.. Will let you know if it worked
You've deconstructed the problem down to ensuring that sqlldr works by itself.  That suggests the root cause is something outside of sqlldr.  If websphere is "hanging", one possibility is that it's timing out (set too low?).  The article offers how to check and change the websphere default.  Hope that helps.
WAS default session timeout is 30 minutes.  This hang is apparently happening after 60 seconds, so it seems unlikely that it is related to the session timeout.
I agree it is not the WAS default session time out. And as the code ranch article states, I have the same problem in that if lesser number of records are there, it gets processed. So must be something with the pipe that is being talked about in the article. I shall post the code here soon to get your help
Here is the code :

command = "sqlplus -S "+_user+"/"+_password+"@"+_sid+" @"+m_file_name;
            String log_safe_command = "sqlplus -S *****/*****@***** @"+m_file_name;            
                  
            Runtime r = Runtime.getRuntime();
            long startTime = System.currentTimeMillis();
            
            try {
                Process process = r.exec(command);
                  command = log_safe_command;

                  if (process == null) {
                        Log.error(BatchImportManager.LOGGER,Messages.getString(E_PROCINIT, command));      
                        throw new Exception(Messages.getString(E_PROCINIT, command));
                  }
                  else {
                        Log.info(BatchImportManager.LOGGER,Messages.getString(I_WAITINGPROC, command));
                        process.waitFor();
                        String elapsed_time = (new Long((System.currentTimeMillis() - startTime)/1000)).toString();
                        Log.info(BatchImportManager.LOGGER,Messages.getString(I_PROCCOMPLETE, new String[] {command, elapsed_time}));
                        StringBuffer strBuffer = new StringBuffer();
                        String line;
                        BufferedReader reader = new BufferedReader(new InputStreamReader(process.getInputStream()));
                        while ((line = reader.readLine()) != null) {
                              strBuffer.append(line).append("\n");
                        }
                        reader.close();
                        if (process.exitValue() != 0) {
                              Log.error(BatchImportManager.LOGGER,Messages.getString(E_BADEXITCODE, new String[]{(new Integer(process.exitValue())).toString(), command}));
                              throw new Exception(Messages.getString(E_BADEXITCODE, new String[]{(new Integer(process.exitValue())).toString(), command}));
                        }
                  }                  
            }
            catch (InterruptedException e) {
                  Log.error(BatchImportManager.LOGGER, Messages.getString(E_WAITING, new String[] {command,e.toString()}));
                  throw new Exception(Messages.getString(E_WAITING, new String[] {command,e.toString()}));
            }
            catch (IOException e) {
                  Log.error(BatchImportManager.LOGGER, Messages.getString(E_EXECUTING, new String[] {command,e.toString()}));
                  throw new Exception(Messages.getString(E_EXECUTING, new String[] {command,e.toString()}));
            }
ASKER CERTIFIED SOLUTION
Avatar of Gary Patterson, CISSP
Gary Patterson, CISSP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The java world article absolutely helped. If you coded according to that then everything works. Basically the problem was that the output from SQLldr was not read, hence the buffer was full, not allowing  SQLLdr to continue