RE: Problem starting job, can anyone point me in the right direction?

2009-05-05T14:34:17Z

Christianto,

Thanks for that last tip. That got rid of my error.

steve

RE: Problem starting job, can anyone point me in the right direction?

2009-04-29T01:48:08Z

Try to disable your scheduler in portal-ext.properties

scheduler.enabled=false

And then restart your application server.

RE: Problem starting job, can anyone point me in the right direction?

2009-04-28T13:11:55Z

Unfortunately that didn't have any impact good or bad, still getting the above error.

RE: Problem starting job, can anyone point me in the right direction?

2009-04-28T04:21:27Z

Try to set these following properties to blank values in your portal-ext.properties :

plugin.repositories.trusted=
plugin.repositories.untrusted=

[Resolved]Problem starting job, can anyone point me in the right direction

2009-04-27T17:42:31Z

I'm working on my first portlet and I've really run into something I can't seem to figure out. I've been googling and reading and searching through the forums, but so far what little I've found on this hasn't really helped. A bit of the stack trace I'm seeing is down below. I'm guessing I have something configured wrong, but I can't for the life of me figure out what. I've undone any changes recently made to the configuration files (at least I think I've undone everything) and the problem persists. When I start the portal things seem to go normally most of the way through, but then it gets to the portlet I'm working on and it starts to make it available. When it gets there this error starts throwing and just keeps going and going. What I see in the browser is the liferay portal start on a tab, then this error is thrown, and the liferay portal tries to start in another tab, with none of the instances of the portal ever really starting. If I didn't kill the process it would just keep opening instances in new tabs until I guess it hit a browser limit on the number of tabs that could be open if there is such a thing. Here is a chunk of the stack trace, hopefully somebody out there can tell me what I've done wrong or at least give me some idea of what to look for. I'm stumped.

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:689)
at java.lang.Thread.run(Thread.java:595)
13:21:27,729 ERROR [JobScheduler:99] org.quartz.ObjectAlreadyExistsException: Un
able to store Job with name: 'com.liferay.portlet.admin.job.CheckRemoteRepositor
iesJob@10912128' and group: 'DEFAULT', because one already exists with this iden
tification.
org.quartz.ObjectAlreadyExistsException: Unable to store Job with name: 'com.lif
eray.portlet.admin.job.CheckRemoteRepositoriesJob@10912128' and group: 'DEFAULT'
, because one already exists with this identification.
at org.quartz.simpl.RAMJobStore.storeJob(RAMJobStore.java:222)
at org.quartz.simpl.RAMJobStore.storeJobAndTrigger(RAMJobStore.java:195)

at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:703)

at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:255)
at com.liferay.portal.job.JobSchedulerImpl.schedule(JobSchedulerImpl.jav
a:96)
at com.liferay.portal.kernel.job.JobSchedulerUtil.schedule(JobSchedulerU
til.java:38)
at com.liferay.portlet.admin.job.AdminScheduler.schedule(AdminScheduler.
java:39)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:331)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1139)