I'm sorry, i haven't explained correctly.
Actually, it's indeed already done when the proxy brings the InvokerLocator
from the server and the parameter is set at the server side.
But, we want to set or modify this parameter 'timeout' at the client side at
every call or give a specific value
Hi,
Is it possible to set the parameter 'timeout' for a EJB call
at the client side.
Actually this parameter is set at the server side with the url parameter
(socket://${jboss.bind.address}:3873/?clientMaxPoolSize=2invokerDestructionDelay=2880timeout=3000)
We are using JBoss AS 5.0.1.GA.
I found the problem.
With JBAS 5.0.0.GA, in an ejb service, the resource is already injected in the
'create' method
against by JBAS 5.1.0.GA.
And we refer to the injected resource in this method.
We 've moved the code from the 'create' method to the 'start' method and now
it's ok.
View the
Hello,
We 're using JBAS 5.0.0.GA, and we inject a JMS administrative resource
(ConnectionFactory) in an ejb session and an ejb service. This works fine.
When we're upgrading to JBAS 5.1.0.GA, only the injection to an ejb session
woks and for the ejb service we have a reference to the null
Thank you !
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4236397#4236397
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4236397
___
jboss-user mailing list
Hello,
We use EJB 3 interceptors at the server side and we want use the target bean
by calling the method 'getTargetObject' of the 'Invocation' object.
Unfortunately, this method return always null at every invocation.
Is it normal ?
Thanks in advance.
JBoss AOP 2.0.0.SP1
JBoss AS 5.0.0.GA
Hello,
We use EJB 3 interceptors at the server side and we want use the target bean
by calling the method 'getTargetObject' of the 'Invocation' object.
Unfortunately, this method return always null at every invocation.
Is it normal ?
Thanks in advance.
JBoss AOP 2.0.0.SP1
JBoss AS 5.0.0.GA
Hi Jay,
My last option is to do runtime weaving and use an aroundinvoke around
handleConnectionException in the SimpleConnectionManager
We are very interested by this feature.
If you have a solution, can you tell us how to do this.
Thanks in advance.
Slimane.
JBM 1.4.1.GA
JBAS 5.0.0.GA
Can I manipulate JMS objects with the connector 'InVM' like :
javax.jms.Topic, javax.jms.TopicPublisher, javax.jms.TopicSession
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217837#4217837
Reply to the post :
I want, for example, create a 'javax.jms.TopicPublisher' instead
'org.jboss.messaging.core.client.ClientProducer' and use it to send (publish)
messages in the VM.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217892#4217892
Reply to the post :
I've got the file SimpleExample.java and the jboss-messaging-2.0.0.alpha1 jars
but apparently these jars are not enough.
How can i get the jars corresponding to the trunk ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217449#4217449
Reply to the post :
Thank you !
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217465#4217465
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217465
___
jboss-user mailing list
Ok, it works fine !
Just a little error in the previous post :
It's not
| org.jboss.messaging.core.remoting.impl.invm.InVMAcceptor
|
but
| org.jboss.messaging.core.remoting.impl.invm.InVMAcceptorFactory
|
Thank you !
View the original post :
You will be able to run JBM2 embedded in your clientVM also. You just need to
instantiate a couple of POJOs. There are examples for both scenarios already
on trunk, and that will be part of the documentation
Can you give me more informations to do this (i haven't found the examples on
trunk)
Hello,
Is it possible to make JMS communications between 2 clients in the same JVM at
the client side that is outside the JBoss server.
We need to do this for validation considerations.
Thanks in advance.
View the original post :
All types that is publish, send, read .. a message.
In fact, my question is : inside a JVM, is it possible to make JMS
communications without starting the JBoss server.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4215739#4215739
Reply to the post :
So can i have it this way: you want start a JBM server without starting jboss
AS, right?
Yes
Then you can try JBM 2.0. 1.4 doesn't support it.
How can i use JBM 2.0 whithout jboss AS ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4215752#4215752
Reply to
Hello,
We have an (service) ejb which publish jms message to 3 topics.
On one topic, it publishes periodically (every 10 seconds) and with this topic
we have sometimes an error which occurs (see logs below) at server side
and after the jms clients don't receive any message from this topic.
We
Hello,
We have an (service) ejb which publish jms message to 3 topics.
On one topic, it publishes periodically (every 10 seconds) and with this topic
we have sometimes an error which occurs (see logs below) at server side
and after the jms clients don't receive any message from this topic.
We
We have a session per topic and we publish with the same connection.
What 's wrong.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210982#4210982
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4210982
Thanks,
I'm going to increase the value of the 'connectionWait' parameter.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210986#4210986
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4210986
A topic has also created from the messaging forum :
http://www.jboss.org/index.html?module=bbop=viewtopict=150732
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210991#4210991
Reply to the post :
Ok, it work's fine.
I'm going to see the details about this new configuration.
Thanks once again.
anonymous wrote :
| That sounds like something that should be fixed. Where did you see it?
|
Yes, i understand the two behaviors.
Sorry, i think my question is not cleary and needs some precisions.
With JBossAS 5.0.0Beta4, we have set the value of the parameter 'timeout' ,
for the server side, in the file
'JBOSS_HOME/server/your_configuration/deploy/ejb3-connectors-service.xml'.
And
Using JBoss Remoting 2.4.0 with JBossAS 5.0.0Beta4, the parameter
'invokerDestructionDelay' is taken into account and the socket connection is
reused for all client requests.
But with JBossAS 5.0.0GA and JBoss Remoting 2.5.0SP2 embedded, the socket
connection is closed, apparently by the
Using JBoss Remoting 2.4.0 with JBossAS 5.0.0Beta4, the parameter
'invokerDestructionDelay' is taken into account and the socket connection is
reused for all client requests.
But with JBossAS 5.0.0GA and JBoss Remoting 2.5.0SP2 embedded, the socket
connection is closed, apparently by the
Sorry,
It's the 'socket' transport , see :
http://www.jboss.com/index.html?module=bbop=viewtopict=134089
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198559#4198559
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4198559
A JIRA has been created :
https://jira.jboss.org/jira/browse/EJBTHREE-1650
It's not a feature request but a bug because with this restriction in
JBoss5.0.0GA
it's impossible to have multiple remoting binds for an EJB.
View the original post :
Hello,
I have the same problem with :
@RemoteBinding(clientBindUrl = socket://0.0.0.0:3873)
It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property jboss.bind.address is set and the hostname '0.0.0.0' is not
replaced.
Is a bug ?
View the original post :
Hello,
I have a problem with :
@RemoteBinding(clientBindUrl = socket://0.0.0.0:3873)
It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property jboss.bind.address is set and the hostname '0.0.0.0' is not
replaced
from the client.
For more information see :
Hello,
I have a problem with :
@RemoteBinding(clientBindUrl = socket://0.0.0.0:3873)
It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property jboss.bind.address is set and the hostname '0.0.0.0' is not
replaced
from the client.
For more information see :
A working Beta4 EJB3 application is broken with CR1.
@Stateful
@Remote(MyInterface.class)
@SecurityDomain(myconfig)
public class MyClassEJB3 implements MyInterface
{
}
A RuntimeException appears when 'MyClassEJB3' is loaded.
anonymous wrote :
| org.jboss.deployers.spi.DeploymentException:
Hello,
The problem has been resolved.
We have generated the JBossAS-5.0.0.CR1 from sources and an XML configuration
file has been generated with some wrong characters (???) at the beginning of
the file.
View the original post :
The two solutions work fine.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4175834#4175834
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4175834
___
jboss-user mailing
Sorry,
I've already created one : https://jira.jboss.org/jira/browse/SECURITY-273
I'm going to make a link to the EJBTHREE-1485
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4175876#4175876
Reply to the post :
Hello,
I have no problem when i start JBossAS-5.0.0.CR1 with the default
configuration.
But, when i start the server with the 'all' configuration (run.sh -c all) i get
this error :
anonymous wrote :
| 13:49:16,425 ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in
prolog.
|
I think the problem comes from the client side.
We have developped an web application and deploy it with JBoss.
For this application, we use the Jakarta common-httpclient to have persistent
connection and this works fine.
I think the problem comes from the HTTPClientInvoker.
Is it possible to
With the servlet transport, there is no conflict with jbossweb port (8080)
because a servlet is used with the connector http.
With the socket transport, the connections remain open when using the
parameters 'invokerDestructionDelay' (client side) and 'timeout' (server side) .
With the servlet
Hi,
The 'timeout' parameter works fine with the socket transport as described in
your config but not with this config (http transport) :
|mbean code=org.jboss.remoting.transport.Connector
|
name=jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
|
As described in this topic :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4148258#4148258
using version 2.4.0 of Remoting and the parameter 'invokerDestructionDelay',
the same socket connection is reused for all client requests to the Server.
This works fine with the socket
As described in this topic :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4148258#4148258
using version 2.4.0 of Remoting and the parameter 'invokerDestructionDelay',
the same socket connection is reused for all client requests to the Server.
This works fine with the socket
As described in this topic :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4148258#4148258
using version 2.4.0 of Remoting and the parameter 'invokerDestructionDelay',
the same socket connection is reused for all client requests to the Server.
This works fine with the socket transport.
The problem has been resolved :
http://www.jboss.com/index.html?module=bbop=viewtopict=134089
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4147436#4147436
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4147436
The version of JBossRemoting which ships with JBoss AS 5.0.0.Beta4 is :
JBossRemoting Version 2.2.2.SP4 (Bluto)
I have downloaded JBossRemoting 2.4.0.CR2 then placed jboss-remoting.jar in
JBoss AS 5.0.0.Beta4 and it works fine.
When we set the parameter invokerDestructionDelay to a positive
When we shutdown the server, we 've got an error in the server.log file :
| 2008-04-29 14:49:39,376 DEBUG
[org.jboss.system.microcontainer.StartStopLifecycleAction] Error during stop
for jboss.aop:service=AspectManager
| java.lang.reflect.UndeclaredThrowableException
| at
We are using JBoss AS 5.0.0.Beta4 but i don't know the version of Remoting
which ships with it.
How can i get the version of Remoting in JBoss AS 5.0.0.Beta4 ?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4147132#4147132
Reply to the post :
The problem has been resolved :
http://www.jboss.com/index.html?module=bbop=viewtopict=134089
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4147230#4147230
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4147230
Sorry, i have had a problem with the message body post.
The correct message body is :
We want to use a ClientSocketFactory and after some reads (Remoting guide)
we have configured this in the file
$JBOSS_HOME/server/my-conf/deploy/ejb3-connectors-service.xml :
?xml version=1.0 encoding=UTF-8?
Hello,
We want to use a ClientSocketFactory and after some reads (Remoting guide)
we have configured this in the file
$JBOSS_HOME/server/my-conf/deploy/ejb3-connectors-service.xml :
?xml version=1.0 encoding=UTF-8?
!--
JBoss EJB3Deployer
$Id: jboss-service.xml 41488 2006-02-25
Sorry, always the problem with the message body post.
The final correct message body is :
We want to use a ClientSocketFactory and after some reads (Remoting guide)
we have configured this in the file
$JBOSS_HOME/server/my-conf/deploy/ejb3-connectors-service.xml :
?xml version=1.0
Hello,
We want to use a ClientSocketFactory and after some reads (Remoting guide)
we have configured this in the file
$JBOSS_HOME/server/my-conf/deploy/ejb3-connectors-service.xml :
?xml version=1.0 encoding=UTF-8?
| !--
|JBoss EJB3Deployer
|
|$Id: jboss-service.xml 41488
Hello,
We are using a Swing client standalone which invokes EJB methods.
After each call, the socket is released.
For security reasons, we have to maintain the connection (keep alive)
and not release it after each call.
Is it possible to do this.
View the original post :
Hello,
We are using a Swing client standalone which invokes EJB methods.
After each call, the socket is released.
For security reasons, we have to maintain the connection (keep alive)
and not release it after each call.
Is it possible to do this.
View the original post :
Hello,
We are using a Swing client standalone which invokes EJB methods.
After each call, the socket is released.
For security reasons, we have to maintain the connection (keep alive)
and not release it after each call.
Is it possible to do this.
Thanks in advance.
View the original post :
Hello,
I'm using the the login module in a swing client standalone to send the login
information into the JBoss server EJB.
Here is the client 'auth.conf' file :
other {
org.jboss.security.ClientLoginModule required
multi-threaded=false;
};
When i invoke an EJB method in the thread
I
Hello,
I'm using the login module 'ClientLoginModule' in a Swing client standalone to
send the login information into the JBoss server EJB.
Here is the client 'auth.conf' file :
other {
org.jboss.security.ClientLoginModule required
multi-threaded=false;
};
When i invoke an EJB method in the
56 matches
Mail list logo
