Hi Adrian,
        Thanks for the suggestion.:-)
        Please find attached the stack trace of the error that occurs at the RMI server. I am using log4j as the logger.
        In both the client and server(RMI/JBoss) the same jars are used in the class path.
        Since I am using jre1.3.1, I 'll check the bug you have specified.
        Please let me know if you have more info.

Thanks
Muraly

At 13:11 08/07/2003 +0100, you wrote:
Hi,

Are you sure you have the same definitions on the client/server,
have they changed recently?

Is there anymore of the stacktrace?
Since the exception is on the server, you might
try looking there.
If it is inside the RMI layer, you might need to look
at your JVM docs for how to enable logging.
It is not clear where your invocation is failing.

There are some limitations to the size of objects that
can be serialized. What do you mean by "huge" and
what types of objects. e.g. java 1.3 has a bug if
Strings are larger than 64K

The jboss and jdk version might help?

Regards,
Adrian

On Tue, 2003-07-08 at 12:14, Muraly R wrote:
> Hi Gurus,
>       Its me back again with porting issues(JOnAS to JBoss).
>
>       Currrently our application is used to Monitor the devices on a network.
> Each element on the network is identified as a Value Object.
>       Coming to issue I am facing, when a particular Device has to ba added to
> the DB, its passed to JBoss for the same.
>
>       When I try to add a device, I get the following error:
>
> java.rmi.ServerException: RemoteException occurred in server thread; nested
> exception is:
>       java.rmi.ServerException: RuntimeException; nested exception is:
>       java.lang.IllegalArgumentException: wrong number of arguments
> java.rmi.ServerException: RuntimeException; nested exception is:
>       java.lang.IllegalArgumentException: wrong number of arguments
> java.lang.IllegalArgumentException: wrong number of arguments
>
> This point of error occurs in my RMI server which makes a call to JBoss
> passing only the VO as argument. I have double checked the method signature
> and the no. of arguments are correct, since there is only one.
> Also one more info. is this happens only with some of the devices, i.e all
> other device addition is successfull.
> This scenario is working fine with JOnAS:-(.
>
> So now I am doubting the issue may be with the type of the VO, in the sense
> the contents of the VO.
>
> My doubt is:
> 1. Is there any size specification involved during marshalling, 'coz for
> the device which is failing the amount of data is huge when compared to
> device which successfully added.
> 2. Is there any way I can reduce the size of the VO passed?
>
> Please share your thoughts if you have faced such scenarios.
>
> Thanks
> Muraly
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
ERROR 08/Jul/2003 16:56:50 [Thread-4] (FullDiscoveryConfigurationElement.java:492): 
command.FullDiscoveryConfigurationElement - Exception in DiscoverFullCommand:

ERROR 08/Jul/2003 16:56:50 [Thread-4] (FullDiscoveryConfigurationElement.java:493): 
command.FullDiscoveryConfigurationElement - 

java.rmi.ServerException: RemoteException occurred in server thread; nested exception 
is: 
        java.rmi.ServerException: RuntimeException; nested exception is: 
        java.lang.IllegalArgumentException: wrong number of arguments
java.rmi.ServerException: RuntimeException; nested exception is: 
        java.lang.IllegalArgumentException: wrong number of arguments
java.lang.IllegalArgumentException: wrong number of arguments
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown 
Source)
        at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
        at sun.rmi.server.UnicastRef.invoke(Unknown Source)
        at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
        at 
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:140)
        at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:108)
        at 
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77)
        at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)
        at 
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:111)
        at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
        at $Proxy1.localExecute(Unknown Source)
        at 
com.cisco.nm.qpm.pdp.CLIEngine.jobManager.JobManager.remoteExecute(JobManager.java:639)
        at 
com.cisco.nm.qpm.share.command.FullDiscoveryConfigurationElement.sendResult(FullDiscoveryConfigurationElement.java:476)
        at 
com.cisco.nm.qpm.share.command.FullDiscoveryConfigurationElement.access$000(FullDiscoveryConfigurationElement.java:56)
        at 
com.cisco.nm.qpm.share.command.FullDiscoveryConfigurationElement$1.disconnectDone(FullDiscoveryConfigurationElement.java:108)
        at 
com.cisco.nm.qpm.pdp.CLIEngine.deviceConfigurationEngine.configurationManager.ConfigurationManager.disconnectDone(ConfigurationManager.java:1017)
        at 
com.cisco.nm.qpm.util.DeviceCommunicator.DeviceCommunicator.disconnect(DeviceCommunicator.java:473)
        at 
com.cisco.nm.qpm.pdp.CLIEngine.deviceConfigurationEngine.configurationManager.ConfigurationManager.disconnect(ConfigurationManager.java:925)
        at 
com.cisco.nm.qpm.pdp.CLIEngine.deviceConfigurationEngine.configurationManager.ConfigurationManager.disconnect(ConfigurationManager.java:910)
        at 
com.cisco.nm.qpm.share.command.FullDiscoveryConfigurationElement.doWork(FullDiscoveryConfigurationElement.java:378)
        at 
com.cisco.nm.qpm.share.command.AsyncJobCommand.execute(AsyncJobCommand.java:191)
        at 
com.cisco.nm.qpm.share.command.DiscoverFullDeviceCommand.execute(DiscoverFullDeviceCommand.java:26)
        at com.cisco.nm.qpm.pdp.CLIEngine.jobManager.Job.run(Job.java:95)
        at java.lang.Thread.run(Unknown Source)

Reply via email to