Tamz SJVSTC not shutting down with P/STOP command

Products

• Trusted Access Manager for Mainframe

Issue/Introduction

I had noticed this last week & assumed I had done something wrong, but this does look like a problem...

P STVSTC issued command amd there no signs of it terminating. In the log, found the following exception:

.Exception in thread "Thread-2" java.lang.NoClassDefFoundError: ch.qos.logback.classic.spi.CallerData     
..at ch.qos.logback.classic.spi.LoggingEvent.getCallerData(LoggingEvent.java:259)                         
..at ch.qos.logback.classic.pattern.FileOfCallerConverter.convert(FileOfCallerConverter.java:22)          
..at ch.qos.logback.classic.pattern.FileOfCallerConverter.convert(FileOfCallerConverter.java:19)          
..at ch.qos.logback.core.pattern.FormattingConverter.write(FormattingConverter.java:36)                   
..at ch.qos.logback.core.pattern.PatternLayoutBase.writeLoopOnConverters(PatternLayoutBase.java:115)      
..at ch.qos.logback.classic.PatternLayout.doLayout(PatternLayout.java:165)                                
..at ch.qos.logback.classic.PatternLayout.doLayout(PatternLayout.java:39)                                 
..at ch.qos.logback.core.encoder.LayoutWrappingEncoder.encode(LayoutWrappingEncoder.java:116)             
..at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:230)                    
..at ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:235)              
..at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:102)                       
..at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:84)          
..at ch.qos.logback.core.sift.SiftingAppenderBase.append(SiftingAppenderBase.java:110)                    
..at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:82)                                      
..at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) 
..at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270)                                 
..at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257)                                         
..at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421)                            
..at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383)                                
..at ch.qos.logback.classic.Logger.debug(Logger.java:482)                                                 
..at com.ca.security.sjvm.main.Application.shutdown(Application.java:89)                                  
..at com.ca.security.sjvm.main.Main$1.run(Main.java:358)                                                  
.Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.CallerData                       
..at java.net.URLClassLoader.findClass(URLClassLoader.java:610)                                           
..at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:948)                                          
..at java.lang.ClassLoader.loadClass(ClassLoader.java:893)                                                
..at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)                                        
..at java.lang.ClassLoader.loadClass(ClassLoader.java:876)                                                
..... 22 more                                                                                             

 

Environment

Release : 1.1

Resolution

Based on symptoms from the staging job (NMOUNT/COPY/MOUNT), that is definitely the culprit. Sites cannot unmount and remount a ZFS out from under a running JVM and expect it to behave properly afterwards. Tasks must be stopped prior to the unmount.