cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Keerthip
‎04-24-2018
  • 10 Posts
  • 1 Likes Given
  • 0 Solutions
  • 3 Likes Received

Re: SAS WebApp installation issue- SAS 94 M5

by Fluorite | Level 6 in Administration and Deployment
‎03-09-2018 11:34 AM
‎03-09-2018 11:34 AM
Hi Juan,   i have checked logs in the mentioned path SASConfig/wap1/Lev1/Web/Logs/SASServer1_1. I am seeing the below errors:   ... 12 more 2018-03-09 13:27:21,265 [MasterServiceThread-0aac8edb-0a36-b43e-3346-958111edba11] WARN [unknown] com.sas.svcs.scheduling.server.impl.ScheduleManager - SAS Distributed In-Process Scheduling exception occurred. org.springframework.jms.UncategorizedJmsException: Uncategorized exception occurred during JMS processing; nested exception is com.atomikos.jms.AtomikosJMSException: Failed to grow the connection pool; nested exception is com.atomikos.datasource.pool.CreateConnectionException: error creating JMS connection at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316) at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469) at org.springframework.jms.core.JmsTemplate.receiveSelected(JmsTemplate.java:695) at org.springframework.jms.core.JmsTemplate.receiveSelected(JmsTemplate.java:687) at com.sas.scheduler.api.servers.ip.engine.mq.JMSClusterSupport$6.run(JMSClusterSupport.java:846) at java.lang.Thread.run(Thread.java:745) Caused by: com.atomikos.jms.AtomikosJMSException: Failed to grow the connection pool at com.atomikos.jms.AtomikosJMSException.throwAtomikosJMSException(AtomikosJMSException.java:55) at com.atomikos.jms.AtomikosConnectionFactoryBean.throwAtomikosJMSException(AtomikosConnectionFactoryBean.java:174) at com.atomikos.jms.AtomikosConnectionFactoryBean.createConnection(AtomikosConnectionFactoryBean.java:593) at org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:456) ... 4 more Caused by: com.atomikos.datasource.pool.CreateConnectionException: error creating JMS connection at com.atomikos.jms.AtomikosJmsXAConnectionFactory.createPooledConnection(AtomikosJmsXAConnectionFactory.java:61) at com.atomikos.datasource.pool.ConnectionPool.growPool(ConnectionPool.java:250) at com.atomikos.datasource.pool.ConnectionPool.borrowConnection(ConnectionPool.java:201) at com.atomikos.jms.AtomikosConnectionFactoryBean.createConnection(AtomikosConnectionFactoryBean.java:591) ... 6 more Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://xxxxxx.net:61616. Reason: java.net.ConnectException: Connection refused (Connection refused) at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:357) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:302) at org.apache.activemq.ActiveMQXAConnectionFactory.createXAConnection(ActiveMQXAConnectionFactory.java:60) at com.atomikos.jms.AtomikosJmsXAConnectionFactory.createPooledConnection(AtomikosJmsXAConnectionFactory.java:58) ... 9 more Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:344) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:501) at org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:464) at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) at org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:168) at org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58) at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:337) ... 12 more 2018-03-09 13:27:21,266 [MasterServiceThread-0aac8edb-0a36-b43e-3346-958111edba11] WARN [unknown] com.sas.svcs.scheduling.server.impl.ScheduleManager - SAS Distributed In-Process Scheduling exception occurred. org.springframework.jms.UncategorizedJmsException: Uncategorized exception occurred during JMS processing; nested exception is com.atomikos.jms.AtomikosJMSException: Failed to grow the connection pool; nested exception is com.atomikos.datasource.pool.CreateConnectionException: error creating JMS connection at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316) at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469) at org.springframework.jms.core.JmsTemplate.receiveSelected(JmsTemplate.java:695) at org.springframework.jms.core.JmsTemplate.receiveSelected(JmsTemplate.java:687) at com.sas.scheduler.api.servers.ip.engine.mq.JMSClusterSupport$6.run(JMSClusterSupport.java:846) at java.lang.Thread.run(Thread.java:745) Caused by: com.atomikos.jms.AtomikosJMSException: Failed to grow the connection pool at com.atomikos.jms.AtomikosJMSException.throwAtomikosJMSException(AtomikosJMSException.java:55) at com.atomikos.jms.AtomikosConnectionFactoryBean.throwAtomikosJMSException(AtomikosConnectionFactoryBean.java:174) at com.atomikos.jms.AtomikosConnectionFactoryBean.createConnection(AtomikosConnectionFactoryBean.java:593) at org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:456) ... 4 more Caused by: com.atomikos.datasource.pool.CreateConnectionException: error creating JMS connection at com.atomikos.jms.AtomikosJmsXAConnectionFactory.createPooledConnection(AtomikosJmsXAConnectionFactory.java:61) at com.atomikos.datasource.pool.ConnectionPool.growPool(ConnectionPool.java:250) at com.atomikos.datasource.pool.ConnectionPool.borrowConnection(ConnectionPool.java:201) at com.atomikos.jms.AtomikosConnectionFactoryBean.createConnection(AtomikosConnectionFactoryBean.java:591) ... 6 more Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://xxxxxx.net:61616. Reason: java.net.ConnectException: Connection refused (Connection refused) at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:357) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:302) at org.apache.activemq.ActiveMQXAConnectionFactory.createXAConnection(ActiveMQXAConnectionFactory.java:60) at com.atomikos.jms.AtomikosJmsXAConnectionFactory.createPooledConnection(AtomikosJmsXAConnectionFactory.java:58) ... 9 more Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:344) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) ... View more

Re: SAS WebApp installation issue- SAS 94 M5

by Fluorite | Level 6 in Administration and Deployment
‎03-09-2018 10:08 AM
‎03-09-2018 10:08 AM
Hi Juan   I found the below error in server.xml & catalina.out  under SASServer1_1. Could you infer anything from these logs?     Server.xml :   ... 6 more 2018-03-09 13:27:27,456 ERROR (Thread-129) [org.apache.catalina.startup.Catalina] Catalina.stop org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[-1]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:238) at org.apache.catalina.startup.Catalina.stop(Catalina.java:728) at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:829) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:238) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:814) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226) ... 2 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:238) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:483) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226) ... 4 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1002) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226) ... 6 more 2018-03-09 13:28:12,347 INFO (ResponseThread-0aac8edb-0a36-b43e-3346-958111edba11) [org.apache.catalina.loader.WebappClassLoaderBase] Illegal access: this web application instance has been stopped already. Could not load [org.springframework.jms.core.JmsTemplate$10]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.springframework.jms.core.JmsTemplate$10]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1305) at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1293)   catalina.out :  INFO [RMI TCP Connection(3)-10.54.180.62] - Metadata connection unavailable. Creating... 2018-03-09 13:27:11,264 [listenerContainer-1] ERROR [unknown] org.springframework.jms.listener.DefaultMessageListenerContainer - Could not refresh JMS Connection for destination 'topic://sas.jms.SASAOPCacheTopic' - retrying in 5000 ms. Cause: The JMS connection has failed: java.io.EOFException 2018-03-09 13:27:11,283 [DefaultMessageListenerContainer-1] ERROR [unknown] org.springframework.jms.listener.DefaultMessageListenerContainer - Could not refresh JMS Connection for destination 'topic://sas.jms.scheduler.pip.broadcastTopic' - retrying in 5000 ms. Cause: The JMS connection has failed: java.io.EOFException 2018-03-09 13:27:11,283 [schedulingListenerContainer-1] WARN [unknown] com.atomikos.jms.AtomikosJMSException - Error in proxy javax.jms.JMSException: java.io.EOFException 2018-03-09 13:27:14,895 ERROR (localhost-startStop-9) [org.apache.catalina.loader.WebappClassLoaderBase] Found RMI Target with stub class class [com.sas.metadata.remote.MdObjectListImpl_Stub] and value [MdObjectListImpl_Stub[UnicastRef [liveRef: [endpoint:xxxxxx.net:44130](local),objID:[1fdf52af:1620aaa0d8f:-7aa0, -3850858118489109859]]]]]. This RMI Target has been forcibly removed to prevent a memory leak. ... View more

Re: SAS WebApp installation issue- SAS 94 M5

by Fluorite | Level 6 in Administration and Deployment
‎03-09-2018 09:00 AM
‎03-09-2018 09:00 AM
I have checked that kb article. jdbc postgres is configured correctly in server.xml file. Issue is still there.. ... View more

SAS WebApp installation issue- SAS 94 M5

by Fluorite | Level 6 in Administration and Deployment
‎03-09-2018 08:55 AM
1 Like
‎03-09-2018 08:55 AM
1 Like
Hi All,   I am facing the below error while installing Web application server . Could you please help with this issue.   The following problem was encountered while configuring SAS Web Application Server Configuration: Application Server has started, however web applications with the following contexts failed to start. Please refer to Application Server logs for more details. PlatformWebServices.   For more information, see the log file located at  /SASConfig/wap1/Lev1/Logs/Configure/vfabrictcsvr_startMidtierServers_2018-03-09-13.26.56.log   Vfabric log :    [appserverTarget] 2018-03-09 13:32:08,235 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with PlatformWebServices context failed to start [appserverTarget] 2018-03-09 13:32:08,235 [main] INFO com.sas.appserver.vfabrictcsvr.Server - getFailedApps() >>> [appserverTarget] 2018-03-09 13:32:08,272 [main] INFO com.sas.appserver.utils.AppServerException - /en_US/AppServerMessages.properties does not exist. [appserverTarget] 2018-03-09 13:32:08,273 [main] INFO com.sas.appserver.vfabrictcsvr.Server - testServer() - Throwing AppServerException [appserverTarget] 2018-03-09 13:32:08,273 [main] INFO com.sas.appserver.vfabrictcsvr.Server - testServer() <<< [appserverTarget] 2018-03-09 13:32:08,279 [main] INFO com.sas.sdw.SDWExceptionHandler - handle() >>> [appserverTarget] 2018-03-09 13:32:08,279 [main] INFO com.sas.sdw.SDWExceptionHandler - handleSDWException() >>> [appserverTarget] 2018-03-09 13:32:08,279 [main] INFO com.sas.sdw.SDWExceptionHandler - target=startMidtierServers, task=com.sas.sdw.SDWExceptionHandler [appserverTarget] 2018-03-09 13:32:08,279 [main] INFO com.sas.sdw.SDWExceptionHandler - message=Application Server has started, however web applications with the following contexts failed to start. Please refer to Application Server logs for more details.</br><ul><li>PlatformWebServices</li></ul> [propertyfile] Updating property file: /sascommon/SAS/SASConfig/wap1/Lev1/Logs/Configure/vfabrictcsvr_config_status.properties [propertyfile] Updating property file: /sascommon/SAS/SASConfig/wap1/Lev1/Logs/Configure/vfabrictcsvr_config_status.properties 2018-03-09 13:32:08,287 [main] INFO com.sas.sdw.SDWExceptionHandler - configStatusFile set. 2018-03-09 13:32:08,293 [main] ERROR com.sas.sdw.SDWExceptionHandler - com.sas.appserver.utils.AppServerException: Application Server has started, however web applications with the following contexts failed to start. Please refer to Application Server logs for more details.</br><ul><li>PlatformWebServices ... View more

Re: SAS 9.4 M5 installation issue

by Fluorite | Level 6 in Administration and Deployment
‎03-08-2018 08:19 AM
‎03-08-2018 08:19 AM
Below is the object spawner log . Nothing is getting created under workspace server logs.   - Request made to cluster SASApp - Logical Workspace Server (A5EPZ598.AW000006). 2018-03-08T14:05:29,855 INFO [00021337] :xxxx - Redirect client in cluster SASApp - Logical Workspace Server (A5EPZ598.AW000006) to server SASApp - Workspace Server (A5EPZ598.AY00000C) at sesklsasgrndev01.emea.astrazeneca.net:8591. 2018-03-08T14:05:29,929 INFO [00021337] :xxxx - New out call client connection (109) for user sastrust@saspw. Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.54.180.61]:8561. 2018-03-08T14:05:29,983 INFO [00021337] :xxxx - There are no grid option sets defined for SAS application server "SASApp". 2018-03-08T14:05:29,984 INFO [00000009] :sas - Client connection 109 for user sastrust@saspw closed. 2018-03-08T14:05:30,038 INFO [00021337] :xxxx - New out call client connection (110) for user sastrust@saspw. Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.54.180.61]:8561. 2018-03-08T14:05:30,078 INFO [00000009] :sas - Client connection 110 for user sastrust@saspw closed. 2018-03-08T14:05:30,249 INFO [00021337] :xxxx- Created grid job 134 using credentials xxxx (child id 12). 2018-03-08T14:05:41,274 ERROR [00021264] :sas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (127). 2018-03-08T14:05:41,274 INFO [00021264] :sas - Grid job 134 owned by user xxxx (child id 12) has ended. 2018-03-08T14:05:41,274 ERROR [00021264] :sas - The specified uuid 0BEAF18C-292E-2548-ACAD-A4A86898FB0C did not match any process managed by this spawner. 2018-03-08T14:05:41,274 ERROR [00021337] :xxxx - The launch of server SASApp - Workspace Server for user xxxx failed. 2018-03-08T14:05:41,275 INFO [00021337] :sas - Client connection 108 for user xxxx closed. ... View more

Re: SAS 9.4 M5 installation issue

by Fluorite | Level 6 in Administration and Deployment
‎03-08-2018 08:09 AM
‎03-08-2018 08:09 AM
Yes , Object spawners are up. Still workspace servers are not validating from SAS Management console. But i am able to run sas code lines from linux host using ./sas -nodms. ... View more

SAS 9.4 M5 installation issue

by Fluorite | Level 6 in Administration and Deployment
‎03-08-2018 08:03 AM
‎03-08-2018 08:03 AM
Hi All,   We have done a fresh install of SAS 94 M5. All the sas services are up in Metadata and Grid control node. Object spawners are up in both the servers.   We are unable to validate SASApp Workspace server.   [3/8/18 2:01 PM] INFO: Starting extended validation for Workspace server (level 1) - Making a connection [3/8/18 2:01 PM] SEVERE: The launch of server SASApp - Workspace Server for user xxxxxx failed. [3/8/18 2:01 PM] SEVERE: Failed to start the server. [3/8/18 2:01 PM] SEVERE: The application could not connect to any server in the cluster "(xxxxxxx.net:8591,xxxxxxx1:8591)".   Could some one help me with this issue? ... View more

Re: SAS 9.4 M5 installation issue

by Fluorite | Level 6 in Administration and Deployment
‎02-20-2018 08:57 AM
1 Like
‎02-20-2018 08:57 AM
1 Like
We have setup the sasauth file using the following link:     Installation Note 49432: Configuring PAM on Linux to authenticate through SAS® against Active Directory or LDAP ... View more

SAS 9.4 M5 installation issue

by Fluorite | Level 6 in Administration and Deployment
‎02-16-2018 09:47 AM
1 Like
‎02-16-2018 09:47 AM
1 Like
Hi All,   We have started a fresh planned installation of our SAS 9.4 M5 on multi machine environment, We have installed metadata 1 & metadata2 (clustered )on different hosts successfully. We are facing issues while installing metadata 3  configuration files on  another host.Below is the error. sas account is already on the current host where installation is being started & the filesystem is shared across all the hosts.Any clues what is causing this issue?         validateUserHostAccount: [propertyfile] Updating property file: /SAS/SASConfig/meta3/Lev1/Logs/Configure/metadatasrvn_config_status.properties [propertyfile] Updating property file: /SAS/SASConfig/meta3/Lev1/Logs/Configure/metadatasrvn_config_status.properties      [exec] Current OS is Linux      [exec] Using input "********"      [exec] Executing '/SAS/SASHome/SASFoundation/9.4/utilities/bin/sasumgmt' with arguments:      [exec] '-stdio'      [exec] '-u'      [exec] 'sas'      [exec]      [exec] The ' characters around the executable and arguments are      [exec] not part of the command.      [exec] NOTE: Access denied.      [exec] Result: 1   [antcall] Exiting /SAS/SASHome/SASFoundation/9.4/misc/base/sasconf/metadatasrv/config/metadatasrv_config.xml.     ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎04-24-2018 10:30 AM
Likes given to
View All
Likes from
View All
Quick links