Jaikiran,
Thanks for your reply, however we need to have 0.0.0.0 set because our server
has multiple addresses and needs to be accessible by all of them. So even if
the fix worked, it would not really work for us.
Dave,
Thanks for posting, if it helps, your experience is exactly like mine, which
Hi Graeme,
org.jboss.remoting.transport.PortUtil.findFreePort() will return an available
port. It also loops until it finds a free port, but it would be cheaper than
creating a Connector each time around the loop.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
anonymous wrote :
| Question 1:
| Is it possible to have each clients socket context connection saved in the
server so that the server can do a push to the registered clients? I am not too
sure if the pull / push callbacks are the right way to go forward. The "Mina"
framework offers this fe
Hi James,
I think that Remoting, in its current form, might be too low level for you.
There is a failover facility in the Transporter code
(org.jboss.remoting.transporter.*), but it's more of a demonstration than a
fully developed feature. There isn't any loadbalancing feature.
For a brief
I believe that the JBoss JNDI implementation does not currently use Remoting by
default. However, see the wiki page JNDIOverHTTPWithUnifiedInvoker
(http://wiki.jboss.org/wiki/JNDIOverHTTPWithUnifiedInvoker about using the
UnifiedInvoker (which does use Remoting) to do JNDI lookups.
Having sa
Hi Venkatramanan,
This really isn't the right forum for your question. You might try
"Installation, Configuration & DEPLOYMENT"
(http://www.jboss.com/index.html?module=bb&op=viewforum&f=61).
The message you're seeing suggests that something other than an RMI registry is
listening on port 1099
Hi Alexey,
Thanks for the information. I'll take a look at NetworkRegistry and
JNDIDetector, although probably not for the next release.
By the way, back when I had time to read novels, I was a big fan of Dan
Simmons. I still can't get the ocean planet bathroom out of my mind. :)
-Ron
View
You're on the right track. A Connector is an MBean, and once you get a
reference to it, you can invoke its methods. You don't need to use the
RMIAdaptor, however, since your service is running in the same JVM as the
connector. You can talk directly to the MBeanServer.
View the original post :
Hi Joshua,
Are you sure the server is bound to 127.0.0.1? Just a thought.
By the way, if the "InvokerLocator" attribute is specified, the "Configuration"
attribute will be ignored.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146966#4146966
Reply to the
Hi,
I was experimenting how to make a EJB to EJB call, and I started with let a EJB
call itself. but no luck, could someone please help and point me to the right
direction?
The EJB code (modified based on some ws code in jboss4guide):
package org.jboss.ws.hello;
|
|
| import javax.ejb
Hi,
I was experimenting how to make a EJB to EJB call, and I started with let a EJB
call itself. but no luck, could someone please help and point me to the right
direction?
The EJB code (modified based on some ws code in jboss4guide):
package org.jboss.ws.hello;
|
|
| import javax.ejb
Which version of the Application Server are you using?
Version 2.4.0 of Remoting has a solution to your problem based on JIRA issue
JBREM-877 "New Socket Connection is being Created for Every Client Request to
the Server". Remoting 2.4.0.CR1 (the latest 2.4.0 release) should be
compatible with
Help me fix this bug please !
I'm using jbpm 3.2 and deploy under jboss SA 4.2.1GA
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName
Hi John,
You're right that RMIClientInvoker doesn't try to reload the server stub in the
event of an invocation error. More generally, Remoting clients don't promise
to seek out a new server if an old one dies, although the socket transport is
more likely to find a new server since it will att
101 - 114 of 114 matches
Mail list logo
