iI have an ear file which successfully deployed on JBoss7 & WebSphere 8.5
When trying on WebLogic 12c I'm getting this error at the AdminServer.log:
####<Apr 10, 2013 5:29:36 PM IDT> <Error> <J2EE> <wbl12t2.autowblciddmeronserver.autop> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1365604176997> <BEA-160228> <AppMerge failed to merge your application. Merge again with the -verbose option for more details. See the error message(s) below.>
####<Apr 10, 2013 5:30:09 PM IDT> <Debug> <Socket> <wbl12t2.autowblciddmeronserver.autop> <AdminServer> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1365604209078> <BEA-000450> <Socket 420 internal data record unavailable (probable closure due idle timeout), event received -32>
and this in the web console:
Error Unable to access the selected application.
Error Exception in AppMerge flows' progression
Error Exception in AppMerge flows' progression
Error com.demo.tasks.api.RTExecutor
Error com.demo.tasks.api.RTExecutor
The ear use jax-ws and jax-rs (using Jersey dependency).
the class com.demo.tasks.api.RTExecutor is interface with #WebService annotation.
Does anyone know what the problem is?
Is there anyway to get more details about the problems (more log files I miss, etc..)?
I was receiving the same error code and, after a bit of digging, I found out that Weblogic wants the extension of you EAR to be all lower case, otherwise it considered it invalid.
So your application must be called YourApp.ear and cannot be called YourApp.EAR for example.
Related
I have been able to use the Essbase console since we imported a new certificate in May. I was fine last week, but beginning Monday I am getting 'Unable to connect to Essbase Administrator Server" when trying to login to the console. I can login to Shared services, but cannot open any folders there. I found the following errors in EssbaseAdminServices0.log.
####<Jun 13, 2022 7:22:57 AM EDT> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <>
<1655119377687> <No identity key/certificate entry was
found under alias ess1ssl in keystore
E:\Oracle\Middleware\ssl\custident.jks on server
EssbaseAdminServices0>
####<Jun 13, 2022 7:22:57 AM EDT> <[ACTIVE] ExecuteThread: '0'
for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
<> <1655119377687> <Inconsistent security configuration,
weblogic.management.configuration.ConfigurationException: No identity
key/certificate entry was found under alias ess1ssl in keystore
E:\Oracle\Middleware\ssl\custident.jks on server
EssbaseAdminServices0>
####<Jun 13, 2022 7:22:57 AM EDT> <[ACTIVE] ExecuteThread: '0'
for queue: 'weblogic.kernel.Default (self-tuning)'> <> <>
<> <1655119377687> <Not listening for SSL,
java.io.IOException: No identity key/certificate entry was found under
alias ess1ssl in keystore E:\Oracle\Middleware\ssl\custident.jks on
server EssbaseAdminServices0.>
I have verified the Oracle cert in the oracle wallet is valid until May 2023, but cannot see if the alias is in the wallet. I did issue a Keytool command and found the alias is listed there. I have restarted the services and rebooted the servers to no avail. I am not aware of anything changing over the weekend. I have also tried using localhost:9000 instead of the server name and that did not work. Essbase itself is working fine, the cubes are loaded and the users have access via Smartview. Suggestions?
Thanks!
MaggieW
Hi My current environment is Weblogic 12c Std
i have 2 servers which is running one Admin server 2 managed servers
Node -1 contains admin & 1 managed servers
Node -2 contains Managed servers
My issues is i am able to stop node-2 managed server node 2 from Admin console but not able to start from Admin console
While start i am getting below Error on Console
Message icon - Warning For server mrm_node2, the Node Manager associated with machine mrm_machine2 is not reachable.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
In Adminserver log i am getting below warning
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1505972472314>
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1505972472314>
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1505972472314>
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1505972472315>
Note:-- I enrolled NM Control on Node-2 also
To be able to start a Managed Server via the Admin Server, the Node Manager needs to be running and obviously be reachable.
You can start the Node Manager with the startNodeManager.sh script in <weblogic-home>/server/bin.
If the Managed Server is already running you can shut it down through the Admin Server even without the Node Manager, because then the Managed Server is already in communication with the Admin Server.
My project war file gets deployed successfully on tomcat 7 but not on weblogic 12c.
While deploying a .war file on Weblogic 12c application server, I am getting the following exception:
<Error> <com.sun.xml.ws.wspolicy.jaxws.PolicyWSDLParserExtension> <DDC5-D-339ST4L> <myserver> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1399618140264> <BEA-000000> <WSP1007: Policy exception occurred when finishing WSDL parsing.
com.sun.xml.ws.policy.PolicyException: WSP1005: Failed to find policy referenced by URI "zip:../wls1212_dev/wls12120/user_projects/domains/mydomain/servers/myserver/tmp/_WL_user/<war name>/oiv6rb/war/WEB-INF/lib/wsit-rt-1.1.jar!/WEB-INF/wsdl/wscoor.wsdl#Addressing_policy".
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:100)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:110)
at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:72)
at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:82)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:109)
at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:91)
at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.postFinished(PolicyWSDLParserExtension.java:970)
at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.postFinished(DelegatingParserExtension.java:191)
at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.postFinished(WSDLParserExtensionFacade.java:338)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:331)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:746)
at com.sun.xml.ws.server.EndpointFactory.create(EndpointFactory.java:254)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:158)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:577)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:560)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:639)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:194)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:173)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:85)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:63)
at javax.servlet.GenericServlet.init(GenericServlet.java:240)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:337)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:288)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.StubSecurityHelper.initServletInstance(StubSecurityHelper.java:98)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:86)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:74)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:60)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:34)
at weblogic.servlet.internal.ServletStubImpl.initStubLifecycleHelper(ServletStubImpl.java:652)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:593)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1924)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1901)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1791)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2807)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1661)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:822)
at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)
at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:586)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
Please suggest something. Let me know in case more details are required.
I want to run a web application on a cluster.There are 2 servers(10.0.0.32 and 10.0.0.192). When I try to run this application on 10.0.0.192 I am getting below error.
By the way I am using adminserver on 10.0.0.32. I can control server 10.0.0.192 without any problem from 10.0.0.32 adminserver.
####<Dec 30, 2013 3:02:36 PM EET> <Error> <HTTP> <dell-PC> <10-0-0-192> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1388408556025> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP#4bd7f3dd:Socket[addr=/10.0.0.32,port=55179,localport=7002] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1076)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:293)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Cause:
The above error indicates that the default configured timeout period of '60' secs is not sufficinet to transfer the complete message to the server.
Resolution:
Increase the Complete Message Time Out to 480 seconds in weblogic console:
Server --> Protocols --> General -> Advanced Attributes -> Complete Message Timeout
You must reboot the server.
A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection'" on WebLogic :
weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection#12c22dd4', in the configured timeout period of '60' secs
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
for this we can increase timeout period by setting the parameters
-Dweblogic.CompleteT3MessageTimeout=
-Dweblogic.CompleteMessageTimeout=
We are receiving the following error -- a thread gets stuck -- when we try to start any managed server in our cluster via the admin console in Weblogic 10.3.2. The managed servers used to start up fine last week. The only difference between this week and last week is that our VM (virtual machine) was powered down for a week. We started it back up and tried to bring up the managed servers and we get this error. My inkling is that something changed in the physical host or VM configuration (external to our operating system), but I have been told that none of that had been changed.
We are running WebLogic on Windows Server 2008.
Any ideas?
<Jan 3, 2011 6:10:45 PM GMT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy fo
r "228" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1#291d575", which is more than the configured time (StuckThreadMaxTime) of "120" second
s. Stack trace:
jrockit.net.SocketNativeIO.readBytesPinned(Native Method)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:32)
java.net.SocketInputStream.socketRead0(SocketInputStream.java)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
java.io.InputStream.read(InputStream.java:85)
com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
com.certicom.tls.record.ReadHandler.read(Unknown Source)
com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:287)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:312)
weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:101)
weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:47)
weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
For us, we received this error because our Weblogic instances, which are configured with an Active Directory provider could not communicate with Active Directory. Once we fixed the communication issue, this problem went away.