BACKGROUN JOB Debugging

How can i Debug background job.

Hi,
You can enter a running program in debug via SM50:
Program/Session > Program > Debugging
If a program runs very quickly then this can be difficult. One option to get around this would be to add a endless loop to your program. Enter debug via SM50 and change conditions so loop exits and you can step through rest of the program.
Alternatively schedule a background job with two programs. First program will be BTCLOOP then your own program. BTCLOOP exists in all systems, it just runs in a endless loop to allow you access the debugger from SM50. As above, once in debug mode just end the loop and your own program will then start in debug mode.
-Paul

Similar Messages

How to set va05 sales order list is backgroun job

Hi Friends,
My problem is when the user trying to take the report of sales order from 1 st january to till date in va05 system is going into dump?
My question is how can we set this as a background job can we solve this issue through background job?
Regards
Rack29

Hello Rack,
I don't think setting this task of generating a report of Sales Order through VA05 in background will prevent your code getting short dumps.
The best thing would be reach out to ABAPer and start analysing transaction code ST22 where the complete DUMP ANALYSIS is given. Then by refering this information and the proper action can be taken up.
Please try out this exercise and kindly revert back if there any issues.
Regards,
Sarthak

Starting backgroun job, when instance starts up

Hi,
having the portal service implementation from earier times in mind and
look for a way to write a backgroung job, which will be started when the CE instance is started.
Therefore each portal service implements the start() method. This possibility I miss for application or any aother kind of J2EE services.
Can you provide information how this can be done on J2EE or composite application level, because I want avoid to be in touch with the prt.
Thanks,
Jens

Hi Jens,
check out the Netweaver Scheduler for Java:
http://help.sap.com/saphelp_nwce10/helpdata/en/44/2da75e13363f0ae10000000a114a6b/frameset.htm
Regards,
Christian

Backgroun job, getting error message

Hello ,
I am trying to run a report in background. In one server it is working fine, but in another server it is giving me error
"450 columns too great for format X_65_255"
line-size of report is 450. It is working fine in one 4.6c server but not in another 4.6c server.
Please advice.
regards

i am already in SPAD, but .....
can't see where to look for and create these formats
regards
well i got it thanks everyone.
I want to close this thread and reward point, but can't see radiobutton on left side, don't know why
Message was edited by: Surpreet Singh Bal

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Very urgent ----Background job

Hi all,
I had executed a Program in background, job got finished but there is one error log saying that
<b>No external transaction was assigned to internal transaction 0020 / 0010</b>
but when i debug in foreground,it is going to that error message line but not displaying the error message,
same case when i debug with sy-batch = 'X' also
only when i schedule ,it is showing that error message

Hi.
You have the possibility to debug a program as a job. For that you have to call transaction sm37 and display your job. When you mark your special job and type in the command jdbg (job-debugging) you are able to debug the program with all system-settings like the job-run.
In the first step you are (in the debugger) somewhere in standard-programs. When you press several times F7 you will come to your programm. An other possibility to get there is to set a breakpoint in your program.
Hope this helps.
Michael

Change source path in batch Job

Hi Experts,
my organization has created job in data services 3.2 to cleanse the data reading from excel flat files. the folder path was store in the global variable(I think) and now they have changed the directories hence is it throwing me below error.
Error, Input file does not exist please confirm existence and restart job, 16 ) >
failed, due to error <50316>: <>>> Error, Input file does not exist please confirm existence and restart job>. I want to update the folder path. I am sure it would be easy but I am very new to BODS.
(12.2) 07-15-14 16:10:08 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Sleeping for 35.000000 seconds... '
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Waking up...... '
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : 'Starting the timer loop number 6...'
(12.2) 07-15-14 16:10:43 (14232:12656) WORKFLOW: Work flow <WF_Metadata_Files> is started.
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> $G_FILENAME_IN : ALL_Metadata_SALES.xls...'
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> looking for input file name
\\infra\finance\production\sales\Metadata\ALL_Metadata_SALES.xls'
(12.2) 07-15-14 16:11:08 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Input file Name is '
(12.2) 07-15-14 16:11:08 (14232:12656) PRINTFN: > 'JOB ERROR' : '>>> Error, Input file does not exist please confirm existence and restart job'
I want to update the folder path \\infra\finance\production\sales\Metadata\ALL_Metadata_SALES.xls to \\Home\BIData\finance\production\sales\Metadata\ALL_Metadata_SALES.xls
when i investigated WF_Metadata_files i saw there is a global called INPUT_DIR i assume I have to change the path there. I tried to find old directory in the batch job but i cant find it and even When i give value to global variable it is still pointing to old path.
Can anybody please help me.
Thanks
Tim

what would be the syntax to point it to particular folder.
I am using ' \\\Home\BIData\finance\production\sales\Metadata ' as this jobs reads more than one file from this folder.
Thanks
Tim

Change source path in batch Job in global variable in data services

Hi Experts,
my organization has created job in data services 3.2 to cleanse the data reading from excel flat files. the folder path was store in the global variable(I think) and now they have changed the directories hence is it throwing me below error.
Error, Input file does not exist please confirm existence and restart job, 16 ) >
failed, due to error <50316>: <>>> Error, Input file does not exist please confirm existence and restart job>. I want to update the folder path. I am sure it would be easy but I am very new to BODS.
(12.2) 07-15-14 16:10:08 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Sleeping for 35.000000 seconds... '
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Waking up...... '
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : 'Starting the timer loop number 6...'
(12.2) 07-15-14 16:10:43 (14232:12656) WORKFLOW: Work flow <WF_Metadata_Files> is started.
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> $G_FILENAME_IN : ALL_Metadata_SALES.xls...'
(12.2) 07-15-14 16:10:43 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> looking for input file name
\\infra\finance\production\sales\Metadata\ALL_Metadata_SALES.xls'
(12.2) 07-15-14 16:11:08 (14232:12656) PRINTFN: > 'JOB DEBUG' : '>>> Input file Name is '
(12.2) 07-15-14 16:11:08 (14232:12656) PRINTFN: > 'JOB ERROR' : '>>> Error, Input file does not exist please confirm existence and restart job'
I want to update the folder path\\infra\finance\production\sales\Metadata\ALL_Metadata_SALES.xls to \\Home\BIData\finance\production\sales\Metadata\ALL_Metadata_SALES.xls
when i investigated WF_Metadata_files i saw there is a global called INPUT_DIR i assume I have to change the path there. I tried to find old directory in the batch job but i cant find it and even When i give value to global variable it is still pointing to old path.
Can anybody please help me.
Thanks
Tim

Hi Tim,
If having specified the value in the global variable it is still pointing to the old path there can be a couple of scenarios applicable
1. There is a different global varaiable being used for the file path
2. The filepath is hardcoded in the file-format or Excel file definition despite the declaration of the global variable.
Are you getting this error when running a dataflow within this workflow or in a script? It will be better to run the workflow in debug mode and look through the stages to find out where exactly in the workflow it fails.
kind regards
Raghu

Reversing Accruals F.81 as a Periodic Job

Hi Guys,
We want to run F.81 , reversing the recurral entries , on a periodic basis. We want to set it as a background job and make it run periodically so that even if the users forget to run the reversals on the first of each month, this process will take care of that.
Is it possible to run F.81 on a periodic basis as a backgroun job?
Please suggest how we can do that. Also when the user enters the accrual document in FBS1, and once he gives the posting date, the Reversal date should be automatically the first of next month. Is it possible to do this so that if i enter the posting date as 22.10.2008, the reversal date should automatically come as 01.11.2008 in FBS1.
Please suggest.
Thanks
srikanth

Hello
Set the variant.
Please check with BASIS, they could schedule the job on recurring basis.
Reg
suresh

Background Job call from a program

Hi all,
We have a program which runs for max of 5 minutes (say).
It is scheduled to run every minute in SM36 so that it keeps continuing to run.
But sometimes even when the previous job is running the one starts up, thereby creating inconsistent results.
So we need to call the job from the running program itself.
How should we go abt this ? Is there any other way available to solve this ?
Thanks in Advance,
Regards,
Vivek K

Hi,
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
Specifying Jobs
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen, where you must select the criteria for the jobs you want to manage. These criteria include:
Job name (which can contain a wildcard (*) to select jobs with related names oru2014by using the wildcard aloneu2014any job). Required.
Name of the user who scheduled the job (the wildcard is allowed here as well). Required.
Job status
Planned or actual start time of the job.
Job start condition or event linked to the start condition
Job step
When and how often the job runs, or " periodicity"
You can also choose Extended Job Selection, where you can more precisely define the specific criteria that determine which jobs to select. If you have administrator Authorizations for Background Processing, you can display jobs in all clients. Without this authorization, only jobs in the client that you are logged on to will be displayed.
Once you have set the criteria for you job selection, choose Execute.
Managing and Monitoring Jobs
Once you have called the Job Overview screen (Transaction SM37 or CCMS ® Jobs ® Maintenance) and selected which jobs you want to manage as described above, you can choose from a wide range of management tasks.
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and choose Goto ® Job log.
To release a job so it can run, select a job from the Job Overview list and choose Goto ® Release.
Regards,
Jagadish

Batch job and background job

Hi
what is the difference between a batch job and backgroun job ??
thanks
kumar

hi kumar,
As far as I know
Batch job are the jobs created with sessions. You can process those sessions in SM35. These are not direct update methods.
Where as the background jobs are the jobs running in the background with out user interaction. Once you schedule the job for the background job it will run with out user interaction according to the given schedule.
You can run the batch jobs also in background.

Can do via SQL but not via PL/SQL

is it possible that a simple; 'create global temporary table..' SQL can run, yet same code being called from an 'execute immediate' within a PL/SQL block throw an; ORA-01031: insufficient privileges exception...(same user)
is it a role/privilege issue or do I need to de a better job debugging?

short version, each user will pass unique values to the proc that via dynamic sql will build these tables based on that iterative select criteria, to be used only during their current working session.
so it's not the 'same' table in structure each time
would not having 'TEMP grantable' be the issue?
trying to find a way to communicate this to the DBA

Deadlock in java

Hey Java Gurus, Help !
I have got this deadlock, while thread 58 is getting used by JRUN Process and thread 26 is my jsp page.
In my jsp page we are using ResourceBundle.
Looks like Thread 26 is waiting for JRunServletLoader which is already locked by thread 58. First can you guys tell from the trace becasue of which object, system got the Deadlock, I think it is JRunServletLoader, Am i correct ?
What could be solution ?? Shall we remove my ResourceBundle call from jsp to JavaBean becasue JavaBean is loaded by defaultLoader which not JRunServletLoader ?? Or any other ideas ??
Thanks in Advance.
t@58 waiting to lock object@0xa9c3ef58:"java/lang/Class"
which is locked by t@26
t@26 waiting to lock object@0xa8f8f918:"com/livesoftware/jrun/JRunServletLoader"
which is locked by t@58
JAVA STACK INFORMATION FOR THREADS LISTED ABOVE:
Java Stack for t@58 (EE = 0x640568) "jcp-7" :
==========
[1] java.util.ResourceBundle.getBundle(ResourceBundle.java:417)
[2] java.util.ResourceBundle.getBundle(ResourceBundle.java:353)
[3] java.text.DateFormatSymbols.getLocaleElements(DateFormatSymbols.java:412)
[4] java.text.DateFormatSymbols.cacheLookup(DateFormatSymbols.java:426)
[5] java.text.DateFormatSymbols.initializeData(DateFormatSymbols.java:454)
[6] java.text.DateFormatSymbols.<init>(DateFormatSymbols.java:107)
[7] java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:283)
[8] java.util.Date.toString(Date.java:978)
[9] com.livesoftware.jrun.JRun.eventLog(JRun.java:613)
[10] com.livesoftware.jrun.JRunServletContext.log(JRunServletContext.java:215)
[11] javax.servlet.GenericServlet.log(GenericServlet.java:319)
[12] javax.servlet.GenericServlet.init(GenericServlet.java:264)
[13] com.livesoftware.jsp.HttpJSPServlet.init(HttpJSPServlet.java:16)
[14] com.livesoftware.jrun.JRunServletLoader.loadServlet(JRunServletLoader.java:59)
[15] com.livesoftware.jrun.JRun.getServlet(JRun.java:506)
[16] com.livesoftware.jrun.JRun.getServlet(JRun.java:494)
[17] com.livesoftware.jrun.JRunServletContext.getServlet(JRunServletContext.java:182)
[18] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[19] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[20] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[21] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[22] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[23] jsp.sparc.PiaVersions._jspService(PiaVersions.java:172)
[24] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[25] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[26] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[27] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[28] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[29] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[30] jsp.sparc.PiaVersionMgmtScreen._jspService(PiaVersionMgmtScreen.java:36)
[31] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[32] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[33] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[34] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[35] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[36] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[37] jsp.sparc.States._jspService(States.java:30)
[38] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[39] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[40] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[41] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[42] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[43] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[44] jsp.sparc.Layout._jspService(Layout.java:26)
[45] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[46] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[47] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[48] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[49] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[50] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[51] jsp.sparc.Dispatch._jspService(Dispatch.java:63)
[52] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[53] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[54] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[55] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[56] com.livesoftware.jrun.JRunGeneric.handleConnection(JRunGeneric.java:106)
[57] com.livesoftware.jrun.JRunGeneric.handleProxyConnection(JRunGeneric.java:77)
[58] com.livesoftware.jrun.service.proxy.JRunProxyServiceHandler.handleRequest(JRunProxyServiceHandler.java:70)
[59] com.livesoftware.jrun.service.ThreadConfigHandler.run(ThreadConfigHandler.java:54)
Java Stack for t@26 (EE = 0x62e438) "jcp-3" :
==========
[1] com.livesoftware.jrun.JRunServletLoader.loadClass(JRunServletLoader.java:227)
[2] java.lang.ClassLoader.loadClass(ClassLoader.java:255)
[3] java.util.ResourceBundle.findBundle(ResourceBundle.java:534)
[4] java.util.ResourceBundle.getBundle(ResourceBundle.java:417)
[5] java.util.ResourceBundle.getBundle(ResourceBundle.java:339)
[6] jsp.sparc.RFPSummaryVersion._jspService(RFPSummaryVersion.java:37)
[7] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[8] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[9] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[10] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[11] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[12] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[13] jsp.sparc.summaryList._jspService(summaryList.java:37)
[14] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[15] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[16] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[17] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[18] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[19] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[20] jsp.sparc.SummaryScreenRFP._jspService(SummaryScreenRFP.java:32)
[21] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[22] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[23] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[24] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[25] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[26] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[27] jsp.sparc.States._jspService(States.java:30)
[28] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[29] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[30] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[31] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[32] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[33] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[34] jsp.sparc.Layout._jspService(Layout.java:26)
[35] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[36] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[37] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[38] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[39] com.livesoftware.jrun.JRunServletContext$JRunRequestDispatcher.include(JRunServletContext.java:376)
[40] com.livesoftware.jsp.JRunPageContext.include(JRunPageContext.java:270)
[41] jsp.sparc.Dispatch._jspService(Dispatch.java:63)
[42] com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
[43] com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:53)
[44] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
[45] com.livesoftware.jrun.JRun.runServlet(JRun.java:231)
[46] com.livesoftware.jrun.JRunGeneric.handleConnection(JRunGeneric.java:106)
[47] com.livesoftware.jrun.JRunGeneric.handleProxyConnection(JRunGeneric.java:77)
[48] com.livesoftware.jrun.service.proxy.JRunProxyServiceHandler.handleRequest(JRunProxyServiceHandler.java:70)
[49] com.livesoftware.jrun.service.ThreadConfigHandler.run(ThreadConfigHandler.java:54)
Found 1 deadlock

Good job debugging this and tracking down the deadlock!
eek. scary.
I guess you could try using a different getBundle call and specify a classloader... looks like the servlet classloader loads the page, which then needs access to the classloader in order to be instantiated (but the classloader is trying to instantiate the page, so isn't available). So maybe you can use a different classloader than the JRunServletLoader. Either that or as you suggest I think you need to consider taking out the resource bundle. =(

The transport request is running all the time, what is the problem

I have a transport request which can transport from DEV to QAS successfully ,but failed when the request transport to PRD, I found the request running for several hours. I do not know what the problem? how can I check this problem?
need your help thanks

Hi
The background job Rddimpdp is not scheduled in the system for client 000...And you want to investigate what happend to the job..
The background job details are kept in table TBTCO..So if you goto SE16 and try to choose the fields which are of your interest..as it(this table) has lot of fields. And in this we have fields like last run time,scheduled by,last job change time etc.So with the above information i hope you will be able to get the information you want.
And if everything is fine ..the backgrouns job alone can vanish someone manually might have done done something ..and that can be found out by above investigation on the table.
Hope this info helps...
Regards
Vani

Problem executing Unix script from Java...

Hi there, I'm having trouble executing a unix script from a java program. The script receives multiple parameters and it seems that one of them ( or more ) is not well interpreted. When I run the script directly from a shell, the script executes without any errors. But, when I run the exact same script with the exact same parameters, it does not work.
Here is the command to execute the script with all the parameters that is executed from the shell ( with success ) and also from the java program ( with errors ):
/z/opus/dcap/intfu001.csh 'NODEBUG^NOTKPROF^NOSTACK' opus dcap JACQUES JACQUES '2625781' 'ORA$PIPE$001D00D70001' JOB^DEBUG^SINISIMU^STATPROD^DECTIDANC^81^503^4080^86^87^151^97^98^99 BUT^N^N^SPRI^0^13^24^3^J^05^N^19^19^19 >> /tmp/switcher8.999.null.pgm.test
And here is my portion of code that executes the script:
Runtime wShell = Runtime.getRuntime();
Process wProc = wShell.exec(cmd_unix_final);
wProc.waitFor();
return wProc.exitValue();
Please give me your thoughts on this!
Thanks in advance!

Ok.
Let's proceed surgically, else we'll never solve or overcome anything.
In the last your reply you wrote:
the normal output is what I get when the script runs successfully, the script first prints a few things
and then does stuff that takes at least 2 or 3 secondsWhat do you mean?
-Finally have you got your script correctly executed?
The stuffs you spoke of are really performed?
If this is the case I can't see the prob.
Is your concern only about exitValue() for it doesn't let you distinguish programmatically
the success or failure of the script execution?
Of course you surely already have a routine in your java code to handle
exceptional situations of errors from the script.
And the "normal output" is just what you must parse to detect those errors.
Then who cares about exitValue() in this case?
Don't invoke it, relay on the stdout and stderr of the script.
-Or you get only a deceiving standard output
that let you think the script execution went alright, while instead it didn't.
In this case we have to investigate some other thing.
I can't still exclude that the problem isn't related with the buffer size of the stdout
allocated by the environment to the subprocess. You spoke of few things printed out.
Be explicit. What's the size of the output you get?
And is the "normal output" complete till the very last char
or is it truncated from somewhere on?
Also it's important that you hit a ps command after the java main process terminates
(or simply when waitFor() returns) and see if the script subprocess hung up.
As an alternative approach directly call your pro*C code from Java through JNI, instead of translating it.
1. Exec.java
public class Exec{
     static{
          System.loadLibrary("Exec");
     public static native void proCFunct();
     public static void main( String[] args){
          proCFunct();
}2. javac Exec.java
3. javah Exec
4.Exec.c
#include "Exec.h"
JNIEXPORT void JNICALL Java_Exec_proCFunct(JNIEnv * a, jclass b){
     //here call the function that executes the script
5. cc -G -I$JAVA_HOME/include -I$JAVA_HOME/include/solaris -I$YOUR_INCLUDES Exec.c -o libExec.so
6. setenv LD_LIBRARY_PATH .
7. java Exec

BACKGROUN JOB Debugging

Similar Messages

Maybe you are looking for