wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: [Wrapper-user] RE: Disabling JVM ping

[Leif M. <le...@ta...>]

Clement, Nathan wrote:

>Thanks for your quick reply!  The application was trying to output about 9MB
>worth of log data at the time (something we're obviously going to try and
>reduce).  I have installed the 3.0.1 version of wrapper and have not seen
>the problem since.  I will monitor it closely over the coming days and let
>you know if the problem re-occurs.
>
Good, it sounded like the same problem.  This new version should not have
any more problems with restarts related to large amounts of output.

>My original question still stands - I'm uncomfortable with the idea of the
>application being restarted automatically.  I'd rather our support people
>have to restart the application manually in the rare event of a JVM hang.
>Would it be possible to disable pinging completely as an option for advanced
>users?  Just a suggestion of course.
>
Wow, you want to disable the feature that led me to create the Wrapper in
the first place...  Having just had problems with restarting I can 
understand
your concern.  But in general, the Wrapper is quite good about only 
restarting
the JVM when it is really necessary.  The ability to sleep well at night and
put the old pager in the bottom drawer where it belongs should be viewed
as a good thing :-)

The wrapper.ping.timeout property controls how long the Wrapper will allow
to pass without the JVM responding to a ping.  The problem was inverted
in your case.  The Wrapper process was busy and failed to ping the JVM.
The JVM side of the Wrapper has a feature that will cause it to exit and let
the Wrapper restart it if it ever fails to be pinged for a long period 
of time.
The thinking there was to avoid the JVM turning into a zombie process if
the Wrapper process ever died abnormally.
The fact that this Java side timeout is hard coded at 30 seconds was an
oversight.  It should have been the same as the ping timeout on the
Wrapper side.   A fix is now in CVS and will be in the 3.0.2 release.   
I don't
want to do a release just for this as it is not a critical problem. 
 Unless you
really need this immediately for some reason, I'll wait until there are more
things needing to be released.  You can also do a build from CVS to get
it sooner.

Cheers,
Leif

[Wrapper-user] RE: Disabling JVM ping

[Clement, N. <ncl...@qv...>]

Leif,

Thanks for your quick reply!  The application was trying to output about 9MB
worth of log data at the time (something we're obviously going to try and
reduce).  I have installed the 3.0.1 version of wrapper and have not seen
the problem since.  I will monitor it closely over the coming days and let
you know if the problem re-occurs.

My original question still stands - I'm uncomfortable with the idea of the
application being restarted automatically.  I'd rather our support people
have to restart the application manually in the rare event of a JVM hang.
Would it be possible to disable pinging completely as an option for advanced
users?  Just a suggestion of course.

Thanks very much for your prompt assistance!

Nathan


From: Leif Mortenson <leif@ta...> 
 Re: Disabling JVM ping   
2003-04-01 04:22  
 Nathan,
     Does your application output large amounts of output to the console? 
  There was bug
 that would cause the native side of the Wrapper to spend too much time 
 processing
 input from the JVM and forget about doing its other jobs.  This was 
 causing timeouts
 like you mentioned below.   It actually had nothing to do with pinging 
 that is why
 changing the ping timeout had no effect for you.
     I fixed this in 3.0.1 that was just released a couple days ago. 
  Could you please give
 that version a try and get back to me about whether or not it fixes your 
 problem.
     Be sure to return any modified timeouts to their default values.
     Also note that there were some changes with the scripts and config 
 file in the 3.0.0
 release.  You should no longer set the pid in the wrapper conf file.  It 
 is now handled
 from within the shell scripts.  This was done to reduce the number of 
 things that a
 user has to modify.
 
 Cheers,
 Leif

Re: [Wrapper-user] Regarding Windows NT Problem

[Leif M. <le...@ta...>]

Great, glad you got it working.

Cheers,
Leif

Ravi Shankar wrote:

> Hi Leif,
>  
> I am sorry, the problem was not in the name as you had mentioned. 
> Unfortunately there were two classes with the same name on the 
> classpath which was causing the conflict. I came to know it later 
> only.Thanks a lot for your help again...
>  
> Cheers
> Ravi

[Wrapper-user] Regarding Windows NT Problem

[Ravi S. <ra...@el...>]

Hi Leif,

I am sorry, the problem was not in the name as you had mentioned. =
Unfortunately there were two classes with the same name on the classpath =
which was causing the conflict. I came to know it later only.Thanks a =
lot for your help again...

Cheers
Ravi

Re: [Wrapper-user] Minor packaging issue with 3.0.1

[Leif M. <le...@ta...>]

Mike,
Thanks for catching that. Not sure how it happened.. Looking at CVS,
it has always been that way... :-/ Anyway. It is is fixed and will be in the
next release.

Cheers,
Leif

Mike Castle wrote:

>Looks like AppNoWrapper.bat.in is not in DOS format in the win32 zip file.
>
>mrc
>  
>

[Wrapper-user] Minor packaging issue with 3.0.1

[<da...@ix...>]

Looks like AppNoWrapper.bat.in is not in DOS format in the win32 zip file.

mrc
-- 
     Mike Castle      da...@ix...      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

Re: [Wrapper-user] Fw: Regarding Windows NT problem

[Leif M. <le...@ta...>]

Ravi,
    I just retested this and your assertion does not appear to be true.
I did the following:

rename Wrapper.exe TestService.exe
TestService -i ..\conf\wrapper.conf
net start TestWrapper
<verified that it was running>
net stop TestWrapper
TestService -r ..\conf\wrapper.conf

    Everything worked perfectly.   Did he rename the Wrapper.exe
after having installed the service?  If so then that is nothing to do with
the Wrapper?  When any service is installed, it places an entry into
the system registry.  You should be able to find it by running "regedit"
and then looking at the following key:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<your service name>

    If I rename the Wrapper binary AFTER having installed it and then
attempt to start the service, I get the following message from the
service manager:
--
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
--
    Attempting to start from the service control panel also gives the
same error.

    Can you verify that you are not seeing a different problem.   You
should not have any problems renaming the Wrapper binary.   You
can not rename the Wrapper.DLL file currently.  That is because of
the way the Java code loads the native library.   But if the Java code
can not locate the native library the program should still work but it
will lose the ability to prevent a JVM restart when the user logs out.

Cheers,
Leif


Ravi Shankar wrote:

> Hi Leif,
>  
> I understood the mistake, it is a mistake from our side.
>  
> To make the filenames generic and compatible with our application, 
> somebody changed the name of Wrapper.exe as ServerStart.exe!. And 
> somewhere in the dll reference is made in your code to Wrapper.exe 
> only. When I changed it back, I got it working!!!
>  
> Thanks anyway.
>  
> Regards,
> Ravi
>  

[Wrapper-user] Fw: Regarding Windows NT problem

[Ravi S. <ra...@el...>]

Hi Leif,

I understood the mistake, it is a mistake from our side.

To make the filenames generic and compatible with our application, =
somebody changed the name of Wrapper.exe as ServerStart.exe!. And =
somewhere in the dll reference is made in your code to Wrapper.exe only. =
When I changed it back, I got it working!!!

Thanks anyway.

Regards,
Ravi

----- Original Message -----=20
From: Ravi Shankar=20
To: wra...@li...=20
Cc: wra...@li... ; =
wra...@li...=20
Sent: Tuesday, April 01, 2003 10:35 PM
Subject: Fw: Regarding Windows NT problem


Hi Leif,

 I have ran into another problem now.

Our Reporting tool is successfully started as a service as I had =
mentioned before. But this tool actually calls a RenderEngine in the =
original application. But when I run it as a service, it seems that =
renderengine is not started successfully because the report is not =
getting generated. When I run the standalone script, however the report =
is generated. There is no errors in wrapper.log file. I tried adding =
like this too:

wrapper.app.parameter.1=3Dcom.elixirtech.report.server.ElixirReportServer=


wrapper.app.parameter.2=3Dcom.elixirtech.report.server.RenderEngine



Any help please?

Thanks and regards,

Ravi

Re: [Wrapper-user] Fw: Regarding Windows NT problem

[Leif M. <le...@ta...>]

I was not clear from your message.  Does the application work at all under
the Wrapper?  Ie. can you run it under the Wrapper in a console?  Or are you
only having problems when running as a service?

When you run the Wrapper under debug mode, it will display the full Java
command generated by the Wrapper.   Copy this into a new batch file.
And (important!) remove the parameter which sets the wrapper.key.   You
can then run that batch file to see how the application behaves without the
Wrapper, but with the exact same configuration as when it is controlled
by the Wrapper.

I can't really help you beyond that without more info.  If the 
application is
not kicking out any error messages, then I have nothing to work with.
 From your email, this looks like code from your company so good news
is that you should be able to debug what is happening in the source.

If it is working under the Wrapper in console mode but not as a service
then it is most likely a path problem.   Compare the command generated
when run as a console to that when run as a service and see if anything
stands out.

Cheers,
Leif

Ravi Shankar wrote:

> Hi Leif,
>  
>  I have ran into another problem now.
>  
> Our Reporting tool is successfully started as a service as I had 
> mentioned before. But this tool actually calls a RenderEngine in the 
> original application. But when I run it as a service, it seems that 
> renderengine is not started successfully because the report is not 
> getting generated. When I run the standalone script, however the 
> report is generated. There is no errors in wrapper.log file. I tried 
> adding like this too:
>  
>
> wrapper.app.parameter.1=com.elixirtech.report.server.ElixirReportServer
>
> wrapper.app.parameter.2=com.elixirtech.report.server.RenderEngine
>
>  
>
> Any help please?
>
> Thanks and regards,
>
> Ravi
>

[Wrapper-user] Fw: Regarding Windows NT problem

[Ravi S. <ra...@el...>]

Hi Leif,

 I have ran into another problem now.

Our Reporting tool is successfully started as a service as I had =
mentioned before. But this tool actually calls a RenderEngine in the =
original application. But when I run it as a service, it seems that =
renderengine is not started successfully because the report is not =
getting generated. When I run the standalone script, however the report =
is generated. There is no errors in wrapper.log file. I tried adding =
like this too:

wrapper.app.parameter.1=3Dcom.elixirtech.report.server.ElixirReportServer=


wrapper.app.parameter.2=3Dcom.elixirtech.report.server.RenderEngine



Any help please?

Thanks and regards,

Ravi

Re: [Wrapper-user] Disabling JVM ping

[Leif M. <le...@ta...>]

Nathan,
    Does your application output large amounts of output to the console? 
 There was bug
that would cause the native side of the Wrapper to spend too much time 
processing
input from the JVM and forget about doing its other jobs.  This was 
causing timeouts
like you mentioned below.   It actually had nothing to do with pinging 
that is why
changing the ping timeout had no effect for you.
    I fixed this in 3.0.1 that was just released a couple days ago. 
 Could you please give
that version a try and get back to me about whether or not it fixes your 
problem.
    Be sure to return any modified timeouts to their default values.
    Also note that there were some changes with the scripts and config 
file in the 3.0.0
release.  You should no longer set the pid in the wrapper conf file.  It 
is now handled
from within the shell scripts.  This was done to reduce the number of 
things that a
user has to modify.

Cheers,
Leif

Clement, Nathan wrote:

>Hi,
>
>I've been using wrapper 2.2.9 and have found that it sometimes restarts the
>JVM incorrectly under heavy load.  I have set wrapper.ping.timeout to 0, but
>it still restarts the application with the following messages in the log
>(note these occur a few seconds apart - i have trimmed the irrelevant parts
>of the log):
>
>Wrapper Process has not received any CPU time for 123 seconds.  Extending
>timeouts.
>
>The Wrapper code did not ping the JVM for 40 seconds.  Quit and let the
>wrapper resynch.
>
>Wrapper Process has not received any CPU time for 57 seconds.  Extending
>timeouts.
>
>JVM exited unexpectedly.
>
>Is there a way to completely disable the pinging/automatic restarting
>functionality? - it seems to be causing us many more problems than it could
>solve.  Our JVM is quite stable and we have experienced no hanging problems
>at all.
>
>Here is the wrapper.conf file:
>
<clip>

[Wrapper-user] Disabling JVM ping

[Clement, N. <ncl...@qv...>]

Hi,

I've been using wrapper 2.2.9 and have found that it sometimes restarts the
JVM incorrectly under heavy load.  I have set wrapper.ping.timeout to 0, but
it still restarts the application with the following messages in the log
(note these occur a few seconds apart - i have trimmed the irrelevant parts
of the log):

Wrapper Process has not received any CPU time for 123 seconds.  Extending
timeouts.

The Wrapper code did not ping the JVM for 40 seconds.  Quit and let the
wrapper resynch.

Wrapper Process has not received any CPU time for 57 seconds.  Extending
timeouts.

JVM exited unexpectedly.

Is there a way to completely disable the pinging/automatic restarting
functionality? - it seems to be causing us many more problems than it could
solve.  Our JVM is quite stable and we have experienced no hanging problems
at all.

Here is the wrapper.conf file:

#********************************************************************
# Wrapper parameters
#********************************************************************
# Java Application
wrapper.java.command=D:\jdk1.3.1\bin\java

# Java Main class
wrapper.java.mainclass=com.metiom.service.WeblogicServiceWrapper

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=..\jars\weblogic_service.jar
wrapper.java.classpath.2=D:\weblogic\lib\weblogic510sp13boot.jar
wrapper.java.classpath.3=D:\weblogic\classes\boot
wrapper.java.classpath.4=..\jars\jce1_2_1.jar
wrapper.java.classpath.5=..\jars\sunjce_provider.jar
wrapper.java.classpath.6=..\jars\US_export_policy.jar
wrapper.java.classpath.7=..\jars\local_policy.jar
wrapper.java.classpath.8=..\jars\jcert.jar
wrapper.java.classpath.9=..\jars\jnet.jar
wrapper.java.classpath.10=..\jars\jsse.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=..\jars\win32
wrapper.java.library.path.2=D:\weblogic\bin
wrapper.java.library.path.3=D:\oracle\ora81\bin

# Java Additional Parameters
wrapper.java.additional.1=-Dweblogic.system.home=.
wrapper.java.additional.2=-Dweblogic.home=D:\weblogic
wrapper.java.additional.3=-Djava.security.manager
wrapper.java.additional.4=-Djava.security.policy==weblogic.policy
wrapper.java.additional.5=-Dfile.encoding=UTF-8

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=weblogic_service.properties

# Ensure that the JVM will not be restarted no matter what happens
wrapper.ping.timeout=0

# Port which the native wrapper code will attempt to connect to
wrapper.port=1778

#********************************************************************
# Wrapper Logging parameters
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=M

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=../logs/console.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=M

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=5m

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=1

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper Unix daemon parameters
#********************************************************************
# File to write process ID to
wrapper.pidfile=/var/run/QISProd.pid

#********************************************************************
# Wrapper NT Service parameters
#********************************************************************
# WARNING - Do not modify any of these parameters when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.ntservice.name=QISProd

# Display name of the service
wrapper.ntservice.displayname=Qvalent iCIS (7001)

# Description of the service
wrapper.ntservice.description=Qvalent iCIS (7001)

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Priority at which the service is run.  NORMAL, LOW, HIGH, or
#  REALTIME
wrapper.ntservice.process_priority=NORMAL


Thanks for any help,

Nathan

RE: [Wrapper-user] RMI services being killed on user logout

[Palmer, D. <Dav...@ph...>]

> 
> Okay... this is pretty strange... at least to me anyway. 
> Basically what I
> have is a server "wrapper" class which starts the RMI registry, then
> instantiates a Implementation class (the thing that extends
> UnicastRemoteObject and implements the remote interface). 

please disregard my post here. this was my bad, damn monday mornings!
I was trying to rebind my remote object to a different port than what i set
as my rmi registry port! Of course i'll get connection refused!!!

sorry folks

./dave


"The sender believes that this E-mail and any attachments were free of any
harmful and malicious code or defects when sent.  This message and its
attachments could have been infected during transmission.  By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action regarding the code
or such defects.  The sender is not liable for any loss or damage arising in
any way from this message or its attachments."

RE: [Wrapper-user] RMI services being killed on user logout

[Palmer, D. <Dav...@ph...>]

> Well, that means, that the registry doesn't stop to exist, 
> when you stop
> the service. I don't know why or how you could kill the registry on
> stopping the service.
> But if you use the rebind method rebind(String name,          
>              
> Remote obj) you should get around this exception.
> 
> 
First, I just want to thank you for the help here. Its nice to see an active
developer community :) It is very much appreciated.

Second... ugh... okay. When trying to start my service now... I get:

INFO   | jvm 1    | 2003/03/31 12:38:23 | getting ready to start logic
engine: rmi://localhost:12773/logicengine
INFO   | jvm 1    | 2003/03/31 12:38:24 | java.rmi.ConnectException:
Connection refused to host: localhost; nested exception is: 
INFO   | jvm 1    | 2003/03/31 12:38:24 | 	java.net.ConnectException:
Connection refused: connect
INFO   | jvm 1    | 2003/03/31 12:38:24 | java.net.ConnectException:
Connection refused: connect
...... snipped stack trace .......

Okay... this is pretty strange... at least to me anyway. Basically what I
have is a server "wrapper" class which starts the RMI registry, then
instantiates a Implementation class (the thing that extends
UnicastRemoteObject and implements the remote interface). This
implementation class does a rebind of the "service" name, which I pass in as
an argument:

------- RMIServer.java ------------
// full service name:
String serviceName = "rmi://"+host+":"+port+"/logic_engine";
// start rmi registry:
java.rmi.registry.LocateRegistry(new Integer(regPort).intValue());
// instantiate remote implementation class:
new RemoteLogicEngineImpl(serviceName);
------- end RMIServer.java --------

------- RemoteLogicEngineImpl.java ---------
public class RemoteLogicEngineImpl extendes UnicastRemoteObject implements
RemoteLogicEngineIntf {
    public RemoteLogicEngineImpl (String service) 
    {
    	Naming.rebind(service_name, this);
    }
    .... exposed remote methods here....
}
-------- end RemoteLogicEngineImpl.java ---


Now... I have change the 'host' parameter from "localhost" to my hostname,
to the IP... all produce the same exception. I have tried different ports...
the same.

I'm just at a loss here. I *know* I am not doing something right. Ugh...
this is why I dislike dealing with 3rd party "blackbox" software. 

./dave

    






"The sender believes that this E-mail and any attachments were free of any
harmful and malicious code or defects when sent.  This message and its
attachments could have been infected during transmission.  By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action regarding the code
or such defects.  The sender is not liable for any loss or damage arising in
any way from this message or its attachments."

Re: [Wrapper-user] Re: Regarding Windows NT problem

[Leif M. <le...@ta...>]

Ravi,
    Thanks I am glad you are finding the Wrapper useful.

    Take a look at the Logging configuration documentation.  Everything you
need to know is right there. ;-)

http://wrapper.tanukisoftware.org/doc/english/props-logging.html

    To limit the size of the wrapper.log file, you should enable log 
rolling and
then set the maximum number of log files.  For example.  The following
properties will configure the Wrapper to roll the log file when it 
reaches 1Mb
in size and then keep the 5 most recent files.  This will use a maximum of
5Mb of disk space. You can set the numbers even smaller of course if you
want.

wrapper.logfile.maxsize=1m
wrapper.logfile.maxfiles=5

If you really want to completely disable logging to the file, you can do 
so by
simply setting the log level to the file to NONE like this:

wrapper.logfile.loglevel=NONE

Cheers,
Leif

[Wrapper-user] Re: Regarding Windows NT problem

[Ravi S. <ra...@el...>]

Hi Leif,

The wrapper tool is wonderful and I am recommending it to many of our =
colleagues and friends.

Is there any way to stop expanding the wrapper.log file or even avoid =
appearing it? It requires a delete every now and then when it is =
increasing in size, thanks for the help.

Thanks and regards,
Ravi

RE: [Wrapper-user] RMI services being killed on user logout

[FReAK La M. <fre...@qu...>]

Hi,

>When we stop the service... the service stops (like one would expect)
except
>that we noticed that the port is still listening for RMI... so even though
>the service is stopped... our RMI server is still listening... which means,
>when we start again, we get a:
>
>ava.net.BindException: Address already in use: JVM_Bind
>
>exception.

Well, that means, that the registry doesn't stop to exist, when you stop
the service. I don't know why or how you could kill the registry on
stopping the service.
But if you use the rebind method rebind(String name,                       
Remote obj) you should get around this exception.

Have a nice day,
FReAK

_____________________________________________
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com

[Wrapper-user] JVM exited unexpectedly

[Richard E. <rem...@ou...>]

I've got a couple of applications I wrap each with its own Java Service
Wrapper. One such
application is JBoss and another is a large java application we have written.
In each case
when the wrapper is requested to stop the application (on both windows and
linux) I get
the following error message in the wrapper log:

ERROR  | wrapper  | 2003/03/27 16:11:55 | JVM exited unexpectedly while
stopping the application.
STATUS | wrapper  | 2003/03/26 08:52:12 | <-- Wrapper Stopped

Any thoughts?

Also, on linux the JBoss successful shutdown message "Shutdown complete" ends
up in JBoss'
apache log4j log but on windows the JBoss shutdown message ends up in the
wrapper log.

Again, any thoughts?


Richard

Svar: RE: [Wrapper-user] RMI services being killed on user logout

[Mikkel D. <mi...@co...>]

>> when we start again, we get a:

>> java.net.BindException: Address already in use: JVM_Bind

>> exception.

>> Is there something I'm missing (again) ???

Not as far as I know. My piece of code to start the registry looks like =
this:

            try {
                try {
                    java.rmi.registry.LocateRegistry.createRegistry
                        (java.rmi.registry.Registry.REGISTRY_PORT);
                    log.event("Started RMI registry");
                } catch (java.rmi.RemoteException rex) {
                    log.event("Could not create RMI registry. It might =
already have been started");
                }

                Naming.rebind("//"+bindName+"/"+RMI_BIND_NAME, remoteObject=
);
            } catch (Exception e) {
                log.sys("Could not bind rmi",e);
            }

Hope it helps.

/Mikkel

RE: [Wrapper-user] RMI services being killed on user logout

[Palmer, D. <Dav...@ph...>]

> >Could you be more explicit on how you are using createRegistry?
> 
> I am sorry, I have only used the createRegistry statement, 
> because I wanted
> to write an application for the wrapper ;-) and I had read that way of
> getting a RMIRegistry in an article at JavaWorld
> (http://www.javaworld.com/javaworld/jw-01-2001/jw-0112-rmi.html) 
> 
>
Now, after reading this information, I haven't been able to figure out the
latest problem with this... so I'll ask here :)

When we stop the service... the service stops (like one would expect) except
that we noticed that the port is still listening for RMI... so even though
the service is stopped... our RMI server is still listening... which means,
when we start again, we get a:

ava.net.BindException: Address already in use: JVM_Bind

exception.

Is there something I'm missing (again) ???

./dave


"The sender believes that this E-mail and any attachments were free of any
harmful and malicious code or defects when sent.  This message and its
attachments could have been infected during transmission.  By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action regarding the code
or such defects.  The sender is not liable for any loss or damage arising in
any way from this message or its attachments."

Re: [Wrapper-user] RMI services being killed on user logout

[FReAK La M. <fre...@qu...>]

Hi there,

>Could you be more explicit on how you are using createRegistry?

I am sorry, I have only used the createRegistry statement, because I wanted
to write an application for the wrapper ;-) and I had read that way of
getting a RMIRegistry in an article at JavaWorld
(http://www.javaworld.com/javaworld/jw-01-2001/jw-0112-rmi.html) 

>I can always find people saying to use it, but I've not been able to find
>any definitive code examples.  Some say do it only if getRegistry fails,
>and use the one returned by createRegistry.  Others never suggest that.
>And I've not been able to glean a whole lot from Sun's docs.

There is some code in that article mentioned above, maybe that helps you a
little bit. 
As far as I know you have to use createRegistry if there is no RMIRegistry
running at the moment. The API states about createRegistry "Creates and
exports a Registry on the local host that accepts requests on the specified
port." I think that should have the same effect as typing rmiregistry on
your console.
If you have created an RMIRegistry the you can get this by using
getRegistry. This will cause some problems, if there is non existing
RMIRegistry at the moment. The API states about this point "Note that a
getRegistry call does not actually make a connection to the remote host. It
simply creates a local reference to the remote registry and will succeed
even if no registry is running on the remote host. Therefore, a subsequent
method invocation to a remote registry returned as a result of this method
may fail. "
http://java.sun.com/products/jdk/1.2/docs/api/java/rmi/registry/LocateRegist
ry.html

Hope that this information was useful for you and have a nice day,
FReAK


My latest project: compile Java on Pocket PC
http://www.freaklamarsch.de/javacw


_____________________________________________
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com

RE: [Wrapper-user] Different property between Windows NT service and batch file

[Takeda T. <tak...@or...>]

Hi Leif,

As you said, the problem was the access permission for a network drive. I
setup the "wrapper.ntservice.account" property. Now, it's working well.

Thank you very much. 

Takeda Takayoshi

> -----Original Message-----
> From: Leif Mortenson [mailto:le...@ta...]
> Sent: Thursday, March 27, 2003 5:10 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Different property between Windows NT
> service and batch file
> 
> 
> Takeda,
> From the NT Service log, I see the following lines:
> ---
> INFO | jvm 1 | 2003/03/27 11:17:42 | ***** WARNING *****
> INFO | jvm 1 | 2003/03/27 11:17:42 | Specified directory 
> doesn't exist:
> x:\tmp\export_home\eyes2020\testdata\data\mapdata
> INFO | jvm 1 | 2003/03/27 11:17:42 |
> ---
> 
> I assume that the x: drive is mapped to a drive on another machine? If
> so this mapping
> is done on a user by user basis under windows. You have 
> probably mapped
> the x: drive to
> the current user so it will work correctly when run in a console. But
> when you run as
> an NT service, the Wrapper is run by default under the SYSTEM 
> user. You
> can see this
> by looking at the process list under the task manager.
> 
> I am not sure if it is possible to map a network drive for the SYSTEM
> user. If anyone
> knows how to do this, please post.
> 
> The only way that I know how to get this working is to run the NT
> service as a given
> user. If you have set up a network drive for that user, then 
> the Wrapper
> should also
> have access.
> 
> Take a look at the wrapper.ntservice.account and 
> wrapper.ntservice.password
> properties at:
> http://wrapper.tanukisoftware.org/doc/english/props-nt.html
> 
> NOTE - After changing these properties, you must uninstall and then
> reinstall
> the service for the settings to take effect. You can verify that the
> Wrapper is
> being run as the correct user by looking at the process list 
> in the task
> manager.
> 
> I have not actually tested accessing a mapped network drive 
> from a Java
> process under the Wrapper before, so please let me know 
> whether or not this
> works.
> 
> Cheers,
> Leif
> 
> 
> 
> 
> Takeda Takayoshi wrote:
> 
> > Hi,
> > I have a problem of a drive recognition. When I run my process by
> > batch file, it works well. But in case of NT service, it doesn't.
> > Because my program doesn't realize a windows drive. I 
> attached 2 logs
> > in each (DEBUG level). I would appreciate any comments you have.
> > Thank you.
> > Takeda Takayoshi
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 

RE: [Wrapper-user] RMI services being killed on user logout

[Palmer, D. <Dav...@ph...>]

> 
> Hi,
> well I am running an RMI Programm using the wrapper with no problem.
> I think that your problem is that you are starting the Registry via
> System.exec()
> I am using java.rmi.registry.LocateRegistry.createRegistry(1099);
> 

this appears to have did the trick! I just added this bit of code...
recompiled... restarted the service. logged out, then logged back in and
whalla! port still available!

thanks :)

./dave

> 


"The sender believes that this E-mail and any attachments were free of any
harmful and malicious code or defects when sent.  This message and its
attachments could have been infected during transmission.  By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action regarding the code
or such defects.  The sender is not liable for any loss or damage arising in
any way from this message or its attachments."

Re: [Wrapper-user] RMI services being killed on user logout

[<da...@ix...>]

In article <412...@qu...>,
FReAK La Marsch <wra...@li...> wrote:
>I am using java.rmi.registry.LocateRegistry.createRegistry(1099);

Could you be more explicit on how you are using createRegistry?

I just migrated our application from using rmiregistry as an external app
to using createRegistry (as part of my migration to wrapper :-).

However, I want to be sure I did it right!  It seems to be working right,
but I'm certainly not convinced it is.

I can always find people saying to use it, but I've not been able to find
any definitive code examples.  Some say do it only if getRegistry fails,
and use the one returned by createRegistry.  Others never suggest that.
And I've not been able to glean a whole lot from Sun's docs.

Thanks,
mrc
-- 
     Mike Castle      da...@ix...      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

Re: [Wrapper-user] Different property between Windows NT service and batch file

[Leif M. <le...@ta...>]

Takeda,
From the NT Service log, I see the following lines:
---
INFO | jvm 1 | 2003/03/27 11:17:42 | ***** WARNING *****
INFO | jvm 1 | 2003/03/27 11:17:42 | Specified directory doesn't exist:
x:\tmp\export_home\eyes2020\testdata\data\mapdata
INFO | jvm 1 | 2003/03/27 11:17:42 |
---

I assume that the x: drive is mapped to a drive on another machine? If
so this mapping
is done on a user by user basis under windows. You have probably mapped
the x: drive to
the current user so it will work correctly when run in a console. But
when you run as
an NT service, the Wrapper is run by default under the SYSTEM user. You
can see this
by looking at the process list under the task manager.

I am not sure if it is possible to map a network drive for the SYSTEM
user. If anyone
knows how to do this, please post.

The only way that I know how to get this working is to run the NT
service as a given
user. If you have set up a network drive for that user, then the Wrapper
should also
have access.

Take a look at the wrapper.ntservice.account and wrapper.ntservice.password
properties at:
http://wrapper.tanukisoftware.org/doc/english/props-nt.html

NOTE - After changing these properties, you must uninstall and then
reinstall
the service for the settings to take effect. You can verify that the
Wrapper is
being run as the correct user by looking at the process list in the task
manager.

I have not actually tested accessing a mapped network drive from a Java
process under the Wrapper before, so please let me know whether or not this
works.

Cheers,
Leif




Takeda Takayoshi wrote:

> Hi,
> I have a problem of a drive recognition. When I run my process by
> batch file, it works well. But in case of NT service, it doesn't.
> Because my program doesn't realize a windows drive. I attached 2 logs
> in each (DEBUG level). I would appreciate any comments you have.
> Thank you.
> Takeda Takayoshi