It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×12,011
×101
×77

question asked: Apr 17 '13, 4:03 a.m.
question was seen: 5,912 times
last updated: Apr 18 '13, 10:09 a.m.

Related questions

Build problem with Weblogic components

0
Canberk Akduygu (992●3●73●71) | asked Apr 17 '13, 4:03 a.m.
Hello,

We have a build problem in our environment. We have two projects(let's say A and B projects). When we send the build request, build system loads those two projects into the server and first build's Project B then project A. A is dependent to B.

If we run jbe.exe by using a bat file,build is terminated successfully. The problem is when we set up a Window's Task Scheduler and created a Basic Task to run the same bat file. Build fails.

When I looked at the logs I see a missing parameter:
Successfull Build:
[wlwbuild] Executing 'D:\tools\bea814\jdk142_05\jre\bin\java.exe' with arguments:
 [wlwbuild] '-XX:-UseThreadPriorities'
 [wlwbuild] '-client'
 [wlwbuild] '-Xms64m'
 [wlwbuild] '-Xss256k'
 [wlwbuild] '-Xmx128m'
 [wlwbuild] '-Djava.system.class.loader=workshop.core.AppClassLoader'
 [wlwbuild] '-classpath'
 [wlwbuild] 'D:\tools\bea814\weblogic81\workshop\wlw-ide.jar'
 [wlwbuild] 'workshop.core.Compile'

Failed Build:
[wlwbuild] Executing 'D:\tools\bea814\jdk142_05\jre\bin\java.exe' with arguments:
 [wlwbuild] '-XX:-UseThreadPriorities'
 [wlwbuild] '-client'
 [wlwbuild] '-Xms64m'
 [wlwbuild] '-Xss256k'
 [wlwbuild] '-Xmx128m'
 [wlwbuild] '-Djava.system.class.loader=workshop.core.AppClassLoader'
 [wlwbuild] 'workshop.core.Compile'

Those two lines are missing in the Failed build's log and that is causing the problem.
 [wlwbuild] '-classpath'
 [wlwbuild] 'D:\tools\bea814\weblogic81\workshop\wlw-ide.jar'

All the classpath variables are defined in the ant.xml. As I said if I use comman line or a bat file, build is successfull.

Does anyone have any idea  what might cause this build problem when we use Windows TaskScheduler?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Scott Cowan (966●3●10) | answered Apr 17 '13, 9:38 a.m.
JAZZ DEVELOPER
Hi Canberk,

I tested running jbe from a batch file using the windows task scheduler and it started with no problems on Windows 7.  This is what I did.

1. Created build engine with ID, test.
2. Tested jbe on command line,

C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse>jbe -repository https://vottscowan.ottawa.ibm.com:9443/ccm -userId scowan -pass scowan -engineId test
2013-04-17 09:17:31 [Jazz build engine] Running build loop...
2013-04-17 09:17:31 [Jazz build engine] Waiting for request...

3. Created build.bat to run jbe with the above parameters

build.bat
---
jbe -repository https://vottscowan.ottawa.ibm.com:9443/ccm -userId scowan -pass scowan -engineId test
---

4. Tested build.bat

C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse>build

C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse>jbe -repository https://
vottscowan.ottawa.ibm.com:9443/ccm -userId scowan -pass scowan -engineId test
2013-04-17 09:19:04 [Jazz build engine] Running build loop...
2013-04-17 09:19:04 [Jazz build engine] Waiting for request...

5. In Task Scheduler I created a basic task called build to run daily to start the program,

"C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse\build.bat"

in,

C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse

6. After clicking the finish button, rather than waiting for the scheduled daily build, I selected the task and clicked the Run button to run it immediately.  It started up a console displaying,

C:\Program Files (x86)\IBM\TeamConcertBuild\buildsystem\buildengine\eclipse>jbe -repository https://vottscowan.ottawa.ibm.com:9443/ccm -userId scowan -pass scowan -engineId test
2013-04-17 09:23:26 [Jazz build engine] Running build loop...
2013-04-17 09:23:26 [Jazz build engine] Waiting for request...

I wasn't able to reproduce the problem you mentioned above.  I also got it to run executing java with the command line,

java -jar plugins\org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -repository https://vottscowan.ottawa.ibm.com:9443/ccm -userId scowan -pass scowan -engineId test

The above is suggested if you choose to run a build engine as a service as described here, https://jazz.net/wiki/bin/view/Main/JbeAsAWindowsService

Hope some of this helps,
Scott

0
permanent link
Canberk Akduygu (992●3●73●71) | answered Apr 17 '13, 9:52 a.m.
Hi Scott,

Actually we don't have any problem with our other builds using Windows task scheduler. Projects which has weblogic dependency has this kind of problem.
I started to think this is something about weblogic.

We had many problems while using Java Service Launcher. We even think about using UC4 for handling those build engines better.
Comments
Scott Cowan commented Apr 18 '13, 9:16 a.m.
JAZZ DEVELOPER

Hi Canberk,

I'm a bit confused.  Is your Windows task running a batch file that starts jbe.exe, or executes a build.  I don't understand where 'workshop.core.Compile' fits in.  Perhaps you can boil this down to something I can test?

Scott

Canberk Akduygu commented Apr 18 '13, 10:08 a.m. | edited Apr 18 '13, 10:09 a.m.

Hi Scott,

Windows Task runs a batch file that starts jbe.exe.

Our java project has a build.xml where I set some classpath variables about weblogic and other 3rd party components. This is where weblogic fits in. While build starts to build my project by using build.xml and Ant command, it fails.

But if I dont use Windows task Scheduler, and I run batch file from command line, there's no problem. Build succeeds.

It's a difficult case to reproduce :(

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.