I installed WebLogic 12.1.2 on my Windows 7 64-bit machine using Java 7. The installation was successful, but I'm running into the following error when attempting to create a new domain. It worked on a similar computer I did this on earlier today so it must be something about this particular machine. Any ideas on what the problem may be?
2015-07-14 20:23:42,509 INFO [AWT-EventQueue-0] com.oracle.cie.wizard.help.DefaultHelpProvider - Initializing help implementation....
2015-07-14 20:23:42,759 INFO [AWT-EventQueue-0] com.oracle.cie.domain.DomainLoader - domain C:\Oracle\Middleware\Oracle_Home\user_projects\domains\learn is not a valid BEA domain
2015-07-14 20:23:42,759 INFO [AWT-EventQueue-0] com.oracle.cie.domain.DomainRegistryWrapper - need to initialize domainRegistrydocument object
2015-07-14 20:23:42,759 INFO [AWT-EventQueue-0] com.oracle.cie.domain.DomainLoader - domain C:\Oracle\Middleware\Oracle_Home\user_projects\domains\learn is not a valid BEA domain
2015-07-14 20:24:33,597 INFO [AWT-EventQueue-0] com.oracle.cie.domain.AbstractTemplate - Setting symbol for component oracle.wls.core.app.server version 12.1.2.0.0 to oracle.wls.core.app.server_12.1.2.0.0/wlserver_ORACLE_HOME
2015-07-14 20:24:33,612 INFO [AWT-EventQueue-0] com.oracle.cie.domain.AbstractTemplate - Setting symbol for component oracle.wls.core.app.server version 12.1.2.0.0 to oracle.wls.core.app.server_12.1.2.0.0/wlserver_ORACLE_HOME
2015-07-14 20:25:11,741 WARNING [AWT-EventQueue-0] com.oracle.cie.domain.gui.panel.ConfigVPanel - Ajusted ordering index 5 is out of bounds.
2015-07-14 20:25:11,741 WARNING [AWT-EventQueue-0] com.oracle.cie.domain.gui.panel.ConfigVPanel - Ajusted ordering index 6 is out of bounds.
2015-07-14 20:25:11,741 WARNING [AWT-EventQueue-0] com.oracle.cie.domain.gui.panel.ConfigVPanel - Ajusted ordering index 7 is out of bounds.
2015-07-14 20:25:19,962 SEVERE [Thread-7] com.oracle.cie.domain.DomainGenerator - Domain Creation Failed!
Domain Location: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\learn
Reason: java.lang.NoSuchFieldError: CN
Exception:
java.lang.NoSuchFieldError: CN
java.lang.NoSuchFieldError: CN
at com.oracle.cie.security.impl.BCSecurityHandlerImpl.generateSubjectPrincipal(BCSecurityHandlerImpl.java:214)
at com.oracle.cie.security.impl.BCSecurityHandlerImpl.generateV3Certificate(BCSecurityHandlerImpl.java:79)
at com.oracle.cie.security.impl.BCSecurityHandlerImpl.sign(BCSecurityHandlerImpl.java:60)
at com.oracle.cie.security.impl.BaseSecurityHandler.initDefaultKeyStore(BaseSecurityHandler.java:94)
at com.oracle.cie.domain.security.WLSSecurityHelper.createDefaultKeyStores(WLSSecurityHelper.java:66)
at com.oracle.cie.domain.DomainGenerator.run(DomainGenerator.java:468)
at java.lang.Thread.run(Thread.java:744)
2015-07-14 20:27:51,631 INFO [AWT-EventQueue-0] com.oracle.cie.common.util.BrowserLauncher - jdk used is : 1.7.0_51
Turns out this was an issue related to a change I made to the java.security file within my JDK for another project I was working on earlier this year. That change brought in a version of Bouncy Castle that does not agree with WebLogic 12.1.2, which apparently expects an older version of that library. The solution for me was to reinstall the JDK entirely to back out my change.
Related
INFO [2020-02-10 07:03:32,933]
curator.utils.Compatibility:[Compatibility::48] - [main] -
Running in ZooKeeper 3.4.x compatibility mode INFO [2020-02-10
07:03:32,934] curator.utils.Compatibility:[Compatibility::61]
- [main] - Using emulated InjectSessionExpiration Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.curator.CuratorZookeeperClient.(Lorg/apache/curator/utils/ZookeeperFactory;Lorg/apache/curator/ensemble/EnsembleProvider;IIILorg/apache/zookeeper/Watcher;Lorg/apache/curator/RetryPolicy;ZLorg/apache/curator/connection/ConnectionHandlingPolicy;)V
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:131)
at
org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:165)
at
org.apache.curator.framework.CuratorFrameworkFactory.newClient(CuratorFrameworkFactory.java:113)
at
org.apache.curator.framework.CuratorFrameworkFactory.newClient(CuratorFrameworkFactory.java:94)
at
com.vnera.common.utils.DistributedSemaphore$CuratorFrameworkWrapper.(DistributedSemaphore.java:166)
at
com.vnera.common.utils.DistributedSemaphore.create(DistributedSemaphore.java:65)
at
com.vnera.tools.DistributedSemaphoreTestTool.main(DistributedSemaphoreTestTool.java:86)
Isn't curator 4.2 compatible with zookeepr 3.4.x?
Any pointers?
It is but you need to make sure your dependencies are correct. Please see the doc here: https://curator.apache.org/zk-compatibility.html
You need to:
Exclude the transitive dependency to ZooKeeper in your Curator dependency statement (the doc has examples for both Gradle and Maven)
Add a hard dependency to ZooKeeper 3.4.x
HI while upgrading to ignite 2.7 we face this issue , this hapepns when ignite is about to start certain custom caches.
2019-01-09 19:28:04.260 UTC [SERVER] [exchange-worker-#38%fdap%] [ERROR] [,] ROOT - Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class o.a.i.i.processors.query.h2.H2DatabaseType]]
java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType
at org.apache.ignite.internal.processors.query.h2.H2DatabaseType.fromClass(H2DatabaseType.java:147)
at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dbTypeFromClass(IgniteH2Indexing.java:2972)
at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2873)
at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:2809)
at org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1633)
at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:805)
at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1330)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2165)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:2023)
at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:924)
at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
There is a ticket also for the same https://issues.apache.org/jira/browse/IGNITE-10612 , will this be solved or is there a release guide on how to overcome the issue .
Please help ...
by putting
<properties>
<h2.version>1.4.197</h2.version>
</properties>
works to resolve this.
since the default of h2 is 1.4.199 which can cause other exceptions. you have to override that as well.
Are you sure that you have correct version of H2 dependency? For AI 2.7 it should be com.h2database h2 1.4.197 and not any other. The error you have posted is linkage error which will arise from having incorrect library version in classpath.
I have tried updating my POM from v8.6.1 to v8.7.2 and in the process successfully re-created a sample repo with the new version's preload tool.
Although I have not altered my java code at all (which runs perfectly with v.8.6.1), now I get an error when trying to retrieve the repository from the manager with the following command:
repository = repositoryManager.getRepository(repositoryId);
The error is the following:
197822 [main] INFO com.ontotext.plugin.magic-predicates - Registering InverseMagicPredicate: http://jena.hpl.hp.com/ARQ/property#strSplit
197823 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'literals-index'
198002 [main] INFO com.ontotext.plugin.literals-index - Literals indices restored.
198003 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'geospatial'
198009 [main] INFO com.ontotext.trree.plugin.geo.GeoSpatialPlugin - Plugin:geospatial initialized
198010 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'sparql-mm'
198400 [main] INFO com.ontotext.graphdb.sparqlmm.FunctionLoader - Registered 48 functions from package com.github.tkurz.sparqlmm.function.
198400 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'dependencies-plugin'
198409 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'similarity'
198429 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'GeoSPARQL'
231881 [main] INFO com.ontotext.trree.geosparql.FunctionLoader - Registered 50 functions from package com.useekm.geosparql.
231882 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'lucene-connector'
231896 [main] ERROR com.ontotext.trree.sdk.impl.PluginManager - Plugin 'lucene-connector' failed to initialize:org/json/simple/parser/ParseException
231897 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'rdfrank'
232224 [main] INFO com.ontotext.trree.sdk.impl.PluginManager - Initializing plugin 'notifications'
232237 [main] ERROR com.ontotext.trree.free.GraphDBFreeSchemaRepository - Error initializing plugins:
java.lang.NullPointerException
at com.ontotext.trree.plugin.externalsync.ExternalSyncPlugin.shutdown(ExternalSyncPlugin.java:803)
at com.ontotext.trree.sdk.PluginBase.shutdown(PluginBase.java:100)
at com.ontotext.trree.sdk.impl.PluginManager.disablePluginInt(PluginManager.java:986)
at com.ontotext.trree.sdk.impl.PluginManager.removePlugin(PluginManager.java:361)
at com.ontotext.trree.sdk.impl.PluginManager.initialize(PluginManager.java:128)
at com.ontotext.trree.OwlimSchemaRepository.initPlugins(OwlimSchemaRepository.java:1979)
at com.ontotext.trree.OwlimSchemaRepository.initializeInternal(OwlimSchemaRepository.java:242)
at org.eclipse.rdf4j.sail.helpers.AbstractSail.initialize(AbstractSail.java:188)
at org.eclipse.rdf4j.repository.sail.SailRepository.initializeInternal(SailRepository.java:151)
at org.eclipse.rdf4j.repository.base.AbstractRepository.initialize(AbstractRepository.java:34)
at org.eclipse.rdf4j.repository.manager.LocalRepositoryManager.createRepository(LocalRepositoryManager.java:270)
at org.eclipse.rdf4j.repository.manager.RepositoryManager.getRepository(RepositoryManager.java:424)
I have specified the -Dregister-external-plugins=.... in the VM Options.
Any ideas what might be wrong? Should I go for a previous version and if so, which one?
Thanks
It looks like you have an incompatible Lucene connector configuration. I recommend deleting the Lucene connector directory and once the repository starts you can recreate the connector(s). The Lucene connector directory is located in the repository's data directory: <graphdb-data-dir>/repositories/<repository-id>/storage/lucene-connector. The easiest way to find <graphdb-data-dir> is looking at the startup messages of GraphDB where it will print something like:
GraphDB Data directory: /opt/test/graphdb-free-8.7.2/data
As Konstantin mentioned the problem might also have to do with register-external-plugins.
I have built a basic application. I have also updated connectOnStartup to true, added WL.Client.connect() in wlCommonInit() and updated worklight.properties:
publicWorkLightHostname=92.1.52.17
publicWorkLightProtocol=http
publicWorkLightPort=9080
The build was successful except for these errors in the development console:
[err] 0 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/C:
/Documents%20and%20Settings/wl/Bureau/workspaces/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
[err] 94 WorklightPU INFO [Scheduled Executor-thread-1] openjpa.Runtime - Starting OpenJPA 1.2.2
[err] 94 WorklightPU INFO [Scheduled Executor-thread-1] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.HSQLDictionary".
[err] 0 WorklightReportsPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightReportsPU', root URL [file:/C:/Documents%20and%20Settings/wl/Bureau/workspaces/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
I have deployed the app manually to the liberty profile, and added the .wlapp to the console.
When starting the app in common from the console I get an error stating that the server was "unable to process the request".
The javascript console show:
Failed to load resource: the server responded with a status of 404
(Not Found)
Let us take a step back.
Worklight 6.0 is already running on Liberty, so what do you mean by "deployed the app manually to the liberty profile"?
Are you in fact trying to transfer your app to another application server? Please edit the question WITH ALL INFORMATION and steps and IBM Information Center topics you have followed for doing so.
Why do you change the port in worklight.properties? If you change the port of the project you should also change the port of the application server you intend to deploy it on. Make sure the ports match(!).
Also note that if you already set connectOnStartup to true, then there is absolutely no need for you to also add WL.Client.connect...
As for the error messages you have pointed out - these are harmless, and have been removed in 6.0.0.1 I believe. Make sure you are running the latest version of Worklight. If they are still there for you, then they are just removed internally and will be gone in a future release.
thanks for your answer. I restart a new liberty profile server and use ant to deploy the war file.
In the studio i have used right clic on app and
build all
instead of
build for remote server
that was my mistake and it works fine now.
I have compare the .wlapp but i'm not sure if they are different.
thanks
Previewing a hybrid app in Worklight Console's MBS in Worklight v5.0.6 was a breeze as it worked right out the box.
Worklight 6.0 has proven to be a bit more tricky. Can someone point me in the right direction to getting my Worklight Console up and running?
Here is my Eclipse console log:
CWWKE0005E: The runtime environment could not be launched.
CWWKE0029E: An instance of server worklight is already running.
I have not altered any port information.
Eclipse.ini:
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20120913-144807
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
Update:
Completed the steps in Idan's response; the result in the Worklight Development Server console view in Eclipse:
[err] 28 WorklightPU WARN [Scheduled Executor-thread-1]
openjpa.Runtime - An error occurred while registering a
ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root
URL
[file:/Users/mwoods/Desktop/TestWorkspace/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar].
The error has been consumed. To see it, set your openjpa.Runtime log
level to TRACE. Load-time class transformation will not be available.
[err] 460 WorklightPU INFO [Scheduled Executor-thread-1]
openjpa.Runtime - Starting OpenJPA 1.2.2
[err] 524 WorklightPU INFO [Scheduled Executor-thread-1] openjpa.jdbc.JDBC - Using dictionary class
"org.apache.openjpa.jdbc.sql.HSQLDictionary".
[err] 1 WorklightReportsPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a
ClassTransformer with PersistenceUnitInfo: name 'WorklightReportsPU',
root URL
[file:/Users/mwoods/Desktop/TestWorkspace/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar].
The error has been consumed. To see it, set your openjpa.Runtime log
level to TRACE. Load-time class transformation will not be available.
And:
Launching worklight (WebSphere Application Server
8.5.5.0/wlp-1.0.3.20130524-0951) on Java HotSpot(TM) 64-Bit Server VM, version 1.6.0_45-b06-451-11M4406 (en_US) [AUDIT ] CWWKE0001I: The
server worklight has been launched. [ERROR ] CWWKO0221E: TCP Channel
defaultHttpEndpoint initialization did not succeed. The socket bind
did not succeed for host * and port 10080. The port might already be
in use.
SOLUTION:
Changed port number and restarted my computer.
I'd be more interested in a step-by-step of what you've done. Please edit your question with the steps.
Lets also try this very basic scenario:
Have a brand new Eclipse Jave EE 4.2.2 ("Juno" SR2), new workspace, with Worklight Studio 6.0 installed
Go to the Servers view, start the Worklight Development Server
Create a new Worklight project
Right-click the project, choose Open Worklight Console
Does the above work?
Based on the update to the question:
The three errors regarding WorklightPU will always be displayed and are not related to your problem; we will try to remove these permanently in the future.
As for your problem: find out which process occupies port 10080, re-start Eclipse and start the Worklight Development Server again.
Alternatively, you can change the new default port number:
Navigate to the Severs view
Expend the Worklight Development Server entry
Double-click on Server Configuration
Choose HTTP Endpoint
On the right side of the window, change the port value
Restart the server
Alternatively #2, restart the machine? :)