anonymous wrote : One thing that worries me with Synchronization is that Synch
is on whole bean and not the methods :).
|
| Now I need to have more than one Stateful session bean.
|
I'm sorry, but I'm failing to understand what your concern is.
Are you saying that you have to split the l
The wiki indicates that it is one of the "system properties that a JMS client
using the UIL2 transport can set".
So you should be able to define it on the JMS client side as below:
java -Dorg.jboss.mq.il.uil2.serverAddr=...
View the original post :
http://www.jboss.com/index.html?module=bb&op
Can you switch to stateful session bean? If yes, you can try the following:
1. Have the stateful sesion bean class implements
javax.ejb.SessionSynchronization interface.
2. Make the database operation transactional, so that in the case of JTA
rollback the data is not updated in the DB.
2. With
I'm not from JBoss/RedHad, but my guess is YES, you need the client jars from
JBoss to access JBoss JNDI tree from a standalone Tomcat.
The reason is, although the JNDI application programming interface is publicly
defined by J2EE spec, the underlying communication protocol (between the JNDI
se
Sorry if my previous post was not clear enough.
I suggested to change the code as follows:
| public void connect()
| {
| try
| {
|
| System.out.println("Now looking up session bean " + jndiName + " ...");
| java.util.Hashtable properties = new java.util.Hashtable();
| properties
AFAIK, a jboss client connects to (jboss server's) port 3873 when it does EJB3
remote method invocation under JBoss 4.2.x default configuration.
Are you sure your client is not calling your session bean at all?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4
InitialContext jndiContext = new InitialContext();
| System.out.println("Now looking up session bean " + jndiName + " ...");
| java.util.Hashtable properties = new java.util.Hashtable();
| properties.put(Context.PROVIDER_URL,"localhost:1099");
|
properties.put(Context.INITIAL_CONTEXT_FACTO
anonymous wrote : The ejb3 connector component of JBoss seems to have a bug of
ignoring the '-b 0.0.0.0' option. Instead of '0.0.0.0', it tries to choose one
(maybe the primary one?) from the IP addresses bound to the machine's network
interfaces. And if it cannot find any valid IP address, it u
anonymous wrote : Can one tell me where i can define new connection factory in
JBOSS 4.2.2 GA and how.
This depends on where your client code runs. If it runs in the same JVM as the
JBoss server, you need to modiy
deploy/jms/jvm-il-service.xml
Otherwise (when your client runs remotely from th
Which OS do you use?
The ejb3 connector component of JBoss seems to have a bug of ignoring the '-b
0.0.0.0' option. Instead of '0.0.0.0', it tries to choose one (maybe the
primary one?) from the IP addresses bound to the machine's network interfaces.
And if it cannot find any valid IP address,
anonymous wrote : Is there any way to bind to all interfaces in 4.2 and
persuade it to return an IP address instead of a hostname in the Naming object?
The easiest way to do this is to use system property 'java.rmi.server.hostname'.
For example, on windows:
SET JAVA_OPTS=-Djava.rmi.server.host
You're probably using '-b hostname' option (or the equivalent long version
'--host=hostname' option) when you start JBoss run.sh/run.bat.
If that is the case, replace the hostname portion with the IP address.
Alternatively, removing the -b (or --host) option will have the same effect,
but if y
With (1), access to JNDI service is done by socket/JRMP based protocol of JBoss.
With (2), it is done by HTTP.
More on this:
http://docs.jboss.org/jbossas/guides/j2eeguide/r2/en/html/ch3.chapter.html#ch3.factories
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
You can do this by using a service archive (a jar that ends with '.sar' suffix).
The contents of the .sar typically would be:
your.war
META-INF/jboss-service.xml
Within the jboss-service.xml, you can define the destination mbean for your
topic (just as in your jbossmq-destinations-service.xml).
If what you want to accomplish is to make sure that your queues/topics are
created everytime your jboss server is rebooted, you can just use the
destination mbeans.
It is described in "Destination MBeans" section in the JBoss administration
guide, and you should be able to find some examples i
OK, then the other things that may be worth checking are:
On the server side,
1) deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml
Do you have JNDIFactorySSL servlet and servlet-mapping defined ?
2) deploy/http-invoker.sar/META-INF/jboss-service.xml
Do you have HTTPProxyFactory defined w
anonymous wrote : javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
| at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
| at javax.naming.InitialContext.lookup(InitialContext.java:355)
| at org.o
> 2) and jndi url as https://192.168.114.86:8080/invoker/JNDIFactorySSL
Did you try https://192.168.114.86:8443/invoker/JNDIFactorySSL ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135019#4135019
Reply to the post :
http://www.jboss.com/index.html?module=
18 matches
Mail list logo
