SetUser failed - Loops are not permitted
Hi,
We're using Build Forge 7.1.2.2-1-0111 and some of our scheduled tasks are not run for some reason. I took a look at today's catalina's log and found the following.
This looks like a similar problem I've already faced (search the forums).
Anything in the projects/schedule configuration could be causing this, or it is a bug?
<pre>
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.api.AuthContext setUser
WARNING: SetUser failed - Loops are not permitted
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.manager.CronManager scheduleBuilds
WARNING: scheduleBuilds: Couldn't schedule job for schedule 'Perforce_Sync'
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
at com.buildforge.services.server.manager.BuildManager.canBeFired(BuildManager.java:358)
at com.buildforge.services.server.manager.BuildManager.createCronBuild(BuildManager.java:1800)
at com.buildforge.services.server.manager.CronManager.scheduleBuilds(CronManager.java:723)
at com.buildforge.services.server.manager.CronManager$CronScheduler.run(CronManager.java:907)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
</pre>
We're using Build Forge 7.1.2.2-1-0111 and some of our scheduled tasks are not run for some reason. I took a look at today's catalina's log and found the following.
This looks like a similar problem I've already faced (search the forums).
Anything in the projects/schedule configuration could be causing this, or it is a bug?
<pre>
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.api.AuthContext setUser
WARNING: SetUser failed - Loops are not permitted
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.manager.CronManager scheduleBuilds
WARNING: scheduleBuilds: Couldn't schedule job for schedule 'Perforce_Sync'
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
at com.buildforge.services.server.manager.BuildManager.canBeFired(BuildManager.java:358)
at com.buildforge.services.server.manager.BuildManager.createCronBuild(BuildManager.java:1800)
at com.buildforge.services.server.manager.CronManager.scheduleBuilds(CronManager.java:723)
at com.buildforge.services.server.manager.CronManager$CronScheduler.run(CronManager.java:907)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
</pre>
4 answers
Hi,
We're using Build Forge 7.1.2.2-1-0111 and some of our scheduled tasks are not run for some reason. I took a look at today's catalina's log and found the following.
This looks like a similar problem I've already faced (search the forums).
Anything in the projects/schedule configuration could be causing this, or it is a bug?
<pre>
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.api.AuthContext setUser
WARNING: SetUser failed - Loops are not permitted
Jul 29, 2011 12:00:43 PM com.buildforge.services.server.manager.CronManager scheduleBuilds
WARNING: scheduleBuilds: Couldn't schedule job for schedule 'Perforce_Sync'
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
at com.buildforge.services.server.manager.BuildManager.canBeFired(BuildManager.java:358)
at com.buildforge.services.server.manager.BuildManager.createCronBuild(BuildManager.java:1800)
at com.buildforge.services.server.manager.CronManager.scheduleBuilds(CronManager.java:723)
at com.buildforge.services.server.manager.CronManager$CronScheduler.run(CronManager.java:907)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
</pre>
Hi,
Who is the owner of the schedule (really only interested if it's root or some other defined user)? If you change the owner of the schedule, does it work?
Brent Ulbricht
RTC Build Lead
I am the owner of the schedule. I'm actually sharing the scheduling with one of my coworker and we're not using the root user.
I've looked at the documentation, which lists the owner field when creating/modifying a schedule, but under my version/permissions, I don't see it, so I can't try to change the owner...
I've looked at the documentation, which lists the owner field when creating/modifying a schedule, but under my version/permissions, I don't see it, so I can't try to change the owner...
Manually editing the database so that all scheduled tasks are under the same user "temporarily" fixes the problem. Temporarily in the sense that this shouldn't have to be done.
Hi,
It's good you've got a workaround. You might want to contact product support about this one. I'm not as familiar with this area and could only tell that it was related to the user.
Brent Ulbricht
RTC Build Lead