Issue: WAS app server v7 does not start in Spring STS. It gets to 100% and just continues to say "launching delegate" and in the system.out file has the standard "open for business" but the server itself in STS never gets to a "Started" status state.
Platform: STS-3.8, Always tried on eclipse neon.
Plugin: IBM WebSphere Application Server Traditional V7.X Developer Tools for Neon
WAS Profile: Created a new profile through the profile management tool for WAS.
Server Config:
- Default
Changes Applied:
- Delete contents of /logs, /temp, /tranlog, /wstemp after my first attempt. Just to clear out the folders. No change in behavior.
Server Start Up Log
************ Start Display Current Environment ************
Host Operating System is Windows 7, version 6.1 build 7601 Service Pack 1
Java version = JRE 1.6.0 IBM J9 2.4 Windows 7 amd64-64 jvmwa6460sr10fp1-20120202_101568 (JIT enabled, AOT enabled)
J9VM - 20120202_101568
JIT - r9_20111107_21307ifx1
GC - 20120202_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
**was.install.root** = C:\IBM\runtimes\base_v7
user.install.root = C:\00_IBM_RAD_PROFILES\stsProfileWAS
Java Home = C:\IBM\runtimes\base_v7\java\jre
ws.ext.dirs = C:\\IBM\\runtimes\\base_v7\\java\\lib;C:\\IBM\\runtimes\\base_v7\\classes;C:\\IBM\\runtimes\\base_v7\\lib;C:\\IBM\\runtimes\\base_v7\\installedChannels;C:\\IBM\\runtimes\\base_v7\\lib\\ext;C:\\IBM\\runtimes\\base_v7\\web\\help;C:\\IBM\\runtimes\\base_v7\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
Current trace specification = *=info:com.ibm.*=all
************* End Display Current Environment *************
[06/07/16 10:36:29:575 ADT] 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
[06/07/16 10:36:29:583 ADT] 00000000 WsServerContr 1 Executing executeUtilityOnWindows with args: C:\00_IBM_RAD_PROFILES\stsProfileWAS\config PC123Node20Cell PC123Node20 server1 -script C:\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\quickServerStart.bat
[06/07/16 10:36:29:583 ADT] 00000000 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
[06/07/16 10:36:29:742 ADT] 00000000 AdminTool A ADMU0128I: Starting tool with the stsProfileWAS profile
[06/07/16 10:36:29:744 ADT] 00000000 AdminTool A ADMU3100I: Reading configuration for server: server1
[06/07/16 10:36:29:827 ADT] 00000000 AdminTool A ADMU3300I: Launch script for server created: C:\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\quickServerStart.bat
Related
I'm using Apache Ignite entity framework Nuget as a second level cache in an ApsNetCore 2.0 web application under IIS(as reverse proxy).
On my development machine (VS2017 Windows 8.1) everything works well. Wen i deploy to WindowsServer 2012 the Ignite crash at startup with :
An error occurred while starting the application.
IgniteException: Failed to load jvm.dll (Please specify IgniteConfiguration.JvmDllPath or JAVA_HOME.)
Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(string configJvmDllPath, ILogger log)
TargetInvocationException: Exception has been thrown by the target of an invocation.
System.RuntimeTypeHandle.CreateInstance(RuntimeType type, bool publicOnly, bool noCheck, ref bool canBeCached, ref RuntimeMethodHandleInternal ctor, ref bool bNeedSecurityCheck)
IgniteException: Failed to load jvm.dll (Please specify IgniteConfiguration.JvmDllPath or JAVA_HOME.)
Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(string configJvmDllPath, ILogger log)
Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
Apache.Ignite.EntityFramework.IgniteDbConfiguration.GetOrStartIgnite(IgniteConfiguration cfg)
Apache.Ignite.EntityFramework.IgniteDbConfiguration..ctor()
I checked and re-chewed, installed the JDK , correct system variables....everything. The error don't goes away. What is interesting is the application run ok as console. When it runs under IIS(reverse proxy) it crashes at startup with the above error.
Any suggestions ?
Thank you
I managed to start the website. How ? Only with JDK 11 and explicit path to jvm.dll on app.config file:
If is not explicit in config then crashes.
The JAVA_HOME from system variable is correct set. Also the Path variable is
%JAVA_HOME%;%JAVA_HOME%\bin;%JAVA_HOME%\bin\server;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\dotnet;C:\Program Files (x86)\dotnet;C:\ProgramData\chocolatey\bin;C:\Program Files\Memurai;C:\Program Files\Java\jdk-15.0.1\bin\
Maybe is a conflict with C:\Program Files\Java\jdk-15.0.1\bin\ ? It carsh with jvm 15. But it works with jvm 11
Looks like the IIS worker process is running in 32-bit mode, so Ignite looks for a 32-bit JDK, which is not present.
And the console app runs in 64-bit mode, using 64-bit JDK, so it works.
Please check the app pool settings in IIS Manager -> Application Pools -> select the app pool you want and -> Advanced Settings.
Additionally, you can enable detailed logging to a file (since you can't see console logs in IIS) - Ignite logs all attempts to resolve the JDK path. For example, with Apache.Ignite.NLog package:
var nlogConfig = new LoggingConfiguration();
var fileTarget = new FileTarget
{
FileName = "/home/pavel/w/ignite_nlog.log"
};
nlogConfig.AddTarget("logfile", fileTarget);
nlogConfig.LoggingRules.Add(new LoggingRule("*", LogLevel.Trace, fileTarget));
LogManager.Configuration = nlogConfig;
var igniteConfig = new IgniteConfiguration
{
Logger = new IgniteNLogLogger()
};
Ignition.Start(igniteConfig);
I've checked the suggested points by Pavel Tupitsyn:
App pool aplication is 64bits (emable 32bits=false)
I've installed apache.Ignite.NLog
I'tested it on my machine and it logs well all java resolves.
I've deployed to windows server 2012 and under IIS i'm getting 'Process Failure'.
The log file looks like:
2020-12-07 19:39:38.3304|DEBUG||Starting Ignite.NET 2.9.0.50002
2020-12-07 19:39:38.3834|WARN||GC server mode is not enabled, this could lead to less than optimal performance on multi-core machines (to enable see http://msdn.microsoft.com/en-us/library/ms229357(v=vs.110).aspx).
2020-12-07 19:39:46.2534|DEBUG||Starting Ignite.NET 2.9.0.50002
so...just a warning (present on my machine too).
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info:
Apache.Ignite.Core.Common.IgniteException
at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(System.String, Apache.Ignite.Core.Log.ILogger)
at Apache.Ignite.Core.Ignition.Start(Apache.Ignite.Core.IgniteConfiguration)
at Nop.Web.Program.Main(System.String[])
well...adding apache.ingite.nlog throws PROCESS FAILURE
Hosting is virtual machine with Windows Server 2012 64bits
Any other ideas please....
I want ot use EJBCA with Wildfly (JBoss) application server as PKI infrastructure.
I can access
http://127.0.0.1:8080/ejbca/
https://127.0.0.1:8442/ejbca/
but not
https://127.0.0.1:8443/ejbca/adminweb/
Then I will get with Firefox:
The connection to 127.0.0.1:8443 was interrupted while the was loading
With wireshark I can see the FIN ACKs of the application server.
I am using Ubuntu 16.04.2 LTS AMD64 virtual machine with Java
java -version
openjdk version “1.8.0_131”
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
and with EJBCA ejbca_ce_6_5.0.5.zip
and with Wildfly (JBoss) application server wildfly-10.0.0.Final.zip
and with MariaDB which seems to work well except above mentioned Administration access in the GUI.
The configuration is similar to this I found on the EJBCA install page. It seems, that the part with port 8443 was not correctly configured. Do you have a hint for me to find a solution for my problem?
Regards
drnie
For configuration details please have a look at the following lines:
----------------------- BEGIN CONFIG -----------------------
configuring MariaDB
after unzipping as User ejbca
configured the following files
setting the keystore password
$EJBCA_HOME /conf/cesecore.properties
setting database properties (DB name, DB url, DB driver, DB user name and DB password)
$EJBCA_HOME /conf/database.properties
setting cms keystore password and app server home
$EJBCA_HOME /conf/ejbca.properties
kept all settings ...
$EJBCA_HOME /conf/install.properties
Added Management user with
cd /home/ejbca/wildfly-10.0.0.Final/bin/
./add-user.sh
started Wildfly app server
--- Add datasource ---
opened the Call Level Interface
/home/ejbca/wildfly-10.0.0.Final/bin/jboss-cli.sh -c
entered the commands
data-source add --name=ejbcads --driver-name="mariadb-java-client-1.2.0.jar" --connection-url="jdbc:mysql://127.0.0.1:3306/ejbca" --jndi-name="java:/EjbcaDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="ejbca" --password="ejbca" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
:reload
--- Configure WildFly Remoting ---
/subsystem=remoting/http-connector=http-remoting-connector:remove
/subsystem=remoting/http-connector=http-remoting-connector:add(connector-ref="remoting",security-realm="ApplicationRealm")
/socket-binding-group=standard-sockets/socket-binding=remoting:add(port="4447")
/subsystem=undertow/server=default-server/http-listener=remoting:add(socket-binding=remoting)
:reload
--- Configure logging ---
/subsystem=logging/logger=org.ejbca:add
/subsystem=logging/logger=org.ejbca:write-attribute(name=level, value=DEBUG)
/subsystem=logging/logger=org.cesecore:add
/subsystem=logging/logger=org.cesecore:write-attribute(name=level, value=DEBUG)
:reload
--- Remove existing TLS and HTTP configuration ---
/subsystem=undertow/server=default-server/http-listener=default:remove
/subsystem=undertow/server=default-server/https-listener=https:remove
/socket-binding-group=standard-sockets/socket-binding=http:remove
/socket-binding-group=standard-sockets/socket-binding=https:remove
:reload
quitting CLI shell
restarted wildfly app server
--- Deploy EJBCA ---
ant clean deployear
--- Run install ---
ant runinstall
--- Deploy TLS keystores to WildFly ---
ant deploy-keystore
in the CLI shell
/interface=http:add(inet-address="0.0.0.0")
/interface=httpspub:add(inet-address="0.0.0.0")
/interface=httpspriv:add(inet-address="0.0.0.0")
/socket-binding-group=standard-sockets/socket-binding=http:add(port="8080",interface="http")
/subsystem=undertow/server=default-server/http-listener=http:add(socket-binding=http)
/subsystem=undertow/server=default-server/http-listener=http:write-attribute(name=redirect-socket, value="httpspriv")
:reload
waiting for reload to complete
Configure identities and socket bindings:
/core-service=management/security-realm=SSLRealm:add()
/core-service=management/security-realm=SSLRealm/server-identity=ssl:add(keystore-path="${jboss.server.config.dir}/keystore/keystore.jks", keystore-password="serverpwd", alias="localhost")
/core-service=management/security-realm=SSLRealm/authentication=truststore:add(keystore-path="${jboss.server.config.dir}/keystore/truststore.jks", keystore-password="changeit")
/socket-binding-group=standard-sockets/socket-binding=httpspriv:add(port="8443",interface="httpspriv")
/socket-binding-group=standard-sockets/socket-binding=httpspub:add(port="8442", interface="httpspub")
restart the application server completely and then
/subsystem=undertow/server=default-server/https-listener=httpspriv:add(socket-binding=httpspriv, security-realm="SSLRealm", verify-client=REQUIRED)
/subsystem=undertow/server=default-server/https-listener=httpspub:add(socket-binding=httpspub, security-realm="SSLRealm")
:reload
--- Finalize Wildfly configurations ---
/system-property=org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH:add(value=true)
/system-property=org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH:add(value=true)
/system-property=org.apache.catalina.connector.URI_ENCODING:add(value="UTF-8")
/system-property=org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING:add(value=true)
/subsystem=webservices:write-attribute(name=wsdl-host, value=jbossws.undefined.host)
/subsystem=webservices:write-attribute(name=modify-wsdl-address, value=true)
:reload
----------------------- END CONFIG -----------------------
I know this is old, but I am betting you did not have the hostname set in web.properties. You need to set httpsserver.hostname=myejbcaservername (default is localhost).
Also, try using FireFox. It has its own certificate store (separate from the OS certificate store) and works better when managing PKIs.
Also, restart your browser if you do have the superadmin certificate installed. If you have hit cancel or done something it will genernally not renegotiate until you use a private browsing window or restart your browser.
I am setting up openOCD and Eclipse on a new operating system, using a Nucleo F030R8 board that debugs fine on another system. When I run the debugger in Eclipse I get "error in final launch sequence":
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: No such file or directory.
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: No such file or directory.
localhost:3333: No such file or directory.
I can run the debugger in terminal with ./openocd -f board/st_nucleo_f0.cfg and get:
*GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.9.0-00073-gdd34716
(2015-05-19-12:55)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results
might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v25 API v2 SWIM v13 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.257369
Info : stm32f0x.cpu: hardware has 4 breakpoints, 2 watchpoints''*
and the LED LD1 blinks alternatively green and red. Similarly, I can run External Tools in Eclipse just fine, but this doesn't open the debugger. So it seems like I'm close, but something isn't quite right. Let me know if you need any other details of my system.
Using:
Eclipse Mars.2 (4.5.2)
Mac 10.12.1
OpenOCD 0.10.0-201601101000-dev
GNU Tools gcc-arm-none-eabi-5_4-2016q3
Ok so I figured it out with major credit due to http://www.carminenoviello.com. Running this in terminal:
>telnet localhost 3333
localhost: nodename nor servname provided, or not known
showed this wasn't working correctly. checking /etc/hosts, the file was empty. I changed it to:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
And that was that. Can now enter debug mode.
I have no idea how step over this problem:
**After amending some code where Glasfish provide an reasonable error message i got this useless message:
"Publishing to GlassFish 4 at localhost [domain 1] has encountered a problem, Cannot deploy abconlinetest" without any other expanation. Even after removing my corrections to force Glassfish to produce the old error message is not possible. Glashfish sticks with this message.
I got this message several times in the past and started always from scratch to set up the application step by step to get into a stable environment.
Below are the start messages from GlashFish.
Glassfish stops always at: 2015-01-16T18:54:02.309+0100|Information:
HV000001: Hibernate Validator 5.0.0.Final Then the messages appears
thhat glassFish is unable to deply the application.
Application uses JSF 2.2 writing the content of two formulars to an
Oracle database.
100|Information: Running GlassFish Version: GlassFish Server Open
Source Edition 4.1 (build 13)
2015-01-16T18:53:56.909+0100|Information: Server log file is using
Formatter class: com.sun.enterprise.server.logging.ODLLogFormatter
2015-01-16T18:53:56.987+0100|Information: Realm [admin-realm] of
classtype [com.sun.enterprise.security.auth.realm.file.FileRealm]
successfully created. 2015-01-16T18:53:56.987+0100|Information: Realm
[file] of classtype
[com.sun.enterprise.security.auth.realm.file.FileRealm] successfully
created. 2015-01-16T18:53:56.987+0100|Information: Realm [certificate]
of classtype
[com.sun.enterprise.security.auth.realm.certificate.CertificateRealm]
successfully created. 2015-01-16T18:53:57.159+0100|Information:
Authorization Service has successfully initialized.
2015-01-16T18:53:57.159+0100|Information: Registered
org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for
persistence-type = replicated in BackingStoreFactoryRegistry
2015-01-16T18:53:57.503+0100|Information: Grizzly Framework 2.3.15
started in: 47ms - bound to [/127.0.0.1:8080]
2015-01-16T18:53:57.534+0100|Information: Grizzly Framework 2.3.15
started in: 0ms - bound to [/127.0.0.1:8181]
2015-01-16T18:53:57.550+0100|Information: Grizzly Framework 2.3.15
started in: 0ms - bound to [/0.0.0.0:4848]
2015-01-16T18:53:57.565+0100|Information: Grizzly Framework 2.3.15
started in: 0ms - bound to [/0.0.0.0:3700]
2015-01-16T18:53:57.565+0100|Information: GlassFish Server Open Source
Edition 4.1 (13) startup time : Felix (1.346ms), startup
services(734ms), total(2.080ms)
2015-01-16T18:53:57.737+0100|Information: Grizzly Framework 2.3.15
started in: 15ms - bound to [/0.0.0.0:7676]
2015-01-16T18:53:57.753+0100|Information: Registered
com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishImpl#3b0ee03a
as OSGi service registration:
org.apache.felix.framework.ServiceRegistrationImpl#2bf94401.
2015-01-16T18:53:57.753+0100|Information: Binding RMI port to single
IP address = 127.0.0.1, port 8.686
2015-01-16T18:53:57.800+0100|Information: JMXStartupService has
started JMXConnector on JMXService URL
service:jmx:rmi://127.0.0.1:8686/jndi/rmi://127.0.0.1:8686/jmxrmi
2015-01-16T18:54:02.309+0100|Information: HV000001: Hibernate
Validator 5.0.0.Final
This worked for me.
Go to Servers.
Expand GlassFish 4 at localhost [domain1].
Expand GlassFish Management.
Right click on your project name and press Delete.
Now run the Project again on Glassfish 4.
Hope it helps.
Approach1:
Removing application from server
GlassFish 4 at localhost [domain1] Right click ---> Stop
Expand application list under server: GlassFish 4 at localhost [domain1]
Right click on the project
Select Remove
Click Yes
GlassFish 4 at localhost [domain1] Right click ---> Clean
GlassFish 4 at localhost [domain1] Right click ---> Publish
Re running project
Project ---> Clean
Project ---> Refresh F5
Project Run As ---> Run on Server
Select GlassFish 4 at localhost [domain1]
Click Next
Select the Project
Click Finish
running the project again, it fixes the error.
Approach2:
Same error, and the detailed error message shows:
cannot Deploy project: java.util.concurrent.TimeoutException
For TimeoutException errors, by increasing the timeout limit for server, will work:
Right click on GlassFish 4 at localhost [domain1] ---> Properties ---> Timeouts ---> Start (seconds) ---> increase the timeout limit in seconds ---> Save
Run the project again with the same steps mentioned above.
My perl script couldn't connect to the selenium standalone server running in localhost port 4444. In different environment different things happen.
Windows 7 : The script works sometimes and sometimes it doesnt.
Selenium server side : starts properly. but there is no new session created when I create remote driver instance.
C:\Users\ganess4\msant\nsn_testeng\tools\AutoBuildPromotionEmail>java -jar selenium-server-standalone-2.37.0.jar
Dec 3, 2013 12:16:43 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a standalone server
12:16:43.882 INFO - Java: Sun Microsystems Inc. 20.14-b01
12:16:43.882 INFO - OS: Windows 7 6.1 x86
12:16:43.894 INFO - v2.37.0, with Core v2.37.0. Built from revision a7c61cb
12:16:43.953 INFO - Default driver org.openqa.selenium.iphone.IPhoneDriver regis
tration is skipped: registration capabilities Capabilities [{platform=MAC, brows
erName=iPhone, version=}] does not match with current platform: VISTA
12:16:43.973 INFO - Default driver org.openqa.selenium.iphone.IPhoneDriver regis
tration is skipped: registration capabilities Capabilities [{platform=MAC, brows
erName=iPad, version=}] does not match with current platform: VISTA
12:16:44.020 INFO - RemoteWebDriver instances should connect to: http://127.0.0.
1:4444/wd/hub
12:16:44.021 INFO - Version Jetty/5.1.x
12:16:44.022 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
12:16:44.023 INFO - Started HttpContext[/selenium-server,/selenium-server]
12:16:44.024 INFO - Started HttpContext[/,/]
12:16:44.074 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler#1754ad
2
12:16:44.074 INFO - Started HttpContext[/wd,/wd]
12:16:44.112 INFO - Started SocketListener on 0.0.0.0:4444
12:16:44.112 INFO - Started org.openqa.jetty.jetty.Server#c1b531
Code Side: Note I did try port 4444 and other variations.
my $browser = "firefox";
my $platform = "WINDOWS";
eval
{
$self->{seldriverarray} = new Selenium::Remote::Driver(browser_name => $browser, platform => $platform);
$self->{seldriverarray}->debug_on;
print Dumper $self->{seldriverarray}->status;
};
Throws the following
Use of uninitialized value in string ne at C:/Dwimperl/perl/site/lib/Selenium/Re
mote/RemoteConnection.pm line 30, <FH> line 48.
Use of uninitialized value in string eq at C:/Dwimperl/perl/site/lib/Selenium/Re
mote/RemoteConnection.pm line 35, <FH> line 48.
Selenium server did not return proper status at C:/Dwimperl/perl/site/lib/Seleni
um/Remote/Driver.pm line 232.
The weirdest thing happens when I run it in another environment
Suse Enterprise Edition:
Selenium server side: see it creates a new session, which implies that the code is not wrong. So, what is stopping the code to launch a new session in windows? I couldnt run the script in linux, because it is timing out for a long time struggling to launch the firefox.
12:32:09.969 INFO - Started org.openqa.jetty.jetty.Server#181edf4
12:32:19.041 INFO - Executing: [new session: {platform=WINDOWS, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox, version=}] at URL: /session)
12:32:19.057 INFO - Creating a new session for Capabilities [{platform=WINDOWS, javascriptEnabled=true, acceptSslCerts=true, browserName=firefox, version=}]
After updating the Net::HTTPS and the IO::Socket::SSL, this got resolved.