service can't run in Scheduled,but run well in Developer

I have faced such problem: when i use Webmethods Developer to run a service it works well. But when i use scheduler to run it, it doesn’t work. the service will load large data into memory when running. is there huge difference between Webmethods Developer and scheduler to run a service?
Any one can help? Thanks very much!
the error:
2008-10-20 00:00:29 CST WMERROR 066506b09df711dd8d1980e70673dd0a080ac7709df711dd8d2580e70673dd0a0cf293d09df711dd9fd580e70673dd0a1224432029085 cnwuleai01.wuling.com:8888 [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service WulingTool.Common:InsertAllBatch.
[ART.114.505] Error while invoking adapter service com.wm.adapter.wmjdbc.services.Insert.
unable to create new native thread >>>BasicData:errorResourceBundleName=com.wm.pkg.art.i18n.resources.AdapterRuntimeResourceBundle,errorMessageArgs=[0]WulingTool.Common:InsertAllBatch,errorCode=117.4002,pipeline= >>>InsertAllBatchInput= >>>BatchNumber=1046707<<< , connectionAlias=WulingTool:WulingAccess, ProcessSequence=20081020000020, GetAllBatchOutput= >>>results= >>>Batch=1046707<<< <<< , $iteration=1586, InsertAllBatchOutput=null<<< ,exceptionDetail=>>>BasicData:errorResourceBundleName=com.wm.adk.resources.ADKErrorResources,errorMessageArgs=[0]com.wm.adapter.wmjdbc.services.Insert,errorCode=114.505,pipeline=com.wm.adk.cci.record.WmRecord@1acb583,stack=java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at com.microsoft.jdbc.base.BaseQueryTimeoutEnforcer.(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.setQueryTimeout(Unknown Source)
at com.microsoft.jdbcx.base.BaseStatementWrapper.setQueryTimeout(Unknown Source)
at com.wm.adapter.wmjdbc.connection.ConnectionInfo.setQueryTimeout(Unknown Source)
at com.wm.adapter.wmjdbc.services.UpdateOperation.execute(UpdateOperation.java:112)
at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:76)
at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:338)
at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:54)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:612)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:235)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:198)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:41WulingTool.Comm

try this,
on web admin, go to Settings > Resources >Scheduler Thread Pool
change the number to a greater one. you should be able to run it as scheduled job.
Tong