Scheduled service is hot or miss
Locked
Scheduled service is hot or miss
 
|
Hello,
I am using the 4.0 branch of OFBiz. I created 2 services: printPackSlip and massPrintPackSlips. massPrintPackSlips is a copy of massPrintOrders, but as the name suggests, it prints packslips instead by accepting a list of shipment id's. I created printPackSlip because it actually selects the appropriate printer based on the caller's address as well as the packslip. printPackSlip is called async from updateShipment when the shipment is marked as packed (The user clicks complete from the pack screen and the packslip automatically prints). printPackSlip calls massPrintPackSlips sync, which in turn calls sendPrintFromScreen async. It may sound (over) complicated, but as I said, I just took existing code, modified it, and added a middleman to supply the parameters. In the end, the sendPrintFromScreen service shows up in the job list and it marked as complete, but does not always work. It might work about 5 times in a row, and then just stop. Does anyone know what the problem could be or how I might go about finding out for myself? Thanks. |
RE: Scheduled service is hot or miss
|
|
I forgot to mention that when I put a breakpoint in sendPrintFromScreen,
it works, so I think that's out of the question. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 11:58 AM To: [hidden email] Subject: Scheduled service is hot or miss Hello, I am using the 4.0 branch of OFBiz. I created 2 services: printPackSlip and massPrintPackSlips. massPrintPackSlips is a copy of massPrintOrders, but as the name suggests, it prints packslips instead by accepting a list of shipment id's. I created printPackSlip because it actually selects the appropriate printer based on the caller's address as well as the packslip. printPackSlip is called async from updateShipment when the shipment is marked as packed (The user clicks complete from the pack screen and the packslip automatically prints). printPackSlip calls massPrintPackSlips sync, which in turn calls sendPrintFromScreen async. It may sound (over) complicated, but as I said, I just took existing code, modified it, and added a middleman to supply the parameters. In the end, the sendPrintFromScreen service shows up in the job list and it marked as complete, but does not always work. It might work about 5 times in a row, and then just stop. Does anyone know what the problem could be or how I might go about finding out for myself? Thanks. |
RE: Scheduled service is hot or miss
|
|
There was just 1 instance in which I did set a breakpoint and the job
did not fire. Something else I'd like to add is that I see the job in the job list and OFBiz says that it completed, but the logs indicate otherwise. Are there any known issues where the job scheduler does not actually fire a task even though it thinks it did? -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 12:45 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss I forgot to mention that when I put a breakpoint in sendPrintFromScreen, it works, so I think that's out of the question. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 11:58 AM To: [hidden email] Subject: Scheduled service is hot or miss Hello, I am using the 4.0 branch of OFBiz. I created 2 services: printPackSlip and massPrintPackSlips. massPrintPackSlips is a copy of massPrintOrders, but as the name suggests, it prints packslips instead by accepting a list of shipment id's. I created printPackSlip because it actually selects the appropriate printer based on the caller's address as well as the packslip. printPackSlip is called async from updateShipment when the shipment is marked as packed (The user clicks complete from the pack screen and the packslip automatically prints). printPackSlip calls massPrintPackSlips sync, which in turn calls sendPrintFromScreen async. It may sound (over) complicated, but as I said, I just took existing code, modified it, and added a middleman to supply the parameters. In the end, the sendPrintFromScreen service shows up in the job list and it marked as complete, but does not always work. It might work about 5 times in a row, and then just stop. Does anyone know what the problem could be or how I might go about finding out for myself? Thanks. |
RE: Scheduled service is hot or miss
|
|
I think I figured it out. printPackSlip was running in a transaction as
was massPrintPackSlips. I set printPackSlip to not use transactions, and so far, it's worked everytime. If anyone knows what *could* have been the issue, I'm all ears. If not, then I guess that's the end of this thread. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Monday, June 22, 2009 12:28 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss There was just 1 instance in which I did set a breakpoint and the job did not fire. Something else I'd like to add is that I see the job in the job list and OFBiz says that it completed, but the logs indicate otherwise. Are there any known issues where the job scheduler does not actually fire a task even though it thinks it did? -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 12:45 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss I forgot to mention that when I put a breakpoint in sendPrintFromScreen, it works, so I think that's out of the question. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 11:58 AM To: [hidden email] Subject: Scheduled service is hot or miss Hello, I am using the 4.0 branch of OFBiz. I created 2 services: printPackSlip and massPrintPackSlips. massPrintPackSlips is a copy of massPrintOrders, but as the name suggests, it prints packslips instead by accepting a list of shipment id's. I created printPackSlip because it actually selects the appropriate printer based on the caller's address as well as the packslip. printPackSlip is called async from updateShipment when the shipment is marked as packed (The user clicks complete from the pack screen and the packslip automatically prints). printPackSlip calls massPrintPackSlips sync, which in turn calls sendPrintFromScreen async. It may sound (over) complicated, but as I said, I just took existing code, modified it, and added a middleman to supply the parameters. In the end, the sendPrintFromScreen service shows up in the job list and it marked as complete, but does not always work. It might work about 5 times in a row, and then just stop. Does anyone know what the problem could be or how I might go about finding out for myself? Thanks. |
RE: Scheduled service is hot or miss
|
|
Ok, last response on this...I figured out what the issue was when I was
debugging the job poller. Even though I set a breakpoint, the job still ran, then I realized something...I still had an instance of the app running on my linux box which was hooked to the same database. So, perhaps this can help someone else should they encounter the same type of unusual behavior. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Tuesday, June 23, 2009 1:30 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss I think I figured it out. printPackSlip was running in a transaction as was massPrintPackSlips. I set printPackSlip to not use transactions, and so far, it's worked everytime. If anyone knows what *could* have been the issue, I'm all ears. If not, then I guess that's the end of this thread. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Monday, June 22, 2009 12:28 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss There was just 1 instance in which I did set a breakpoint and the job did not fire. Something else I'd like to add is that I see the job in the job list and OFBiz says that it completed, but the logs indicate otherwise. Are there any known issues where the job scheduler does not actually fire a task even though it thinks it did? -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 12:45 PM To: [hidden email] Subject: RE: Scheduled service is hot or miss I forgot to mention that when I put a breakpoint in sendPrintFromScreen, it works, so I think that's out of the question. -----Original Message----- From: Sanders, Brian [mailto:[hidden email]] Sent: Friday, June 19, 2009 11:58 AM To: [hidden email] Subject: Scheduled service is hot or miss Hello, I am using the 4.0 branch of OFBiz. I created 2 services: printPackSlip and massPrintPackSlips. massPrintPackSlips is a copy of massPrintOrders, but as the name suggests, it prints packslips instead by accepting a list of shipment id's. I created printPackSlip because it actually selects the appropriate printer based on the caller's address as well as the packslip. printPackSlip is called async from updateShipment when the shipment is marked as packed (The user clicks complete from the pack screen and the packslip automatically prints). printPackSlip calls massPrintPackSlips sync, which in turn calls sendPrintFromScreen async. It may sound (over) complicated, but as I said, I just took existing code, modified it, and added a middleman to supply the parameters. In the end, the sendPrintFromScreen service shows up in the job list and it marked as complete, but does not always work. It might work about 5 times in a row, and then just stop. Does anyone know what the problem could be or how I might go about finding out for myself? Thanks. |
Re: Scheduled service is hot or miss
|
|
In other words a different app server picked up the scheduled service and ran it? That sounds like the normal behavior to me... -David On Jun 24, 2009, at 9:07 AM, Sanders, Brian wrote: > Ok, last response on this...I figured out what the issue was when I > was > debugging the job poller. Even though I set a breakpoint, the job > still > ran, then I realized something...I still had an instance of the app > running on my linux box which was hooked to the same database. So, > perhaps this can help someone else should they encounter the same type > of unusual behavior. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Tuesday, June 23, 2009 1:30 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > I think I figured it out. printPackSlip was running in a transaction > as > was massPrintPackSlips. I set printPackSlip to not use transactions, > and > so far, it's worked everytime. If anyone knows what *could* have been > the issue, I'm all ears. If not, then I guess that's the end of this > thread. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Monday, June 22, 2009 12:28 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > There was just 1 instance in which I did set a breakpoint and the job > did not fire. Something else I'd like to add is that I see the job in > the job list and OFBiz says that it completed, but the logs indicate > otherwise. Are there any known issues where the job scheduler does not > actually fire a task even though it thinks it did? > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Friday, June 19, 2009 12:45 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > I forgot to mention that when I put a breakpoint in > sendPrintFromScreen, > it works, so I think that's out of the question. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Friday, June 19, 2009 11:58 AM > To: [hidden email] > Subject: Scheduled service is hot or miss > > Hello, > > I am using the 4.0 branch of OFBiz. I created 2 services: > printPackSlip > and massPrintPackSlips. massPrintPackSlips is a copy of > massPrintOrders, > but as the name suggests, it prints packslips instead by accepting a > list of shipment id's. I created printPackSlip because it actually > selects the appropriate printer based on the caller's address as > well as > the packslip. printPackSlip is called async from updateShipment when > the > shipment is marked as packed (The user clicks complete from the pack > screen and the packslip automatically prints). printPackSlip calls > massPrintPackSlips sync, which in turn calls sendPrintFromScreen > async. > It may sound (over) complicated, but as I said, I just took existing > code, modified it, and added a middleman to supply the parameters. In > the end, the sendPrintFromScreen service shows up in the job list > and it > marked as complete, but does not always work. It might work about 5 > times in a row, and then just stop. Does anyone know what the problem > could be or how I might go about finding out for myself? Thanks. > |
RE: Scheduled service is hot or miss
|
|
Maybe "unexpected" would have been a better word to use in this case. :)
-----Original Message----- From: David E Jones [mailto:[hidden email]] Sent: Wednesday, June 24, 2009 11:53 AM To: [hidden email] Subject: Re: Scheduled service is hot or miss In other words a different app server picked up the scheduled service and ran it? That sounds like the normal behavior to me... -David On Jun 24, 2009, at 9:07 AM, Sanders, Brian wrote: > Ok, last response on this...I figured out what the issue was when I > was > debugging the job poller. Even though I set a breakpoint, the job > still > ran, then I realized something...I still had an instance of the app > running on my linux box which was hooked to the same database. So, > perhaps this can help someone else should they encounter the same type > of unusual behavior. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Tuesday, June 23, 2009 1:30 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > I think I figured it out. printPackSlip was running in a transaction > as > was massPrintPackSlips. I set printPackSlip to not use transactions, > and > so far, it's worked everytime. If anyone knows what *could* have been > the issue, I'm all ears. If not, then I guess that's the end of this > thread. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Monday, June 22, 2009 12:28 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > There was just 1 instance in which I did set a breakpoint and the job > did not fire. Something else I'd like to add is that I see the job in > the job list and OFBiz says that it completed, but the logs indicate > otherwise. Are there any known issues where the job scheduler does not > actually fire a task even though it thinks it did? > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Friday, June 19, 2009 12:45 PM > To: [hidden email] > Subject: RE: Scheduled service is hot or miss > > I forgot to mention that when I put a breakpoint in > sendPrintFromScreen, > it works, so I think that's out of the question. > > -----Original Message----- > From: Sanders, Brian [mailto:[hidden email]] > Sent: Friday, June 19, 2009 11:58 AM > To: [hidden email] > Subject: Scheduled service is hot or miss > > Hello, > > I am using the 4.0 branch of OFBiz. I created 2 services: > printPackSlip > and massPrintPackSlips. massPrintPackSlips is a copy of > massPrintOrders, > but as the name suggests, it prints packslips instead by accepting a > list of shipment id's. I created printPackSlip because it actually > selects the appropriate printer based on the caller's address as > well as > the packslip. printPackSlip is called async from updateShipment when > the > shipment is marked as packed (The user clicks complete from the pack > screen and the packslip automatically prints). printPackSlip calls > massPrintPackSlips sync, which in turn calls sendPrintFromScreen > async. > It may sound (over) complicated, but as I said, I just took existing > code, modified it, and added a middleman to supply the parameters. In > the end, the sendPrintFromScreen service shows up in the job list > and it > marked as complete, but does not always work. It might work about 5 > times in a row, and then just stop. Does anyone know what the problem > could be or how I might go about finding out for myself? Thanks. > |
Re: Scheduled service is hot or miss
|
|
Yeah, I can see how that would apply... ;) "Unexpected" things often come into play when weird things are happening. -David On Jun 24, 2009, at 9:56 AM, Sanders, Brian wrote: > Maybe "unexpected" would have been a better word to use in this > case. :) > > -----Original Message----- > From: David E Jones [mailto:[hidden email]] > Sent: Wednesday, June 24, 2009 11:53 AM > To: [hidden email] > Subject: Re: Scheduled service is hot or miss > > > In other words a different app server picked up the scheduled service > and ran it? > > That sounds like the normal behavior to me... > > -David > > > On Jun 24, 2009, at 9:07 AM, Sanders, Brian wrote: > >> Ok, last response on this...I figured out what the issue was when I >> was >> debugging the job poller. Even though I set a breakpoint, the job >> still >> ran, then I realized something...I still had an instance of the app >> running on my linux box which was hooked to the same database. So, >> perhaps this can help someone else should they encounter the same >> type >> of unusual behavior. >> >> -----Original Message----- >> From: Sanders, Brian [mailto:[hidden email]] >> Sent: Tuesday, June 23, 2009 1:30 PM >> To: [hidden email] >> Subject: RE: Scheduled service is hot or miss >> >> I think I figured it out. printPackSlip was running in a transaction >> as >> was massPrintPackSlips. I set printPackSlip to not use transactions, >> and >> so far, it's worked everytime. If anyone knows what *could* have been >> the issue, I'm all ears. If not, then I guess that's the end of this >> thread. >> >> -----Original Message----- >> From: Sanders, Brian [mailto:[hidden email]] >> Sent: Monday, June 22, 2009 12:28 PM >> To: [hidden email] >> Subject: RE: Scheduled service is hot or miss >> >> There was just 1 instance in which I did set a breakpoint and the job >> did not fire. Something else I'd like to add is that I see the job in >> the job list and OFBiz says that it completed, but the logs indicate >> otherwise. Are there any known issues where the job scheduler does >> not >> actually fire a task even though it thinks it did? >> >> -----Original Message----- >> From: Sanders, Brian [mailto:[hidden email]] >> Sent: Friday, June 19, 2009 12:45 PM >> To: [hidden email] >> Subject: RE: Scheduled service is hot or miss >> >> I forgot to mention that when I put a breakpoint in >> sendPrintFromScreen, >> it works, so I think that's out of the question. >> >> -----Original Message----- >> From: Sanders, Brian [mailto:[hidden email]] >> Sent: Friday, June 19, 2009 11:58 AM >> To: [hidden email] >> Subject: Scheduled service is hot or miss >> >> Hello, >> >> I am using the 4.0 branch of OFBiz. I created 2 services: >> printPackSlip >> and massPrintPackSlips. massPrintPackSlips is a copy of >> massPrintOrders, >> but as the name suggests, it prints packslips instead by accepting a >> list of shipment id's. I created printPackSlip because it actually >> selects the appropriate printer based on the caller's address as >> well as >> the packslip. printPackSlip is called async from updateShipment when >> the >> shipment is marked as packed (The user clicks complete from the pack >> screen and the packslip automatically prints). printPackSlip calls >> massPrintPackSlips sync, which in turn calls sendPrintFromScreen >> async. >> It may sound (over) complicated, but as I said, I just took existing >> code, modified it, and added a middleman to supply the parameters. In >> the end, the sendPrintFromScreen service shows up in the job list >> and it >> marked as complete, but does not always work. It might work about 5 >> times in a row, and then just stop. Does anyone know what the problem >> could be or how I might go about finding out for myself? Thanks. >> > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |