[JBoss-user] [Management, JMX/JBoss] - Re: problem adding notification listener from remote client
Ok. How do I export the NitificationClient as a RMI service, then ? If I skip the 'bind' action, then I get The NullPointerException back. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3865558#3865558 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865558 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Management, JMX/JBoss] - Re: problem adding notification listener from remote client
I didn't find any example of remote RMINotificationListener in adminDevel guide
(nor in wiki's or faq's). However I tried to register the listener as a rmi
service.
So I made my listener extend UnicastRemoteObject and I added this code:
| public TestMain() {
| try{
| /*if (System.getSecurityManager() == null) {
| System.setSecurityManager(new RMISecurityManager());
| }*/
| DistantNotificationClient dnc = new DistantNotificationClient();
| Naming.bind(//138.203.236.159:1098/DistantNotificationClient, dnc);
| String url = jnp:// + etbs159 + :1099;
| String ini = org.jnp.interfaces.NamingContextFactory;
| String pkgs = org.jboss.naming,org.jnp.interfaces;
| Hashtable env = new Hashtable();
| env.put(java.naming.provider.url, url);
| env.put(java.naming.factory.initial, ini);
| env.put(java.naming.factory.url.pkgs, pkgs);
| Context ic = new InitialContext(env);
| RMIAdaptor server = (RMIAdaptor) ic.lookup(jmx/rmi/RMIAdaptor);
| ObjectName emitterName = new
ObjectName(osp.smf.test:service=BroadcasterTest);
| server.addNotificationListener(emitterName, dnc, null, new
Long(System.currentTimeMillis()));
| }catch(Exception e){
| e.printStackTrace();
| }
|
| }
|
Now I get the following exception:
anonymous wrote :
| java.rmi.NoSuchObjectException: no such object in table
|
| at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
|
| at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
|
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:350)
|
| at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
|
| at java.rmi.Naming.bind(Naming.java:111)
|
| at com.alcatel.osp.mbean.test.TestMain.(TestMain.java:18)
|
| at com.alcatel.osp.mbean.test.TestMain.main(TestMain.java:80)
|
|
I couldn't find info on this exception that matches my problem. I ran my
application from the same machine as JBoss (running Solaris 9).
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3865172#3865172
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3865172
---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Management, JMX/JBoss] - problem adding notification listener from remote client
Hi all,
I've got a NullPointerException while using the addNotificationListener API in
RMIAdaptor with JBoss 3.2.6. I first tried the example code from the admin and
development guide and this works well, so I suppose the RMI adaptor is
correctly configured. The exception occurs while registering the listener, so I
don't even receive a first Notification object.
Here is my code
| public class DistantNotificationClient
| implements RMINotificationListener, Serializable {
|
| public DistantNotificationClient() {
| try{
| String url = jnp:// + etbs159 + :1099;
| String ini = org.jnp.interfaces.NamingContextFactory;
| String pkgs = org.jboss.naming,org.jnp.interfaces;
| Hashtable env = new Hashtable();
| env.put(java.naming.provider.url, url);
| env.put(java.naming.factory.initial, ini);
| env.put(java.naming.factory.url.pkgs, pkgs);
| Context ic = new InitialContext(env);
| RMIAdaptor server = (RMIAdaptor) ic.lookup(jmx/rmi/RMIAdaptor);
| ObjectName emitterName = new
ObjectName(osp.smf.test:service=BroadcasterTest);
| server.addNotificationListener(emitterName, this, null, new
Long(System.currentTimeMillis()));
| }catch(Exception e){
| e.printStackTrace();
| }
|
| }
|
| public void handleNotification(Notification event, Object handback){
| String type = event.getType();
| String message = event.getMessage();
| System.out.println(type = +type+ \t message = +message);
| }
| }
|
|
and here is the Exception
anonymous wrote :
| java.lang.NullPointerException
|
| at
org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:234)
|
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
|
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|
| at java.lang.reflect.Method.invoke(Method.java:324)
|
| at
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
|
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
|
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
|
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
|
| at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
|
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
|
| at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:360)
|
| at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
|
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|
| at java.lang.reflect.Method.invoke(Method.java:324)
|
| at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
|
| at sun.rmi.transport.Transport$1.run(Transport.java:148)
|
| at java.security.AccessController.doPrivileged(Native Method)
|
| at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
|
| at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
|
| at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
|
| at java.lang.Thread.run(Thread.java:534)
|
| at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
|
| at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
|
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
|
| at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
|
| at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:135)
|
| at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:96)
|
| at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:58)
|
| at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
|
| at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:55)
|
| at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
|
| at $Proxy0.addNotificationListener(Unknown Source)
|
| at
com.alcatel.osp.mbean.test.DistantNotificationClient.(DistantNotificationClient.java:30)
|
| at
com.alcatel.osp.mbean.test.DistantNotificationClient.main(DistantNotificationClient.java:87)
|
|
Does anybody have an idea of what went wrong ?
I certainly missed something or did something wrong but I can't find the
problem.
Thanks for your help !
Maxime
View the original post :
[JBoss-user] [JBoss.NET] - Re: Axis EJB provider not registered with JBoss 3.2.6
Tell me if I'm wrong, but there are some features I need that are missing in WS4J: - web service session: we have a complex and costly login phase to determine the user profile. This phase is much more complex than what the J2EE security mechanisms offer. This is done by an Axis handler that calls an external native process. This profile (along with other user related info) must be stored in a session to avoid computing it again and again. - stateful EJB endpoint: the clients must be able to rollback some actions in some case. So we provide transactional support. This can only be achieved by using stateful EJB's, I think. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3855311#3855311 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855311 --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss.NET] - Re: Axis EJB provider not registered with JBoss 3.2.6
Thank you. I replaced the old handler !--service name=WSTest type= regenerateElement=true | provider=java:EJB style=rpc use=encoded | ... by service name=WSTest type= regenerateElement=true | provider=Handler style=rpc use=encoded | parameter name=handlerClass value=org.jboss.net.axis.server.EJBProvider/ | ... | and it works much better. I just want to say that the code using the java:EJB provider was generated by JBuilder. It seems JBuilder uses the standard Axis handler even when we are stating JBoss as application server. So the modification must be made manually for every web service meant to run into JBoss. I assume this should be automatic so I'll report this issue to Borland shortly. Thanks for your comment. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3855153#3855153 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855153 --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss.NET] - Axis EJB provider not registered with JBoss 3.2.6
Hi,
I try to call an EJB from a client using axis web services. So I defined java:EJB as
the Axis provider. All this work fine with JBoss 3.2.3. But I decided to switch to
3.2.6 and I have this kind of errors:
No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}EJB'
So I had a look at the definition of providers. This is what we have in 3.2.3:
static {
| providers.put(WSDDConstants.QNAME_JAVARPC_PROVIDER, new
WSDDJavaRPCProvider());
| providers.put(WSDDConstants.QNAME_JAVAMSG_PROVIDER, new
WSDDJavaMsgProvider());
| providers.put(WSDDConstants.QNAME_HANDLER_PROVIDER, new
WSDDHandlerProvider());
| providers.put(WSDDConstants.QNAME_EJB_PROVIDER, new WSDDJavaEJBProvider());
| providers.put(WSDDConstants.QNAME_COM_PROVIDER, new WSDDComProvider());
| providers.put(WSDDConstants.QNAME_BSF_PROVIDER, new WSDDBsfProvider());
| providers.put(WSDDConstants.QNAME_CORBA_PROVIDER, new
WSDDJavaCORBAProvider());
| providers.put(WSDDConstants.QNAME_RMI_PROVIDER, new WSDDJavaRMIProvider());
| try {
| loadPluggableProviders();
| } catch (Throwable t){
| String msg=t + JavaUtils.LS + JavaUtils.stackToString(t);
| log.info(Messages.getMessage(exception01,msg));
| }
| }
|
and this is what we have in 3.2.6:
static
|{
| providers.put(WSDDConstants.QNAME_JAVARPC_PROVIDER, new
WSDDJavaRPCProvider());
| providers.put(WSDDConstants.QNAME_JAVAMSG_PROVIDER, new
WSDDJavaMsgProvider());
| providers.put(WSDDConstants.QNAME_HANDLER_PROVIDER, new
WSDDHandlerProvider());
| providers.put(WSDDConstants.QNAME_COM_PROVIDER, new WSDDComProvider());
| try
| {
| loadPluggableProviders();
| }
| catch (Throwable t)
| {
| String msg = t + JavaUtils.LS + JavaUtils.stackToString(t);
| log.info(Messages.getMessage(exception01, msg));
| }
|}
|
The EJBProvider is not loaded, and I think this is why I can't call EJB's from web
services anymore. Is this a normal situation, or did I miss something ? Do we have to
call EJB's differently now ?
Thanks for your help.
Maxime
PS: for testing purposes, I created a simple web service with 1 dummy method in a
session EJB using JBuilder X with JBoss 3.2.x configuration, but I get the same
behaviour.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3853748#3853748
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3853748
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
