현재.. MSSQL 2005와 WebLogic9.2 에 Java 1.5를 사용하고 있습니다.
WebLogic9.2를 퍼플리싱하게되면 다음과 같은 에러가 떨어지며..
JDBC가 끊어지는 현상이 발생하고 있습니다.
조언 부탁드립니다..
에러는 다음과 같습니다. =======================================================
javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jdbc.rpms' didn't find subcontext 'jdbc'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jdbc.rpms' didn't find subcontext 'jdbc'. Resolved '']; remaining name 'jdbc/rpms']; Link Remaining Name: 'jdbc/rpms'
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:103)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:884)
at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:174)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:130)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:130)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at com.nexzone.common.dao.TransactionDAO.initialize(TransactionDAO.java:116)
at com.nexzone.common.dao.TransactionDAO.<init>(TransactionDAO.java:38)
at com.nexzone.user.UserBO.getUser(UserBO.java:63)
at com.nexzone.user.UserAction.doLogin(UserAction.java:100)
at com.nexzone.common.filter.SessionFilter.doFilter(SessionFilter.java:53)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.nexzone.common.filter.EncodingFilter.doFilter(EncodingFilter.java:54)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3229)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2002)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1908)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1362)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.rpms' didn't find subcontext 'jdbc'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'jdbc.rpms' didn't find subcontext 'jdbc'. Resolved '']; remaining name 'jdbc/rpms'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jndi.internal.ServerNamingNode_922_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:374)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:101)
... 26 more
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.rpms' didn't find subcontext 'jdbc'. Resolved ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:550)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:440)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:436)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:58)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:975)
... 2 more
============================================================================================================================ 위 현상은 BPM 설정시.. System.setProperty("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory"); System.setProperty("java.naming.provider.url", "t3://" + WL_SERVER+ ":" + WL_PORT);
이라고 설정하는 부분이 있었는데 이부분 때문에 발생하는 현상이였습니다.
이 부분을 다음과 같이 설정을 바꾸었습니다.
주석 처리를 하고... \bea\user_projects\domains\pms_domain\bin\ 폴더에 존재하는 setDomainEnv.cmd(.sh) 258라인에 다음 구문을 추가합니다.
public class StartupSample implements T3StartupDef { public void setServices(T3ServicesDef services) {} public String startup(String name, Hashtable args) throws Exception { // do startup actions here return "message to appear in log"; } }
위 예제와 같은 방식으로 사용하면 되었는데...
지금 확인해보니 이 클래스가 Deprecated 되었더군요..
혹시 weblogic9.2 버전에서 start-up class 를 등록하는 방법 아시는 분이 계시면 도움 부탁드립니다.
댓글을 달아 주세요