Hi Ron,
unfortunately I am not able to create a JIRA issue. Whenever I try I get this
strange error:
anonymous wrote : Errors
| Assign To: The default assignee does NOT have ASSIGNABLE permission OR
Unassigned issues are turned off.
|
May you please create the JIRA Request?
Thank you
Allright, I entered th new JIRA request. You can find it here:
[url]
http://jira.jboss.com/jira/browse/JBREM-752[/url]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4050917#4050917
Reply to the post :
Hi Ron,
I guess we' ve solved the problem. Actually your hint with reuseAddress was
the right way. In the Class SocketServerInvoker reuseAddress always is set to
true, but it is set after the socket is bound. A colleague of mine found the
reason for the Bind problem. He called my attention to
Hi Ron,
I've send you a sample by mail. Actually I don't know how I can set
reuseAddress from outside the Remoting Framework. But I have another idea: I do
use the inner Class ClientAuthSocketFactory from the
org.jboss.test.remoting.transport.socket.ssl.serversocketrefresh.TestServer
Class as
Hi there,
I have a problem with connections between my client and my server when using
sslsocket protocol. My server unexpectedly shuts down during refresh. I looked
at it for my self and this is what I found out:
It happens that somehow during a refresh in the SocketServerInvoker, the socket
Hi Ron,
I tested my source code with the changes you mentioned in this Topic:
http://www.jboss.com/index.html?module=bbop=viewtopict=85355postdays=0postorder=ascstart=10
And well... those changes solved this problem, too. So thank you.
Claudia
View the original post :
Hi Ron,
I found out, that sslsocket does not work on that example anymore after
exchanging the remoting version 2.2.0 with the CVS sources. When using version
2.2.0 again it works fine. Are you working on that? Or is this another issue?
View the original post :
Hi Ron,
I guess I'll have a look to the bisocket protocol. But first, there is still a
problem with my example. I wanted to exchange on the client side this method:
| public void setupConnection(int port, String host) throws Exception {
| log.info(setting up connection to JNDI
Hi Ron,
actually the source code I'm working at is not yet in production. It is still
in experimental stage. I found that issue by chance, when I wanted to run my
tests with different protocols. So I guess it will not happen very often that
the protocol changes on one port.
I'm pleased to
anonymous wrote :
| These changes are committed to the CVS repository and will be part of the
next release.
|
Sorry, I overlooked this line.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031944#4031944
Reply to the post :
Hi there,
I have a confusing problem with my client and server. The problem does not
occur always (so might be a timing issue) but sometimes my client receives an
InvalidStateException from the server. Actually it sometimes times out or just
stucks, when my server runs into this Exception. I
Hi. I saw that the JIRA issue http://jira.jboss.com/jira/browse/JBREM-654 has
been closed. Is the fix already in the CVS repository?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4029246#4029246
Reply to the post :
I wrote you an email with the source code attached.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025745#4025745
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025745
___
Well, duh, of course I am. ;-)
(And thanks for the hint with lower and upper case writing, as I am not a
native speaker, I live and learn)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024986#4024986
Reply to the post :
exactly. My Client is not able to access my Server after killing the Server and
restarting it with a new Protocol. I need to restart the Server a second time,
before my Client is able to connect to it. The funny thing is, that Detection
works perfectly even after the first restart.
Here's a
I'm sorry for the previous reply. I tested my Server with the wrong Client.
Could you please delete or (if not possible to delete) ignore this port? Thank
you
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024619#4024619
Reply to the post :
A change from multiplex protocol to socket causes a lot of logging messages but
does run.
The other way round it does not. When killing a server that runs socket
protocol and then restart it with multiplex protocol, it will not be detected
by a JNDI and my Client is not able to connect to it.
Thank you Ron. I exchanged the detection packages in may application with those
from the CVS repository and used the new Constructor. And voila it runs.
Thanks a lot.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024656#4024656
Reply to the post :
anonymous wrote :
| The detectors will periodically ping the servers they know about to see if
they are still alive. The ping is an actual invocation on the server, so, for
sslsocket, there will be an SSL handshake, for which the client will need a
truststore.
|
Well the problem is, that
Hi,
I wonder why this jira issue (http://jira.jboss.com/jira/browse/JBREM-534) has
been closed. Is it fixed already? I am using Remoting Versions 2.0.0 CR1 and
2.0.0 GA. And I have exactly the problem, that when killing a server and
restarting it afterwards with another protocol (I tried
Hello,
I have an issue with a Server, that is not registering correctly with an JNDI
Server (I have this issue with sslsocket as well as with sslmultiplex). In my
understandung a JNDI Server should not need to have a certificate all Servers
need to trust. I this right? And if so, can anybody
The new JIRA issue is http://jira.jboss.com/jira/browse/JBREM-654
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995262#3995262
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995262
great thing. So I will wait and hope, that this issue is solved soon ;-).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995266#3995266
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995266
Clarich
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994916#3994916
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994916
___
jboss-user mailing list
jboss-user@lists.jboss.org
Clarich wrote : (As you can see at
http://jira.jboss.com/jira/browse/JBREM-591)
Sorry, I did attach the wrong link. I meant this jira request:
http://jira.jboss.com/jira/browse/JBREM-646
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994918#3994918
Reply
Hello,
it seems as if the dynamic loading of a new keystore at runtime is not possible
when using Transporters (beaming POJOs). Is it possible to implement this in
the next Release? May I post this request in jira?
View the original post :
I don't know if this matches the previous mentioned issue or if this is an
issue for its own, but I have the problem that when running two Clients using
Transporters to connect to a target POJO on the server side and using SSL to do
this, always the second client is handled as beeing the first
I would like to know if it is possible to send Streams (e.g. as return Values)
when using POJOS. Especially I am interested in sending Streams from a Server
to a Client. When I try it out, I run into an UndeclaredThrowableException. Are
there any workarounds for it? If it is not possible to
28 matches
Mail list logo
