RE: reinstall TC service after java upgrade?

2018-11-09 Thread Berneburg, Cris J. - US
Thanks André

cjb> I upgraded Java from 8u181 to 8u191 on our dev (JDK) and test 
cjb> (JRE) Windows 2012 servers today.  After doing so, the Tomcat 
cjb> 8.5(.32) Windows services would no longer start.  Removing and 
cjb> re-adding the service fixed the service.

mt> You need to reconfigure where the service looks for the JRE.
mt> Normally you'd do that with Tomcat[7|8|9]w.exe

cjb> why doesn't the service just use the JAVA_HOME or JRE_HOME
cjb> environment vars?  Is that so there can be multiple services
cjb> running with different versions of Java simultaneously?

aw> Basically yes.  Each service also picks up many other arguments there.
aw> For a complete explanation, I recommend :
aw> https://wiki.apache.org/tomcat/FAQ/Windows#Q11
aw> (disclaimer : I get bonus points each time someone reads that)

I read it, possibly again.  André ++;

Can we put a note in there saying that if a different version of Java is 
installed and the old one is removed, the registry entries are no longer valid 
and need to be refreshed by running Tomcat[#]w.exe to reference the new Java?


Note that the JVM location is also stored in the Windows Registry by 
Tomcat[#]w.exe (prunmgr) and is referenced by the service wrapper (prunsrv).  
This means that if the Java location changes, such as removing an older JVM and 
installing a newer version, the Registry entries will no longer be valid, and 
the Tomcat service will no longer run.  Running Tomcat[#]w.exe and updating the 
JVM location on the Java tab or selecting the "Use default" checkbox can remedy 
that.

"One more thing [...]"

Wait a minute.  Could it simply be that the "Use default" checkbox (for JVM) on 
the Java tab was unchecked for me?  Argh.  Cris --;

--
Cris Berneburg
CACI Lead Software Engineer



RE: Default context.xml with parallel deployment

2018-11-09 Thread Gilles SCHLIENGER
I tried my best with this solution.

Actually, using external entities for an XML attribute is not supported with an 
external file, so the solution in the FAQ does not seem good.

I get a strange error when I do a SYSTEM reference to an external XML file, the 
webapp can not start.
I get for my jdbc datasource :
IntrospectionUtils: Assert: Illegal params null ContextResource[name=jdbc/...

So I'm afraid I can't use this solution...

Regards
Gilles


-Message d'origine-
De : Gilles SCHLIENGER [mailto:gilles.schlien...@cncc.fr] 
Envoyé : vendredi 9 novembre 2018 10:15
À : Tomcat Users List
Objet : RE: Default context.xml with parallel deployment

Thank you very much Mark for your answer.
I will look into the xml entities, I did not know about this feature.

I was wondering if a feature like having a "myapplication.xml.default" could be 
a good idea to include in future Tomcat releases ?

Thanks again
Regards
Gilles


-Message d'origine-
De : Mark Thomas [mailto:ma...@apache.org] 
Envoyé : jeudi 8 novembre 2018 23:37
À : users@tomcat.apache.org
Objet : Re: Default context.xml with parallel deployment

On 08/11/2018 20:45, Gilles SCHLIENGER wrote:
> Hi everyone,
> 
> We are using Tomcat 9.0.8.
> 
> We are using xml context files in  
> $CATALINA_BASE/conf/[enginename]/[hostname]/ to store the database connexion 
> information.
> 
> When using parallel deployment, I understand that you should use for specific 
> context xml files :
> - for myapplication##1.war : myapplication##1.xml
> - for myapplication##2.war : myapplication##2.xml
> 
> We would like to have a default context xml file ONLY available for the « 
> myapplication » application but for all versions
> 
> It seems we could use a file called « context.xml.default » but the 
> properties would be also available to other applications, which we don't want.
> 
> Is there a way to have a context.xml file available to all versions of the 
> same application or any other way to do it ?

There isn't an explicit Tomcat feature that would do this.

Could you do something with XML entities? There is a description of them
here: https://wiki.apache.org/tomcat/FAQ/Password in the context of
moving passwords to an external file.

Could you create myapplication.txt and then ship each app with a simple
context.xml file that included the above file?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: Default context.xml with parallel deployment

2018-11-09 Thread Gilles SCHLIENGER
Thank you very much Mark for your answer.
I will look into the xml entities, I did not know about this feature.

I was wondering if a feature like having a "myapplication.xml.default" could be 
a good idea to include in future Tomcat releases ?

Thanks again
Regards
Gilles


-Message d'origine-
De : Mark Thomas [mailto:ma...@apache.org] 
Envoyé : jeudi 8 novembre 2018 23:37
À : users@tomcat.apache.org
Objet : Re: Default context.xml with parallel deployment

On 08/11/2018 20:45, Gilles SCHLIENGER wrote:
> Hi everyone,
> 
> We are using Tomcat 9.0.8.
> 
> We are using xml context files in  
> $CATALINA_BASE/conf/[enginename]/[hostname]/ to store the database connexion 
> information.
> 
> When using parallel deployment, I understand that you should use for specific 
> context xml files :
> - for myapplication##1.war : myapplication##1.xml
> - for myapplication##2.war : myapplication##2.xml
> 
> We would like to have a default context xml file ONLY available for the « 
> myapplication » application but for all versions
> 
> It seems we could use a file called « context.xml.default » but the 
> properties would be also available to other applications, which we don't want.
> 
> Is there a way to have a context.xml file available to all versions of the 
> same application or any other way to do it ?

There isn't an explicit Tomcat feature that would do this.

Could you do something with XML entities? There is a description of them
here: https://wiki.apache.org/tomcat/FAQ/Password in the context of
moving passwords to an external file.

Could you create myapplication.txt and then ship each app with a simple
context.xml file that included the above file?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: Default context.xml with parallel deployment

2018-11-09 Thread Gilles SCHLIENGER
Hi Guido,

Thank you very much for your answer.

Our context xml file contains  and  elements

Can you give me more details about what you mean by seamlink ?

We want toovoid having to create a new file in 
$CATALINA_BASE/conf/[enginename]/[hostname]/ everytime we deploy a war with a 
new version of the application.

Thanks a lot again
Regards
Gilles


-Message d'origine-
De : Jäkel, Guido [mailto:g.jae...@dnb.de] 
Envoyé : vendredi 9 novembre 2018 08:22
À : 'users@tomcat.apache.org'
Objet : RE: Default context.xml with parallel deployment

Dear Giles,

what aspects do you use in you  myapplication#foo.xml ? You may symlink this 
files from an application-specific master template, e.g. myapplication.xml

greeatings

Guido

>-Original Message-
>From: Gilles SCHLIENGER [mailto:gilles.schlien...@cncc.fr]
>Sent: Thursday, November 08, 2018 9:46 PM
>To: users@tomcat.apache.org
>Subject: Default context.xml with parallel deployment
>
>Hi everyone,
>
>We are using Tomcat 9.0.8.
>
>We are using xml context files in  
>$CATALINA_BASE/conf/[enginename]/[hostname]/ to store the database connexion 
>information.
>
>When using parallel deployment, I understand that you should use for specific 
>context xml files :
>- for myapplication##1.war : myapplication##1.xml
>- for myapplication##2.war : myapplication##2.xml
>
>We would like to have a default context xml file ONLY available for the « 
>myapplication » application but for all versions
>
>It seems we could use a file called « context.xml.default » but the properties 
>would be also available to other applications,
>which we don't want.
>
>Is there a way to have a context.xml file available to all versions of the 
>same application or any other way to do it ?
>
>Thanks a lot in advance !
>Regards
>Gilles

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org