[jboss-user] [JBoss Remoting Users] - Re: why would version == SocketWarpper.CLOSING ?
http://www.fortunecity.com/lavender/tombstone/839/simpsons/Monty_excellent.wav View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269121#4269121 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269121 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: why would version == SocketWarpper.CLOSING ?
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=bb&op=viewtopic&p=4269119#4269119 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269119 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - JBoss RMI + Serialization performance issue
"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 are evaluating Java RMI and JBoss RMI over socket + Jboss serialization. We see that Java RMI with Java serialization is always atleast 20% faster than Jboss RMI + socket + Jboss serialization. | | i am unable to understand the below from the test cases. | | 1. The payload uses byte[1024] empty array always. and the object is never serialized. | 2. why byte[] as theres not thing there to serialize in it | 3. Even on using byte[1024] to be sent across using jboss and java rmi we see java rmi is superior on our machines. | | If this is the case then how ar the graphs generated? Or am i missing something very important. Please help. | | -- | ravi | Actually, the byte array gets wrapped in some Remoting objects, which do indeed get serialized. By "Java RMI with Java serialization" I assume you mean the "raw_socket" results, or maybe the "raw_rmi" results, and by "Jboss RMI + socket + Jboss serialization" I assume you mean "socket transport with jboss serialization". Is that right? If so, then I can't explain why you're seeing results different than ours. Who knows? Different machines, different jdk's, etc. By the way, before I released version 2.4.0.GA, I did a lot of testing and tuning, and, in the end, the performance of 2.4.0.GA and whatever the latest 2.2.x release was at the time were very close, within a few percentage points. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260914#4260914 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260914 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Set the 'timeout' parameter at the client side for an EJ
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=bb&op=viewtopic&p=4259726#4259726 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259726 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Set the 'timeout' parameter at the client side for an EJ
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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259481#4259481 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259481 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - JBoss ESB issue
"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 error in JBOSS ESB server. But I am not getting this error if I am using org.jboss.remoting.Client for making the connection. Could you pls. let me know why I am getting this error? | | Thanks | | Gowri | Hi Gowri, The JBR-Socket listener, if I understand correctly, is a JBossRemoting server, expecting to respond to requests from a JBossRemoting client. So you would either have to use a JBossRemoting client or make your client look like a JBossRemoting client. The latter is possible, but why bother? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258020#4258020 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258020 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: No ping on secondaryBindPort
What you want to do turn on the following parameters in remoting-bisocket-service.xml: | | (taken from the recent JBossMessaging release 1.4.0.SP3_CP09), upgrade to Remoting release 2.2.3.SP1 in which the "generalizeSocketException" parameter is introduced, and (possibly - I'm not sure if it's necessary) upgrade JBossMessaging. That should work around the firewall killing idle connections. See JIRA issue JBMESSAGING-1733 "Update settings in remoting-bisocket-service.xml" at https://jira.jboss.org/jira/browse/JBMESSAGING-1733. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258019#4258019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258019 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: JNDI Lookup Fails, Causes Failed EJB2 MDB
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=bb&op=viewforum&f=221 . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258018#4258018 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258018 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: J2EE remote client HTTP tunneling
"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 listening on ports other than 80. However, one of the primary design principles of Remoting is the ability to swap one Remoting transport for another. In your case, you can get closer to your goal with the servlet transport, in which all of the various proxies connect to a Remoting servlet, which then passes the invocations to the appropriate subsystem. Of course, you would need a servlet container (i.e., a JBossWeb (aka Tomcat) connector) listening on port 80. Can you do that? Or will the network powers open up, say, 8080 (the default JBossWeb port in the Application Server - see $JBOSS_HOME/server/$CONFIG/deploy/jboss-web.deployer/server.xml)? The configuration details are given in the wiki entry "EJB, JMS and JNDI over HTTP with Unified Invoker" at http://www.jboss.org/community/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker. What do you think? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258016#4258016 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258016 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Help Me
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 the connection fails. It could be because the client closed unexpectedly. It could be because of a network failure. It could be because a firewall has killed an idle connection. Do any of these sound plausible? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258011#4258011 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258011 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker
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
|
| jboss.aop:service=AspectDeployer
| socket://${jboss.bind.address}:3873
|
|
| org.jboss.aspects.remoting.AOPRemotingInvocationHandler
|
|
|
|
If you add "timeout" to the InvokerLocator attribute, it will be used by the
Remoting server defined by the MBean and also by all of its clients:
|
| jboss.aop:service=AspectDeployer
| socket://${jboss.bind.address}:3873/?timeout=1
|
|
| org.jboss.aspects.remoting.AOPRemotingInvocationHandler
|
|
|
|
For more information about Remoting configuration, see Chapter 5 of the
Remoting Guide: http://jboss.org/jbossremoting/docs/guide/2.2/html/index.html.
-Ron
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258010#4258010
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258010
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Remoting release 2.5.2 is available
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 flexible configuration (see, for example,
org.jboss.remoting.Remoting.CONFIG_OVERRIDES_LOCATOR);
* added immediate shutdown option for socket transport;
* multiple bug fixes.
Upgrading to 2.5.2 s particularly recommended if you are using JBossMessaging
in Application Server 5.x. See, for example,
https://jira.jboss.org/jira/browse/JBREM-1146 "Treat IOException("Connection
reset by peer") as a retriable exception" and
https://jira.jboss.org/jira/browse/JBREM-1147
"BisocketClientInvoker.createSocket() in callback mode should check for
replaced control socket"
for more information. Note that these changes were made, in part, to improve
resilience in the presence of firewalls that kill idle connections.
To see the release notes, go to
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313483&styleName=Text&projectId=10031&Create=Create.
Version 2.5.2 of jboss-remoting.jar may be found
* in the old repository at http://repository.jboss.com/jboss/remoting/ , and
* in the maven2 repository at
https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/remoting/jboss-remoting/
or
http://anonsvn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/remoting/jboss-remoting
.
The distribution zip file may be found at
http://www.jboss.org/jbossremoting/downloads/ .
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257976#4257976
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257976
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Remoting release 2.2.3.SP1 is available
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 JBossMessaging release 1.4.0.SP3.CP09) is
particularly recommended if you are using JBossMessaging in Application Server
4.2. See, for example,
https://jira.jboss.org/jira/browse/JBREM-1146 "Treat IOException("Connection
reset by peer") as a retriable exception"
https://jira.jboss.org/jira/browse/JBREM-1147
"BisocketClientInvoker.createSocket() in callback mode should check for
replaced control socket", and
https://jira.jboss.org/jira/browse/JBREM-1152 "If MicroSocketClientInvoker gets
a SocketException in getConnection(), it should retry"
for more information.
To see the release notes, go to
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313585&styleName=Text&projectId=10031&Create=Create.
Version 2.2.3.SP1 of jboss-remoting.jar may be found in the old repository at
http://repository.jboss.com/jboss/remoting/ .
The distribution zip file may be found at
http://www.jboss.org/jbossremoting/downloads/ .
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257970#4257970
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257970
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: port problem on windows embedded pos
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:40404&serializationtype=java | instead of | socket://10.32.10.88:40404/?serializationtype=java | Later on, the parsing code in the InvokerLocator class turned the port into -1. Moral: check InvokerLocator. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255199#4255199 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255199 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: JNDI Lookup in multi-classloader environment
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=bb&op=viewforum&f=214 . -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254972#4254972 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254972 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker
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 turning on the check connection facility, since it involves an extra round trip i/o. Did you mean to turn that on? I think that if you turn it off, the problem might go away. "mayankmit2002" wrote : | I have already set jnp.sotimeout value to | I don't recognize "jnp.sotimeout", but the parameter that controls socket timeouts in Remoting is "timeout". Setting "timeout" might also solve your problem. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254970#4254970 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254970 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Disable Weak Ciphers for PCI-DSS
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 Hope that helps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254969#4254969 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254969 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: port problem on windows embedded pos
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=bb&op=viewtopic&p=4254968#4254968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254968 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Problem running with Maven
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=bb&op=viewtopic&p=4254918#4254918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254918 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: is JBoss remoting good choice for me ?
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 transport you're using. In the socket transport, which is the most commonly used transport, the parameter "maxPoolSize" determines the maximum number of worker threads, where each worker thread services one invocation at a time. The default value is "300", so that you could have up to 300 clients connected simultaneously. "maestr() wrote : | Is it thread safe ? | The Remoting code is thread safe. It's up to you to make your ServerInvocationHandler thread safe. "maestr()" wrote : | How should I implement ServerInvocationHandler to invoke specified in a request method on the server side ? | So far I do it like this: | That looks reasonable. Note that, in addition to the parameter, you can pass an entire map of objects by calling |public Object invoke(Object param, Map metadata) throws Throwable; | in org.jboss.remoting.Client. In the ServerInvocationHandler the map can be retrieved with org.jboss.remoting.InvocationRequest.getRequestPayload(). Good luck. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254284#4254284 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254284 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: port problem on windows embedded pos
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 the question on the JBossMessaging users forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=238 . Good luck. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254267#4254267 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254267 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: invoker locator config vs. request metadata params
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 specification by system properties. There's a discussion here: http://java.sun.com/javase/6/docs/technotes/guides/net/proxies.html. It's for jdk 6, but the system properties go back to jdk 1.4 As far as setting the "http.proxyHost" and "http.proxyPort" parameters in the InvokerLocator, well, there isn't a way to do it as of now. I can think of two reasons: (1) it's really a client specific issue, not relevant to the server, and (2) a new HttpURLConnection is created with each invocation, so it's natural to grab the parameters from the metadata map passed to the invocation. Nonetheless, in a context like the Application Server, where most configuration gets downloaded from the server, I can see why you might want to be able to configure these properties in the InvokerLocator. If you want to create a JIRA issue, I'll make it possible. By the way, Remoting 2 is more or less in maintenance mode now, so I won't be doing much new development. But for you ... :) -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254227#4254227 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254227 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - TransporterClient threaded port
"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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253692#4253692 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253692 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: port problem on windows embedded pos
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 something is going wrong when JBossMessaging starts up on the server. Look for suspicious complaints in the server.log. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253690#4253690 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253690 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Weird port number on connection fail
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 unique value to distinguish this InvokerLocator from any other InvokerLocators. When a callback client (on the server side), which JBossMessaging uses to sends messages to a consumer, wants a new socket, it writes a message to the client, and the exception you're seeing means that that process failed. It could be a problem with the connection over which that message is written, but it's more likely that there's a problem on the client side. Take a look at your client side logs. If you see a complaint from ConnectionValidator about a failed connection, try increasing the values of | 1 | 5000 | in your $JBOSS_HOME/server/$CONFIG/jboss-messaging.sar/remoting-bisocket-service.xml. That will reduce the likelihood of spurious connection failures on a busy network or between busy hosts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253689#4253689 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253689 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Pass a custom object into callback handler
See thread "Callback Identification" at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159348. I think it's the same issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253669#4253669 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253669 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Callback Identification
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=bb&op=viewtopic&p=4253666#4253666 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253666 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Problem running with Maven
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 put some jars in the maven repository, which I do for the use of the Application Server. I continue to put all of the jars in the "old" repository at http://repository.jboss.com/jboss/remoting/ . -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253665#4253665 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253665 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Remoting Users] - Re: Socket invocator and long transactions
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=bb&op=viewtopic&p=4253624#4253624 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253624 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
"Chul Yoon" wrote : | I assume I can just set the write timeout attribute for JBM in remoting-bisocket-service.xml | | Something like this?: | | | | 20 | | | That will set "writeTimeout" on the server side, which will affect (1) writing responses to the client and (2) sending messages to the client. If you want to configure the client side as well, then add the "isParam" attribute, which will put "writeTimeout" in the InvokerLocator which gets sent to the client: | 20 | -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250478#4250478 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250478 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
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) preview: 8/19/09-14:59" when loaded Note that release 2.2.3.SP1 is scheduled for September 14, 2009. Right now I don't have a release date for 2.5.2. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250467#4250467 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250467 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Pass a custom object into callback handler
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=bb&op=viewtopic&p=4248281#4248281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248281 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss Remoting and compression
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 magnitude longer in linux than in Windows. I've changed CompressingMarshaller so that it reuses a single GZipOutputStream but replaces the Deflater with each call to write(). CompressingUnMarshaller has the symmetric changes with respect to Inflater. Now NewCompressingMarshallerTestCase takes about 18 seconds on my Fedora laptop. I've attached to JBREM-1077 "Fix problem in CompressingMarshaller" a copy of jboss-remoting.jar from the 2.x branch with the changes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248222#4248222 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248222 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: HTTPUnMarshaller and InvocationResponse objects
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 preserved and sent back to the client, but 2. HTTPUnMarshaller shouldn't be using the value of content-type. Maybe Remoting should send a new metadata value, say 'remoting-type', to be used by HTTPUnmarshaller, which would then remove it from the metadata map before it gets back to the client. I've created JBREM-1145 "HTTPUnMarshaller shouldn't use the value of content-type to determine the type of an object". Now it makes sense? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247653#4247653 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247653 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss Remoting and compression
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 strings to the server and back. It is also attached to JBREM-1077. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246317#4246317 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246317 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Problem with remote JBM access from applet running on co
"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 org.jboss.util.propertyeditor.PropertyEditors to set its own bean properties, and, in doing so, it looks for an editor for "marshaller" and "unmarshaller". There's no such editor, and, normally, PropertyEditors just skips over the property, but, in this case, there's an attempt to load the class remotely, which fails. So it's a strange interaction between Remoting and the applet environment. I just wondered if you guys had ever run across this issue before. Can it be that no one has ever tried to run JBossMessaging in an applet? If its been done and no one complained, then maybe there's something specific to kweebo's situation. Thanks, -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244792#4244792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244792 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Writing a custom invoker howto?
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 TestClientInvoker(InvokerLocator locator, Map configuration) {
| super(locator, configuration);
|}
|
|protected String getDefaultDataType() {
| return SerializableMarshaller.DATATYPE;
|}
|
|protected void handleConnect() throws ConnectionFailedException {
|}
|
|protected void handleDisconnect() {
|}
|
|protected Object transport(String sessionId, Object invocation, Map
metadata, Marshaller marshaller, UnMarshaller unmarshaller)
|throws IOException, ConnectionFailedException, ClassNotFoundException {
| Socket s = new Socket(locator.getHost(), locator.getPort());
| InputStream is = s.getInputStream();
| OutputStream os = s.getOutputStream();
| System.out.println(this + " writing " + invocation);
| marshaller.write(invocation, os);
| Object response = unmarshaller.read(is, metadata);
| System.out.println(this + " returning " + response);
| s.close();
| return response;
|}
| }
|
and the server invoker is
| package org.jboss.remoting.transport.test;
|
| /* imports */
|
| public class TestServerInvoker extends ServerInvoker
| {
|private Thread t;
|private ServerSocket ss;
|private boolean running;
|private UnMarshaller unmarshaller;
|private Marshaller marshaller;
|
|public TestServerInvoker(InvokerLocator locator, Map configuration) {
| super(locator, configuration);
|}
|
|protected String getDefaultDataType() {
| return SerializableMarshaller.DATATYPE;
|}
|
|public boolean isTransportBiDirectional() {
| return false;
|}
|
|public void start() throws IOException {
| super.start();
| unmarshaller = MarshalFactory.getUnMarshaller(getDataType(),
serializationType);
| marshaller = MarshalFactory.getMarshaller(getDataType(),
serializationType);
| ss = new ServerSocket(locator.getPort(), -1,
InetAddress.getByName(locator.getHost()));
| t = new Thread() {
| public void run() {
| try {
|while (running) {
| Socket s = ss.accept();
| InputStream is = s.getInputStream();
| OutputStream os = s.getOutputStream();
| Object request = unmarshaller.read(is, null);
| System.out.println(TestServerInvoker.this + " read " +
request);
| Object response = invoke(request);
| System.out.println(TestServerInvoker.this + " returning "
+ response);
| marshaller.write(response, os);
| s.close();
|}
| } catch (Exception e) {
|running = false;
| }
| }
| };
| t.start();
| running = true;
|}
|
|public void stop() {
| running = false;
| try {
| ss.close();
| } catch (IOException e) {
| }
|}
| }
|
Note that by setting the default datatype to "serializable", I'm reusing the
standard serializing marshaller and unmarshaller used by, for example, the
"socket" transport.
Hope that helps.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244786#4244786
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244786
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Problems after Migration from WebSphere to JBoss (Broken
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 | | | | 6 | | 2 | | | These parameters turn on a control connection test facility in the bisocket transport, and we've seen problems with it lately. The fact is that the JBossMessaging code has never used it (they turned it off, in effect, by making the ping frequency "infinite"), so it's never really been tested in the context of JBossMessaging. I assume your goal in turning it on was to keep the connection alive in the context of the firewall, and I would suggest something like: | 6 | MAX_INT / 6 | (where, of course, MAX_INT / 6 is replaced by an actual integer). This sets the window in which the ping is expected to "infinity", so that you get the pinging without the possibility of a late ping. "dahm" wrote : | We checked that with the firewall and network people and they said that idle connections will be closed after 1 hour. | We built an keep alive client which sends a message to itself (via the server of course) | every 3 minutes and waits for it 10 seconds. If it does not receive the message it will display a message to the user | and restart the connection to the topic. | What's happening, I guess, is that the firewall is killing a connection, but the Remoting client tries to use it anyway, right? The problem with the "keep alive client", though, is that the Remoting bisocket transport uses a pool of connections, and there's no guarantee that the keep alive client will use, and keep alive, all of them. Here's an alternative suggestion. I made it recently in another context and haven't gotten any feedback yet, but it's something to try. If a Remoting invocation results in a SocketException, the invocation will be retried if the parameter "numberOfCallRetries" is set to a value greater than 1. Now, "numberOfCallRetries" is explicitly set to 1 in the "do not change" section of remoting-bisocket-service.xml, but it seems like a reasonable thing to try. Here's yet another untested suggestion. If you set the parameter "idleTimeout" to a value "n" > 0, then a thread on the server will periodically wake up and shut down any ServerThreads that have been idle for more than "n" seconds. Since the ServerThread's socket will get closed, the client should avoid using that connection. "dahm" wrote : | We found that using remoting 2.5.2 may be an issue, should we go back to the 2.2 branch? | The fact is that AS 4.2 hasn't been tested, by us, with Remoting 2.4/2.5. I'm not aware of any reason wh AS 4.2 shouldn't work with Remoting 2.4/2.5, but going back to the 2.2 branch is a viable strategy in the face of problems. However, in this case, I suspect you'd see the same firewall issues. Let us know how it goes. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244173#4244173 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244173 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBR-Socket
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=bb&op=viewforum&f=246 ? Thanks, Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244177#4244177 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244177 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Performance slowdown on JBoss 4.2.3.GA
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=bb&op=viewforum&f=221 and see if any one there has some ideas? If you do, could you post on this thread a pointer to the new thread so I can follow it? Thanks, Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244176#4244176 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244176 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Socket timeout exception handler
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 SocketFactory with a listener that can be called by the custom SocketInputStreams. To read about configuring Remoting with custom SocketFactories, take a look at Section "5.7. Socket factories and server socket factories" of the Remoting Guide at http://www.jboss.org/jbossremoting/docs/guide/2.5/html/index.html. How you would inject the listener into the SocketFactory depends on the context. If you're running in the Application Server, you could use MBeans (or POJOs if you're using AS 5). If you're running outside the AS, you could do it programmatically. If you like this idea and need more pointers, let me know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244181#4244181 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244181 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Writing a custom invoker howto?
"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 org.jboss.remoting.MicroRemoteClientInvoker.invoke(). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244184#4244184 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244184 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: javax.jms.JMSException: Failure on underlying remoting c
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=bb&op=viewtopic&p=4244188#4244188 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244188 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss5 && DetectorService
Is multicasting enabled? Are the client and server on the same subnetwork? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244185#4244185 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244185 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: hyperic postfix plugin
Please post your question on the "JBoss Operations Network" forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=285 . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244186#4244186 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244186 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Help with HA Remoting with JBoss
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: | env.put(Context.PROVIDER_URL, host + ":" + port); | so in your code you want | detector.setPort(1100); | where 1100 is the default port for HA-JNDI, as you can see in the "jboss:service=HAJNDI" MBean in $JBOSS_HOME/server/all/deploy/cluster-service.xml. For more about HA-JNDI, see section "14. Clustered JNDI Services" in the AS documentation: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/4/html/index.html. Let me know how it goes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244495#4244495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244495 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Problem for Timer of BisocketServerInvoker
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=bb&op=viewtopic&p=4244497#4244497 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244497 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: ServerInvocationHandler Performance problem
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 org.jboss.remoting.transport.socket.ServerThread. The ServerThread manages invocations coming in over a single socket. It sits in a loop like this: | while (socket is open) | read invocation | process invocation | return result | So the ServerThread could be sitting in SocketInputStream.read() waiting for the next invocation, but I guess you could still consider it an active connection. To get the number of currently active ServerThreads, you can do something like: | ((SocketServerInvoker) serverInvoker).getCurrentClientPoolSize() | assuming you have access to the ServerInvoker. For example, if you're trying to make the call from an implementation of org.jboss.remoting.ServerInvocationHandler, you can implement ServerInvocationHandler.setInvoker() to store a reference to the ServerInvoker. If I've misunderstood your question, please try again. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244411#4244411 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244411 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: javax.jms.JMSException: Failure on underlying remoting c
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., | 2 | 1 | you might reduce the number of occurrences. 2. We just added some major fixes on the JBossRemoting / JBossMessaging boundary in EAP 4.3.CP05 (Remoting 2.2.3 / JBM 1.4.0.SP3_CP08), which seems to be available now. I'm not sure if they will affect your situation, but I think that anyone using JBossMessaging should probably upgrade to these new jars. Of course, if you have a support contract, you would have to do the whole upgrade. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244403#4244403 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244403 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Performance slowdown on JBoss 4.2.3.GA
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=bb&op=viewtopic&p=4244405#4244405 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244405 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss5 && DetectorService
Glad to hear it. Thanks for the update. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244404#4244404 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244404 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: version confusion
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 keep it working. So I think it's safe to start using Remoting 2. Remoting 3 will be the Remoting of the future. David Lloyd could tell you more about the status of Remoting 3, but I believe 3.0.0.GA is missing some functionality. I believe 3.1.0 will be more "featureful", and the next release will be 3.1.0.CR1. I can't tell you when it will appear. Remoting 3 will have the advantage of being in active development, so, if there's a feature you want, you're more likely to get it Remoting 3 than in Remoting 2. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244413#4244413 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244413 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Monitoring Invokers
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=bb&op=viewforum&f=64 . Also, you could be more specific about what you mean by "monitor". -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244419#4244419 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244419 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
"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=bb&op=viewtopic&p=4244416#4244416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244416 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
"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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244417#4244417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244417 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Monitoring EJBs
Hi Toni, For this one I'm going to suggest the EJB 3.0 forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=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=bb&op=viewtopic&p=4244420#4244420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244420 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Remoting in JBoss 4.2.3 Question: handling timeout and d
Hi Frank, I'm going to suggest posing the question in the EJB 3.0 forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=221 . -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244418#4244418 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244418 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Failsafe RMI
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 event of a network failure, but I suspect you're better off handling the failure at the application level. "goldi" wrote : | - SSB from JBoss2 calls SSB on JBoss1, SSB on JBoss1 changes things in the DB after that the connection between the two JBoss gets lost | + how to rollaback the changes in the database? | Here you want to look into transactions. If you're not familiar with the O'Reilly book Enterprise JavaBeans 3.0 by Bill Burke (who works for JBoss) and Richard Monson-Haefel, that's a good source. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244433#4244433 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244433 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Problem with remote JBM access from applet running on co
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 BisocketClientInvoker bean properties. One of BisocketClientInvoker's bean properties is "marshaller", but there is no editor for it. In the normal course of events, PropertyEditors sees that there is no editor and quietly moves on. I suspect that in your case, the Applet classloader tries to load a MarshallerEditor over the network, which results in different behavior. To be honest, I've never seen this problem before, and don't really know how to handle it. One possibility would be to create a do nothing MarshallerEditor with the same codebase as your applet. You could ask on the "JBoss Messaging" forum (http://www.jboss.org/index.html?module=bb&op=viewforum&f=238) if they have any experience with the use of JBM in an applet. If you do that, I'd appreciate it if you could post a link to that thread so I could follow it. Thanks, Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244453#4244453 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244453 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JMS receiving connection dropped (ConnectionValidator),
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. I don't know which versions of JBossMessaging have been updated - you could ask on the "JBoss Messaging" forum (http://www.jboss.org/index.html?module=bb&op=viewforum&f=238). In general, I think that anyone using JBossMessaging should probably upgrade to these new jars. I suppose it's too late for the beer? :) -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244479#4244479 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244479 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Problem with remote JBM access from applet running on co
"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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244695#4244695 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244695 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Writing a custom invoker howto?
"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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244698#4244698 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244698 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: make ejb3 client use ServerAuthMode=false on sslsocket t
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 : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244480#4244480 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244480 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Can not get connection to server - port out of range -1
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=bb&op=viewtopic&p=4243040#4243040 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243040 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Netty JBossRemoting
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=bb&op=viewtopic&p=4243039#4243039 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243039 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Netty JBossRemoting
"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 default TTL value, which, I believe, is 1. So the multicast detector, in its current form, is restricted to its local network. "mattlf" wrote : | what is the reason for Remoting2 to use its own multicast mechanism? I read that JBoss cluster is based on JGroup. Do you think JGroup could provide value to JBoss Remoting with its multicast capability? | I wasn't present at the creation of the discovery subsystem, but I'm going to say 1. jgroups, which is very powerful, flexible software, could indeed offer a lot of functionality, but 2. it probably wasn't considered desirable to introduce a dependency on jgroups. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243038#4243038 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243038 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: binary protocol?
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=bb&op=viewtopic&p=4243037#4243037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243037 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Performance slowdown on JBoss 4.2.3.GA
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, for example, or JBossMessaging? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243036#4243036 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243036 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Compatibility/Performance of Remoting 2.5.1
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. Also, I wouldn't expect much of a performance difference. If you discover any contradictions to my suppositions, please let me know. Thanks, Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243035#4243035 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243035 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Download area empty
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 source for 2.5.1, go to http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/2.5.1/src/main/ -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243033#4243033 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243033 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Access to client SSL certificate in server invokation ha
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 Throwable; | If you're using a system like EJB3 where Remoting is running under the surface, it would be harder to do, though you could probably do something with a custom interceptor on the client side. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243032#4243032 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243032 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss remoting - Compatability with non JBoss J2EE Appli
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 like, as long as there's a jboss-remoting.jar sitting around. For example, you could configure and start up a Remoting server (technically, create an org.jboss.remoting.transport.Connector) in a servlet and then communicate with it from a client outside the Application Server, as long as the client creates an org.jboss.remoting.Client and connects it to the Connector. Basically, you would be starting a Remoting client/server system like any other, except the server is running in the context of an Application Server. There are simple examples in the Remoting distribution (go to Downloads on http://labs.jboss.com/jbossremoting ) and discussion of the examples in the Remoting Guide ( http://labs.jboss.com/jbossremoting/docs/guide/2.5/html/index.html ). Let me know if you have more questions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243009#4243009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243009 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Connections to Linux servers fail
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 failing. Not that it matters, really. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243005#4243005 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243005 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: RMI and port forwarding problem
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=bb&op=viewforum&f=214. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243000#4243000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243000 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Streming to and from the server
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=bb&op=viewtopic&p=4242999#4242999 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242999 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Problems after Migration from WebSphere to JBoss (Broken
Sorry for the delay. Is this problem still outstanding? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242997#4242997 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242997 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Race condition in ConnectionValidator
JBREM-1144 "Extend connection identity to server side". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242996#4242996 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242996 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Remoting connector not respecting jboss.bind.address
Ok, cool. Confirming, once again, the power of procrastination. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242992#4242992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242992 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: clientConnectAddress not working
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, | | | | | | 192.168.0.82 | 216.23.33.2 | ... | will cause the server to bind to 192.168.0.82 but will lead to the InvokerLocator | socket://216.23.33.2 ... | It is thus that the value of "clientConnectAddress" is communicated to the client, which looks only at the address in the InvokerLocator. The discussion in Remoting Guide must be lacking, so I've created JIRA-1142 "Clarify use of "clientConnectAddress" in RemotingGuide" to remind me to extend it. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242742#4242742 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242742 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Remoting connector not respecting jboss.bind.address
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=bb&op=viewtopic&p=4242734#4242734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242734 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: HTTPUnMarshaller and InvocationResponse objects
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 that anything with a content-type starting with "text/" should be read as a string by HTTPUnMarshaller. That means that an org.jboss.remoting.ServerInvocationHandler should set the content-type to something starting "text/" only if it returns a response of Java type String. Does that sound reasonable to you? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242732#4242732 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242732 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Remoting release 2.2.3 is available
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 Server 4.2. See https://jira.jboss.org/jira/browse/JBMESSAGING-1456 "Messages stuck in being-delivered state in cluster" and https://jira.jboss.org/jira/browse/JBREM-1128 "Introduce connection identity concept" for more information. To see the release notes, go to https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313088&styleName=Text&projectId=10031&Create=Create . Version 2.2.3 of jboss-remoting.jar may be found in the old repository at http://repository.jboss.com/jboss/remoting/. The distribution zip file may be found at http://www.jboss.org/jbossremoting/downloads/ . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232617#4232617 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232617 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: remoting with .NET
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=bb&op=viewforum&f=200. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226303#4226303 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226303 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Looking for a basic tutorial on how to get JBoss Remotin
See my response on the other thread, "JBoss remoting - Compatability with non JBoss J2EE Applicati", at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153078. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226302#4226302 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226302 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: JBoss remoting - Compatability with non JBoss J2EE Appli
"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 about glassfish (except that it's well known to be inherently evil :) ). 1. Remoting could function as an essentially standalone subsystem, where you configure it with your own invocation handler, which is your application code. In JBoss AS, there are configuration files which you can add, or edit, to tell the AS to start up your Remoting app. Since the handler is running in the application server, it can get access to other objects and services running at the same time. 2. In JBoss AS, Remoting is built into the internal fabric of the server. For example, EJB3 invocations are, by default, transported by Remoting. The EJB3 system is built and configured to, for example, create a proxy for an EJB3 that makes Remoting invocations to a Remoting server which is configured with an EJB3 specific invocation handler. Now, the JBoss AS is flexible enough that you could change all of that, but generally, you don't want to do more than maybe make some adjustments on the periphery. The details are independent of your EJB3 application. Since I'm not sure I understand your question, I'm not sure that I've come close to answering it, but I hope that helps. If not, try again. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226301#4226301 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226301 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: org.jboss.remoting.marshal.InvalidMarshallingResource: C
"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 org/jboss/remoting, unpack jboss-remoting.jar in the same directory, and then pack it up again. "peter_pinnau" wrote : | When will a JBoss 4.2.4 be released which fixes that issue? | I assume you're talking about the community Application Server and not the Enterprise Application Platform (EAP). EAP 4.2/4.3 (based on AS 4.2) will be around for some time, since it's intended to provide long term stability, but I doubt (without knowing for sure) whether there will ever be a 4.2.4 AS. All the energy is going into 5.x these days. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226122#4226122 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226122 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Race condition in ConnectionValidator
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 scenario, with the exception that I'm not sure I understand the timing of the stopping and restarting of the server. I'm assuming that the sequence is: 1. ConnectionValidator pings successfully 2. Server goes down 3. Server comes back 4. ConnectionValidator pings successfully and then JBossMessaging fails. The ConnectionValidator was intended to detect that a connection exists to a server at a certain InvokerLocator. It doesn't detect that the server that it pinged last time is the same as the one it pings this time. So it's getting a "happy ping" at step 4. But JBossMessaging isn't happy because the new server doesn't have the same state as the old server. I think the solution is to turn the happy ping into an unhappy ping. For example, the server could return its unique identity and the ConnectionValidator could compare to the previous result. If, in fact, I'm interpreting your scenario correctly, then I'll create a JIRA issue for it. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226093#4226093 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226093 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: make ejb3 client use ServerAuthMode=false on sslsocket t
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) ctx.lookup("HelloWorldBean/remote");
|
you're bringing over a proxy object which knows about port 3873.
2. "deckrider" wrote : I've read how one can use SSLSocketFactory to somehow
configure the client to use SSLSocketBuilder.REMOTING_SERVER_AUTH_MODE=false
... . How would I change my stand alone test client to make this work?"
I'd like to be able to say: just add "org.jboss.remoting.serverAuthMode=false"
to the EJB3 InvokerLocator. That is:
|
sslsocket://${jboss.bind.address}:3873/?org.jboss.remoting.serverAuthMode=false
|
but, unfortunately, that doesn't work right now. I've created JBREM-1121
"Client SocketFactory should be configurable by InvokerLocator" to fix that.
For now, there is one parameter that you could add to the InvokerLocator which
will get used by the client: "socketFactoryClassName". That is, you could
write your own SocketFactory and insure that it doesn't authenticate the
server. The easiest way to do that, I think, is to write a MySocketFactory
class that (1) uses SSLSocketBuilder to create an appropriate
NoServerAuthenticateSocketFactory, and (2) just wraps the
NoServerAuthenticateSocketFactory. That is, calls to
MySocketFactory.createSocket() return the result of
NoServerAuthenticateSocketFactory.createSocket(). Then modify the
InvokerLocator:
|
sslsocket://${jboss.bind.address}:3873/?socketFactoryClassName=org.deckrider.MySocketFactory
|
For more information about SSLSocketBuilder, see Section "5.7.6
SSLSocketBuilder" of the Remoting Guide at
http://www.jboss.org/jbossremoting/docs/guide/2.2/html/index.html .
It's a pain, but it should work. Hope that helps.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226080#4226080
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226080
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
"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 original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225797#4225797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225797 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Review of JBossRemoting + JBossSerialization: Nice. Very nic
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 -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225795#4225795 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225795 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Remoting release 2.5.1 is available
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 https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12312978&styleName=Text&projectId=10031&Create=Create . Version 2.5.1 of jboss-remoting.jar may be found * in the old repository at http://repository.jboss.com/jboss/remoting/ , and * in the maven2 repository at https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/remoting/jboss-remoting/ or http://anonsvn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/remoting/jboss-remoting The distribution zip file may be found at http://www.jboss.org/jbossremoting/downloads/ . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225792#4225792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225792 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Looking for a basic tutorial on how to get JBoss Remotin
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 JBoss Remoting" at http://www.onjava.com/pub/a/onjava/2005/02/23/remoting.html. It's somewhat old, so you should check the details against a current version of the Remoting Guide (e.g., http://www.jboss.org/jbossremoting/docs/guide/2.5/html/index.html). For example, "xmbean-dd" in the MBean declaration is archaic. For a current example of a Remoting server configuration, see the MBean called "jboss.remoting:service=Connector,transport=socket" in $JBOSS42_HOME/server/default/conf/jboss-service.xml. If your question is the latter, well, then, everything that works in AS 4.2 should continue to work in AS 5. In particular, MBean declarations will still be recognized. However, AS 5 also supports the configuration of ordinary POJOs, and Remoting 2.4/2.5 has updated its server side configuration to use declarations of org.jboss.remoting.ServerConfiguration instances. See, for example, $JBOSS5_HOME/server/default/deploy/remoting-jboss-beans.xml. I hope that helps. And, of course, we'd be happy if you want to contribute a tutorial. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222885#4222885 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222885 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: RMI from JBoss 4.3 to JBoss 4.2
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=bb&op=viewforum&f=50). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222878#4222878 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222878 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: LeasePinger error after Timer thread death + fix (happen
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=bb&op=viewtopic&p=4222874#4222874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222874 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Bridge error because of network problems also influences
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. Howard, why do you think there's a problem with LocalClientInvoker? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219631#4219631 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219631 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: forceRemote timeout Problems
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 org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:853) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1640) | shows Client.invoke() calling LocalClientInvoker.invoke(), which calls ServerInvoker.invoke(). If the server were in a different JVM, you would see Client.invoke() calling BisocketClientInvoker.invoke(), followed by a sequence of calls ending with a socket write. By setting the "force_remote" parameter to true, you are telling Remoting to avoid the network bypass and call BisocketClientInvoker. That's OK, but when you add | true | to the MBean configuration, you're setting "force_remote" on the server but not the client. You want to add 'isParam="true"': | true | which adds "force_remote=true" to the InvokerLocator. The client then gets the "force_remote" parameter from the InvokerLocator. I think that should solve your timeout problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219627#4219627 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219627 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Socket Timeout?
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: | | | | | | ... | | 6 | ... | | ... | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219356#4219356 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219356 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Remoting] - Re: Messaging blocked by long time-out
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 about the broken connection, and
it should attempt to shut it down. Now, Remoting won't try to kill a Socket in
the middle of a read() or write(), but I'm a little surprised that
JBossMessaging doesn't clean things up enough to prevent all the other clients
from receiving messages.
Are you seeing the output from
| log.trace("Notified connection listener of lease expired due to lost
connection from client (client session id = " + clientHolder.getSessionId());
|
on your server logs?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219349#4219349
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219349
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Messaging blocked by long time-out
There is further discussion about this issue on the thread "Messaging blocked by long time-out" on the Remoting forum at http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219345#4219345 . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219348#4219348 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219348 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Timeout for Disconnected JBM Client
"rtm333" wrote :
| Any chance that this problem of very long timeouts in spite of being
configured as much shorter is related to (and hopefully solved with) JIRA
JBMESSAGING-1482 ("Client remoting configuration not properly passed to jboss
remoting")?
|
JBMESSAGING-1482 is specific to configuring
org.jboss.remoting.ConnectionValidator, which runs on the client to detect
connection failures.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219347#4219347
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219347
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
