Oh, I see you said that you moved from Windows to Linux, so I assume you are
running the client on Linux now. The ps command should provide the command line
(though you will have to redirect stdout to get the full line).
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
Even swing clients have command lines.
Are you running on Windows? If so, get the listdlls utility from sysinternals
() )and run it:
listdlls java
or
listdlls javaw
That will tell you the command line used to run the app. Unless someone has
implemented their own executable that loads the JV
hello,
maybe there is a problem with naming Service.
I can see the Nameservice Port with a portscanner.
But in the JMX Console i see the naming service started on the
expected port.
The jndi.properties are in the classpath of the client.
What could that be?
best regards
View the original post :
Hello,
There is no commandline. It is a Swing Client.
Best regards
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152878#4152878
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152878
__
And the full command line used to run the client???
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152813#4152813
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152813
___
jbo
Hello,
the class i see in the verbose mode in the working environment is
NamingServer_Stub
from the jbossall_client and never NamingServer.
Here is the full stacktrace
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError:
org/jnp/server/NamingServer
at
org.jboss.nami
Please post the full command line you use to run the client.
I am surprise this class did not show up when you used -verbose:class - this
class is needed for anything that uses JNDI, which is about anything that the
client might do.
Also, if the exception you post the full output for the client
