Weblogic 10.3.4 & Spring 3.0.6 & web.xml - spring

currently working on developing a rest service that needs to be deployed on Weblogic 10.3.4. Using Spring 3.0.6 examples online but the basic loading of the DispatcherServlet seems to be causing problems with Weblogic.
<servlet>
<servlet-name>mvc-dispatcher</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
The exception shown in the weblogic console window was:
<07-Nov-2011 20:29:33 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
log4j:WARN No appenders could be found for logger (org.springframework.web.servlet.DispatcherServlet).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
=============== DEBUG MESSAGE: unimplemented bytecode ================
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_PRIV_INSTRUCTION (0xc0000096) at pc=0x026b26d0, pid=7200, tid=7924
#
# JRE version: 6.0_21-b51
# Java VM: Java HotSpot(TM) Client VM (17.0-b17 mixed mode windows-x86 )
# Problematic frame:
# j javax.validation.Validation.byDefaultProvider()Ljavax/validation/bootstrap/GenericBootstrap;+0
#
# An error report file with more information is saved as:
# C:\bea\user_projects\domains\saw_ca_wl10\hs_err_pid7200.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
The exception shown in the target AdminServer log was
####<07-Nov-2011 20:29:54 o'clock GMT> <Info> <EJB> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697794074> <BEA-010008> <EJB Deploying file: KCS-ejb-0.0.1-SNAPSHOT.jar>
####<07-Nov-2011 20:29:54 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697794499> <BEA-149060> <Module KCS-ejb-0.0.1-SNAPSHOT.jar of application KCS-ear-0 successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
####<07-Nov-2011 20:29:54 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697794499> <BEA-149059> <Module /KCS-webApp of application KCS-ear-0 is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697795146> <BEA-149060> <Module /KCS-webApp of application KCS-ear-0 successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697795270> <BEA-149059> <Module KCS-ejb-0.0.1-SNAPSHOT.jar of application KCS-ear-0 is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697795301> <BEA-149060> <Module KCS-ejb-0.0.1-SNAPSHOT.jar of application KCS-ear-0 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697795301> <BEA-149059> <Module /KCS-webApp of application KCS-ear-0 is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <Deployer> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320697795302> <BEA-149060> <Module /KCS-webApp of application KCS-ear-0 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<07-Nov-2011 20:29:55 o'clock GMT> <Info> <ServletContext-/KCS-webApp> <JGOGGINS212> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1320697795498> <BEA-000000> <Initializing Spring FrameworkServlet 'mvc-dispatcher'>
Building using Maven and have all the spring-core/web/webmvc/context all defined as runtime dependent.
Also tried to copy the "org.springframework.web.servlet-3.0.5.RELEASE,jar" file to the bea\modules folder in an attempt to resolve runtime issues within weblogic.
Tried the weblogic-application.xml,
<prefer-application-packages>
<package-name>org.springframework.*</package-name>
<package-name>org.springframework.web.*</package-name>
<package-name>org.springframework.web.servlet.*</package-name>
<prefer-application-packages>
All that, same problem.
I noted that the release notes have stated that "This version of WebLogic Server supports Spring 3.0.", http://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm#BGGEAIJJ

Function code is limited by the size 64 KB in both version of Java 7 and 8. When our code exceeds more than 64 KB in function Compiler failed to compile the whole code and throws error as Unimplemented Byte Code
COMPILE ERROR:
ERROR MESSAGES/STACK TRACES THAT OCCUR :
=============== DEBUG MESSAGE: unimplemented bytecode ================
A fatal error has been detected by the Java Runtime Environment:
Note: Here function is consider as
1)Function is normal function one we write in jsp or java file.
2)Our normal jsp(Java Server Page) page is also treated as function when it is complied in java programming
Example:
// The Function Size Should Less Than 64KB
public static function myFunction(){
// Your Code
}

Related

Paring log text through grok filter in logstash on the given log structure

2019-04-01 10:57:35|[a1vx4d9r - ecaf-myself - N2PENL-ECFA0141.india.airtel.itm - servlet:/reserveNumbers/getAvailableNumbers/v1?httpMethodRestrict=POST ][[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO|com.airtel.common.aop.LogExecutionTime|EXECUTION TIME LOGGING METHODNAME: postResponseFromESB EXECUTION TIME: 472 ms
Above is the log format.
Please help in writing a grok filter in logstash that separates the fields as shown below:
timestamp: 2019-04-01 10:57:35
user_id:a1vx4d9r
project name: ecaf-myself
host_name: N2PENL
api_name:ECFA0141.india.airtel.itm - servlet:/reserveNumbers/getAvailableNumbers/v1?httpMethodRestrict=POST
thread_id: [ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'
log_level: INFO
Method_name:postResponseFromESB
Method_time:472
Writing grok filters are easy with all the required patterns already defined here. You could use this app to try out your grok filter, and see if it is matching your log pattern: http://grokdebug.herokuapp.com/
For the above example, the below grok filter will work. You can check and fine tune it to fit your needs using the above two resources:
%{TIMESTAMP_ISO8601}.*\[%{WORD:user_id}* - %{NOTSPACE:project_name}* - %{WORD:host_name}*-%{DATA:api_name} \]%{GREEDYDATA:thread}\] %{WORD:log_level}.*METHODNAME: %{WORD:Method_name}.*EXECUTION TIME: %{INT:Method_time}

Receive 500 error in Load test of weblogic

I try to load test an ADF web site that deployed on a Weblogic server with WPLT 6.6 . when I Replay single transaction, everything is OK and also when I try to load test for one user everything is OK, but when the second concurrent user enter the test, the server response with 500 error (validation). I do not know what is the problem.
welogic's log :
####<Jul 11, 2017 10:48:16 AM IRDT> <Info> <DiagnosticsWatch> <APP-EGOV> <EBOX_MNGS02> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3992c89e-704b-431b-8d6d-3e5db34763d3-000025c7> <1499753896280> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-320204> <Executing action FMWDFW-notification with timeout period 0 seconds.>
####<Jul 11, 2017 10:48:57 AM IRDT> <Error> <HTTP> <APP-EGOV> <EBOX_MNGS02> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3992c89e-704b-431b-8d6d-3e5db34763d3-000027cf> <1499753937625> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101020> <[ServletContext#142750200[app:EboxInboxApp module:Inbox path:null spec-version:3.1]] Servlet failed with an Exception
java.lang.RuntimeException: An attempt has been made to update the immutable value associated with parameter DSID in context 3992c89e-704b-431b-8d6d-3e5db34763d3-000027cf,0. The parameter is not updateable.
at oracle.dms.context.internal.wls2.WLS2ExecutionContext.setValueAccordingToDescriptor(WLS2ExecutionContext.java:639)
at oracle.dms.context.ExecutionContext.setValue(ExecutionContext.java:1021)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:211)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3654)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3620)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:196)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2423)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2280)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2258)
at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1626)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1586)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
>
####<Jul 11, 2017 10:48:57 AM IRDT> <Notice> <Diagnostics> <APP-EGOV> <EBOX_MNGS02> <[STANDBY] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3992c89e-704b-431b-8d6d-3e5db34763d3-000027d8> <1499753937628> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-320068> <Watch "UncheckedException" in module "Module-FMWDFW" with severity "Notice" on server "EBOX_MNGS02" has triggered at Jul 11, 2017 10:48:57 AM IRDT. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: MESSAGE = [ServletContext#142750200[app:EboxInboxApp module:Inbox path:null spec-version:3.1]] Servlet failed with an Exception
java.lang.RuntimeException: An attempt has been made to update the immutable value associated with parameter DSID in context 3992c89e-704b-431b-8d6d-3e5db34763d3-000027cf,0. The parameter is not updateable.
at oracle.dms.context.internal.wls2.WLS2ExecutionContext.setValueAccordingToDescriptor(WLS2ExecutionContext.java:639)
at oracle.dms.context.ExecutionContext.setValue(ExecutionContext.java:1021)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:211)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3654)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3620)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
Here is the most common cause of an HTTP 500 during a performance test
Failure to check every request for a positive expected result (not just HTTP 200) and then a failure to branch the code when an unexpected result occurs. The HTTP 500 then occurs one or two steps down the line past the point where the valid HTTP 200 request response with the unexpected response content appears. The end result is that the next (or possibly next next) request is out of context with the state of the business process. As an unhandled exception from development (because a natural user would not be able to progress) an HTTP 500 results.
As to why the business process has come off the rails? The reasons are multitude. You could have some unhandled dynamic data related to session, state, time, security tokens, user credentials, business process data/keys, etc... You may have data which is in a different state that what is needed for the business process, such as trying to re-use, use-once data. You may even have someone else changing the state of your data during your test if you share your environment and test data with other groups at the same time.
If you are not actively checking in your test code for a positive, expected condition with each test step (test 101 stuff) then what you are doing is "throwing load" and these types of HTTP 500 errors should be expected and common.

weblogic is running (without asking username and password) but Oracle form doesn't open, 404 Error occures

I have a issue in Oracle WebLogic and don't know how to go through it. Please Help.
First I start the WebLogic and it gives no error and turns into running state without asking username and password.
Then if I go to http://vm-pc:7001/forms/frmservlet then following page displays:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Moreover, http://vm-pc:7001/console/login/LoginForm.jsp links works correctly, ask me username and password and then shows me the health of my adminserver 100% OK and Running
Please help me what I am missing ..
Thanks
Last lines from AdminServer.log
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426719869> <BEA-000365> <Server state changed to STANDBY>
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426719884> <BEA-000365> <Server state changed to STARTING>
####<> <Info> <SAFService> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426719931> <BEA-281003> <SAF Service has been initialized.>
####<> <Info> <SAFService> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426719962> <BEA-281002> <SAF Service has been started.>
####<> <Info> <WseeCore> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426719994> <BEA-220502> <The Wsee Service is starting>
####<> <Info> <Deployer> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720072> <BEA-149209> <Resuming.>
####<> <Info> <WebLogicServer> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720306> <BEA-000256> <Invoking weblogic.transaction.internal.StartupClass.main(null)>
####<> <Info> <Diagnostics> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720384> <BEA-320000> <The Diagnostics subsystem is initializing on Server AdminServer.>
####<> <Info> <Store> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720400> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
####<> <Info> <Store> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720400> <BEA-280103> <The persistent file store "WLS_DIAGNOSTICS" will cache in weblogic.store.io.file.direct.FileMapping[granularity=65536 io=mapped].>
####<> <Info> <Store> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720572> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (f1c1e427-9a57-4a60-94ba-ebb09401a1b3) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=23.>
####<> <Info> <Log Management> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720697> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs/base_domain.log.>
####<> <Notice> <Log Management> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426720728> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<> <Info> <Diagnostics> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426721369> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426722056> <BEA-000365> <Server state changed to ADMIN>
####<T> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426722947> <BEA-000365> <Server state changed to RESUMING>
####<> <Info> <Management> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426722947> <BEA-141052> <The auto deployment poller has started.>
####<> <Warning> <Server> <VM-PC> <AdminServer> <DynamicListenThread[Default[2]]> <<WLS Kernel>> <> <> <1473426723103> <BEA-002611> <Hostname "VM-PC", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1>
####<> <Info> <Server> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426723103> <BEA-002610> <Dynamic Listener Service initialized.>
####<> <Notice> <Server> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426723103> <BEA-002613> <Channel "Default" is now listening on fe80:0:0:0:0:100:7f:fffe:7001 for protocols iiop, t3, ldap, snmp, http.>
####<> <Notice> <Server> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426723103> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
####<> <Notice> <Server> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426723103> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426723103> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode>
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426723259> <BEA-000365> <Server state changed to RUNNING>
####<> <Notice> <WebLogicServer> <VM-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1473426723259> <BEA-000360> <Server started in RUNNING mode>
####<> <Info> <J2EE> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426726369> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
####<> <Info> <EJB> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426727213> <BEA-010008> <EJB Deploying file: mejb.jar>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730004> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730676> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730692> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730707> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730723> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <WebService> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473426730723> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<> <Info> <EJB> <VM-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473426730989> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
####<> <Info> <Health> <VM-PC> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1473426781812> <BEA-310002> <89% of the total memory in the server is free>
####<> <Info> <WorkManager> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473427794505> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<> <Info> <netuix> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473427798711> <BEA-423101> <[console] Initializing the NetUIx container>
####< <Info> <netuix> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473427799602> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<> <Info> <netuix> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473427800464> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
####<> <Info> <netuix> <VM-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1473427800636> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<> <Info> <Health> <VM-PC> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1473427872292> <BEA-310002> <62% of the total memory in the server is free>

Remote Coherence client gives error

My remote coherence server(with script got from coherence 3.6.1 download) is getting started with ipaddress as 169.177.81.97 and port as 8088.I have not started weblogic server for this.Now when I try to connect it with client in different machine it gives me an error:
2016-08-08 15:06:20.423/0.237 Oracle Coherence 3.6.1.0 <Info> (thread=main, member=n/a): Loaded operational configuration from "jar:file:/C:/Test/RemoteCache/lib/coherence.jar!/tangosol-coherence.xml"
2016-08-08 15:06:20.427/0.241 Oracle Coherence 3.6.1.0 <Info> (thread=main, member=n/a): Loaded operational overrides from "jar:file:/C:/Test/RemoteCache/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2016-08-08 15:06:20.429/0.243 Oracle Coherence 3.6.1.0 <Info> (thread=main, member=n/a): Loaded operational overrides from "file:/C:/Test/RemoteCache/bin/tangosol-coherence-override.xml"
2016-08-08 15:06:20.435/0.249 Oracle Coherence 3.6.1.0 <D5> (thread=main, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
Oracle Coherence Version 3.6.1.0 Build 19636
Grid Edition: Development mode
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
2016-08-08 15:06:20.618/0.432 Oracle Coherence GE 3.6.1.0 <Info> (thread=main, member=n/a): Loaded cache configuration from "file:/C:/Test/RemoteCache/bin/example-config.xml"
2016-08-08 15:06:20.900/0.714 Oracle Coherence GE 3.6.1.0 <D5> (thread=ExtendTcpCacheService:TcpInitiator, member=n/a): Started: TcpInitiator{Name=ExtendTcpCacheService:TcpInitiator, State=(SERVICE_STARTED), ThreadCount=0, Codec=Codec(Format=POF), Serializer=com.tangosol.io.DefaultSerializer, PingInterval=0, PingTimeout=5000, RequestTimeout=5000, ConnectTimeout=10000, SocketProvider=SystemSocketProvider, RemoteAddresses=[/169.177.81.97:8088], SocketOptions{LingerTimeout=0, KeepAliveEnabled=true, TcpDelayEnabled=false}}
2016-08-08 15:06:20.907/0.721 Oracle Coherence GE 3.6.1.0 <D5> (thread=main, member=n/a): Connecting Socket to 169.177.81.97:8088
2016-08-08 15:06:20.949/0.763 Oracle Coherence GE 3.6.1.0 <Info> (thread=main, member=n/a): Connected Socket to 169.177.81.97:8088
2016-08-08 15:06:30.972/10.786 Oracle Coherence GE 3.6.1.0 <Info> (thread=main, member=n/a): Error establishing a connection with 169.177.81.97:8088: ******com.tangosol.net.RequestTimeoutException: request timed out after 10000 millis
Exception in thread "main" com.tangosol.net.messaging.ConnectionException: could not establish a connection to one of the following addresses: [169.177.81.97:8088]; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor****
at** com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator$TcpConnection.open(TcpInitiator.CDB:64)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:12)
at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:5)
at com.tangosol.coherence.component.net.extend.RemoteService.doStart(RemoteService.CDB:11)
at com.tangosol.coherence.component.net.extend.RemoteService.start(RemoteService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:28)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:1057)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:892)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:874)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1231)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:290)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:712)
at com.test.TestClient.main(TestClient.java:15)
2016-08-08 15:06:30.973/10.787 Oracle Coherence GE 3.6.1.0 <Error> (thread=main, member=n/a): Error while starting service "ExtendTcpCacheService": com.tangosol.net.messaging.ConnectionException: could not establish a connection to one of the following addresses: [169.177.81.97:8088]; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator$TcpConnection.open(TcpInitiator.CDB:64)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:12)
at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:5)
at com.tangosol.coherence.component.net.extend.RemoteService.doStart(RemoteService.CDB:11)
at com.tangosol.coherence.component.net.extend.RemoteService.start(RemoteService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:28)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:1057)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:892)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:874)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1231)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:290)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:712)
at com.test.TestClient.main(TestClient.java:15)
2016-08-08 15:06:30.974/10.788 Oracle Coherence GE 3.6.1.0 <D5> (thread=ExtendTcpCacheService:TcpInitiator, member=n/a): Stopped: TcpInitiator{Name=ExtendTcpCacheService:TcpInitiator, State=(SERVICE_STOPPED), ThreadCount=0, Codec=Codec(Format=POF), Serializer=com.tangosol.io.DefaultSerializer, PingInterval=0, PingTimeout=5000, RequestTimeout=5000, ConnectTimeout=10000, SocketProvider=SystemSocketProvider, RemoteAddresses=[/169.177.81.97:8088], SocketOptions{LingerTimeout=0, KeepAliveEnabled=true, TcpDelayEnabled=false}}
Client code:
tangosol-coherence-override.xml
<cache-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config
coherence-cache-config.xsd">
<caching-scheme-mapping>
<cache-mapping>
<cache-name>dist-extend</cache-name>
<scheme-name>remote</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<remote-cache-scheme>
<scheme-name>remote</scheme-name>
<service-name>ExtendTcpCacheService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>169.177.81.97</address>
<port>8088</port>
</socket-address>
</remote-addresses>
<connect-timeout>10s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>5s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-cache-scheme>
<remote-invocation-scheme>
<scheme-name>extend-invocation</scheme-name>
<service-name>ExtendTcpInvocationService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>169.177.81.97</address>
<port>8088</port>
</socket-address>
</remote-addresses>
<connect-timeout>10s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>5s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-invocation-scheme>
</caching-schemes>
</cache-config>
example-config.xml
<?xml version="1.0"?>
<cache-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config
coherence-cache-config.xsd">
<caching-scheme-mapping>
<cache-mapping>
<cache-name>dist-extend</cache-name>
<scheme-name>remote</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<remote-cache-scheme>
<scheme-name>remote</scheme-name>
<service-name>ExtendTcpCacheService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>169.177.81.97</address>
<port>8088</port>
</socket-address>
</remote-addresses>
<connect-timeout>10s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>5s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-cache-scheme>
<remote-invocation-scheme>
<scheme-name>extend-invocation</scheme-name>
<service-name>ExtendTcpInvocationService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>169.177.81.97</address>
<port>8088</port>
</socket-address>
</remote-addresses>
<connect-timeout>10s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>5s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-invocation-scheme>
</caching->
</cache-config>
TestClient.java
package com.test;
import com.tangosol.net.AbstractInvocable;
import com.tangosol.net.CacheFactory;
import com.tangosol.net.InvocationService;
import com.tangosol.net.NamedCache;
import java.util.Map;
public class TestClient {
public static void main(String[] asArgs)
throws Throwable
{
NamedCache cache = CacheFactory.getCache("dist-extend");
Integer IValue = (Integer) cache.get("key");
if (IValue == null)
{
IValue = new Integer(2);
}
else
{
IValue = new Integer(IValue.intValue() + 1);
}
cache.put("key", 5);
System.out.print("The value of the key is " + cache.get("key"));
}
}
Server Startup script:
#!/bin/sh
# This will start a cache server
# specify the Coherence installation directory
COHERENCE_HOME=/apps/p1devbDomain/coherence
# specify the JVM heap size
MEMORY=512m
if [ ! -f ${COHERENCE_HOME}/bin/cache-server.sh ]; then
echo "coherence.sh: must be run from the Coherence installation directory."
exit
fi
if [ -f $JAVA_HOME/bin/java ]; then
JAVAEXEC=$JAVA_HOME/bin/java
else
JAVAEXEC=java
fi
JAVA_OPTS="-Xms$MEMORY -Xmx$MEMORY -Djava.net.preferIPv4Stack=true"
echo $COHERENCE_HOME
echo starting with
echo $JAVAEXEC -server -showversion $JAVA_OPTS -cp "$COHERENCE_HOME/lib/coherence.jar;$COHERENCE_HOME/lib/coherence-web-spi.war" -Dtangosol.coherence.management.remote=true -Dtangosol.coherence.cacheconfig=WEB-INF/classes/session-cache-config.xml -Dtangosol.coherence.distributed.localstorage=true -Dtangosol.coherence.session.localstorage=true com.tangosol.net.DefaultCacheServer $1
echo ----------------------------------------------------
$JAVAEXEC -server -showversion $JAVA_OPTS -cp "$COHERENCE_HOME/lib/coherence.jar:$COHERENCE_HOME/lib/coherence-web-spi.war" -Dtangosol.coherence.management.remote=true -Dtangosol.coherence.extend.enabled=true -Dtangosol.coherence.cacheconfig=WEB-INF/classes/session-cache-config.xml -Dtangosol.coherence.distributed.localstorage=true -Dtangosol.coherence.session.localstorage=true com.tangosol.net.DefaultCacheServer $1 &
Can someone help on this.

Change the leak time threshold in weblogic 10.3.6

I am seeing this error in the logs but the JDBC connection never runs out (only have one), I wanted to increase the threshold to see if the exception goes away.
Exception:
[[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)']
2013-07-23 17:07:10.913 0 Error Exception java.lang.Throwable: Connection leak found: created statck
java.lang.Throwable: Connection leak found: created statck
at glog.util.j2ee.jdbc.ASJTSConnection.(ASJTSConnection.java:23)
at glog.util.j2ee.jdbc.ASConnectionEstablisher.connect(ASConnectionEstablisher.java:44)
at glog.util.j2ee.jdbc.WLConnectionPoolInstance.reserve(WLConnectionPoolInstance.java:46)
at glog.util.j2ee.jdbc.ASConnectionPoolInstance.reserve(ASConnectionPoolInstance.java:60)
at glog.util.datasource.AppServerConnectionPool.reserve(AppServerConnectionPool.java:34)
at glog.util.datasource.DataSource.reserve(DataSource.java:143)
at glog.util.datasource.DataSource.reserve(DataSource.java:137)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:301)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:291)
at glog.util.jdbc.noserver.T2SharedConnection.open(T2SharedConnection.java:57)
at glog.server.query.JDBCConnection.open(JDBCConnection.java:30)
at glog.server.query.JDBCFinder.openConnection(JDBCFinder.java:283)
at glog.server.query.JDBCFinder.open(JDBCFinder.java:146)
at glog.server.query.ListRetrieverBean.retrieve(ListRetrieverBean.java:39)
at glog.server.query.ListRetrieverServerSideEJBWrapper.retrieve(ListRetrieverServerSideEJBWrapper.java:40)
at glog.server.query.query_ListRetriever_whmeh3_EOImpl.retrieve(query_ListRetriever_whmeh3_EOImpl.java:58)
at glog.server.query.query_ListRetriever_whmeh3_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Resources