8:45 a.m.
Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/754550#754550
--------------------------------------------------------------
I recommend to use the jboss-ejb-client.properties (and not the remoting-project URL
remote://... which is deprecated)
Have a look to
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+...
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+...
Does this work?
The reason is that AS7 is a new implementation andtherefor the ejb-client works different,
specially in case of multithreading. There is a JIRA with enhancements
https://issues.jboss.org/browse/EJBCLIENT-34 EJBCLIENT-34 for this, but it is not finished
right now.
Also I'll reproduce your issue and see how to achieve this.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754550#754550]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:56 a.m.
Oliver Katzer [https://community.jboss.org/people/olli24] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/754576#754576
--------------------------------------------------------------
Thanks for fast answer.
I can confirm that the multithreading case works, if the EJB Client properties are set via
file jboss-ejb-client.properties, instead of setting them as InitContext properties.
My only InitContext property is now:
properties = new Properties();
properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
return new InitialContext(properties);
The other properties are now defined in the file jboss-ejb-client.properties:
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=oliver2
remote.connection.default.port=9000
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754576#754576]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:17 a.m.
Bijoy James [https://community.jboss.org/people/bijoyjp] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/754675#754675
--------------------------------------------------------------
Hi,
where i need to place "jboss-ejb-client.properties" file in Jboss 7.1.1 Final
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754675#754675]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:31 a.m.
Oliver Katzer [https://community.jboss.org/people/olli24] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/754685#754685
--------------------------------------------------------------
You have 3 options:
1) Place the "jboss-ejb-client.properties" file in the classpath of the
application
2) Set the path to file via System Property as JRE command line parameter
-Djboss.ejb.client.properties.file.path=C:\jboss-ejb-client.properties
3) Set the path to file via System Property during runtime
System.setProperty("jboss.ejb.client.properties.file.path",
"C:\\jboss-ejb-client.properties");
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754685#754685]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:56 a.m.
Oliver Katzer [https://community.jboss.org/people/olli24] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755388#755388
--------------------------------------------------------------
Hi Wolf-Dieter
During testing I faced something really strange.
If my multithreading remote client runs under JRE 1.6.0_27 everything is fine, as I
confirmed.
But if I let run the same remote client under other JRE versions like 1.6.0_21 or
1.6.0_34, after some remote method invocations I get again the IllegalStateException: No
EJBReceiver available for node name oliver2
This is the StackTrace:
java.lang.IllegalStateException: No EJBReceiver available for node name oliver2
at
org.jboss.ejb.client.EJBClientContext.requireNodeEJBReceiver(EJBClientContext.java:613)
at
org.jboss.ejb.client.EJBClientContext.requireNodeEJBReceiverContext(EJBClientContext.java:648)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:71)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
That means I still have a problem.
What does it really mean that “No EJBReceiver” is available?
What can I do to make an “EJBReceiver” available?
Can I increase something in the JBoss EBJClient?
And really strange is the different between the JRE versions on client side.
My JBoss runs under JDK 1.6.0_27 or JDK 1.6.0_34, but this make no different.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755388#755388]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
7:31 a.m.
Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755405#755405
--------------------------------------------------------------
What does it really mean that “No EJBReceiver” is available?
The client context will be initialized by the jboss-ejb-client.properties and/or the
InitialContext. In fact for both there is a list of available server-connections.
If you do a lookup(...) the client create a Proxy based on the Remote interface (notice
there is no server access as this was in previous versions!)
If you use the proxy and execute a method the list of servers are hunted whether it can
handle the request (EJB identificator is [ejb:]app/modul/bean!view)
All possibilities are given to a selector class (default is Random....) to choice one of
the posibilities.
If there are none you get such Exception
reasons:
* no EJB with that name deployed
* no server available (for this ejb)
* connection closed by error (should be reopend if possible)
If you run the same code in different JVM versions, your behaviour looks like a JVM bug
(nio), What if you use the last Java7 (I would prefer that for AS7)
Could you reproduce it with a upstream compilation (As7.2.X or 7.1.3)?
You might set logging org.jboss.ejb.client=TRACE to see more informations
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755405#755405]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:47 a.m.
Oliver Katzer [https://community.jboss.org/people/olli24] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755512#755512
--------------------------------------------------------------
If I use on client side a JRE which causes the problem I see in the JBoss log file
"JBAS011806: Channel end notification received"
JBoss log
2012-08-23 15:48:17,068 TRACE [org.jboss.remoting.remote] Closed inbound channel on
Connection handler for Remoting connection 0133bcc2 to /10.1.2.81:52129
2012-08-23 15:48:17,069 TRACE [org.jboss.remoting.resource] Completed close of Channel ID
7fb4e1bd (inbound) of Remoting connection 0133bcc2 to /10.1.2.81:52129
*2012-08-23 15:48:17,069 INFO [org.jboss.as.naming] JBAS011806: Channel end notification
received, closing channel Channel ID 7fb4e1bd (inbound) of Remoting connection 0133bcc2 to
/10.1.2.81:52129*
2012-08-23 15:48:17,069 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] Channel
Channel ID 7fb4e1bd (inbound) of Remoting connection 0133bcc2 to /10.1.2.81:52129 closed.
2012-08-23 15:48:17,070 TRACE [org.jboss.remoting.resource] Closing Channel ID 7fb4e1bd
(inbound) of Remoting connection 0133bcc2 to /10.1.2.81:52129 synchronously
2012-08-23 15:48:17,070 TRACE [org.xnio.nio.selector] Beginning select on
sun.nio.ch.WindowsSelectorImpl@10bc3c9
2012-08-23 15:48:17,071 TRACE [org.xnio.nio.selector] Selected on
sun.nio.ch.WindowsSelectorImpl@10bc3c9
2012-08-23 15:48:17,072 TRACE [org.xnio.nio.selector] Selected key
sun.nio.ch.SelectionKeyImpl@192722c for java.nio.channels.SocketChannel[connected oshut
local=oliver2/10.1.2.81:9000 remote=/10.1.2.81:52129]
2012-08-23 15:48:17,072 TRACE [org.xnio.listener] Invoking listener Read listener for
org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <145502b> on
channel TCP socket channel (NIO) <145502b>
2012-08-23 15:48:17,073 TRACE [org.xnio.listener] Invoking listener
org.jboss.remoting3.remote.RemoteReadListener@168ef25 on channel
org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <145502b>
2012-08-23 15:48:17,074 TRACE [org.xnio.channels.framed] Copying message from
java.nio.HeapByteBuffer[pos=4 lim=5 cap=8196] into java.nio.HeapByteBuffer[pos=0 lim=8192
cap=8192]
2012-08-23 15:48:17,074 TRACE [org.jboss.remoting.remote] Received connection close
request
For "JBAS011806: Channel end notification received" I found this:
https://issues.jboss.org/browse/AS7-1338 https://issues.jboss.org/browse/AS7-1338
But if I use on client side the newest JRE 1.7.0_06, JBoss prompts no "Channel end
notification received".
Everything is working fine.
It seems its bug inside the JRE, in the NIO part as you mentioned.
In the fixed bug list of JRE 1.7.0_06 are some bugs for NIO listed.
http://www.oracle.com/technetwork/java/javase/2col/7u6-bugfixes-1733378.html
http://www.oracle.com/technetwork/java/javase/2col/7u6-bugfixes-1733378.html
Conclusion:
I will use now on client side at least JRE 1.7.0_06 and I am happy.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755512#755512]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:30 a.m.
Oliver Katzer [https://community.jboss.org/people/olli24] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755656#755656
--------------------------------------------------------------
Even it’s working, I can see on client side following warning.
org.jboss.ejb.client.remoting.ChannelAssociation - Unsupported message received with
header 0xffffffff
What does this mean, can I ignore this?
In many AS7 samples in the internet I can see this warning, but I didn’t find a clarifying
about this warning.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755656#755656]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:46 a.m.
Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755666#755666
--------------------------------------------------------------
You can ignore this WARN, this is a internal info and in further releases this will be a
DEBUG/TRACE message.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755666#755666]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:59 a.m.
Bijoy James [https://community.jboss.org/people/bijoyjp] created the discussion
"Re: EJB bean is not working in Multi threading of JBoss 7.1.1 Final"
To view the discussion, visit: https://community.jboss.org/message/755726#755726
--------------------------------------------------------------
I think now my problem solved and its working fine.
I used below code
objProperties = new Properties();
objProperties.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
objProperties.put(Context.PROVIDER_URL, "remote://" + Url);
objProperties.put("jboss.naming.client.ejb.context", true);
objProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
jndiContext = new InitialContext(objProperties);
obj = jndiContext.lookup("JMSRa/JMSRA!Home.JMSRAHome");
/*
* jar name is JMSRa
*/
home = (JMSRAHome) PortableRemoteObject.narrow(obj, JMSRAHome.class);
objRemote = home.create();
jndiContext.close();
If am not using jndiContext.close(); means my application is not working, I don’t kno
what’s the reason
And "jboss-ejb-client.properties" in the client application class path also.
In the “jboss-ejb-client.properties” file I used below properties
remote.connections=default
remote.connection.default.host=localhost
remote.connection.default.port=4447
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
Thanks for https://community.jboss.org/people/wdfink Wolf-Dieter Fink and
https://community.jboss.org/people/olli24 Oliver Katzer for your valuable helps
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755726#755726]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4885
days inactive
4889
days old
jboss-dev-forums@lists.jboss.org
9 comments
3 participants
participants (3)
-
Bijoy James -
Oliver Katzer
-
Wolf-Dieter Fink