Service component entity properties

Table 4-1 lists the service component entity properties.

Table 4-1: Service component entity properties

Management Console property

Configuration file property

Description

Component

component

Identifies the component to run as the service. Specify the identifier for the component’s generated DJC adapter for the EJB remote or local interface. For remote interfaces, this has the form:

ejb.components.module.componentRemote

Where module is the name of the EJB module or CORBA package, and component is the name of the component. For local interfaces, it has the form:

ejb.components.module.componentLocal

For example, for component MyService in module MyPackage, specify the remote interface adaptor as ejb.components.MyPackage.MyComponentRemote.

Depends On

dependsOn

Specifies other service components that must be running before this component can run.

Start Order

startOrder

Allows you to configure the starting order for multiple services. Lower numbered services start before higher number services.

Start Before Binding

startBeforeBinding

Specifies whether EAServer must perform JNDI name bindings before calling the start method. Disable this setting if your start method makes intercomponent calls or accesses resources using JNDI.

Run Thread Count

runThreadCount

Specifies how many instances to run. Each instance runs in a separate thread—see “When multiple threads are requested”

Stop Wait Time

stopWaitTime

When stopping the service, how long to wait for the stop method to return before giving up. Specify the time in milliseconds.

Allow Start Failure

allowStartFailure

Whether the server can run and accept client connections if this service fails to start.

When multiple threads are requested

The host server calls the component’s run method from the specified number of threads. If the Sharing option is enabled, all threads call run on the same component instance as start was called in. Otherwise, each thread will create a new instance of the component and call run on that instance. Each thread terminates when run returns. This feature is useful when your service component performs a background task that lends itself to parallel processing. For example, if the run implementation extracts work requests from a queue and performs the requested operation, you can configure the server so multiple threads read requests from the queue and process them simultaneously. The component must be coded to ensure that access to the queue is thread-safe, for example, in Java, you might create synchronized methods to queue and dequeue.

The component must be stateless in order to run in multiple threads.

NoteThe start method and stop methods are only called on one instance of a service component. If Sharing is not enabled for the component, start must store any data required by the run method or other methods in a way that allows access from other class instances. For example, use static class fields or a persistent data store.