Hi John,
SocketWrapper.CLOSING should be sent only when a ServerThread shuts down and
closes its socket. What's going on on the server side?
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4269119#4269119
Reply to the post :
http://www.fortunecity.com/lavender/tombstone/839/simpsons/Monty_excellent.wav
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4269121#4269121
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4269121
ravi_eze wrote :
| hi,
|
| This is w.r.t.
http://labs.jboss.com/jbossremoting/docs/benchmark/performance_benchmark.html
where comparision between diffarent protocols is done. The page also gives the
JUnit code that generated the graphs. we are trying out with 2.5.2. version.
|
| We
Ah, I see. Well, Remoting has a facility for setting the timeout for each
invocation, but there's no way to access it from the EJB layer. I'm not even
sure what that would look like.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4259726#4259726
Reply to the
It's already done. When you retrieve an EJB3 proxy from JNDI, the proxy brings
the InvokerLocator with it, and the Remoting client uses the parameters in the
InvokerLocator. In this case, the Remoting client will use a timeout value of
3000.
View the original post :
Remoting version 2.2.3.SP1 is available. It features
* Introduction of write timeout facility;
* improved reliability for callbacks in bisocket transport;
* improved treatment of invocation retries in socket and bisocket
* miscellaneous bug fixes.
Upgrading to 2.2.3.SP1 (and also
Remoting version 2.5.2 is available. It features
* Introduction of connection identity concept;
* introduction of write timeout facility;
* improved reliability for callbacks in bisocket transport;
* improved treatment of invocation retries in socket and bisocket transports;
* more
Hi Mayank,
mayankmit2002 wrote :
| I'am just unable to set the socket time out at the client end
|
The timeout isn't set in the initial context call. If you look in
$JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml,
you'll see the MBean definition
|
I would need more information to know precisely what's going wrong. I'm
guessing that the exception occurs in the context of a JBossMessaging
connection, where the JBossMessaging server is trying to send some messages to
a consumer client. For some reason, the attempt to write the messages to
bwarren wrote :
| Is JBoss Remoting the way to go here?
|
Well, as it happens, JBossRemoting is the way you've already gone. EJBs,
EJB3s, and JBossMessaging connections all, by default, use JBossRemoting as
their transport layer, each, again by default, with their own Remoting servers
It's certainly not a Remoting issue. I'm going to suggest posting to the EJB
3.0 Users forum at
http://www.jboss.org/index.html?module=bbop=viewforumf=221 .
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4258018#4258018
Reply to the post :
What you want to do turn on the following parameters in
remoting-bisocket-service.xml:
| !--
| attribute name=numberOfCallRetries isParam=true5/attribute
| attribute name=pingFrequency isParam=true3/attribute
| attribute name=pingWindowFactor
Gowri wrote :
| I am using JBOSS ESB socket listener in my project. I tried to connect to
the server with this socket listener (JBR-Socket ) using a simple java client
program which uses Socket API to make the connection. When I execute this
program, I am getting Worker thread initialization
I don't know if this is relevant, but I just noticed I had a unit test that was
creating an InvokerLocator with port == -1. It turns out that I was creating
| socket://10.32.10.88:40404serializationtype=java
|
instead of
| socket://10.32.10.88:40404/?serializationtype=java
|
Hi Peter,
Strange. I haven't been able to duplicate your experience. Are you using the
standard remoting-sslbisocket-service.xml file, or have you modified it?
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254968#4254968
Reply to the post :
Here are a couple of places to look:
* JavaTM Secure Socket Extension (JSSE) Reference Guide at
http://www.j2ee.me/j2se/1.5.0/docs/guide/security/jsse/JSSERefGuide.html
* javax.net.ssl.SSLServerSocket javadoc at
http://www.j2ee.me/j2se/1.4.2/docs/api/javax/net/ssl/SSLServerSocket.html
Hi Mayank,
I notice that Thread-29, which is holding the java.util.linkedl...@2c1b1c that
the other two threads are blocked on, is in the middle of a
ClientSocketWrapper.checkConnection(), which is called only if the parameter
socket.check_connection is set to true. I usually advise against
Hi Praveen,
The JDNI system does not, by default, use Remoting. I'd suggest trying the
JNDI and Naming forum at
http://www.jboss.org/index.html?module=bbop=viewforumf=214 .
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254972#4254972
Reply to the
I've closed JBREM-1151, having updated the Remoting Guide. The tool Tattletale
was extremely useful. It's available from http://www.jboss.org/tattletale.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4254918#4254918
Reply to the post :
Hi John,
I haven't played with the proxy stuff, but Remoting has nothing to do with the
system properties - if they're set, they should be picked up when the
HttpURLConnection is created. In other words, as far as I can tell, there's
nothing in Remoting to break with respect to proxy
Hi Razvan,
I don't have a lot to add. You could also try increasing the log level,
particularly of JBossMessaging, to TRACE. Look for jboss-log4j.xm in
$JBOSS_HOME/server/$CONFIG/conf. In fact, I think this issue has more to do
with JBossMessaging than JBossRemoting. You might try posing
I think you're on the right track.
maestr() wrote :
| Assuming that I have a JB Remoting endpoint configured on a specific port,
can many clients get connection to the endpoint in a same time?
|
That's a matter of configuration, and how you do the configuration depends on
the
For the record, I finished JBREM-1107
SocketServerInvoker.IdleTimeoutTask interrupts ServerThreads during long
invocation for release 2.2.3.SP1. No fix is necessary in Remoting 2.4/2.5.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4253624#4253624
Hi Eric,
I'm sorry you had a bad experience. I've created JBREM-1151 Correct
dependency discussion in Chapter 4 of Remoting Guide to remind me to clarify
this stuff.
As for maven, Remoting 2 is not mavenized and will never be. Remoting 3 will
be mavenized. You're right that I just manually
That's a good question. Such a facility doesn't currently exist. If you want
to contribute a solution, I would be open to it.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4253666#4253666
Reply to the post :
See thread Callback Identification at
http://www.jboss.org/index.html?module=bbop=viewtopict=159348. I think it's
the same issue.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4253669#4253669
Reply to the post :
Actually, that number, strange as it seems, is fine. Normally, that number
would be the port where the bisocket://10.33.32.22:1810191292/callback? ...
callback server (on the client side) would be listening, but the bisocket
transport doesn't open a port on the client, so this number is just a
Interesting problem. That InvokerLocator,
bisocket://uc_0183_0181/?JBM_clientMaxPoolSize ..., should have a port
following the host. The way JBossMessaging works is, you download a connection
factory, and the connection factory carries with it the InvokerLocator, which
suggests that
cuthbe wrote :
| How do I configure a remoting service to run on a single port but handle
multiple client connections.
|
No configuration is necessary. Remoting servers use a ServerSocket which can
accept multiple client connections.
View the original post :
I've just attached to JBREM-1120 two versions of jboss-remoting.jar with the
write timeout facility implemented:
* 2.2.3.SP1 preview (874 kb): writes Remoting version: 2.2.3.SP1-preview:
8/19/2009 - 14:54 when loaded
* 2.5.2 preview (1.07 Mb): writes JBossRemoting Version 2.5.2 (Flounder)
Chul Yoon wrote :
| I assume I can just set the write timeout attribute for JBM in
remoting-bisocket-service.xml
|
| Something like this?:
|
|
| | attribute name=writeTimeout20/attribute
| |
|
That will set writeTimeout on the server side, which will affect (1)
There's another chapter to the story.
I noticed recently that NewCompressingMarshallerTestCase, which runs in about
half a minute on my Windows laptop, takes about 13 minutes on one of the Red
Hat linux test machines. It turns out that the GZipOutputStream constructor
takes an order of
I'm not really sure what you're asking for. What do you want to do with this
custom object?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4248281#4248281
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4248281
Hi Tom,
Yeah, sorry for the confusion. I can't reconstruct what I was thinking, but I
probably forgot about the fact, even though you mentioned it, that
CoyoteInvoker is wrapping the result in an InvocationResponse.
I think
1. the content-type returned by the ServerInvoctionHandler should be
I've applied Doychin's fix to branch 2.2 (for release 2.2.3.SP1) and branch 2.x
(for release 2.5.2).
Previews of jboss-remoting.jar from each of these branches are attached to
JBREM-1077 if anyone one wants to test the new versions.
I've tested the changes with a sample EJB3 that copies
For the record, JBREM-1121 Client SocketFactory should be configurable by
InvokerLocator is fixed in Remoting release 2.2.3. The changes have also been
applied to the Remoting 2.x branch and will appear in release 2.5.2.
-Ron
View the original post :
mbeierl wrote :
| There is no documentation on how to write a custom transport?
|
Well, there's Chapter 6. Adding a New Transport in the Remoting Guide:
http://www.jboss.org/jbossremoting/docs/guide/2.5/html/index.html.
View the original post :
gaohoward wrote : Hi, this sounds like a remoting issue. You can post it to
the remoting forum as well.
|
Yeah, I sent him here. :) I just wanted to see if you guys had ever seen JBM
running in an applet, or knew of any workarounds.
-Ron
View the original post :
Hi Tom,
I want to add that we've recently made some major fixes on the JBossRemoting /
JBossMessaging boundary in Remoting 2.2.3 and JBM 1.4.0.SP3_CP08. They are
related to the ConnectionValidator, so they may be relevant to your situation.
The same changes will be ported to Remoting 2.5.2.
Well, the problem with MarshallerEditor is that it doesn't exist.
When BisocketClientInvoker initializes itself, it uses a class called
org.jboss.util.propertyeditor.PropertyEditors, which calls
java.beans.PropertyEditorManager.findEditor() to try to find editors to set all
the
Hi Goldi,
goldi wrote :
| - SSB from JBoss2 tries to call SSB on JBoss1 and JBoss1 is down
| + how to retry the call?
|
| - SSB from JBoss2 calls SSB on JBoss1 and the connection gets lots during
the call
| + how to retry the call?
|
Well, Remoting can retry an invocation in the
Hi Frank,
I'm going to suggest posing the question in the EJB 3.0 forum:
http://www.jboss.org/index.html?module=bbop=viewforumf=221 .
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244418#4244418
Reply to the post :
Hi Toni,
For this one I'm going to suggest the EJB 3.0 forum:
http://www.jboss.org/index.html?module=bbop=viewforumf=221 .
And, again, say more about what you mean by monitor.
Good luck,
Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244420#4244420
waylandc wrote : Any ETA on 2.2.2SP12?
Release 2.2.2.SP12 morphed into 2.2.3, which was released in May. The next
release, 2.2.3.SP1, should come out in early September, and I'll aim to get the
write timeout facility in that release.
View the original post :
jlaemthonglang wrote : does this bug affect JBM queue too? or topics only?
As far as I know, it should affect both. I'm sure someone from JBossMessaging
could be more definite.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244416#4244416
Reply to the post :
Hi Toni,
The fact is that JRMPInvoker and JRMPInvokerHA aren't part of Remoting, and I
don't know much about them. I'm going to suggest that you pose the question in
the Clustering/JBoss forum:
http://www.jboss.org/index.html?module=bbop=viewforumf=64 .
Also, you could be more specific about
I can tell you that Remoting 2 is entering the twilight of its lifetime, though
I expect it to be in active maintenance mode for a few years. That is, there
won't be much new development, but I'll continue to fix bugs. It's in some of
our products supported by contacts, so we're obligated to
Glad to hear it. Thanks for the update.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244404#4244404
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244404
___
jboss-user mailing
Thanks, Vinay. I put a watch on that thread. Hopefully we'll get to the
bottom of this issue.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244405#4244405
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244405
Hi Kris,
Well, that just shows that every day, in every way, we get better and better.
:)
I have two suggestions.
1. On a busy network, or busy hosts, a spurious failure is always possible. If
you lengthen the ping cycle, e.g.,
| attribute name=validatorPingPeriod
Hi Alfonso,
Sorry to be dense, but I'm just not following you. Are you asking how to
determine how many connections are coming into a Remoting server?
If so, and assuming you are using the socket transport, then I can tell you
that each connection to the server is represented by an
Are you still having this problem?
Note:
1. The fix for JBREM-1005 is in Remoting 2.5.1.
2. The parameter you want is pingFrequency, not pingTimerFrequency.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244497#4244497
Reply to the post :
Well, I've never tried to do what you're asking about, but it looks like it's
just a matter of telling JNDIDetector which URL to connect to so that it gets
an InitialContext from HA-JNDI instead of JNDI. In particular,
JNDIDetector.createContext() does this:
|
Please post your question on the JBoss Operations Network forum:
http://www.jboss.org/index.html?module=bbop=viewforumf=285 .
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244186#4244186
Reply to the post :
Is multicasting enabled? Are the client and server on the same subnetwork?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244185#4244185
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244185
Hi Kris,
I don't know enough about JBossMessaging to comment on these ExceptionListener
callbacks. Could you tell me what they are saying?
Thanks,
Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244188#4244188
Reply to the post :
mbeierl wrote :
| But where do I find out what arg0, arg1, ... etc are and how I am supposed
to use them?
|
Take a look at an existing transport. For example,
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport().
Also, note that the transport() method is called by
There's no built in listener facility (except in the context of callbacks from
the server to the client).
However, if you want to have some fun, you could write a custom SocketFactory
that creates custom Sockets that return custom SocketInputStreams. You would
want to configure the
Hi Vinay,
That's a very interesting finding, and I don't have a clue what could cause the
slowdown. Could you start a thread on the EJB 3.0 forum
http://www.jboss.org/index.html?module=bbop=viewforumf=221 and see if any one
there has some ideas? If you do, could you post on this thread a
Hi Rupert,
When you say gateway, it makes me think you are talking about JBossESB. I
hope so, since I don't know what you're talking about. :)
If I'm right, could you post the question on the JBossESB forum:
http://www.jboss.org/index.html?module=bbop=viewforumf=246 ?
Thanks,
Ron
View the
Hi Markus,
I've seen some similar firewall issues lately, and I can make some suggestions:
dahm wrote :
| Remarkable settings on the server side:
|
| in bisocket-remoting.xml: Enabled pings
|
|
| | attribute name=pingFrequency isParam=true6/attribute
| | attribute
Well, I've written probably the simplest possible transport, called test.
It's dumb, but it works.
The client invoker is
| package org.jboss.remoting.transport.test;
|
| /* imports */
|
| public class TestClientInvoker extends RemoteClientInvoker {
|
|public
timfox wrote : There are tests in the JBM test suite which should be checking
it runs ok in a restricted security environment.
It's not really a security issue.
org.jboss.remoting.transport.MicroSocketClientInvoker (ancestor of
BisocketClientInvoker) uses
Hi John,
The fact is that clientConnectAddress is used only on the server side by
org.jboss.remoting.transport.transport.Connector to generate an InvokerLocator
from a declarative XML configuration (e.g., an MBean). So, for example,
| mbean code=org.jboss.remoting.transport.Connector
|
Ok, cool. Confirming, once again, the power of procrastination. :)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242992#4242992
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242992
JBREM-1144 Extend connection identity to server side.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242996#4242996
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242996
___
Sorry for the delay. Is this problem still outstanding?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242997#4242997
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242997
___
Hi Ondrej,
There are no plans to extend streaming in Remoting 2, but Remoting 3 will have
a general purpose streaming mechanism.
Thanks for the links!
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242999#4242999
Reply to the post :
Your problem isn't a Remoting problem. I'm going to suggest that you post the
question to the JNDI/Naming/Network forum at
http://www.jboss.org/index.html?module=bbop=viewforumf=214.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243000#4243000
Reply to the
Hi Frank,
I don't have any good suggestions. As far as I know, it's just a fact of life
that underscores in host names cause problems. See, for example,
http://en.wikipedia.org/wiki/Hostname.
By the way, I can't see from your stacktrace just which call in
MicroSocketClientInvoker is
Ok, I think I understand your question a little better. It sounds like you
want to run some stealth system started up in a servlet but otherwise
independent of the Application Server. Is that about right?
I can tell you that you can start up Remoting clients and servers in any
context you
Hi Tom,
Clearly, the empty download page was a temporary glitch.
In any case, for the record, you can go to the svn repository to get source
code for any of the released jars. Each release is saved in
http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/
For example, to get the
Hi Vinay,
The 2.5 releases represent minor evolutionary changes from the 2.4 releases,
and I'm not aware of any incompatibilities, other than the fact that the coyote
invoker (the server side of the Remoting http transport) in the 2.5 releases
doesn't work with apache Tomcat, only JBossWeb.
Hi Vinay,
Have you made any progress with this issue?
Of course, if you're using the same version of Remoting in both cases, I feel
fairly safe in assuming it's not a Remoting problem. Of course, you never know.
When you say rmi call, which particular subsystem are you talking about.
EJB3,
You are quite correct, Trustin. I would add only that the http and servlet
transports use http connections, so the serialized objects are encoded. But
there's no XML.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243037#4243037
Reply to the post :
There's no built in way to do that. If you are using a pure Remoting client /
server system, then you could send the certificate along with the invocation in
the metadata map passed to the org.jboss.remoting.Client method
|public Object invoke(Object param, Map metadata) throws
mattlf wrote :
| Is the multicast in the discovery mechanism going to work over different
subnets
|
org.jboss.remoting.detection.multicast.MulticastDetector uses a
java.net.MulticastSocket, and doesn't call MulticastSocket.setTTL() or
MulticastSocket.setTimeToLive(), so it uses the
By the way, Remoting does use a home grown distributed testing framework called
jrunit, an extension of junit, and jrunit uses jgroups.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243039#4243039
Reply to the post :
Hi Tom,
It's not understanding the syntax toms-d2003x64/10.1.3.10. Try
socket://toms-d2003x64:1600 or socket://10.1.3.100:1600.
-Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243040#4243040
Reply to the post :
Hi Tom,
HTTPMarshaller and HTTPUnMarshaller include special handling for strings in
order to avoid serialization. The problem is that old test for string or
not string, which worked prior to JBREM-653 allow user to set content-type
for http responses is no longer appropriate.
I'm thinking
Hey Brian,
A brief scan of the related thread suggests that it turned out that Remoting
isn't the source of the problem. Is that true?
Thanks,
Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242734#4242734
Reply to the post :
Remoting version 2.2.3 is available. It features
* Introduction of connection identity concept;
* upgrading of servlet transport;
* improved configuration flexibility;
* miscellaneous bug fixes.
Upgrading to 2.2.3 is particularly recommended if you are using JBossMessaging
in Application
Hi Tarek,
thammoud wrote :
| anonymous wrote :
| | Make the tt (WaitOnConnectionCheckTimerTask) a class member (Must be
volatile).
| |
|
| Did not mean a static. Sorry for the confusion.
|
My mistake. Maybe I was thinking in C++? :)
I think I can explain your first
peter_pinnau wrote :
| How can I repack the jbossall-client.jar so that the patched
jboss-remoting.jar is used.
|
Probably the easiest thing to do is just put the new jboss-remoting.jar in
front of jbossall-client.jar in the classpath. Or, you could unpack
jbossall-client.jar, delete
vybe3142 wrote :
| can /how can I get jboss demoting functional within an enterprise app
deployed on a non jboss app server eg glassfish?
|
Not sure I understand the question. There are a couple of ways Remoting could
live in an application server. Note that I don't know anything
See my response on the other thread, JBoss remoting - Compatability with non
JBoss J2EE Applicati, at
http://www.jboss.org/index.html?module=bbop=viewtopict=153078.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226302#4226302
Reply to the post :
Hi Eugene,
I'm guessing that you're using JBoss Web Services to connect to .NET, right?
They use Remoting to send Soap messages, but I don't much about what they do.
I'm going to suggest you try the JBossWS forum at
http://www.jboss.org/index.html?module=bbop=viewforumf=200.
-Ron
View the
Remoting version 2.5.1, the version targeted for JBoss Application Server
5.1.0.CR1, is available. It features
* a security fix
* improved configurability
* a number of bug fixes
To see the release notes, go to
Check out JBoss Remoting + JBoss Serialization kills JavaRMI and Spring
Remoting, a blog about the combination of JBossSerialization and JBossRemoting:
http://www.theserverlabs.com/blog/2009/02/19/jboss-remoting-jboss-serialization-kills-javarmi-and-spring-remoting/comment-page-1/#comment-1530
timfox wrote :
| Ron, do you have a JIRA and ETA for this?
|
JBREM-1120 Add a socket write timeout facility.
I was hoping to get something into Remoting 2.5.1, which I just released, but
time didn't allow. I've scheduled JBREM-1120 for releases 2.2.2.SP12 and 2.5.2.
-Ron
View the
I think there are two issues here.
1. deckrider wrote : but I also don't want the client to know about port 3873
If you mean client in the sense of your own application code, then don't
worry. It doesn't need to know about port 3873. When you execute
| hello = (HelloWorld)
Yup: CLONE [JBREM-851] - In LeasePinger replace Timer if it has shut down
(https://jira.jboss.org/jira/browse/JBREM-).
What was I thinking?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222874#4222874
Reply to the post :
This question doesn't seem to have any relationship to Remoting. I'm going to
suggest that you try the Tomcat, HTTPD, Servlets JSP forum
(http://www.jboss.org/index.html?module=bbop=viewforumf=50).
View the original post :
Well, I'm not sure if you're asking how, in general, to make an invocation on
the JBoss Application Server, or if you already know how to use, say, AS 4.2
and want to know how to do the same with AS 5.
If it's the former, then there's a tutorial written by John Mazzitelli called
Introducing
I have a question.
On the server side, there is an org.jboss.remoting.Lease which, if it doesn't
receive pings from the client in a timely fashion, will declare that a
connection is broken and inform any registered listeners. Now JBossMessaging
registers a listener, so it should be informed
If you're using the UnifiedInvoker, which is based on JBossRemoting, then you
can go to $JBOSS_HOME/server/$CONFIG/conf/jboss-service.xml and update the
jboss.remoting:service=Connector,transport=socket MBean with a timeout
parameter:
| mbean code=org.jboss.remoting.transport.Connector
|
Hi Markus,
When a Remoting client and server are in the same JVM, the client will, by
default, make a method call directly on the server instead of marshalling and
unmarshalling invocations over a pair of sockets. For example,
| at
Hi guys,
I posted an answer on the related Remoting forum.
I don't know what's going on here, but, for what it's worth, I can tell you
that Remoting doesn't create leases when the client and server are in the same
JVM (unless you set force_remote to true). Don't know if that's relevant.
Hi Tarek,
thammoud wrote :
| ron.si...@jboss.com wrote :
| | Are you actually seeing a case where the client's JMS connection
listener does not get called yet the connection is invalid ?
| |
|
| Yes. Only when the server restarts in a time that is less than the ping
period
I don't see anything too unusual here, since
sun.net.www.protocol.http.HttpURLConnection.getInputStream() and
java.io.BufferedInputStream.read() are both synchronized methods. Rather than
a lock problem, I would guess that jrockit.net.SocketNativeIO.readBytesPinned()
is hanging, waiting for
1 - 100 of 190 matches
Mail list logo
