Weblogic Server 10.3.0 keystore error: inconsistent security configuration - certificate

Apologies I am a little out of my element with this one so hopefully have all the needed information here...
We run the following on our local developer test system: Weblogic Server 10.3.0 with Java 1.6.0_38.
I have a developer who is developing some code with a new payment processor and they need to import a self-signed certificate from the vendor, into the java keystore for Weblogic.
The Weblogic system is pretty out of the box. SSL doesn't even run on the managed servers. Our CMS vendor installed it (poorly) and there are a lot of defaults.
The developer attempted to import the cert a few times by doing the following...
He was provided a certificate from the vendor
He put it in a text file on the weblogic server (I checked this and it looked good)
He found the keystore (JKS) in the managed server config so he knew where to import it to
Got the keystore password (on second attempt)
He ran the following command to import the certificate into the keystore...
C:\Java\jdk1.6.0_20\bin\keytool -import -alias moneris_test_java -file K:\Java\jdk1.6.0_20\test_cert.der -keystore K:\apps\core\appserver\weblogic\config\teststore.jks
The password was correct and I can see both certificates (this one and one other) in the keystore.
I believe he had tried to recreate the keystore as well when there was no password found for the old one. He then went into the WLS console and updated the keystore passphrases to the new one he created.
I found him the password, we renamed the original keystore back to the original naming and we were able to import the new certificate. Doing a keytool -list we can see that both certificates are installed there. We also went back into WLS console and updated the passphrases to the correct one and also checked the file path was the same in Weblogic as what we had for the keystore.
Now whenever he tries to start his managed server we get he following. The ms starts but complains it cannot load the key and the application is unable to make a connection to the vendor.
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias testcert from the jks keystore file K:\bmapps\core\appserver\web
logic\config\teststore.jks.>
<Aug 20, 2013 4:03:23 PM PDT> <Alert> <Security> <BEA-090716> <Failed to retrieve identity key/certificate from keystore K:\bmapps\core\appserver\weblogic\config\teststore.jks under alias testcert on
server mec>
<Aug 20, 2013 4:03:23 PM PDT> <Error> <WebLogicServer> <BEA-000297> <Inconsistent security configuration, weblogic.management.configuration.ConfigurationException: Failed to retrieve identity key/cert
ificate from keystore K:\bmapps\core\appserver\weblogic\config\teststore.jks under alias testcert on server mec>
<Aug 20, 2013 4:03:23 PM PDT> <Emergency> <Security> <BEA-090034> <Not listening for SSL, java.io.IOException: Failed to retrieve identity key/certificate from keystore K:\bmapps\core\appserver\weblog
ic\config\teststore.jks under alias testcert on server mec.>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias testcert from the jks keystore file K:\bmapps\core\appserver\web
logic\config\teststore.jks.>
<Aug 20, 2013 4:03:23 PM PDT> <Alert> <Security> <BEA-090716> <Failed to retrieve identity key/certificate from keystore K:\bmapps\core\appserver\weblogic\config\teststore.jks under alias testcert on
server mec>
<Aug 20, 2013 4:03:23 PM PDT> <Error> <WebLogicServer> <BEA-000297> <Inconsistent security configuration, weblogic.management.configuration.ConfigurationException: Failed to retrieve identity key/cert
ificate from keystore K:\bmapps\core\appserver\weblogic\config\teststore.jks under alias testcert on server mec>
<Aug 20, 2013 4:03:23 PM PDT> <Emergency> <Security> <BEA-090034> <Not listening for SSL, java.io.IOException: Failed to retrieve identity key/certificate from keystore K:\bmapps\core\appserver\weblog
ic\config\teststore.jks under alias testcert on server mec.>
<Aug 20, 2013 4:03:23 PM PDT> <Warning> <Server> <BEA-002611> <Hostname "8LG63M1.mecnet.lcl", maps to multiple IP addresses: 172.16.79.6, 127.0.0.1>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.16.79.6:7010 for protocols iiop, t3, ldap, snmp, http.>
<Aug 20, 2013 4:03:23 PM PDT> <Warning> <Server> <BEA-002611> <Hostname "local.mec.ca", maps to multiple IP addresses: 172.16.79.6, 127.0.0.1>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7010 for protocols iiop, t3, ldap, snmp, http.>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "mec" for domain "bluemartini" running in Development Mode>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Aug 20, 2013 4:03:23 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

When the cert was imported, the alias used was "moneris_test_java" while WebLogic is looking for "testcert", so that might be one problem.
Additionally, I don't see anywhere that the corresponding private key was imported into the keystore. Can you check if it was or not? If this is being used as an identity keystore for the server, both a private key and corresponding certificate will be needed.

Related

Why does Eclipse sometimes hang when my program connects to JBoss

Sometimes when I run my project, that connects to JBoss, it will hang.
For example here is the log output for when it hangs:
Dec 14, 2021 11:57:58 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.5.Final
Dec 14, 2021 11:57:58 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
Dec 14, 2021 11:57:58 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
Dec 14, 2021 11:57:58 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
Dec 14, 2021 11:57:58 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 2 and marshalling strategies [river]
Dec 14, 2021 11:57:58 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext#29f5ca0b, receiver=Remoting connection EJB receiver [connection=Remoting connection <71c88986>,channel=jboss.ejb,nodename=DevApp00:DevApp00]} on channel Channel ID ec955d48 (outbound) of Remoting connection 04a8743d to devapp00.magcore.XXXXXXXXXXXXX.com/XX.XX.XX.XXX:XXXX
Dec 14, 2021 11:57:59 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 2 and marshalling strategies [river]
Dec 14, 2021 11:57:59 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext#29f5ca0b, receiver=Remoting connection EJB receiver [connection=Remoting connection <6d5bcb39>,channel=jboss.ejb,nodename=DevApp01:DevApp01]} on channel Channel ID c9163bbe (outbound) of Remoting connection 50ba181a to devapp01.magcore.XXXXXXXXXXXXX.com/XX.XX.XX.XXX:XXXX
Dec 14, 2021 11:57:59 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 2 and marshalling strategies [river]
Dec 14, 2021 11:57:59 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext#29f5ca0b, receiver=Remoting connection EJB receiver [connection=Remoting connection <7900f3c9>,channel=jboss.ejb,nodename=DevApp01:DevApp01]} on channel Channel ID aa5e4733 (outbound) of Remoting connection 6075ef24 to /XX.XX.XX.XXX:XXXX
Here is the log output when it doesn't hang:
Dec 14, 2021 11:58:42 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.5.Final
Dec 14, 2021 11:58:42 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
Dec 14, 2021 11:58:42 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
Dec 14, 2021 11:58:42 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 2 and marshalling strategies [river]
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext#4ae0a5dc, receiver=Remoting connection EJB receiver [connection=Remoting connection <71ed5401>,channel=jboss.ejb,nodename=DevApp00:DevApp00]} on channel Channel ID b0b91086 (outbound) of Remoting connection 11244593 to devapp00.magcore.XXXXXXXXXXXXX.com/XX.XX.XX.XXX:XXXX
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 2 and marshalling strategies [river]
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext#4ae0a5dc, receiver=Remoting connection EJB receiver [connection=Remoting connection <3f7dbbe3>,channel=jboss.ejb,nodename=DevApp01:DevApp01]} on channel Channel ID a49da456 (outbound) of Remoting connection 7900f3c9 to devapp01.magcore.XXXXXXXXXXXXX.com/XX.XX.XX.XXX:XXXX
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.ClusterContext registerEJBReceiver
INFO: Added a new EJB receiver in cluster context ejb for node DevApp01:DevApp01. Total nodes in cluster context = 1
Dec 14, 2021 11:58:43 AM org.jboss.ejb.client.ClusterContext registerEJBReceiver
INFO: Added a new EJB receiver in cluster context ejb for node DevApp00:DevApp00. Total nodes in cluster context = 2
Here is my jboss-ejb-client.properties
endpoint.name=client-endpoint
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
invocation.timeout=3000
reconnect.tasks.timeout=2000
remote.connections=dev1,dev2
remote.clusters=ejb
# Dev1 - Node 1
remote.connection.dev1.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.dev1.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL=300000
remote.connection.dev1.host=devapp00.magcore.XXXXXXXXXXXXX.com
remote.connection.dev1.port=XXXX
remote.connection.dev1.username=XXXXXXXXXX
remote.connection.dev1.password=XXXXXXXXXX
# Dev2 - Node 2
remote.connection.dev2.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.dev2.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL=300000
remote.connection.dev2.host=devapp01.magcore.XXXXXXXXXXXXX.com
remote.connection.dev2.port=XXXX
remote.connection.dev2.username=XXXXXXXXXX
remote.connection.dev2.password=XXXXXXXXXX
# cluster 1
remote.cluster.ejb.connect.timeout=2500
remote.cluster.ejb.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.cluster.ejb.connect.options.org.xnio.Options.SSL_ENABLED=false
remote.cluster.ejb.username=XXXXXXXXXX
#Dev Password
remote.cluster.ejb.password=XXXXXXXXXX
This morning I tried 26 times and is hung every time, but it doesn't always hang.
If I deploy this via WebStart, it seems to work just fine.
Interestingly, it seems as if it is hanging on setting up the cluster. I don't know why I didn't see this before, but it doesn't really help me solve the problem.

Missing mandatory element error in the uv4l streaming server

I'm trying to get the RPi streaming video to Janus server over the internet architecture.
Firstly, I have installed and configured the UV4L streaming server in the RPi zero, just like the linux project mentioned, and the ip:port/stream is working perfectly fine, and i can rtc the video in local network.
Now, I need the communication to happen over internet, so I have a janus server setup in the server.
In the RPi UV4L server, I first wanted to try the stream to the public Janus server first, so I tried doing it using the "Join the room with janus", but when I click start, I get logs
Oct 27 04:52:52 DevIoT uv4l[7990]: <notice> [server] HTTP/HTTPS Streaming & WebRTC Signalling Server v1.1.125 built on Sep 5 2019
Oct 27 04:52:52 DevIoT uv4l[7990]: <warning> [server] SSL is not enabled for the Streaming Server. Using unsecure HTTP.
Oct 27 04:52:52 DevIoT uv4l[7990]: <notice> [core] Streaming Server loaded!
Oct 27 04:52:52 DevIoT uv4l[7990]: <warning> [core] Cannot create /dev/video0 because file already exists
Oct 27 04:52:52 DevIoT uv4l[7990]: <notice> [core] Registering device node /dev/video1
Oct 27 04:52:52 DevIoT uv4l[7990]: <notice> [server] Web Streaming Server listening on port 8080
Oct 27 04:53:22 DevIoT uv4l[7990]: <notice> [webrtc] WebRTC Renderer extension successfully loaded
Oct 27 04:53:22 DevIoT uv4l[7990]: <notice> [server] WebRTC, Signalling Server and STUN Server extensions successfully loaded
Oct 27 04:53:26 DevIoT uv4l[7990]: <warning> [server] Missing mandatory element (admin_key)
Oct 27 04:53:33 DevIoT uv4l[7990]: <warning> [server] Janus session error: Missing mandatory element (admin_key)
Oct 27 04:53:33 DevIoT uv4l[7990]: <notice> [server] Waiting for 3 seconds before reconnecting to https://janus.conf.meetecho.com...
Please tell me how to resolve it? or What I'm doing wrong here? Or any alternative solutions, I need the RTC from rpi to a public server.

how to run springboot maven project in weblogic from eclipse for development

i have a springboot webservices project created in eclipse neon and working fine with embeded tomcat provided by spring boot, but i want my spring-boot maven webservices project to be run on weblogic instead of tomcat because at the end of the day we are going to deploy our project in welogic as a webservices which will be used by angulr5 ui.
what i tried so far.
my pom.xml looks something like this.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>springboot</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>war</packaging>
<name>springboot</name>
<description>Demo project for Spring Boot</description>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>1.5.9.RELEASE</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<java.version>1.8</java.version>
</properties>
<dependencies>
<!-- <dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>-->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<exclusions>
<exclusion>
<artifactId>tomcat-embed-el</artifactId>
<groupId>org.apache.tomcat.embed</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-tomcat</artifactId>
<scope>provided</scope>
<exclusions>
<exclusion>
<artifactId>tomcat-embed-el</artifactId>
<groupId>org.apache.tomcat.embed</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
</plugins>
</build>
</project>
my src->main->webapp->WEB-INF->weblogic.xml is,
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
http://xmlns.oracle.com/weblogic/weblogic-web-app
http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd">
<wls:container-descriptor>
<wls:prefer-application-packages>
<wls:package-name>org.slf4j.*</wls:package-name>
</wls:prefer-application-packages>
</wls:container-descriptor>
</wls:weblogic-web-app>
i'm getting this error.
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000
.
CLASSPATH=C:\PROGRA~1\Java\JDK18~1.0_1\lib\tools.jar;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\net.sf.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\modules\features\oracle.wls.common.nodemanager.jar;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derbynet.jar;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derby.jar
.
PATH=C:\Oracle\MIDDLE~1\ORACLE~1\USER_P~1\domains\BASE_D~1\bin;;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\bin;C:\Oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\org.apache.ant_1.9.2\bin;C:\PROGRA~1\Java\JDK18~1.0_1\jre\bin;C:\PROGRA~1\Java\JDK18~1.0_1\bin;C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64\oci920_8;C:\PROGRA~1\Java\JRE18~1.0_1\bin\server;C:\PROGRA~1\Java\JRE18~1.0_1\bin;C:\PROGRA~1\Java\JRE18~1.0_1\lib\amd64;C:\PROGRA~3\Oracle\Java\javapath;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WINDOW~1\v1.0\;C:\PROGRA~1\TORTOI~1\bin;C:\PROGRA~1\Intel\WiFi\bin\;C:\PROGRA~1\COMMON~1\Intel\WIRELE~1\;C:\PROGRA~1\nodejs\;C:\PROGRA~1\Java\JDK18~1.0_1\bin;D:\softwares\apache-maven-3.5.2-bin\apache-maven-3.5.2\bin;C:\Users\Adarsha\AppData\Local\MICROS~1\WINDOW~1;C:\Users\Adarsha\AppData\Roaming\npm;C:\PROGRA~1\Java\JDK18~1.0_1\bin;D:\softwares\apache-maven-3.5.2-bin\apache-maven-3.5.2\bin;C:\PROGRA~1\MICROS~2\bin;D:\softwares\eclipse
.
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
***************************************************
Starting WLS with line:
C:\PROGRA~1\Java\JDK18~1.0_1\bin\java -server -Xms256m -Xmx512m -XX:CompileThreshold=8000 -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.policy -Xverify:none -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -javaagent:C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\debugpatch-agent.jar -da -Dwls.home=C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server -Dweblogic.home=C:\Oracle\MIDDLE~1\ORACLE~1\wlserver\server weblogic.Server
<16 Jan, 2018 5:18:57 PM SGT> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<16 Jan, 2018 5:18:58 PM SGT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<16 Jan, 2018 5:18:58 PM SGT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 25.152-b16 from Oracle Corporation.>
<16 Jan, 2018 5:18:58 PM SGT> <Info> <RCM> <BEA-2165021> <"ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>
<16 Jan, 2018 5:18:59 PM SGT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.2.1.2.0 Mon Oct 3 04:35:36 PDT 2016 1827450>
<16 Jan, 2018 5:19:00 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<16 Jan, 2018 5:19:00 PM SGT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<16 Jan, 2018 5:19:00 PM SGT> <Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.>
<16 Jan, 2018, 5:19:01,707 PM SGT> <Notice> <Log Management> <BEA-170019> <The server log file weblogic.logging.FileStreamHandler instance=1211306809
Current log file=C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log
Rotation dir=C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\servers\AdminServer\logs
is opened. All server side log events will be written to this file.>
<16 Jan, 2018, 5:19:01,927 PM SGT> <Notice> <Security> <BEA-090946> <Security pre-initializing using security realm: myrealm>
<16 Jan, 2018, 5:19:02,215 PM SGT> <Notice> <Security> <BEA-090947> <Security post-initializing using security realm: myrealm>
<16 Jan, 2018, 5:19:02,729 PM SGT> <Notice> <Security> <BEA-090082> <Security initialized using administrative security realm: myrealm>
<16 Jan, 2018, 5:19:03,304 PM SGT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://192.168.0.221:7001/jndi/weblogic.management.mbeanservers.runtime.>
<16 Jan, 2018, 5:19:03,850 PM SGT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://192.168.0.221:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
<16 Jan, 2018, 5:19:04,93 PM SGT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://192.168.0.221:7001/jndi/weblogic.management.mbeanservers.edit.>
<16 Jan, 2018, 5:19:04,842 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<16 Jan, 2018, 5:19:04,843 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<16 Jan, 2018, 5:19:04,886 PM SGT> <Notice> <Log Management> <BEA-170036> <The Logging monitoring service timer has started to check for logged message counts every 30 seconds.>
<16 Jan, 2018, 5:19:08,402 PM SGT> <Error> <HTTP> <BEA-101165> <Could not load user defined filter in web.xml: weblogic.websocket.tyrus.TyrusServletFilter.
java.lang.ClassCastException: org.apache.tomcat.websocket.server.WsServerContainer cannot be cast to org.glassfish.tyrus.server.TyrusServerContainer
at weblogic.websocket.tyrus.TyrusServletFilter.init(TyrusServletFilter.java:80)
at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:400)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
Truncated. see log file for complete stacktrace
>
<16 Jan, 2018, 5:19:08,425 PM SGT> <Notice> <Log Management> <BEA-170027> <The server has successfully established a connection with the Domain level Diagnostic Service.>
<16 Jan, 2018, 5:19:08,472 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>
<16 Jan, 2018, 5:19:08,678 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>
<16 Jan, 2018, 5:19:08,738 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,143 PM SGT> <Warning> <Server> <BEA-002611> <The hostname "Adarsha", maps to multiple IP addresses: 192.168.0.221, fe80:0:0:0:20a3:a0e4:2ddb:1b94%20, fe80:0:0:0:3c28:330d:88b4:e09d%7, 2001:0:9d38:6abd:3c28:330d:88b4:e09d.>
<16 Jan, 2018, 5:19:10,145 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 2001:0:9d38:6abd:3c28:330d:88b4:e09d:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,149 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,157 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.221:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,158 PM SGT> <Notice> <WebLogicServer> <BEA-000331> <Started the WebLogic Server Administration Server "AdminServer" for domain "base_domain" running in development mode.>
<16 Jan, 2018, 5:19:10,158 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,159 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 2001:0:9d38:6abd:3c28:330d:88b4:e09d:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,160 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,161 PM SGT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.221:7001 for protocols iiop, t3, ldap, snmp, http.>
<16 Jan, 2018, 5:19:10,165 PM SGT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<16 Jan, 2018, 5:19:10,178 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
<16 Jan, 2018, 5:19:15,339 PM SGT> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Initializing callbacks>
<16 Jan, 2018, 5:19:15,341 PM SGT> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Added MBeanServerConnection in DomainRuntimeServiceMBean >
<16 Jan, 2018, 5:19:15,342 PM SGT> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Callback is done>
<16 Jan, 2018, 5:19:15,344 PM SGT> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Connection already exists for the server. Did not attempt to connect to the server>
<16 Jan, 2018, 5:19:15,470 PM SGT> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=All Servers : Resolving connection list DomainRuntimeServiceMBean>
<16 Jan, 2018, 5:19:36,553 PM SGT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "142248479790392" for task "2" on [partition-name: DOMAIN]. Error is: "weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.apache.tomcat.websocket.pojo.PojoEndpointBase"
weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.apache.tomcat.websocket.pojo.PojoEndpointBase
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: org.apache.tomcat.websocket.pojo.PojoEndpointBase
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:1026)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:987)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:83)
at weblogic.utils.classloaders.GenericClassLoader.doFindClass(GenericClassLoader.java:608)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:540)
Truncated. see log file for complete stacktrace
>
<16 Jan, 2018, 5:19:36,568 PM SGT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application "_auto_generated_ear_" on [partition-name: DOMAIN].>
<16 Jan, 2018, 5:19:36,575 PM SGT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating start task for application "_auto_generated_ear_".>
<16 Jan, 2018, 5:19:36,575 PM SGT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.apache.tomcat.websocket.pojo.PojoEndpointBase
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: org.apache.tomcat.websocket.pojo.PojoEndpointBase
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:1026)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:987)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:83)
at weblogic.utils.classloaders.GenericClassLoader.doFindClass(GenericClassLoader.java:608)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:540)
Truncated. see log file for complete stacktrace
Please help me resolve this.

RemoteException in connecting to Tomee (OpenEJB)

Working from the hello world sample, what can I do on tleilax to allow doge to connect to the locally running OpenEJB server? I've read through the documentation on how startup OpenEJB, but must be missing a step from the manual.
On tleilax, deploying Hello.jar:
thufir#tleilax:~$ openejb deploy Hello.jar
Mar 07, 2015 10:34:30 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=ejbd://localhost:4201}
Mar 07, 2015 10:34:31 PM org.apache.openejb.client.EventLogger log
INFO: ConnectionOpened{uri=ejbd://localhost:4201}
Mar 07, 2015 10:34:31 PM org.apache.openejb.client.EventLogger log
INFO: ServerAdded{server=ejbds://127.0.0.1:4203} ClusterMetaDataUpdated{provider=ejbd://localhost:4201, version=1425796337772, uris=2}
Mar 07, 2015 10:34:31 PM org.apache.openejb.client.EventLogger log
INFO: ServerAdded{server=ejbd://127.0.0.1:4201} ClusterMetaDataUpdated{provider=ejbd://localhost:4201, version=1425796337772, uris=2}
Mar 07, 2015 10:34:31 PM org.apache.openejb.client.EventLogger log
INFO: ServerRemoved{server=ejbd://localhost:4201} ClusterMetaDataUpdated{provider=ejbd://localhost:4201, version=1425796337772, uris=2}
Application deployed successfully at "Hello.jar"
App(id=/home/thufir/apache-openejb-4.7.1/apps/Hello.jar)
EjbJar(id=Hello, path=/home/thufir/apache-openejb-4.7.1/apps/Hello.jar)
Ejb(ejb-name=HelloBean, id=HelloBean)
Jndi(name=HelloBeanRemote)
Jndi(name=global/Hello/HelloBean!org.acme.Hello)
Jndi(name=global/Hello/HelloBean)
some output from tleilax openejb showing the deploy:
INFO: OpenWebBeans Container has started, it took 241 ms.
Mar 07, 2015 10:34:32 PM org.apache.openejb.assembler.classic.Assembler startEjbs
INFO: Created Ejb(deployment-id=HelloBean, ejb-name=HelloBean, container=My Stateless Container)
Mar 07, 2015 10:34:32 PM org.apache.openejb.assembler.classic.Assembler startEjbs
INFO: Started Ejb(deployment-id=HelloBean, ejb-name=HelloBean, container=My Stateless Container)
Mar 07, 2015 10:34:32 PM org.apache.openejb.assembler.classic.Assembler createApplication
INFO: Deployed Application(path=/home/thufir/apache-openejb-4.7.1/apps/Hello.jar)
scanning tleilax for open ports:
thufir#doge:~$
thufir#doge:~$ nmap 192.168.1.3
Starting Nmap 6.46 ( http://nmap.org ) at 2015-03-07 22:42 PST
Nmap scan report for 192.168.1.3
Host is up (0.00092s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
22/tcp open ssh
119/tcp open nntp
Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
thufir#doge:~$
the bound services on tleilax:
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager start
INFO: ** Bound Services **
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: NAME IP PORT
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: httpejbd 127.0.0.1 4204
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: multipoint 127.0.0.1 4212
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: admin 127.0.0.1 4200
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: ejbd 127.0.0.1 4201
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: multicast 239.255.2.3 6142
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: ejbds 127.0.0.1 4203
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager printRow
INFO: multipulse 239.255.2.3 6142
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager start
INFO: -------
Mar 07, 2015 10:32:17 PM org.apache.openejb.server.SimpleServiceManager start
INFO: Ready!
So, the server is ready on tleilax. Why can't the client connect properly?
thufir#doge:~$
thufir#doge:~$ java -classpath .:NetBeansProjects/HelloClient/dist/HelloClient.jar:apache-openejb-4.7.1/lib/openejb-client-4.7.1.jar:netbeans-8.0.2/enterprise/modules/ext/javaee-api-7.0.jar org.acme.HelloClient
Mar 07, 2015 10:49:46 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=ejbd://192.168.1.3:4201}
Mar 07, 2015 10:49:46 PM org.apache.openejb.client.EventLogger log
WARNING: ConnectionFailed{uri=ejbd://192.168.1.3:4201 cause=java.io.IOException: Cannot connect to server 'ejbd://192.168.1.3:4201'. Check that the server is started and that the specified serverURL is correct.}
Mar 07, 2015 10:49:46 PM org.apache.openejb.client.EventLogger log
WARNING: BootstrappingConnection{provider=ejbd://192.168.1.3:4201}
Mar 07, 2015 10:49:46 PM org.apache.openejb.client.EventLogger log
WARNING: ConnectionFailed{uri=ejbd://192.168.1.3:4201 cause=java.io.IOException: Cannot connect to server 'ejbd://192.168.1.3:4201'. Check that the server is started and that the specified serverURL is correct.}
Mar 07, 2015 10:49:46 PM org.apache.openejb.client.EventLogger log
SEVERE: ConnectionStrategyFailed{strategy=StickyConnectionStrategy, cluster=org.apache.openejb.client.ClusterMetaData#7d261f7f, server=ejbd://192.168.1.3:4201}
Exception in thread "main" javax.naming.NamingException: Cannot lookup '/HelloBeanRemote'. [Root exception is java.rmi.RemoteException: Unable to connect; nested exception is:
java.io.IOException: Cannot connect to server 'ejbd://192.168.1.3:4201'. Check that the server is started and that the specified serverURL is correct.]
at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:405)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at org.acme.HelloClient.main(HelloClient.java:16)
Caused by: java.rmi.RemoteException: Unable to connect; nested exception is:
java.io.IOException: Cannot connect to server 'ejbd://192.168.1.3:4201'. Check that the server is started and that the specified serverURL is correct.
at org.apache.openejb.client.Client.processRequest(Client.java:167)
at org.apache.openejb.client.Client.request(Client.java:141)
at org.apache.openejb.client.JNDIContext.request(JNDIContext.java:211)
at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:399)
... 2 more
Caused by: java.io.IOException: Cannot connect to server 'ejbd://192.168.1.3:4201'. Check that the server is started and that the specified serverURL is correct.
at org.apache.openejb.client.SocketConnectionFactory$SocketConnection.failure(SocketConnectionFactory.java:334)
at org.apache.openejb.client.SocketConnectionFactory$SocketConnection.open(SocketConnectionFactory.java:308)
at org.apache.openejb.client.SocketConnectionFactory.getConnection(SocketConnectionFactory.java:162)
at org.apache.openejb.client.ConnectionManager.getConnection(ConnectionManager.java:112)
at org.apache.openejb.client.AbstractConnectionStrategy.connect(AbstractConnectionStrategy.java:105)
at org.apache.openejb.client.AbstractConnectionStrategy.connect(AbstractConnectionStrategy.java:81)
at org.apache.openejb.client.ConnectionManager.getConnection(ConnectionManager.java:88)
at org.apache.openejb.client.Client.processRequest(Client.java:165)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
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.openejb.client.SocketConnectionFactory$SocketConnection.open(SocketConnectionFactory.java:300)
... 11 more
thufir#doge:~$
thufir#doge:~$
For what it's worth, I checked that the HelloClient runs locally from tleilax fine:
thufir#tleilax:~$
thufir#tleilax:~$ java -classpath .:HelloClient.jar:apache-openejb-4.7.1/lib/openejb-client-4.7.1.jar:netbeans-8.0.2/enterprise/modules/ext/javaee-api-7.0.jar org.acme.HelloClient
Mar 07, 2015 10:56:46 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=ejbd://127.0.0.1:4201}
Mar 07, 2015 10:56:46 PM org.apache.openejb.client.EventLogger log
INFO: ConnectionOpened{uri=ejbd://127.0.0.1:4201}
Mar 07, 2015 10:56:46 PM org.apache.openejb.client.EventLogger log
INFO: ServerAdded{server=ejbds://127.0.0.1:4203} ClusterMetaDataUpdated{provider=ejbd://127.0.0.1:4201, version=1425796337772, uris=2}
Hello World!!!!
thufir#tleilax:~$
Of course, the client running locally on tleilax connects to 127.0.0.1, while the client on doge connects, or tries to connect, to the ip adress for tleilax: 192.168.1.3; the ip address is hardcoded in the sample.

How do I run a web application using SpringSource Toolsuite?

I'd like to run my Spring application using STS, but I have no idea how to do that. I see the tc server instance, and I can run it, but this does not start my application. I've tried dragging my project workspace onto it, but that hasn't worked either. I've right-clicked and read/checked out all of the options on the context-sensitive menu, but I don't see anything to run my project inside tc server. Does anyone know how?
EDIT:
This is what I get when running the project. I see nothing about my project's war at all. It is included as a "web module" when I check out the tc server settings though. And it does have a web.xml and all of that other good stuff. The project works fine in maven's tomcat goal and inside IDEA. I am just having problems getting it to run in eclipse.
Mar 30, 2012 3:35:51 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tc Runtime property decoder using memory-based key
Mar 30, 2012 3:35:51 PM com.springsource.tcserver.security.PropertyDecoder <init>
INFO: tcServer Runtime property decoder has been initialized in 206 ms
Mar 30, 2012 3:35:52 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 30, 2012 3:35:52 PM com.springsource.tcserver.serviceability.rmi.JmxSocketListener init
INFO: Started up JMX registry on 127.0.0.1:6969 in 65 ms
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 741 ms
Mar 30, 2012 3:35:52 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 30, 2012 3:35:52 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: VMware vFabric tc Runtime 2.6.3.RELEASE/7.0.23.A.RELEASE
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\Users\me\Documents\workspace-sts-2.9.0.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\conf\Catalina\localhost\trainingdividend.xml
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:trainingdividend' did not find a matching property.
Mar 30, 2012 3:35:52 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\me\Documents\workspace-sts-2.9.0.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\webapps\insight.war
Mar 30, 2012 3:35:52 PM com.springsource.insight.collection.tcserver.ltw.TomcatWeavingInsightClassLoader start
INFO: Context [localhost|insight] will not be woven
Mar 30, 2012 3:35:53 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Mar 30, 2012 3:36:03 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'Spring MVC Dispatcher Servlet'
Mar 30, 2012 3:36:05 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Mar 30, 2012 3:36:05 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 13468 ms
If you are missing the Run As > Run on Server option, then chances are your project does not have the Dynamic Web Module facet.
I was running into 404 errors in my J2ee project, created using Dynamic WebModules. Initially I thought it was a context problem, as the url that STS was attempting to run was quite wrong. However the project the context was correct. But needed to get rid of the errors shown in the markers tab (which may not stop attempts to run as Server) before I made any progress.
After resolving obvious code, jar,path errors, I then check if I can export a war file correctly. If not, it is usually an issue in the DEPLOYMENT ASSEMBLY portion of the projects properties (at least in my Java project). Specifying the class files and jars from required projects is needed to get the correct war file structure. Once accomplished, bye bye 404s