[JBoss JIRA] Created: (JBREM-640) Implement an asynchronous method for handling callbacks.
by Ron Sigal (JIRA)
Implement an asynchronous method for handling callbacks.
--------------------------------------------------------
Key: JBREM-640
URL: http://jira.jboss.com/jira/browse/JBREM-640
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
Tim Fox:
Currently, it's my understanding that push callbacks (using socket transport anyway) are synchronous, i.e. the server side thread that executes the callback blocks until the callback has been delivered to the client side and returned.
Is it currrently possible to execute asynch push callbacks? I.e. the thread that calls the callback returns immediately once it has registered the callback with remoting. And it is then delivered on a different thread?
Ideally executing using some kind of executor (e.g. PooledExecutor) with a bounded queue size which blocks when it is full would be ideal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBAS-4021) Distinct system properties for mcast_port in each config file
by Brian Stansberry (JIRA)
Distinct system properties for mcast_port in each config file
-------------------------------------------------------------
Key: JBAS-4021
URL: http://jira.jboss.com/jira/browse/JBAS-4021
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Optional
Fix For: JBossAS-4.2.0.CR1
Using a startup switch for the JGroups UDP mcast_port is not possible in a non-multiplexer environment, because every channel should use a separate port. But, we can add some properties to the standard config files to make it easier for users to set the ports via -D.
cluster-service.xml -- ${jboss.hapartition.mcast_port:45566}
jboss-web-cluster.sar/META-INF/jboss-service.xml -- ${jboss.webpartition.mcast_port:45577}
ejb3-entity-cache-service.xml -- ${jboss.ejb3entitypartition.mcast_port:43333}
ejb3-clustered-sfsbcache-service.xml -- ${jboss.ejb3sfsbpartition.mcast_port:45551}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months