I cant find any way to display PSU version on a Oracle Weblogic 12c installation.
The only method is OPatch lspatches but require access to single installation.
On previous (10.3.x) the PSU version and single Patch are shown on application server log, WLST and JMX.
You can run OPatch like you mentioned:
opatch lsinventory
Or with your weblogic home set:
source $WL_HOME/server/bin/SetWLSEnv.sh
java weblogic.version
Or from the weblogic admin console:
Go to the Servers link
Customize this table
Check the WebLogic Version box and add it to the right side
Click Apply
And when starting a server:
With 12c you should see something like <Apr 20, 2015 4:58:52 PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 >
With 10.3 you would have also seen the same thing like <Apr 20, 2015 5:34:42 PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 17069175, 17213621, 17780729 Thu Sep 11 17:27:51 MDT 2014
The only way to see versions in WLS 12.1.2 and later (as of this date) is through OPatch. See Doc ID 1676652.1 for more information.
Related
Is there a way to suppress output from the web driver - e.g.
Feb 09, 2023 1:22:13 PM org.openqa.selenium.chromium.ChromiumDriver lambda$new$3
WARNING: Unable to find version of CDP to use for . You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.7.2` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's.
Feb 09, 2023 1:22:14 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find CDP implementation matching 110
Feb 09, 2023 1:22:14 PM org.openqa.selenium.chromium.ChromiumDriver lambda$new$3
WARNING: Unable to find version of CDP to use for . You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.7.2` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
ChromeDriver was started successfully.
If this is really what you want:
Add a setUp Thread Group to your Test Plan
Add JSR223 Sampler to the Thread Group
Put the following code into "Script" area:
java.util.logging.LogManager.getLogManager().reset()
def globalLogger = java.util.logging.Logger.getLogger(java.util.logging.Logger.GLOBAL_LOGGER_NAME)
globalLogger.setLevel(java.util.logging.Level.OFF)
Next time you run your test all Selenium-related logging will go away.
I've got a plain vanilla install of ignite 2.14, with the binaries downloaded from https://ignite.apache.org/download.cgi (exact link https://dlcdn.apache.org/ignite/2.14.0/apache-ignite-2.14.0-bin.zip). I'm on Windows 10, IGNITE_HOME is not set in the PATH (this is optional), and Ignite's using this java runtime:
OpenJDK Runtime Environment 1.8.0_201-2-redhat-b09 Oracle Corporation
OpenJDK 64-Bit Server VM 25.201-b09
I start an ignite node using the default configuration provided in the downloaded zip apache-ignite-2.14.0-bin.zip :
ignite.bat ..\config\default-config.xml
This starts fine. Following the instructions at https://ignite.apache.org/docs/latest/tools/control-script I can check the state and see I've got a single node cluster in state ACTIVE (the default-config.xml must not have native persistence enabled, so the cluster goes to ACTIVE state automatically).
I can then set the state to INACTIVE like so:
control.bat --set-state INACTIVE
This works fine. However if I set the state to active again like so:
control.bat --set-state ACTIVE
I get the error pasted below and the cluster stays in the INACTIVE state. I first came across this error when using Ignite in embedded server mode, but I can still reproduce it with a fresh out-of-the-box ignite install (not using embedded). I'm surprised that a plain vanilla install just calling a couple of basic commands falls over like this. Any idea what's happening?
This is the error:
C:\temp\apache-ignite-2.14.0-bin\bin>control.bat --set-state ACTIVE
Nov 17, 2022 4:27:17 PM
org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection
INFO: Client TCP connection established: /127.0.0.1:11211 Nov
17, 2022 4:27:17 PM
org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection
close INFO: Client TCP connection closed: /127.0.0.1:11211 Nov 17,
2022 4:27:17 PM org.apache.ignite.internal.client.util.GridClientUtils
shutdownNow WARNING: Runnable tasks outlived thread pool executor
service [owner=GridClientConnectionManager,
tasks=[java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask#6d7b4f4c]]
Control utility [ver. 2.14.0#20220929-sha1:951e8deb] 2022 Copyright(C)
Apache Software Foundation User: info Time: 2022-11-17T16:27:16.344
null suppressed:
Command [SET-STATE] finished with code: 4 Error stack trace: class
org.apache.ignite.internal.client.GridClientException: null
suppressed:
at org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.handleClientResponse(GridClientNioTcpConnection.java:632)
at org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.handleResponse(GridClientNioTcpConnection.java:563)
at org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter$NioListener.onMessage(GridClientConnectionManagerAdapter.java:691)
at org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:116)
at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3734)
at org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
at org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1211)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
at java.lang.Thread.run(Thread.java:748)
Control utility has completed execution at: 2022-11-17T16:27:17.642
Execution time: 1298 ms Press any key to continue . . .
It's a known issue, which is, unfortunately, not fixed yet.
As a workaround, you can execute the command with the autoconfirmation flag --yes, as shown below:
control.bat --set-state ACTIVE --yes
I get the following error when I run the configure-tomcat-mysql.xml. This script is provided in the installation folder and I have made the necessary changes.
BUILD FAILED
/home/madmin/software/ibm/configure-tomcat-mysql.xml:143: The element <applicationserver> inside <installmobilefirstadmin>, Tomcat version cannot be defined.
server details:
1.8.0_181
Linux Ubuntu 16.04
ant 1.9.6
tomcat 8
mysql:5.7.23
MFP V8
Thanks for your help
==UPDATE ---
I install tomcat 7 and had the same issue
Using CATALINA_BASE: /usr/share/tomcat7
Using CATALINA_HOME: /usr/share/tomcat7
Using CATALINA_TMPDIR: /usr/share/tomcat7/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar
Server version: Apache Tomcat/7.0.68 (Ubuntu)
Server built: Jun 27 2016 18:13:17 UTC
Server number: 7.0.68.0
OS Name: Linux
OS Version: 4.15.0-1015-gcp
Architecture: amd64
JVM Version: 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13
[installmobilefirstadmin] [13/08/2018 16:01:16:631 UTC] Mon Aug 13 16:01:16 UTC 2018 WARN: Establishing SSL connec
tion without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ req
uirements SSL connection must be established by default if explicit option isn't set. For compliance with existing
applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification
.
BUILD FAILED
/home/madmin/configure-tomcat-mysql.xml:143: The element <applicationserver> inside <installmobilefirstadmin>, Tom
cat version cannot be defined.
== Update 2 ===
I redo the entire install by downloading again the V8 zip file and the install manager but I get the same result
Can you let me know how to debug or resolve this issue
Starting Weblogic Server is not starting the server and the console is forced to shutdown. I couldn't figure out why this is happening. Any help is really appreciated.
I tried running the admin console and here is the error message:
Access is denied.
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=512m
.
WLS Start Mode=Production
.
CLASSPATH=C:\Oracle\MIDDLE~2\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar;C:\Oracle\Middleware\o
racle_common\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\Middleware\oracle_commo
n\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\Oracle\Middleware\oracle_common\
modules\oracle.jmx_11.1.1\jmxspi.jar;C:\Oracle\Middleware\oracle_common\modules\
oracle.odl_11.1.1\ojdl.jar;C:\Oracle\Middleware\as_1\common\wlst\lib\adf-share-m
beans-wlst.jar;C:\Oracle\Middleware\as_1\common\wlst\lib\mdswlst.jar;C:\Oracle\Middleware\as_1\common\wlst\resources\oamap_help.jar;C:\O
racle\Middleware\as_1\common\wlst\resources\oamAuthnProvider.jar;C:\Oracle\Middl
eware\as_1\common\wlst\resources\ossoiap_help.jar;C:\Oracle\Middleware\as_1\comm
on\wlst\resources\ossoiap.jar;C:\
Oracle\MIDDLE~2\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~2\ORAC
LE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\MIDDLE~2\OR
ACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~2\WLSERV~1.3\server\li
b\xqrl.jar
.
PATH=C:\Oracle\Middleware\as_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\Sys
tem32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Java\jdk
1.6.0_43;C:\Program Files\Java\jdk1.6.0_43\bin;C:\Oracle\Middleware\as_1\opmn\bi
n;C:\Oracle\Middleware\as_1\opmn\lib;C:\Oracle\Middleware\as_1\perl\bin
.
***************************************************
* 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 weblogic with Java version:
java version "1.6.0_43"
Java(TM) SE Runtime Environment (build 1.6.0_43-b01)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_4\bin\java -Xms256m -Xmx512m -XX:MaxPermSize=512m
-Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~2\WLSERV~1.
3\server\lib\weblogic.policy -Dweblogic.ProductionModeEnabled=true -da -Dplat
form.home=C:\Oracle\MIDDLE~2\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~2\WLSERV~1.3
\server -Dweblogic.home=C:\Oracle\MIDDLE~2\WLSERV~1.3\server -Xms512m -Xmx1024
m -XX:PermSize=256m -XX:MaxPermSize=512m -Doracle.home=C:\Oracle\Middleware\as_1
-Ddomain.home=C:\Oracle\Middleware\user_projects\domains\FormsReports -Dcommon.
components.home=C:\Oracle\MIDDLE~2\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.co
mmons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\O
racle\MIDDLE~2\USER_P~1\domains\FORMSR~1 -Djrockit.optfile=C:\Oracle\MIDDLE~2\OR
ACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=
C:\Oracle\MIDDLE~2\USER_P~1\domains\FORMSR~1\config\FMWCON~1\servers\AdminServer
-Doracle.domain.config.dir=C:\Oracle\MIDDLE~2\USER_P~1\domains\FORMSR~1\config\
FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~2\USER_P~1\domains\FORMSR~
1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~2\USER_P~1\doma
ins\FORMSR~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Orac
le\MIDDLE~2\USER_P~1\domains\FORMSR~1\config\fmwconfig\jps-config.xml -Doracle.d
eployed.app.dir=C:\Oracle\MIDDLE~2\USER_P~1\domains\FORMSR~1\servers\AdminServer
\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:
\Oracle\MIDDLE~2\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~2\ORACL
E~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.ne
t.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwc.oracle.home=C:\Oracle\Midd
leware\as_1 -Dclassic.oracle.home=C:\Oracle\Middleware\as_1 -Dem.oracle.home=C:
\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.
discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsT
oConsole=false weblogic.Server
<Oct 7, 2015 9:30:50 AM SGT> <Info> <Security> <BEA-090905> <Disabling CryptoJ J
CE Provider self-integrity check for better startup performance. To enable this
check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Oct 7, 2015 9:30:50 AM SGT> <Info> <Security> <BEA-090906> <Changing the defaul
t Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable
this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Oct 7, 2015 9:30:50 AM SGT> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.14-b01 from Sun Mi
crosystems Inc.>
<Oct 7, 2015 9:30:51 AM SGT> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Oct 7, 2015 9:30:52 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Oct 7, 2015 9:30:52 AM SGT> <Info> <WorkManager> <BEA-002900> <Initializing sel
f-tuning thread pool>
<Oct 7, 2015 9:30:52 AM SGT> <Notice> <Log Management> <BEA-170019> <The server
log file C:\Oracle\Middleware\user_projects\domains\FormsReports\servers\AdminSe
rver\logs\AdminServer.log is opened. All server side log events will be written
to this file.>
<Oct 7, 2015 9:30:53 AM SGT> <Error> <Socket> <BEA-000438> <Unable to load perfo
rmance pack. Using Java I/O instead. Please ensure that wlntio.dll is in: 'C:\PR
OGRA~1\Java\JDK16~1.0_4\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windo
ws;C:\Oracle\Middleware\as_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\Syste
m32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Java\jdk1.
6.0_43;C:\Program Files\Java\jdk1.6.0_43\bin;C:\Oracle\Middleware\as_1\opmn\bin;
C:\Oracle\Middleware\as_1\opmn\lib;C:\Oracle\Middleware\as_1\perl\bin;C:\Program
Files\TortoiseSVN\bin;.'
>
Oct 7, 2015 9:30:56 AM oracle.security.jps.internal.credstore.ssp.CsfWalletManag
er openWallet
WARNING: Opening of wallet based credential store failed. Reason java.io.IOExcep
tion: C:\Oracle\Middleware\user_projects\domains\FormsReports\config\fmwconfig\b
ootstrap\cwallet.sso (Access is denied)
Oct 7, 2015 9:30:56 AM oracle.security.jps.internal.keystore.file.FileKeyStoreIn
tegrityChecker <init>
WARNING: Key store file integrity checker initialization failed. Reason oracle.s
ecurity.jps.service.keystore.KeyStoreServiceException: JPS-01050: Opening of wal
let based credential store failed. Reason java.io.IOException: C:\Oracle\Middlew
are\user_projects\domains\FormsReports\config\fmwconfig\bootstrap\cwallet.sso (A
ccess is denied)
Oct 7, 2015 9:30:56 AM oracle.security.jps.internal.keystore.file.FileKeyStoreMa
nager openKeyStore
WARNING: Opening of file based keystore failed.
<Oct 7, 2015 9:30:56 AM SGT> <Error> <Security> <BEA-090892> <The loading of OPS
S java security policy provider failed due to exception, see the exception stack
trace or the server log file for root cause. If still see no obvious cause, ena
ble the debug flag -Djava.security.debug=jpspolicy to get more information. Erro
r message: JPS-06514: Opening of file based keystore failed.>
<Oct 7, 2015 9:30:56 AM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server su
bsystem failed. Reason: weblogic.security.SecurityInitializationException: The l
oading of OPSS java security policy provider failed due to exception, see the ex
ception stack trace or the server log file for root cause. If still see no obvio
us cause, enable the debug flag -Djava.security.debug=jpspolicy to get more info
rmation. Error message: JPS-06514: Opening of file based keystore failed.
weblogic.security.SecurityInitializationException: The loading of OPSS java secu
rity policy provider failed due to exception, see the exception stack trace or t
he server log file for root cause. If still see no obvious cause, enable the deb
ug flag -Djava.security.debug=jpspolicy to get more information. Error message:
JPS-06514: Opening of file based keystore failed.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.lo
adOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-06514: Opening of file b
ased keystore failed.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<
init>(PolicyDelegationController.java:167)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
vaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based ke
ystore failed.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPServ
ice(PolicyUtil.java:2855)
at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(Pol
icyUtil.java:3097)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<
init>(PolicyDelegationController.java:164)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
vaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06
514: Opening of file based keystore failed.
at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKe
yStore(FileKeyStoreManager.java:374)
at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.do
Init(FileKeyStoreServiceImpl.java:104)
at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
nit>(FileKeyStoreServiceImpl.java:76)
at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
nit>(FileKeyStoreServiceImpl.java:66)
at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(Ke
yStoreProvider.java:157)
Truncated. see log file for complete stacktrace
>
<Oct 7, 2015 9:30:56 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FAILED>
<Oct 7, 2015 9:30:56 AM SGT> <Error> <WebLogicServer> <BEA-000383> <A critical s
ervice failed. The server will shut itself down>
<Oct 7, 2015 9:30:56 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FORCE_SHUTTING_DOWN>
C:\Oracle\Middleware\user_projects\domains\FormsReports>
For some reason WebLogic Server is unable to access cwallet.sso. It looks like there's a couple of other files along the way it can't access as well.
Check permissions on the domain directory structure and make sure your current user can access required files. If that doesn't help at all, try running startWebLogic as an Administrator user on the machine.
I just recently had a problem with an incorrect set of JCE Unlimited Jurisdiction files. Moving them back to the old version made this error go away.
My OS is win 7 ultimate 32 bit
After installing JDK 7u9, eclipse Juno (4.2) SR1 for Java EE
and finally adding into it the new server
Apache TomEE 1.5.0 October 2nd, 2012 apache-tomee-1.5.0-webprofile.zip
(using eclipse wizard to add new servers and choosing tomcat 7 profile and then the directory where it's installed)
i'm getting the following console error
...
...
...
nov 13, 2012 8:07:53 PM org.apache.tomee.catalina.OpenEJBContextConfig processAnnotationsFile
SEVERE: OpenEJBContextConfig.processAnnotationsFile: failed.
java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 32
C:\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\testtomee01\WEB-INF\classes
^
at java.util.regex.Pattern.error(Unknown Source)
...
...
...
the server, eventually seems to start but then you get the 404 error on every page under http://localhost:8080/
tomEE installation directory is C:\apache-tomee-webprofile-1.5.0
eclipse installation directory is C:\eclipse
and java jre under C:\Program Files\Java\jre7
It looks like the current Windows release is broken. You'll have to download a fixed version as suggested in the bug report found here: https://issues.apache.org/jira/browse/TOMEE-436
The 1.5.1 snapshots are available for download here: 1.5.1-SNAPSHOT
Yes, should have been fixed and included in the next release (1.5.1).
FYI, it should be available next week.
Jean-Louis