Small contribution to the instalation process

Hello!
I dont know is this a contribution, bug or my mistake …

Following error appears during instalation process of X-Application. I had Tamino libraries inside lib dir of Tomcat, after removing them problem disappears.

Here is the error description from running property. Setup process went ok, i think that You may prevent this situation somehow suring setup or put a note in documentation (or mayby there is a note but i havent found it …) .Let me, add one more think - X-Application is exactly what i need to prepare i.e. quick pilot project THANKS.

I hope this help!



Additional info:
Database is created and setup process without any errors.

Database version 3.1.1.4

Database op system: win 2000 p

Database is alive.

Database has a collections and data according to the operation processed by setup

Error description from explorer screen after running property example



!Error!


An error occurred in the application program. Please report the following problem to your webmaster.


Error message: 017: TaminoStore Exception.


Help message: The connection to the Tamino database could not be established. An administrator should have a look to the stack trace for checking whether the settings of the web.xml file are correct or the database is started up.


Exception Type: MajorEnvironmentException


Stacktrace:

MajorEnvironmentException: 017: TaminoStore Exception.
com.softwareag.tamino.db.api.connection.TServerNotAvailableException
Server Not Available!
NestedException:Invocation constructor failed.
NestedException without message!
at com.softwareag.tamino.db.api.connection.TConnectionFactory.newConnection(TConnectionFactory.java:50)
at com.softwareag.xtools.xapplication.store.TaminoStore.connect(TaminoStore.java:301)
at com.softwareag.xtools.xapplication.store.TaminoStore.(TaminoStore.java:246)
at com.softwareag.xtools.xapplication.jsp.ApplicationContext.newStore(ApplicationContext.java:194)
at com.softwareag.xtools.xapplication.jsp.ApplicationContext.(ApplicationContext.java:77)
at com.softwareag.xtools.xapplication.jsp.ApplicationContext.forServlet(ApplicationContext.java:122)
at com.softwareag.xtools.xapplication.jsp.ServletSessionContext.findApplicationContext(ServletSessionContext.java:168)
at com.softwareag.xtools.xapplication.jsp.ServletSessionContext.findSessionContext(ServletSessionContext.java:95)
at com.softwareag.xtools.xapplication.jsp.ServletSessionContext.findSessionContext(ServletSessionContext.java:70)
at com.softwareag.xtools.xapplication.jsp.JspTag.checkContext(JspTag.java:226)
at com.softwareag.xtools.xapplication.jsp.JspTag.doStartTag(JspTag.java:114)
at Home_1._jspService(Home_1.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
at org.apache.tomcat.core.Handler.service(Handler.java:235)
at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Http10Interceptor.java:176)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
at java.lang.Thread.run(Thread.java:484)







powered by Tamino X-Application




Here is the env.cmd settings:



:: X-Application configuration



:: Location where X-Application is installed.

:: Specify an absolute path here.

:: Do not use quotes, even if the path contains spaces.

:: Do not append / or .

set XAPPLICATION_HOME=c:/xapplication_312



:: Location of your JDK

:: JAVA_HOME points to your JDK 1.3.

:: If JAVA_HOME is already defined in your environment, you don’t have

:: to assign a value here. Otherwise, un-comment the following line and

:: supply a proper value.

:: Do not use quotes, even if the path contains spaces.

:: If you want to run the tests, JAVA_HOME has to point to a local JDK!

set JAVA_HOME=c:/java/jbuilder5/jdk1.3



:: Command to launch Java virtual machine.

:: Usually, there is no need to change this variable:

set JAVACMD=%JAVA_HOME%/bin/java



:: Location where Tomcat is installed

set TOMCAT_HOME=c:/java/Tomcat3.3



:: Port number Tomcat listens to

:: There is no need to change this variable unless you changed the

:: port Tomcat listens to (i.e. you changed the

::

:: line in tomcat-3.3/conf/server.xml).

:: If so, set this variable to the same value you specified for

:: for the port attribute.

:: Note: Tamino Webdav server includes Tomcat 3.3 configured for port 4000.

:: Specify port 4000 here (and the propert TOMCAT_HOME above)

:: to use Webdav’s Tomcat.

set TOMCAT_PORT=8080



:: URL pointing to your Tamino database.

:: Has to be an existing database, X-Application does not create a Tamino database.

:: Note that this is not a URL to Tomcat.

set TAMINO_URL=http://localhost/tamino/xa



:: Tamino collection containing example and demo data

:: X-Application’s setup script installs sample and testing data in

:: this collection. Examples and demo applications work with this data.

:: X-Application creates a new collection if the specified collection does

:: not exist. To avoid conflicts with existing data, we suggest to specify

:: a new collection here.

set XAPPLICATION_COLLECTION=xapplication312



:: Java compiler used to build X-Application.

:: Usually, there is no need to change this variable. Unless you want to

:: speedup compilation by using jikes …

:: Say “classic”, “modern”, “jikes” or “jvc”. When using jikes, make sure it’s

:: in your path. Technically, this variable specifies ant’s “build.compiler” property.

set BUILD_COMPILER=classic



:: Tomcat might need some more memory.

set TOMCAT_OPTS=-Xmx256M

[This message was edited by Harald Wolf on 30 Jul 2002 at 22:28.]

I’m not sure if I understand correctly.

Did you have Tamino API for Java in one of Tomcat’s lib directories before installing X-Application? In which lib directory?

What did you do to produce the error message you sent? Running the setup script or launching an example application?

Michael

Software AG Germany, Darmstadt

Hello,

could you have a look at your web.xml file for the simple examples and check if the parameters for the TaminoUrl is collectly set. In your case, it must be

http://localhost/tamino/xa


The path for the web.xml is

%XAPPLICATION_HOME%/examples/jsp/simple/WEB-INF/web.xml

Another think useful to analyze the problem is the output window of tomcat. Could you start Tomcat, invoke the first simple example and post the output of Tomcat to the community?

Many thanks,
Christian.

In my case problem was in existing libraries for Tamino such as (c:\java\Tomcat3.3\xerces.jar ,c:\java\Tomcat3.3\TaminoAPI4J.jar …). The error appears NOT during setup but when i try to run i.e. property demo (http://localhost:8080/property …)

The error message sugested that Tamino DB is not running or path for DB was set wrong - but either database was running and path was set corectly.
If you wat to see the same message please copy TaminoAPI for Java jar to your Tomcat/lib directory.

I think I understand now, thank you for your efford to explain it to me.

I’d like to add an extra test for this error situation to improve the error message. But both the xerces and the tamino api jar file names change between individual version. Thus, I don’t know which jar files to test for. Plus: jar files in tomcat’s lib directory also change between different version of Tomcat.

In short: adding a test/special error message is very fagile and might event report none-problems.
Do you think you problem is very common? If not, I’d prefer to add no test …

Michael

Software AG Germany, Darmstadt

I belive that adding an “bold” note in installation part of documentation will be perfectly clear. I think it’s not very frequent problem but i had similar problem with previous version of XApplication (i belive even first preview of XApplication - there was a problem with JAXP libs), anyway note ibn documentation would be great.

Ok. The next version will have a bold hint in the Tomcat install instructions. Something like “Make sure there are no conflicting jar files in Tomcat’s common directory. Particularly dangerous are jaxp and tamino api jar files.”

Michael

Software AG Germany, Darmstadt

Thank You

hint has been added in X-Application 3.1.3.

Regards, Harald