[#RIO-279] StaticCybernode should provide better feedback when a 'fork' directive is used in a service declaration

Rio

StaticCybernode should provide better feedback when a 'fork' directive is used in a service declaration

Created: 03/Aug/10 07:18 PM Updated: 04/Aug/10 01:41 AM

Component/s:

Deployment

Affects Version/s:

4.1

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. screenshot.jpg
(721 kB)

Environment:

Mac OS X

Description

« Hide

If a fork:'yes' is specified in an opstring that is handed to a StaticCybernode, the deployment fails with this stack trace:

SEVERE: Failed to load the ServiceBean [Gateway] classpath []
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:417)
at java.lang.Integer.parseInt(Integer.java:499)
at org.rioproject.cybernode.exec.ServiceBeanExecManager.exec(ServiceBeanExecManager.java:140)
at org.rioproject.cybernode.JSBDelegate$1.run(JSBDelegate.java:515)

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Ronald A. Bowers added a comment - 03/Aug/10 07:21 PM

Screenshot showing the test class and the logging from the run.

[ Permalink | « Hide ]

Dennis Reedy added a comment - 03/Aug/10 07:26 PM

Forking a service using the StaticCybernode is not supported. In the future the SC will reject requests to instantiate a forked service

[ Permalink | « Hide ]

Dennis Reedy added a comment - 03/Aug/10 07:52 PM

The StaticCybernode does not support the instantiation of a service declared to be forked. A JSBInstantiatonException is thrown when processing this type of service

[ Permalink | « Hide ]

Ronald A. Bowers added a comment - 04/Aug/10 01:41 AM

Yeah, I knew that SC doesn't support fork and I remember it when I write a SC-specific opstring, but in this case I cut and pasted an existing opstring and forgot to remove the fork directive.