Tomcat 4.0b3 on Ultra 5 Solaris 8 Seg Fault at startup

[Glenn McAllister <gl...@somanetworks.com>]

Hey all.

I've searched the archives and the faq is down, so I'm posting my
problem here.  My appologies if this is a known issue, I'm more than
happy to RTFM if someone would point me in the right direction.

My setup is

- SunOS  5.8 Generic_108528-06 sun4u sparc SUNW,Ultra-5_10  (Solaris 8)
- java version "1.2.1"  Solaris VM (build Solaris_JDK_1.2.1_03, native
threads, sunwjit)
- Tomcat 4.0-b3 standalone from tarball - no integration with Apache,
not built from source.

Its a plain vanilla tomcat install that works just fine on my RH7,
Blackdown 1.2.2 setup.  When I run $CATALINA_HOME/bin/startup.sh, I get
the following in logs/catalina.out:

Starting service Tomcat-Standalone
Apache Tomcat/4.0-b3
Segmentation Fault
    si_signo [11]: Segmentation Fault
    si_errno [0]: Error 0
    si_code [1]: SEGV_MAPERR [addr: 0x28]

 stackpointer=FFBECFB0

Exiting Thread (sys_thread_t:0xff304708) : no stack
"Finalizer" (TID:0x121d2c, sys_thread_t:0x121cb0, state:CW, thread_t:
t@6, threadID:0xfeca1d78, stack_bottom:0xfeca2000, stack_size:0x20000)
prio=8

[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:106)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:128)
[3] java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:175)
-------------------
"Reference Handler" (TID:0x12e64c, sys_thread_t:0x12e5d0, state:CW,
thread_t: t@5, threadID:0xfecd1d78, stack_bottom:0xfecd2000,
stack_size:0x20000) prio=10

[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:107)
-------------------
"Signal dispatcher" (TID:0x10e25c, sys_thread_t:0x10e1e0, state:MW,
thread_t: t@4, threadID:0xfed21d78, stack_bottom:0xfed22000,
stack_size:0x20000) prio=10

-------------------
"main" (TID:0x39e94, sys_thread_t:0x39e18, state:R, thread_t: t@1,
threadID:0x25200, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
*current thread*

[1]
org.apache.catalina.loader.StandardLoader.start(StandardLoader.java:586)

[2]
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1028)
[3]
org.apache.catalina.core.StandardContext.start(StandardContext.java:3054)

[4]
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1028)
[5]
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1028)
[6]
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:253)
[7]
org.apache.catalina.core.StandardService.start(StandardService.java:341)

[8]
org.apache.catalina.core.StandardServer.start(StandardServer.java:447)
[9] org.apache.catalina.startup.Catalina.start(Catalina.java:707)
[10] org.apache.catalina.startup.Catalina.execute(Catalina.java:627)
[11] org.apache.catalina.startup.Catalina.process(Catalina.java:177)
[12] java.lang.reflect.Method.invoke(Native Method)
[13] org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:114)
-------------------

Can anyone help me out, point me in the right direction, whatever? :-)

Thanks.

Glenn McAllister
SOMA Networks, Inc.

Tomcat in VisualAge for Java

[Mandy Chan <my...@hotmail.com>]

Hi...

I'm working on integrating Tomcat into the latest version of the VisualAge
for Java 3.5.3 IDE and was wondering if there was a preference for which
Tomcat version people would like to see/use?  The latest release build of
Tomcat 3.2.1 or the latest milestone build of 4.0?

This would be a free downloadable component for which VisualAge for Java
users can install over their development environment.

Thanks for any of your comments in advance, Mandy

Re: Tomcat 4.0b3 on Ultra 5 Solaris 8 Seg Fault at startup

[Glenn McAllister <gl...@somanetworks.com>]

Glenn McAllister wrote:

> Hey all.
>
> I've searched the archives and the faq is down, so I'm posting my
> problem here.  My appologies if this is a known issue, I'm more than
> happy to RTFM if someone would point me in the right direction.

Although I didn't get a response, I did get on the right track when I tried
a different JVM.  I got the more often encountered bus error, and searching
in the archives turned up the fact that we needed to use at least the
1.2.2_5 version of the JVM.  I installed the 1.2.2_7 version, and everything
is fine.

Did I miss a pointer in the docs to say which JVM to use?

Glenn