Bug 4936 – WorkManager config broken

Bug 4936 - WorkManager config broken

Summary:

WorkManager config broken

Status:	RESOLVED FIXED

Product:	Java WS Core
Component:	globus_wsrf_core
Version:	unspecified
Platform:	PC Linux

Importance:	P3 blocker
Target Milestone:	4.2.0
Assigned To:	Rachana Ananthakrishnan

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-01-04 10:03 by Peter Lane
Modified:	2007-01-04 11:19 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Peter Lane 2007-01-04 10:03:54

The following error is generated when using RFT in HEAD:

javax.naming.NamingException: No set method found for property: maxPoolSize
    at
org.apache.naming.factory.BeanFactory.getObjectInstance(BeanFactory.java:192)
    at
org.globus.wsrf.jndi.BasicBeanFactory.getObjectInstance(BasicBeanFactory.java:40)
    at org.globus.wsrf.jndi.BeanFactory.getInstance(BeanFactory.java:117)
    at org.globus.wsrf.jndi.BeanFactory.getObjectInstance(BeanFactory.java:84)
    at
org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:135)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:827)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:155)
    at
org.apache.naming.SynchronizedContext.lookup(SynchronizedContext.java:69)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:815)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:155)
    at
org.apache.naming.SynchronizedContext.lookup(SynchronizedContext.java:69)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:815)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:155)
    at
org.apache.naming.SynchronizedContext.lookup(SynchronizedContext.java:69)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:815)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
    at
org.apache.naming.SynchronizedContext.lookup(SynchronizedContext.java:81)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.apache.naming.SelectorContext.lookup(SelectorContext.java:145)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at
org.globus.transfer.reliable.service.ReliableFileTransferImpl.startTransfers(ReliableFileTransferImpl.java:316)
    at
org.globus.transfer.reliable.service.ReliableFileTransferImpl.start(ReliableFileTransferImpl.java:121)

This suggests that the WorkManager config code is broken. Looking in the
jndi-config.xml file for globus_wsrf_core, there is indeed a maxPoolSize
parameter for the WorkManager config. Either this needs to be removed or the
bean class that stores the config parameters needs to be fixed.

------- Comment #1 From Rachana Ananthakrishnan 2007-01-04 11:19:40 -------

Fix committed to trunk.