weblogic

CommonJ TimerManager versus EJB3 TimerService

醉酒当歌 提交于 2019-11-29 02:11:47
I have to implement a simple (not clustered) timer for WebLogic and it seems there are two different 'standard' options Timer and Work Manager API (CommonJ) EJB3.0 TimerService Does anyone have any advice on using the CommonJ TimerManager versus using the EJB3 TimerService in WebLogic 10.0? Thank you. TimerService in EJB 3.0 is somewhat limited as compared to CommonJ Timer Manager. For example, it requires boilerplate code and container-specific configuration to implement flexible task scheduling. This was simplified with the introduction of @Scheduled annotation in EJB 3.1. If you are stick

weblogic jsessionid

泪湿孤枕 提交于 2019-11-29 01:00:24
问题 I run Weblogic 10.3 locally and have a question about the sessionId that it generates. When i print session.getId() i see something that resembles this: BBp9TAACMTglQ2TDFAKR4tpyXg73LZDQJ2PtT9x8htG1tWY122aa!869187422!1308677666322 what are these exclamation points and what follows it, specifically the second pair: !1308677666322 ? It looks like sometimes the server appends it and sometimes it doesn't. I believe weblogic appends it if I use the same browser to login to my app for the second

SaaS设计:自动化服务启停设计示例

狂风中的少年 提交于 2019-11-29 00:34:55
业内部时常有服务启停的需求,有时是因为在进行故障排除时需要对某些服务进行启停;有时是因为这些服务在线时间长了容易发生异常,需要定期进行启停;有时是因为需要进行更新包的投产发布,需要进行服务的启停。 不管怎样,企业中的运维工作中离不开服务启停,而每次进行服务启停如果都要手工登陆目标服务进行操作的话,不但繁琐低效,而且容易出现错误操作。 在远程连接的时候特别容易操作错误,比如通过远程桌面或者是ssh连接,本来想要重启A服务器上的服务,不小心把B服务器上的服务重启了。所以,我们可以借助自动化运维平台,来开发一个用于批量、自动执行服务启停的SaaS。 本文就对服务启停SaaS的设计进行一些讨论。下面我们就分类进行讨论要完成一个服务启停动作要包含的要素。 启停操作设计 要进行服务启停,首先我们要知道一般在企业内部对应用进行运维的过程中,都需要对应用服务执行什么操作。常见的操作有 【启动服务】 、 【 停止服务】 和 【重启服务】 ,另外还有如果按常规方法停止服务后,服务不响应请求时,需要一个 【强制杀进程】 的操作。 在执行完上面的操作后,通常我们还需要进行一下检查这个操作是否成功。 【启动服务】 后,我们需要检查服务是否启动成功; 【停止服务】 后,我们需要检查服务是否停止成功等。 那么我们就要设计出针对这些动作的检查动作了,一般的检查动作有: 检查该服务的进程是否在运行

Cannot access HTTPS from Weblogic

心不动则不痛 提交于 2019-11-29 00:12:02
I have a problem with Weblogic accessing an HTTPS server, I can access other HTTPS urls, like google or microsoft. The code that tries to connect to the url is: URL url = new URL("https://myserver.com"); HttpURLConnection connection = (HttpURLConnection) url.openConnection(); connection.setRequestMethod("GET"); connection.setRequestProperty("User-Agent", "Mozilla/5.0"); // fails here responseCode = connection.getResponseCode(); I get the following stack trace: java.io.IOException: Connection closed, EOF detected at weblogic.socket.JSSEFilterImpl.handleUnwrapResults(JSSEFilterImpl.java:539) at

Weblogic administration console way too slow

﹥>﹥吖頭↗ 提交于 2019-11-28 23:25:50
问题 I've installed weblogic 10.3.3, configured simple domain with default configuration. And after starting weblogic I cannot use it via admin console because it is starting too slow (~10 mins). It seems that admin console application is being deployed incorrectly. Even when I enable 'staging' mode in AdminConsole deployment options, it does not help. Does anybody have a solution for this problem? It really bugs me out. Configuration properties: Server: Dell PowerEdge r410 server (Six-core Intel®

Supported Oracle WebLogic Server Versions

♀尐吖头ヾ 提交于 2019-11-28 22:58:04
The following table outlines the degree to which various versions of Oracle WebLogic Server are supported by WebLogic Server Tools. 11 g Release 1 Patch Set 3 (10.3.4) 11 g Release 1 Patch Set 2 (10.3.3) 11 g Release 1 Patch Set 1 (10.3.2) 11 g Release 1 (10.3.1) 10 g Release 3 (10.3) 10.0 9.2 9.1 9.0 8.1 J2EE 1.3 Supported. Supported. Supported. Supported. Supported. Supported. Supported. Supported. Supported. Supported. J2EE 1.4 Supported. Supported. Supported. Supported. Supported. Supported. Supported. Supported. Supported. Java EE 5 Supported. Supported. Supported. Supported. Supported.

Indirectly referenced from required .class file

我与影子孤独终老i 提交于 2019-11-28 21:04:01
I'm getting an error message when I try to build my project in eclipse: The type weblogic.utils.expressions.ExpressionMap cannot be resolved. It is indirectly referenced from required .class files I've looked online for a solution and cannot find one (except for those sites that make you pay for help). Anyone have any idea of a way to find out how to go about solving this problem? Any help is appreciated, thanks! Kevin How are you adding your Weblogic classes to the classpath in Eclipse? Are you using WTP, and a server runtime? If so, is your server runtime associated with your project? If you

Weblogic Transaction Timeout : how to set in admin console in WebLogic AS 8.1

萝らか妹 提交于 2019-11-28 19:12:04
I face the following exception: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds this is set within the Stateless Session EJB Bean as javax.transaction.UserTransaction jtaTransaction.setTransactionTimeout(300) but I cannot figure out, where in the application console to set this property. After logging in, on the home page of the Server Console you should see 3 sections: Information and Resources Domain Configurations Services Configurations Under Services Configurations there is subsection Other Services . Click the JTA Configuration link under Other

JSF Session Fail over and Partial State Saving

让人想犯罪 __ 提交于 2019-11-28 17:55:51
问题 Running on JSF 2.0.9, Weblogic 10.3.4. We're now running JSF in our production environment but have encountered some issues with Session Replication and fail over. We are using viewscope for our beans and I have ensured they are Serializable/transient and that the transient variables are effectively stateless. However session fail over is not working. I have done extensive testing and managed to get it working by setting the following params in web.xml <context-param> <param-name>javax.faces

How does weblogic clustering work?

有些话、适合烂在心里 提交于 2019-11-28 17:13:43
问题 I'm new to weblogic. I've read http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/overview.html and searched this topic on the internet but still had a hard time understanding some of weblogic's clustering concepts. Can anybody confirm/correct my understandings below? a cluster contains one or more logical servers which can reside on one or many physical servers when deploying a j2ee app to a cluster, it is tied to one server in that cluster external users of the deployed app aren't