I had a JavaFx project running perfectly on JDK 8. To connect with the database, the client calls remote interface which in turn calls the EJBs deployed on the server.
However, after successfully upgrading the JDK to 13, I am getting the below error when the database call is made...
SEVERE: CORBA MARSHAL 1330446347 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: WARNING: 00810011: Exception from readValue on ValueHandler in CDRInputStream vmcid: OMG minor code: 11 completed: Maybe
javax.ejb.EJBException: CORBA MARSHAL 1330446347 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: WARNING: 00810011: Exception from readValue on ValueHandler in CDRInputStream vmcid: OMG minor code: 11 completed: Maybe
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:127)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:99)
at com.sun.proxy.$Proxy42.loadView(Unknown Source)
Any hints on how to resolve this issue are highly appreciated.
Related
My SonarQube version is sonarqube-7.5 community edition.
Sonar Scanner version is sonar-scanner-3.3.0.1492-windows
I downloaded sonar-plsql-plugin-3.3.0.2273.jar and placed it in \sonarqube-7.5\extensions\plugins\ folder.
My operating system is Windows.
When I try to start SonarQube, I get the below exception in web.log file.
The PLSQL plugin which I am using is compatible with SonarQube 6.7+ and I am using version 7.5 (https://docs.sonarqube.org/display/PLUG/SonarPLSQL)
How could I resolve this issue and start the server?
2019.01.28 16:00:00 INFO web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000
2019.01.28 16:00:01 ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
java.lang.IllegalStateException: Fail to load plugin SonarPLSQL [plsql]
at org.sonar.server.plugins.ServerExtensionInstaller.installExtensions(ServerExtensionInstaller.java:82)
at org.sonar.server.platform.platformlevel.PlatformLevel4.start(PlatformLevel4.java:586)
at org.sonar.server.platform.Platform.start(Platform.java:211)
at org.sonar.server.platform.Platform.startLevel34Containers(Platform.java:185)
at org.sonar.server.platform.Platform.access$500(Platform.java:46)
at org.sonar.server.platform.Platform$1.lambda$doRun$0(Platform.java:119)
at org.sonar.server.platform.Platform$AutoStarterRunnable.runIfNotAborted(Platform.java:371)
at org.sonar.server.platform.Platform$1.doRun(Platform.java:119)
at org.sonar.server.platform.Platform$AutoStarterRunnable.run(Platform.java:355)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: com/sonarsource/plugins/license/api/LicensedPluginRegistration
at com.sonar.plsql.plugin.PlSqlPlugin.define(Unknown Source)
at org.sonar.server.plugins.ServerExtensionInstaller.installExtensions(ServerExtensionInstaller.java:72)
... 9 common frames omitted
Caused by: java.lang.ClassNotFoundException: com.sonarsource.plugins.license.api.LicensedPluginRegistration
at org.sonar.classloader.ParentFirstStrategy.loadClass(ParentFirstStrategy.java:39)
at org.sonar.classloader.ClassRealm.loadClass(ClassRealm.java:87)
at org.sonar.classloader.ClassRealm.loadClass(ClassRealm.java:76)
... 11 common frames omitted
2019.01.28 16:00:02 INFO web[][o.s.p.StopWatcher] Stopping process
Sonar PLSQL plugin is a commercial product. You cannot install it on SonarQube Community edition. You have to buy at least Developer edition. Read more at Plans & Pricing.
We've built a CordApp which connects with RabbitMQ and requires a configuration file to configure the subscribers and publishers to the message queues.
The CorDapp is build against 3.2-corda but fails to load the configuration file when running on a Corda Enterprise 3.2 node.
The following exception is appended to the logs when we start the Corda web server:
Starting as webserver: localhost:8080 [ERROR] 11:59:24+0000 [main]
messaging.XXX.initializeQueues - Exception caught when subscribing to
Rabbit queues [ERROR] 11:59:24+0000 [main]
messaging.XXX.initializeQueues -
net.corda.nodeapi.internal.config.ConfigUtilities.parseAs(Lcom/typesafe/config/Config;Lkotlin/reflect/KClass;)Ljava/lang/Object;
java.lang.NoSuchMethodError:
net.corda.nodeapi.internal.config.ConfigUtilities.parseAs(Lcom/typesafe/config/Config;Lkotlin/reflect/KClass;)Ljava/lang/Object;
Nov 27, 2018 11:59:25 AM
org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
The code that loads the configuration is as follows:
val connectionConfig = defaultConfig!!
.resolve()
.getConfig("app-integration.rabbitMqConnectionConfiguration")
.parseAs<RabbitMqConnectionConfiguration>()
Given we are using a generic parseAs<RabbitMqConnectionConfiguration>() method, we assume that this is intended to subsequently call a parseAs(Config, KClass): Object method, but for some reason, it seems to be missing?
I would actually take a look at #joel's suggestion above. Corda is not an 'open core' project just yet.
So it's possible that you should compile the cordapps against the enterprise jar to determine whether the issue is the app or a different API between the two corda versions.
My other suspicion is that there might be different versions of java that are being used in the corda OS and the corda enterprise.
I would also see if this issue persists in the latest version of corda as well.
I have a problem to deploy EJB and WAR modules at the same time in NetBeans 8.2 on GlassFish 4.1.1. The following message is shown:
[[ Exception Occurred :Error occurred during deployment: Exception while preparing the app : Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ejb.NewMessage/em] in the scope of the module called [TestEJB-ejb]. Please verify your application.. Please see server.log for more details.]]
When I checked server.log file of GlassFish server, I faced with the following erreor message:
[2018-07-28T12:59:45.406+0430] [glassfish 4.1] [SEVERE] [] [javax.enterprise.system.core] [tid: _ThreadID=427 _ThreadName=admin-listener(7)] [timeMillis: 1532766585406] [levelValue: 1000] [[
Exception while preparing the app : Could not resolve a persistence unit corresponding to the persistence-context-ref-name [ejb.NewEntityFacade/em] in the scope of the module called [TestEJB-ejb]. Please verify your application.]]
Is there any solution for that?
Thanks for your help.
If you did not start to create your app or if you did not choose your programming framework, you can switch to Java Spring with less headache!
Read the first paragraph of the following link:
https://en.wikipedia.org/wiki/Spring_Framework
I am running weblogic portal 10.3
We recently upgraded our oracle from 11.2 to 12.1.0.2.0
The 11g database schema was dumped when Weblogic was running and then imported to the 12c DB.
But now I see a strange problem:
On startup in my managedServer1.log.yyyy-MM-ddTHH-mm log file I see the following exception:
####<Sep 8, 2016 11:28:41 AM CEST> <Error> <DataSync> <devmaster.xxx.com> <managedServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0002F70BB8045A5B8E84> <e54db9af27ea4009:1806ee21:157091f8869:-7ffd-0000000000000002> <1473326921799> <BEA-400610> <Error performing initial refresh of persistent store. DataSync is probably in an incomplete or corrupted state.com.bea.p13n.management.data.repository.PersistenceException: Failed to refresh JDBC Persistence Manager.
at com.bea.p13n.management.data.repository.persistence.transactions.AbstractTx.sync(AbstractTx.java:67)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:215)
at com.bea.p13n.management.data.repository.persistence.JdbcPersistenceManager.refresh(JdbcPersistenceManager.java:113)
at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:164)
at com.bea.p13n.management.data.repository.MasterDataRepository.<init>(MasterDataRepository.java:49)
at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:441)
at com.bea.p13n.property.internal.PropertySetManagerImpl.ejbCreate(PropertySetManagerImpl.java:274)
at com.bea.p13n.property.internal.PropertySetManager_bjbwe8_Impl.ejbCreate(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:232)
at weblogic.ejb.container.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:132)
at weblogic.ejb.container.manager.StatelessManager.preInvoke(StatelessManager.java:148)
at weblogic.ejb.container.internal.BaseRemoteObject.preInvoke(BaseRemoteObject.java:229)
at weblogic.ejb.container.internal.StatelessRemoteObject.__WL_preInvoke(StatelessRemoteObject.java:41)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:24)
at com.bea.p13n.property.internal.PropertySetManager_bjbwe8_EOImpl.getPropertySets(Unknown Source)
at com.bea.wsrp.consumer.management.ProducerManagerImpl.internalGetCustomUserProperties(ProducerManagerImpl.java:867)
at com.bea.wsrp.consumer.management.ProducerManagerImpl.<init>(ProducerManagerImpl.java:116)
at com.bea.wsrp.consumer.management.producer.ProducerManager$Factory.<clinit>(ProducerManager.java:663)
at com.bea.wsrp.consumer.registry.DbProducerRegistryAdapter.sync(DbProducerRegistryAdapter.java:60)
at com.bea.wsrp.consumer.registry.ProducerRegistry$AddOrUpdateProducerAction.run(ProducerRegistry.java:725)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at com.bea.wsrp.consumer.registry.ProducerRegistry.refreshProducers(ProducerRegistry.java:420)
at com.bea.wsrp.consumer.registry.ProducerRegistry.loadRegistry(ProducerRegistry.java:286)
at com.bea.wsrp.consumer.registry.ProducerRegistry.load(ProducerRegistry.java:196)
at com.bea.wsrp.consumer.registry.ProducerRegistry.getInstance(ProducerRegistry.java:160)
at com.bea.netuix.servlets.manager.PortalServlet.startProducerRegistryFilePoller(PortalServlet.java:599)
at com.bea.netuix.servlets.manager.PortalServlet.reinitInternal(PortalServlet.java:313)
at com.bea.netuix.servlets.manager.PortalServlet.initInternal(PortalServlet.java:268)
at com.bea.netuix.servlets.manager.PortalServlet.access$200(PortalServlet.java:125)
at com.bea.netuix.servlets.manager.PortalServlet$ServletLifecycleListenerImpl.init(PortalServlet.java:2190)
at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:183)
at com.bea.netuix.servlets.manager.PortalServlet.init(PortalServlet.java:259)
at com.bea.netuix.servlets.manager.PortalServlet.init(PortalServlet.java:236)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1984)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1958)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1877)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3174)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1527)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:489)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:187)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:379)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: com.bea.p13n.management.data.repository.PersistenceException: Cannot commit: java.sql.SQLException: Could not commit with auto-commit set on
at com.bea.p13n.management.data.repository.persistence.transactions.AbstractTx.doTransaction(AbstractTx.java:118)
at com.bea.p13n.management.data.repository.persistence.transactions.AbstractTx.sync(AbstractTx.java:62)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:215)
at com.bea.p13n.management.data.repository.persistence.JdbcPersistenceManager.refresh(JdbcPersistenceManager.java:113)
at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:164)
at com.bea.p13n.management.data.repository.MasterDataRepository.<init>(MasterDataRepository.java:49)
The result of this is that EJBs cause some NullPointerExceptions and my code fails. If I refresh the page enough times, the EJBs seem to be refreshed and start working fine.
But on restarts this problem shows up again.
I tried clearing out the WEBLOGICJMSSTATE table before start up, but there seems to be no effect.
Any suggestions?
Thanks.
Turned out to be an issue with the new driver. I guess the clue was in the text
java.sql.SQLException: Could not commit with auto-commit set on
I got rid of the error setting this JVM param:
-Doracle.jdbc.autoCommitSpecCompliant=false
Thanks to the answer here: java.sql.SQLException: Could not commit with auto-commit set on at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:4443)
I am trying to build a sample spring MVC app using Maven and getting deployed in JBoss 7 application server.
While trying to build using maven, it builds fine without error. However while trying to deploy using JBoss 7, I am getting this following error.
Kindly help to give ideas what might be the cause of this error.
13:48:36,408 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."firstSpring-1.0-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."firstSpring-1.0-SNAPSHOT.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "firstSpring-1.0-SNAPSHOT.war"
Caused by: java.lang.RuntimeException: Error getting reflective information for class org.springframework.web.servlet.tags.EvalTag with ClassLoader ModuleClassLoader for Module "deployment.firstSpring-1.0-SNAPSHOT.war:main" from Service Module Loader
Caused by: java.lang.NoClassDefFoundError: org/springframework/expression/PropertyAccessor
Caused by: java.lang.ClassNotFoundException: org.springframework.expression.PropertyAccessor from [Module "deployment.firstSpring-1.0-SNAPSHOT.war:main" from Service Module Loader]