[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging
by ovidiu.feodorov@jboss.com
I have merged Ron's HTTP branch into the trunk (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingMergingActivity). All functional tests were passing on the branch, prior to merging. The smoke tests (including the http test) were also passing. The branch should be considered dead, no changes must be applied to it. I will delete it soon.
After the merge, the trunk uses a new Remoting version (2.2.0.Alpha4), and the Remoting Callback API to send messages from server to client.
The latest trunk version uses asynchronous push callbacks (and polling under the hood for HTTP). The pre-merge trunk relied on synchronous calls to send messages from server to client and expected synchronous delivery confirmation (not to be mistaken with client acknowledgment). Such a behavior cannot be expected from asynchronous callbacks, so I modified MessageCallbackHandler to asynchronously send delivery confirmations back to server, and the ServerConsumerEndpoint to manage those delivery confirmations sent by the client.
One case in which delivery confirmation management is necessary is when the consumer is closed. The ServerConsumerEndpoint cannot be closed if there are messages in transit from server to client, and the delivery confirmation count mechanism is used to confirm that there are no in-flight messages.
New configuration parameters for HTTP
The polling period (in ms) can be configured, in this order:
1. By setting "jboss.messaging.callback.pollPeriod" system property on the client. This overrides any other configuration.
2. By specifying it as value of the "callbackPollPeriod" attribute, in the HTTP Connector configuration on the server (remoting-service.xml).
3. By relying on the hardcoded JMSRemotingConnection.CALLBACK_POLL_PERIOD_DEFAULT value (100 ms), if no value is explicitly specified.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988051#3988051
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988051
19 years, 4 months
[Design of JBoss Portal] - Re: Virtual hosts and multiple portal server instances
by sverker
Hi guys
I didn't receive much feedback on the virtual-host stuff. While I understand that it's not high priority for you to support virtual-hosts, I need to urgently solve this as I have some projects which has been on hold waiting for JBoss Portal (or similar component) but now I have to move on.
There are three alternatives:
1. Use JBoss Portal with my own modifications for virtual-host support and merge back later when eventually this issue is solved.
2. Dump JBoss Portal and use something else.
3. Work together with you guys to get virtual-host support implemented the correct way.
No 1 solves the problem temporarily but can potentially cause bigger problems later when migrating to mainstream release.
No 2 is possible but the alternatives I've been looking at I didn't like too much as they aren't properly integrated with the rest of the app server.
No 3 is preferable, but how can we move forward? I can write the code but need to communicate with you regarding how to design and integrate the support.
In http://jboss.org/index.html?module=bb&op=viewtopic&t=92151 Julien mentions namespaces. That the war file foo.war would be deployed to webapp:foo.default.default.
This would work, the namespace is like I used context in my proposal implementation. The virtual host details will then be bound to the webapp:foo namespace.
What do you think about that approach?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988018#3988018
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988018
19 years, 4 months