weblogic

I use log4j for logging in my project. Here is it's sample setup: public class MyClass { private final Logger logger = Logger.getLogger(MyClass.class); public MyClass() { BasicConfigurator.configure(); Logger.getLogger(MyClass.class).setLevel(Level.INFO); } ... } The problem is that on each next logger call it duplicates log messages (I mean on first call there is only 1 message, on second call there are 2 same messages, then there are 3 of them and so on). It seems that each time new logger's instance is created and used with all old instances. How to avoid this problem? Thanks. UPP. Tried to

eclipse中启动weblogic中出错异常,但weblogic已正常启动. 可通过修改eclipse的配置文件eclipse.ini解决,如下: -Dsun.lang.ClassLoader.allowArraySyntax=true 来源： oschina 链接： https://my.oschina.net/u/242695/blog/159601

In Weblogic 10.3, how do I inject a remote EJB from one EAR into a Stateless bean of another, both EARs being deployed in the same container? Ideally I'd like to do as much as possible with annotations. So suppose I have the following interface: public interface HelloService { public String hello(); } implemented by the following EJB: @Stateless @Remote public class HelloServiceBean implements HelloService { public String hello() { return "hello"; } } Suppose they're packaged and deployed in server.ear . Now in client.ear , I have the following: @Stateless public class HelloClientBean { @EJB

I've recently setup a new Weblogic 12c environment. On deploying an application that I know works in Weblogic 11g I get the error "The url-pattern /resources/* in web application is mapped to multiple Servlets." The mapping it's referring to is in the web.xml inside the application.ear that's being deployed, but it's only mapped once: <servlet-mapping> <servlet-name>velocity</servlet-name> <url-pattern>/resources/*</url-pattern> </servlet-mapping> The project doesn't contain any other references to the url pattern /resources/*, can someone explain where the duplicated mapping is coming from

Oracle purchased BEA and their WebLogic suite of tools. They still have a competing product in their own 10gAS Application Server. Both are Java EE , enterprise grade, servers. While it make take some time due to maintenance agreements, it would be unusual for them to continue to produce two products within the same architectural space. So... Will they retire their previous application server in favor of WebLogic? Is WebLogic the one that will be retired? How long of a process is this likely to be? Years? What have they done with PeopleSoft vs. Oracle Applications? Likely the same pattern will

I have installed Weblogic Server 10.3.6, and I use the below script to start my server: user_projects/domains/my_domain/bin/startWebLogic.sh I found below command to start the server in background: nohup startWebLogic.sh & But when I use this command I am getting this output: -bash-3.2$ nohup ./startWebLogic.sh & [2] 25379 -bash-3.2$ nohup: appending output to `nohup.out' So here I have to press Enter to come out of this and go to new line. Now my requirement is that when I run the command then the server should start and I have to come out of this to a new line, like: -bash-3.2$ nohup .

Is this enough to enable SSL on weblogic server? Open console > Environment > Servers > open a managed server where your application is deployed > check 'SSL Listen Port Enabled' checkbox. Once I did that, I could open my application on HTTPS using HTTPS port. Why I am asking this question because on this page: http://docs.oracle.com/cd/E13222_01/wls/docs81/secmanage/ssl.html In section - Configuring SSL, they're not suggesting this simple step. I understand that by enabling SSL using the way I did, I am using weblogic's default certificate, but for testing I don't mind that. Please confirm.

I'm having trouble with a field annotated as @Resource in a Spring bean. What I have: A field, with setter method, annotated @Resource @Resource private URL someUrl; public void setSomeUrl(URL someUrl) { this.someUrl = someUrl; } An <env-entry> tag in my deployment descriptor (web.xml) <env-entry> <env-entry-name>someUrl</env-entry-name> <env-entry-type>java.net.URL</env-entry-type> <env-entry-value>http://somedomain.net/some/path</env-entry-value> </env-entry> The application fails to start with a BeanCreationException , which I dont' expect because I don't necessarily want spring to inject a