weblogic

linux命令重启weblogic

北慕城南 提交于 2019-12-05 19:59:01
1.连接该服务器 2,杀掉进程 ps -ef|grep weblogic 结果展示的第三行,root 后面的 kill -9 进程号 验证是否真的关闭weblogic了,----- 访问项目。挂了就证明已经关闭了 3.重启按时 /home/oracle/ws.sh 4.等待 验证:访问项目可以进入就行 来源: https://www.cnblogs.com/Darkqueen/p/11943541.html

Why java uses default location keystore/truststore of JAVA_HOME/lib/security/cacerts though I have supplied -Djavax.net.ssl.trustStore properties

心不动则不痛 提交于 2019-12-05 18:28:05
In my java application I am running with supplied -Djavax.net.ssl.trustStore System properties as below. -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.trustStorePassword=XXXXX -Djavax.net.ssl.trustStoreType=jks -Djavax.net.debug=ssl This is my Complete command line : $JAVA_HOME/bin/java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Xms512m -Xmx1024m -XX:MaxPermSize=192m -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.keyStore=/myapp/app.jks -Djavax.net.ssl.trustStorePassword=XXXXX -Djavax.net.ssl.keyStorePassword=XXXXX -Dweblogic.security.SSL

在WebLogic新建针对Oracle数据库的JNDI数据源

佐手、 提交于 2019-12-05 18:20:06
一、在WebLogic新建针对Oracle数据库的JNDI数据源   进入weblogic管理控制台,此处是远程访问: http://192.168.1.144:7001/console   点击左侧【 域结构】→【base domain】 → 【服务】 → 【数据源】 然后点击右侧【 新建】 → 【般数据源】, 如下图所示:      填写JDBC数据源的【名称】、【jndi名称】,选择数据库类型,如选择【oracle】,下一步      选择Oracle数据库的驱动程序,如下图所示:      这里选择【Oracle' s Driver (Thin)for Instance connections;Version:Any】,点击【下一步】按钮,进入下一个配置步骤:      这里使用默认配置即可 ,点击【下一步】按钮,进入下一个配置步骤:如下图所示:   填写数据库的连接信息:要连接的数据库,数据库的IP地址,连接数据库时使用的端口号,登录数据库时使用的用户名和密码      点击【下一步】按钮,进入下一个配置步骤:如下图所示:      连接测试结果如下:      点击【下一步】按钮,进入下一个配置步骤:如下图所示:      点击【完成】,这样WebLogic就会创建一个新的JDBC数据源,如下图所示:      到此

Weblogic(CVE-2017-10271)漏洞复现

陌路散爱 提交于 2019-12-05 17:51:32
WebLogic XMLDecoder反序列化漏洞(CVE-2017-10271) 漏洞编号 :CVE-2017-10271 漏洞描述 :WebLogic WLS组件中存在CVE-2017-10271远程代码执行漏洞,可以构造请求对运行WebLogic中间件的主机进行攻击,近期发现此漏洞的利用方式为传播挖矿程序。 受影响WebLogic版本 :10.3.6.0.0,12.1.3.0.0,12.2.1.1.0,12.2.1.2.0。 A、环境搭建    不解释 B、漏洞利用: 1、初步判断:访问 http://192.168.8.148:7001/wls-wsat/CoordinatorPortType11,存在下图则说明可能存在漏洞 2、构造POST包进行测试,写入test.txt POST /wls-wsat/CoordinatorPortType HTTP/1.1 Host: 192.168.8.148:7001 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Upgrade-Insecure-Requests:

Error: Could not find or load main class weblogic.security.Encrypt

大憨熊 提交于 2019-12-05 16:27:11
I am trying to encrypt a database password for my Java EE Application in the terminal. according to this tutorial The steps are as follows: Change directory to your domain’s bin folder (For Eg. cd WLS_home\user_projects\domains\mydomain\bin) Use setDomainEnv.cmd/sh script to setup the environment Run java weblogic.security.Encrypt which will prompt for the password and will print the encrypted value in stdout. However, when I execute 'java weblogic.security.Encrypt', I am presented with the following: Error: Could not find or load main class weblogic.security.Encrypt I am developing my project

Strange java.beans.Introspector behavior on WebLogic with DCEVM and HotSwapAgent

孤者浪人 提交于 2019-12-05 15:56:22
I am running WebLogic on JVM 1.7 with DCEVM (full implementation) and HotSwapAgent with custom plugin that gets triggered on every onClassLoad. I run into problems with Freemarker, which uses java.beans.Introspector. What I discovered is the fact that when I call Introspector.flushCaches on the method called by HotSwapAgent (through ReflectionCommand), then the BeanInfo in Introspector is invalidated properly (checked with debugger in that thread). However when I make request to the WLS appserver, then Introspector for the worker thread shows the old values! This seems like some thread-local

WebLogic and OSGi

自古美人都是妖i 提交于 2019-12-05 14:03:30
Is there a way to run an OSGi container in the Weblogic Application Server? I know that it works with JBoss, Glassfish and there are possibilities to add an Equinox servlet bridge to your OSGi project (implementation of the bridge is too old). But I want something similar to JBoss/Glassfish functionality where it is very easy to deploy your OSGi environment, because there are already OSGi implementations. Most of the articels I found were very old and there are no more recent ones. Can someone help with hints or better some links? Maybe Bnd could create a .war file for me, but how can I

Weblogic 12.1.3 PrivilegedActions class not found

老子叫甜甜 提交于 2019-12-05 13:53:11
i create a simple we project that call a jms queue and put in a message. Here the code: public class QueueSend { // Defines the JNDI context factory. public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory"; // Defines the JMS context factory. public final static String JMS_FACTORY="jms/MyConnectionFactory"; // Defines the queue. public final static String QUEUE="jms/MyTestQueue"; private QueueConnectionFactory qconFactory; private QueueConnection qcon; private QueueSession qsession; private QueueSender qsender; private Queue queue; private TextMessage msg; /** * Creates

WebLogic ERROR: No credential mapper entry found for password indirection user=db_user?

喜夏-厌秋 提交于 2019-12-05 12:36:33
Every time I try to deploy my EJB service app to Weblogic 10.3 server, I get following error: java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=db_user for data source my_ds How to solve this?? The Oracle forums have posted a solution for this, if you are deploying to another Weblogic server other than the Integrated one with JDeveloper. While generating ear file for an application from JDev, it will generate a *-jdbc.xml file for

JMS performance

吃可爱长大的小学妹 提交于 2019-12-05 09:57:51
问题 I'm having a bit of trouble with understanding JMS from a performance perspective. We have this very straightforward code in our application: QueueConnection connection = null; QueueSession session = null; QueueSender sender = null; TextMessage msg = null; try { // The JNDIHelper uses InitialContext to look up things QueueConnectionFactory qcf = JNDIHelper.lookupFactory(); Queue destQueue = JNDIHelper.lookupQueue(); // These objects are created for every message, which is quite slow