weblogic

How to specify portable jndi datsource lookup in grails

孤街浪徒 提交于 2020-01-17 05:45:20
问题 I know JNDI lookup in grails is as simple as datasource { jndiName = "java:comp/env/myDataSource" } this works great on Tomcat. On other containers (WebLogic, JBOSS, etc.) the jndiName for the same thing would be just myDataSource . The question is how do I configure this to be generic and portable so that the code does not need to be changed based on the deploy target? 回答1: You might be able to key off a system property that you know will be set when running in Tomcat and not set anywhere

Is it safe to delete the stage directory?

有些话、适合烂在心里 提交于 2020-01-17 05:10:28
问题 One of my servers is running out of capacity, mostly due to WebLogic's stage folder. I've been looking for information and it seems to be a temporal folder, but unlike older versions, on WL11g this folder is out of the tmp folder. So I'm not sure whether or not I can safely remove it. 回答1: Stage directory is where weblogic copies all the applications that it needs to deploy on to the managed servers. Wls does not delete any file from this folder. So in the long run if you have done deployment

WLST query (List deployed applications and hosts together)

北城余情 提交于 2020-01-16 14:40:36
问题 I have two WLST queries. I execute it through WebLogic Scripting Tool console. These queries are: 1) List of deployed applications and status: connect('weblogic','password','t3://localhost:7001') cd('AppDeployments') deplymentsList=cmo.getAppDeployments() for app in deplymentsList: domainConfig() cd ('/AppDeployments/'+app.getName()+'/Targets') mytargets = ls(returnMap='true') domainRuntime() cd('AppRuntimeStateRuntime') cd('AppRuntimeStateRuntime') for targetinst in mytargets: curstate4=cmo

WLST query (List deployed applications and hosts together)

旧街凉风 提交于 2020-01-16 14:40:21
问题 I have two WLST queries. I execute it through WebLogic Scripting Tool console. These queries are: 1) List of deployed applications and status: connect('weblogic','password','t3://localhost:7001') cd('AppDeployments') deplymentsList=cmo.getAppDeployments() for app in deplymentsList: domainConfig() cd ('/AppDeployments/'+app.getName()+'/Targets') mytargets = ls(returnMap='true') domainRuntime() cd('AppRuntimeStateRuntime') cd('AppRuntimeStateRuntime') for targetinst in mytargets: curstate4=cmo

weblogic access.log日志常见分析

随声附和 提交于 2020-01-16 03:10:24
1,查看apache进程: ps aux | grep httpd | grep -v grep | wc -l // ps aux是显示所有进程和其状态。 2,查看80端口的tcp连接: netstat -tan | grep "ESTABLISHED" | grep ":80" | wc -l 3,通过日志查看当天ip连接数,过滤重复: cat access_log | grep "19/May/2011" | awk '{print $2}' | sort | uniq -c | sort -nr 4,当天ip连接数最高的ip都在干些什么(原来是蜘蛛): cat access_log | grep "19/May/2011:00" | grep "61.135.166.230" | awk '{print $7}' | sort | uniq -c | sort -nr | head -n 10 5,当天访问页面排前10的url: cat access_log | grep "19/May/2010:00" | awk '{print $7}' | sort | uniq -c | sort -nr | head -n 10 6,用tcpdump嗅探80端口的访问看看谁最高 tcpdump -i eth0 -tnn dst port 80 -c 1000 | awk -F".

weblogic忘记用户密码

末鹿安然 提交于 2020-01-15 13:09:04
1、进入%DOMAIN_HOME%/security目录,执行   java -cp /opt/weblogic/bea/middleware/wlserver_10.3/server/lib/weblogic.jar weblogic.security.utils.AdminAccount weblogic password . 2、进入%domain_home%/servers/%AdminServer%/data/ldap目录下,删除DefaultAuthenticatormyrealmInit.initialized 3、重启Server,用新帐号登录Admin Console,这样就拥有了进入后台的admin用户和密码(weblogic / password) 4、进入修改Console,安全领域 --> myrealm --> 用户和组,即可以修改原用户weblogic的密码。 5、停止wls服务器,编辑%DOMAIN_HOME%/servers/AdminServer/security/boot.properties   username=weblogic   password=password 来源: https://www.cnblogs.com/yangxuyang/p/12195925.html

Should EJBs be instance variables and marked as transient in JSF Managed Beans?

你说的曾经没有我的故事 提交于 2020-01-15 05:22:20
问题 We have several JSF Managed beans with Request, View, and Session Scope and are running WebLogic 11g (10.3.2). Weblogic does not support the @EJB annotation in a JSF Managed Bean, so we have used these procedures http://technology.amis.nl/2008/12/06/ejb-dependency-injection-of-session-bean-facade-in-jsf-12-on-weblogic-103-jsf-with-jpa/ to create a ServletConextListener to load EJB references using the @EJB annotation. Effectively, from within the JSF Managed Bean, we are then able to look up

Weblogic后台报:'weblogic.kernel.Default (self-tuning)

女生的网名这么多〃 提交于 2020-01-14 12:01:05
本文转载: https://blog.csdn.net/mail_bai/article/details/7440940 ]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds . Stack trace: Thread-3847 "[STUCK] ExecuteThread: '92' for queue: 'weblogic.kernel.Default (se lf-tuning)'" <alive, suspended, priority=1, DAEMON> {。。。。。} ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "653" secon ,"weblogic.kernel.Default"是从客户端提交请求后产生的线程所在的队列名。这个队列的线程数默认是15个。如果超过15个线程堵塞,则部署的应用将不能访问。同时后台报: <2008-2-27 下午09时37分48秒 CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '14' for queue: 'weblogic

Weblogic webservice clients.(clean references)

泪湿孤枕 提交于 2020-01-14 09:37:28
问题 I created a pool of ports (webservice clients) because creating on the fly on each request the client lead to a bottleneck Now I noticed that the webservice clients hold references to the request and response... Is that normal... ? Unfortunately the payload is quite big for this websevice and like this even if not used for a while the pool holds references to some not anymore used responses...increasing heap .. Is there a way to clean those references after receiving the response ? Update:

Eclipse validation error deploying EAR to WebLogic: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee'

試著忘記壹切 提交于 2020-01-13 16:30:33
问题 Out of the box, it is not possible to deploy an EAR to Oracle WebLogic using Eclipse. Environment details: Eclipse version: Indigo (includes Oracle Enterprise Pack for Eclipse 12.1.1.0.0) Weblogic version: 10.3.5 (11gR1) Oracle guide: http://www.oracle.com/technetwork/articles/javaee/marx-oepe-spring-095718.html The error I receive when trying to start the server is: java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail. at oracle.eclipse.tools