Startup Steps performed by weblogic 6.1 SP5

Hi,
I am beginner and very new to weblogic. I am working on an application developed on weblogic 6.1 SP5. There is an issue where weblogic shut down. The server is a two node Cluster server. Weblogic shut down on one node and failed to startup on the second node as well, and we had to restart the server. Reading the logs, only thing we found was there were some thread dumps indicating that there was a deadlock condition due to which the threads were waiting and the server hung.
Could anyone suggest as to what can cause the server to hang?
Also, I wanted to know what are the basic operations that a weblogic server performs during startup like allocating memory, connecting to database etc or provide pointers to any references for weblogic?
Thanks
Minal

Similar Messages

Needed help on connecting weblogic 8.1 SP5 with oracle 10g and mysql 5.0

Hi !!
Hope you are doing well...
Can anyone tell me how to connect weblogic 8.1 SP5 with an oracle 10g DB on windows..
also, how to connect weblogic 8.1 SP5 with mysql 5.0 on windows..
Please step by step... very urgent..
Thanks!! Jhonson

Shouldn't this be posted in BEA forums?
Try getting help there and if you encounter any Oracle related exception, you can post here.

Problem in deploying an ear file in weblogic 8.1 SP5

Hi,
When I tried deploying my ear file in Weblogic 8.1 SP5, I am getting the following error:
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for counter-ejb.jar
Module: counter-ejb.jar Error: Exception preparing module: EJBModule(counter-ejb.jar,status=NEW)
Unable to deploy EJB: com_liferay_counter_service_ejb_CounterServiceEJB from counter-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'mail/MailSession' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
at weblogic.ejb20.deployer.EnvironmentBuilder.addConnectorRef(EnvironmentBuilder.java:294)
at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:232)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:384)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1181)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:952)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1437)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3149)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1590)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1234)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1077)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2530)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2480)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
The config.xml is
<?xml version="1.0" encoding="UTF-8"?>
<Domain ConfigurationVersion="8.1.5.0" Name="mydomain">
<Server ListenAddress="" ListenPort="7001" Name="myserver"
NativeIOEnabled="true" ReliableDeliveryPolicy="RMDefaultPolicy" ServerVersion="8.1.5.0">
<SSL Enabled="false" HostnameVerificationIgnored="false"
IdentityAndTrustLocations="KeyStores" Name="myserver"/>
</Server>
<JMSFileStore Directory="rmfilestore" Name="FileStore"/>
<WSReliableDeliveryPolicy DefaultRetryCount="10"
DefaultTimeToLive="60000" Name="RMDefaultPolicy" Store="FileStore"/>
<JDBCConnectionPool
DriverName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
Name="LiferayPool" PasswordEncrypted="{3DES}MO3m0i6yVqM="
Properties="user=lportal;url=jdbc:microsoft:sqlserver://localhost:1433;selectMethod=cursor;userName=lportal;dataSourceName=SQL2000JDBC;databaseName=lportal;serverName=localhost"
Targets="myserver" TestConnectionsOnReserve="true"
TestTableName="SQL SELECT * from sysobjects" URL="jdbc:microsoft:sqlserver://localhost:1433"/>
<JDBCTxDataSource JNDIName="jdbc/LiferayPool" Name="LiferayPool"
PoolName="LiferayPool" Targets="myserver"/>
<Security Name="mydomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true"/>
<EmbeddedLDAP
CredentialEncrypted="{3DES}VKU1Z+Rt+9H2BdJ/IWLykO3UHDGbDN2w3so0iy8xk1o=" Name="mydomain"/>
<SecurityConfiguration
CredentialEncrypted="{3DES}HVQXen+OHn1WVUhPVXQ5Etq0wZGW3TnCcMyK65ekuw56D9CS2M/ODdh/PomFZBYLRYlkhysTEvGDijpcBUYz6FzUcyq5JYry"
Name="mydomain" RealmBootStrapVersion="1"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<JMSServer Name="WSStoreForwardInternalJMSServermyserver"
Store="FileStore" Targets="myserver">
<JMSQueue CreationTime="1155021233552"
JNDIName="jms.internal.queue.WSStoreForwardQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSStoreForwardQueuemyserver"/>
<JMSQueue CreationTime="1155021233723"
JNDIName="jms.internal.queue.WSDupsEliminationHistoryQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSDupsEliminationHistoryQueuemyserver"/>
</JMSServer>
<MailSession JNDIName="mail/MailSession" Name="mail/MailSession"
Properties="mail.pop3.host=localhost;mail.imap.host=localhost;mail.transport.protocol=smtp;mail.smtp.host=localhost;mail.store.protocol=imap" Targets="myserver"/>
</Domain>
The ejb-jar.xml is :
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <enterprise-beans>
          <session>
               <display-name>CounterServiceEJB</display-name>
               <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
               <home>com.liferay.counter.service.ejb.CounterServiceHome</home>
               <remote>com.liferay.counter.service.ejb.CounterServiceEJB</remote>
               <ejb-class>com.liferay.counter.service.ejb.CounterServiceEJBImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Bean</transaction-type>
               <resource-ref>
                    <res-ref-name>jdbc/LiferayPool</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <resource-ref>
                    <res-ref-name>mail/MailSession</res-ref-name>
                    <res-type>javax.mail.Session</res-type>
                    <res-auth>Container</res-auth>
               </resource-ref>
          </session>
     </enterprise-beans>
     <assembly-descriptor>
          <method-permission>
               <unchecked />
               <method>
                    <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
                    <method-name>*</method-name>
               </method>
          </method-permission>
     </assembly-descriptor>
</ejb-jar>
The weblogic-ejb-jar.xml is:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>mail/MailSession</res-ref-name>
          <jndi-name>MailSession</jndi-name>
          </resource-description>
          </reference-descriptor>
          <jndi-name>com_liferay_counter_service_ejb_CounterServiceEJB</jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
Please Help!
Thanks in Advance.
- Karthikeyan

Hi,
I am still getting the error even after changing the JNDI name.
The modified weblogic-ejb-jar.xml is:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
<reference-descriptor>
<resource-description>
<res-ref-name>mail/MailSession</res-ref-name>
<jndi-name>mail/MailSession</jndi-name>
</resource-description>
</reference-descriptor>
<jndi-name>com_liferay_counter_service_ejb_CounterServiceEJB</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Thanks..
- Karthikeyan

How to increase the performance of Weblogic server 7.0?

How to increase the performance of Weblogic server 7.0 ?
also, how do i avoid typing the server login and password evertime I start the
webserver?

How to increase the performance of Weblogic server 7.0 ?It depends on what is not running fast enough for you.
also, how do i avoid typing the server login and password evertime I
start the webserver?In the startWebLogic shell script (.cmd or .sh) add:
set WLS_USER=weblogic
set WLS_PW=password
(Replace "password" with whatever your password is.)
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"winston" <[email protected]> wrote in message
news:3fe42d33$[email protected]..
>

Apache Proxy Plug-in with WebLogic 8.1 SP5 - Transfer Encoding:Chunked

Hello All,
Configuration: Apache 2.0.48
Plugin - mod_wl128_20.so
WebLogic Version - 8.1 SP5
There is no SSL between Apache and WebLogic server.
Apache seems to have issue when the response from WebLogic has: Hdrs from WLS:[Transfer-Encoding]=[chunked]
I turned on the debugging on Apache side with DebugAll flag and WLS sends data to Apache plug-in.
Is is a known issue? Is there any CR to fix it? Please let me know if you need further details.
Any help is appreciated.
Thanks,
Janani

Hi Vishwas,
Thank you for the reply. I forgot to mention that Apache and WebLogic are on Solaris 9 platform.
Accesing a webapp hosted on WebLogic through Apache->plug-in->WebLogic return 500 internal server error, but other webapps hosted on the same WebLogic domain works properly. Looking at the Response Hdrs from WebLogic shows that WLS returns transfer-encoding=chunked. The other webapps which work properly has content-length set and transfer-encoding is not chunked.
So, the question is does Apache Plug-in for weblogic 8.1 SP5 read the chunked data properly?
Thanks,
Janani

Server Hangs while compiling some EJB in Weblogic 6.1 SP5 on AIX 4.3.3

Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5 on an AIX 4.3.3
box.
CMP is being used and my EJBs are not being compiled( though there are no errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info> <Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX 4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh

The only thing to do again with "hangs" is to take thread dumps. As for why
things are going wrong...... I am at a loss other than some AIX weirdness.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
>
Hi Mark,
I tried it out ....I ran EJBC on all my EJB's and then tried to deploy myapplication.
Application got deployed and the server was up, but JSP's dosent getcompiled(
i.e when I want to run my application, my server hangs again).
I tried one more option.. I pointed my JAVAHOME in startweblogic.sh to anSP3
JDK .. and it worked!! Now with this JDK Iam able to deploy my entireapplication
( with out precompiled) also run through the application without anyproblems.
I then over wrote the existing JDK ( of SP5 ) with that of SP3 and thentried.
Which also works fentastically!!!
I can feel something fishy here ....
Any help in this regard is most welcome.
Thanks and Regards...
Nagesh
"Mark Griffith" <[email protected]> wrote:
Deshpande:
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
Thanks again.
For
Q1> How much time was between the two dumps?
A1> There was a minute gap B/w the two dumps. ( since it took so longto
write
the Core)
Q2> How long have you waited with no progress seeming to be made?
A1> Over a whole night. ( appx 14 hours).
Now I believe you would have figured out what the problem is.Not sure if this is a statement saying you think I have figured it out,
or a
statement saying you think I should have figured it out but I haven't.
Anyway... Did you try running ejbc on the "app" first?
Meanwhile also it would be great, if you would tell me the proceduresto
get support
form the BEA and AIX to solve the Issue.
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/services/custome
r_support/contacts/
>>
I would suggest sending as much detail as possible, including zips of
the
thread dumps and pointers to this newsgroup conversation [email protected]
>>
I do however suggest you first try running ejbc.
Cheers
mbg
Thanks in advance.
R
Deshpande.
"Mark Griffith" <[email protected]> wrote:
Nagesh:
Wow, AXI outputs some interesting thread dumps. ;)
So the interesting thread (and the problem) is:
"main" (TID:0x300C41D8, sys_thread_t:0x30010A60, state:CW, native
ID:0x1)
prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:429)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:130)
at weblogic.utils.Executable.exec(Executable.java(Compiled Code))
at weblogic.utils.Executable.exec(Executable.java(Inlined CompiledCode))
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.j
a
v
a(Compiled Code))
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java(Inlin
e
d
Compiled Code))
at
weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java(InlinedCompiled
Code))
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java(CompiledCode))
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:176)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploymen
t
T
arget.java(Compiled Code))
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployme
n
t
Target.java:286)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments
D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deplo
y
m
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployment
s
ServerMBean_CachingStub.java:3015)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Ap
p
l
icationManager.java:376)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMana
g
e
r.java:164)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy48.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.star
t
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1309)
at weblogic.management.Admin.finish(Admin.java:650)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:547)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:214)
at weblogic.Server.main(Server.java:35)
So the Server never gets out of the Main thread to run, because theEJBC
compilation is "stuck", ejbc is running because either the EJB being
deployed was previously deployed on a different version of WLS orejbc
had
never been run on those beans. Either there is a problem on the AIX
VM
where execing processes are not returning, OR the ejb that ejbc isrunning
on is huge and is taking a REALLY long time. How much time was
between
the
two dumps? How long have you waited with no progress seeming to bemade?
Depending on the answers to these questions it maybe that there isa
VM bug
and you will need to contact BEA support to see the procedure forworking
with AIX to resolve the issue.
You maybe able to work around the problem by running EJBC on the ejb
in
question prior to starting the server.
http://edocs.bea.com/wls/docs61/ejb/EJB_utilities.html#1075296
Cheers
mbg
"deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi, Mark,
Thanks for the early reply.
I have attached two consecutive dumps Zipped.
Pls look into the same and helpme out.
Thanks in advance.
Regards,
Nagesh
"Mark Griffith" <[email protected]> wrote:
When it hangs, you need to get thread dumps.
"kill -3 PID" is how this works on Solaris. Additionally if the
terminal/shell has focus that started the process you can do "CTRL
Break"
as
well. The thread dumps will go to std-out/err, so you'll have
to
redierect
std-out and err of the shell. (Make sure you don't nohup the
process
(if
AIX even supports that) since this prevents sigquits). When thehang
occurs
take a thread dump, wait 10 seconds and take another one, thenplease
zip
and attach the file in a post.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5
on
an
AIX
4.3.3
box.
CMP is being used and my EJBs are not being compiled( though
there
are no
errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info><Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX
4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh

Problems with using JSTL with Weblogic 8.1 SP5 - Help!

I keep getting the following error when trying to run my application using JSP tags under Weblogic 8.1 SP5 (using Jrockit in production mode):
/searchinput.jsp(2): Error in using tag library uri='/WEB-INF/lib/regain-search.tld' prefix='search': cannot find tag class: 'net.sf.regain.ui.server.taglib.TagMsg'
probably occurred due to an error in /searchinput.jsp line 2:
<%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
I have the following jar files in my /WEB-INF/lib directory:
jakarta-regexp-1.4.jar
jstl.jar
standar.jar
log4j-1.2.11.jar
struts.jar
lucene-1.4.3.jar
jsp-api.jar
and the regain-search.tld.
I am using JSTL 1.0.6 (earliest version I could find of JSTL 1.0).
The class files that the tld file is pointing to are in the WEB-INF/classes directory of the application (which is an exploded war file).
Here is what I have as reference in my web.xml file:
<taglib>
<taglib-uri>/WEB-INF/lib/regain-search.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/regain-search.tld</taglib-location>
</taglib>
and it is referenced in searchinput.jsp as:
<%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
I've looked everyone on the Web trying to find an answer to this - but nothing I've tried has worked.
This all works fine in Tomcat 5.0
Please let me know what I'm doing wrong.
Thanks in advance,
Kelly

I keep getting the following error when trying to run my application using JSP tags under Weblogic 8.1 SP5 (using Jrockit in production mode):
/searchinput.jsp(2): Error in using tag library uri='/WEB-INF/lib/regain-search.tld' prefix='search': cannot find tag class: 'net.sf.regain.ui.server.taglib.TagMsg'
probably occurred due to an error in /searchinput.jsp line 2:
<%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
I have the following jar files in my /WEB-INF/lib directory:
jakarta-regexp-1.4.jar
jstl.jar
standar.jar
log4j-1.2.11.jar
struts.jar
lucene-1.4.3.jar
jsp-api.jar
and the regain-search.tld.
I am using JSTL 1.0.6 (earliest version I could find of JSTL 1.0).
The class files that the tld file is pointing to are in the WEB-INF/classes directory of the application (which is an exploded war file).
Here is what I have as reference in my web.xml file:
<taglib>
<taglib-uri>/WEB-INF/lib/regain-search.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/regain-search.tld</taglib-location>
</taglib>
and it is referenced in searchinput.jsp as:
<%@ taglib uri="/WEB-INF/lib/regain-search.tld" prefix="search" %>
I've looked everyone on the Web trying to find an answer to this - but nothing I've tried has worked.
This all works fine in Tomcat 5.0
Please let me know what I'm doing wrong.
Thanks in advance,
Kelly

EmptyNestingStackException on WebLogic 8.1 SP5

Hello,
I am encountering this strange error when testing a portal application running on Weblogic 8.1, SP5.
The strange thing is although this exception is thrown, the method AAAAA of the parent controller is still executed (it sets a few session variables), and an error page is displayed. XXXXX is the nested controller.
This only occur on IE6. I tested on Firefox and Opera, both works fine.
Has this got something to do with the session handling?
Please assist. Thanks in advance! :-)
2007-04-25 23:08:28,657 DEBUG [WEBLOGGER] - Start setting the exception errorMessage object into the request object... errorMessage:Empty nesting stack for returned action AAAAA from Page Flow /portlets/XXXXX/XXXXX.jpf.
2007-04-25 23:08:28,657 ERROR [WEBLOGGER] - Unhandled exception occur!portlets.XXXXX.XXXXX
2007-04-25 23:08:28,657 DEBUG [WEBLOGGER] - Finish setting the exception errorMessage object into the request object... errorMessage:com.bea.wlw.netui.pageflow.EmptyNestingStackException: Empty nesting stack for returned action AAAAA from page flow /portlets/XXXXX/XXXXX.jpf.
at com.bea.wlw.netui.pageflow.FlowController.forwardTo(Lorg/apache/struts/action/ActionForward;Lorg/apache/struts/action/ActionMapping;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Ljava/lang/String;Lorg/apache/struts/config/ModuleConfig;Lorg/apache/struts/action/ActionForm;Ljavax/servlet/ServletContext; )Lorg/apache/struts/action/ActionForward;(FlowController.java:1120)
at
Edited by stmoong at 04/25/2007 8:06 PM

Hi, one of my colleagues helped to resolve this issue. The problem was the form was submitted twice in the JSP, hence, this problem occurs.
Hope this would be helpful for others who might encounter this similar problem.

NT startup parmaters for multiple weblogic servers started as a service

I have the need to start multiple weblogic servers, using NT services.
I have created a second folder with a properties file listening on another
port.
I am using the following startup parameter
-J-Dweblogic.system.name=Test
My question, this works when I type the startup parameter, is their anyway
to have this automatically entered
on server startup.
Is their a registry setting to make this permanent
Thanks

The answer is...
- Use a product to turn applications into an NT Service (e.g.
ServiceMill)
- Directly run the Weblogic Server Java class via that application
--> As many WLs on one machine as you like.
Send mail if you need specific details.
Best regards
Daniel Hoppe
-----Original Message-----
From: [email protected] (Ed) [mailto:[email protected]]
Posted At: Wednesday, August 30, 2000 2:34 AM
Posted To: install
Conversation: NT startup parmaters for multiple weblogic servers started
as a service
Subject: Re: NT startup parmaters for multiple weblogic servers started
as a service
I wish that was the case.
The problem is, while you enter the startup parameter once, it only
is good for that startup of the weblogic server,
The next time the server reboots and the services start, unless you
re-enter the startup parameter -J-Dweblogic.system.name=Foldername
The weblogic server starts using the wrong properties file.
Is their anyway using NT services to have the correct instance of WL
to start everytime.
I have checked this newsgroup and this question has been posted
before, but so far no one seems to have the answer.
I know in a production eniviorment someone must be running more that
one instance of a WL server as a service, Hopefully their is an
answer on how this is done.
Thank you
Kumar Allamraju <[email protected]> wrote:
Not that i know of.
but you are specifying this startup parameter only one time too!!!
Kumar
None of your bussines wrote:
I have the need to start multiple weblogic servers, using NT
services.
I have created a second folder with a properties file listening onanother
port.
I am using the following startup parameter
-J-Dweblogic.system.name=Test
My question, this works when I type the startup parameter, is theiranyway
to have this automatically entered
on server startup.
Is their a registry setting to make this permanent
Thanks

Workflow start step performs Exclusive checkout

We need to upload data to records that are in workflow and checked out by the workflow start step. Unfortunately the workflow start step performs an Exclusive checkout of the record which means that the background MDM Impor Server user cannot automatically join the checkout, the user first needs to be invited to the checkout, which needs a manual step of modifying the join permissions of the checkout, which is not what we want to do.
I have also noticed that when an existing record is checked out Exclusively the user's roles are pulled through into the permitted roles section of the join permission screen of the checkout. When a new record is checked out Exclusively the user's roles are not pulled through to the permitted roles section of the join permission screen of the checkout. This looks like a bug to me.
We are using MDM 7.1 SP08.
Please advise any workarounds to this problem. I can think of a few, but none are very elegant, e.g.:
1. Use API to invite import user to checkout before import is started (requires coding)
2. Get the user that owns the workflow to manually invite the import user (not guaranteed to remember)
3. Complete workflow and stat new wokflow without chekout before import is started.
Any advice will be appreciated.

Hi Johann,
I got you point.
Its not a bug in MDM these are the constraints in MDM :(.
To understand more read section CHECKOUT AND WORKFLOW FAILURE CONDITIONS of the import manager refernce guide.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/72b8e7a42301bae10000000a42189b/MDMImportManager71.pdf
In our lanscape we too have a scenario where we are creating/ records in MDM leaving Material Number Blank (Record Add workflow).
But once this record with balnk Material Number is syndicated to source system we stop this workflow.
Now from source system through change pointer we get a file immediately with material Number and MDMID.
which we process through MDIS and trigger another workflow(Record Import)
I guess this matches with the third option you described to start and stop workflow and trigger import.
Regards,
Neethu Joy

Pitfallls of BPM - Individual Step Performance

Hi Experts,
I have some question regarding BPM steps.
Pitfallls of BPM - Individual Step Performance
can anyone guide me on this topic please?
Thanx in advance.
Regards,
joel

multiple recv node in fork
if multiple recv step is waiting for a message from the same sender then only one recv step is processed at random. the remining rec steps are forced to wait.
transformation step
no value mapping within the transformation step
Container Operation
message cannot be changed with container operation

Physical Database Design Steps & Performance Considerations

Hi,
We have a Oracle 9i install need help to create a DB.
Required to know the Physical Database Design Steps & Performance Considerations.
like
1-Technical consideration of DB as per server capacity. how to calculate..?
2- What will be the best design parameter for DB...?
Can you please help how to do that. Any metalink ID help to get those information.
thanks
kishor

there is SOOO much to consider . . . .
Just a FEW things are . . .
Hardware - What kind of Host is the database going to run on?
CPU and Memory
What kind of Storage
What is the Network like?
What is the database going to do OLTP or DW?
Start with your NEEDS and work to fulfill those needs on the budget given.
Since you say Physical Database Design . . . is your Logical Database Design done?
Does it fulfill the need of your application?

At startup: "Unable to resolve weblogic.jdbc.connectionPool"

WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNamingNode_WLSkel.java:230)

Just installed SP2 on top of WebLogic Server 6.0 SP1.
I still get the same message in weblogic.log while it was starting up:
####<Jun 28, 2001 12:53:00 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <> <> <000000> <IIOP subsystem enabled.>
####<Jun 28, 2001 12:53:10 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <system> <> <000214> <WebLogic Server (6.0
Service Pack 2 05/24/2001 11:55:28 #117037) "myserver"
(c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000 BEA Systems, Inc.>
####<Jun 28, 2001 12:53:23 PM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 28, 2001 12:53:26 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:27 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:28 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:29 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[7126974831161186990S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@504ec1>
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: ''
Unresolved:'jdbc' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
Daniel Hoppe wrote:
Hi,
it's a problem in SP1, doesn't seem to cause any harm. Afaik it's fixed
in RP1 and in SP2
Daniel
-----Urspr?ngliche Nachricht-----
Von: Jesus M. Salvo Jr. [mailto:[email protected]]
Bereitgestellt: Mittwoch, 20. Juni 2001 02:17
Bereitgestellt in: jndi
Unterhaltung: At startup: "Unable to resolve
weblogic.jdbc.connectionPool"
Betreff: At startup: "Unable to resolve weblogic.jdbc.connectionPool"
WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool
ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool:
'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter>
<pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,
7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundExceptio
n(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingN
ode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamin
gNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNaming
Node_WLSkel.java:230)

Weblogic 6.1 sp5 core dump by OCI driver

I have encountered a core dump problem on weblogic server 6.1 SP5 the error message
as below, I am using weblogic oci driver for oracle "libweblogicoci37.so" , anyone
can help?
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 4 occurred at PC=0x242795c
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.

Galen Boyer wrote:
On Sun, 28 Mar 2004, [email protected] wrote:
Galen Boyer wrote:
On Sat, 27 Mar 2004, [email protected] wrote:
One way to get a substantial boost in reliability is to switch
to the latest appropriate Oracle thin driver.But then you can suffer performance losses.Actually, the latest oracle thin drivers are very fast. The 10g
driver in particular. Well, we are on 9i here and we have lots of CLOB and BLOB
operations. Understood. The latest should work. (How comfortable does that make you ;) )
It is a sad choice we used to have to make between
faster-but-buggy homicidal old OCI code (wherein a bug in one
module can cause a segfault in an innocent unrelated module's
execution, and bring down a whole JVM) and the reliability of
Java. Fortunately, the future is at hand. The future is at hand? I do believe you are starting to sound a
bit like an evangelist. :-)Yep. Back in '96 when we wrote and marketed all the first JDBC drivers
for MS SQLServer, Oracle, Informix and Sybase, we did it solely
so enable our application server to be able to do real work. We were all
absolutely sure the driver market would dry up in 6 months as all the
DBMS vendors made excellent free type-4 drivers. We were over-optimistic.
Sybase's driver still requires you to install non-standard tables and
procedures in the DBMS. Oracle drivers are sloutching toward sufficiency,
but their first GA driver had a hard-wired value of READ_UNCOMMITTED
for getTransactionIsolation, and if you tried setTransactionIsolation
of either READ_COMMITTED or SERIALIZABLE, the driver would throw an
exception! We actually had a weblogic workaround to intercept this
jdbc call and send the "ALTER SESSION " to do what the customer wanted!
At the same time we had a major struggle to get Oracle to admit that
in spite of their documentation, OCI was not threadsafe (killing our
OCI-based driver in weblogic applications) until 7.1.4 on solaris
and NT, and 8.0.5 on other platforms. Did you know they had separate
codelines for OCI on each platform? For a while each platform's OCI
had a different hard-wired limit of the number of simultaneous connections
on client could have? For a while that limited what our application server
could do. OCI was written for simple teller-like client applications.
The new thin drivers take on more of the possible client-side
processing, and can do RAC failover etc. JoeOh well. I for one am a bit skeptical that Oracle is going to
fix java driver bugs before OCI bugs and I don't have any reason
to commit to any "platform independent" solution like java's thin
driver. We are completely based on Oracle here and we have a
J2EE solution for the app just cause we had to choose something.
If thin is better, than we will go with that.The last highest-level talks I had with Oracle folks they indicated that
they wanted everyone to go thin. OCI was a headache for them. Their
OCI code was undocumented and all the original experts had left the company.
That was in 2000 or so, so it is likely better now. They may well have
invested a lot of reverse-documentation by now.
One of the benefits of Java is the reliability. I think you'll
ultimately be happier with the thin. We do want you successful.
Joe

Startup exception on the weblogic Dev Server

Hi,
I deployed the war file (having servlets, jsps, js, struts and hibernate modules) on the weblogic recently. On the startup I got following error as message
java.lang.NullPointerException
Errors were encountered while performing this operation.
and on checking the log I got following exception:
HTTP:101216]Servlet: "InitPropsLoader" failed to preload on startup in Web application: "MyApp.war". java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at java.util.Properties.setProperty(Properties.java:143) at java.lang.System.setProperty(System.java:731) at com.cs.cbrs.utils.InitPropsLoader.init(InitPropsLoader.java:11) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1899) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1873) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1791) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3005) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I am using following jar files for this app---
total 40216
-rw-r--r-- 1 54829 Jul 13 10:11 activation.jar
-rw-r--r-- 1 443432 Jul 13 10:11 antlr-2.7.6.jar
-rw-r--r-- 1 16777 Jul 13 10:11 asm-attrs.jar
-rw-r--r-- 1 26360 Jul 13 10:11 asm.jar
-rw-r--r-- 1 608376 Jul 13 10:11 c3p0-0.9.1.jar
-rw-r--r-- 1 282338 Jul 13 10:11 cglib-2.1.3.jar
-rw-r--r-- 1 188671 Jul 14 07:27 commons-beanutils-1.7.0.jar
-rw-r--r-- 1 117787 Jul 14 07:27 commons-beanutils.jar
-rw-r--r-- 1 90001 Jul 14 07:27 commons-chain-1.1.jar
-rw-r--r-- 1 36174 Jul 14 07:27 commons-cli-1.1.jar
-rw-r--r-- 1 46725 Jul 14 07:27 commons-codec-1.3.jar
-rw-r--r-- 1 175426 Jul 14 07:27 commons-collections-2.1.1.jar
-rw-r--r-- 1 165119 Jul 14 07:27 commons-collections-2.1.jar
-rw-r--r-- 1 575389 Jul 14 07:27 commons-collections-3.2.1.jar
-rw-r--r-- 1 164051 Jul 14 07:27 commons-collections.jar
-rw-r--r-- 1 143602 Jul 14 07:27 commons-digester-1.8.jar
-rw-r--r-- 1 98079 Jul 14 08:07 commons-digester.jar
-rw-r--r-- 1 57779 Jul 14 07:27 commons-fileupload-1.2.1.jar
-rw-r--r-- 1 19274 Jul 14 07:27 commons-fileupload.jar
-rw-r--r-- 1 305001 Jul 14 07:27 commons-httpclient-3.1.jar
-rw-r--r-- 1 87776 Jul 14 07:27 commons-io-1.3.2.jar
-rw-r--r-- 1 299994 Jul 14 07:27 commons-jxpath-1.3.jar
-rw-r--r-- 1 261809 Jul 14 07:27 commons-lang-2.4.jar
-rw-r--r-- 1 54011 Jul 14 07:27 commons-lang.jar
-rw-r--r-- 1 38015 Jul 14 07:27 commons-logging-1.0.4.jar
-rw-r--r-- 1 52915 Jul 14 07:27 commons-logging-1.1.jar
-rw-r--r-- 1 44598 Jul 14 07:27 commons-logging-api-1.1.jar
-rw-r--r-- 1 27718 Jul 14 07:27 commons-logging.jar
-rw-r--r-- 1 87077 Jul 14 07:27 commons-pool-1.4.jar
-rw-r--r-- 1 119555 Jul 14 07:27 commons-validator-1.3.0.jar
-rw-r--r-- 1 40658 Jul 14 07:27 commons-validator.jar
-rw-r--r-- 1 362717 Jul 14 07:27 commons-vfs-1.0.jar
-rw-r--r-- 1 313898 Jul 13 10:11 dom4j-1.6.1.jar
-rw-r--r-- 1 208048 Jul 13 10:11 ehcache-1.2.3.jar
-rw-r--r-- 1 2255753 Jul 13 10:11 hibernate-3.2.5.ga.jar
-rw-r--r-- 1 265130 Jul 13 10:11 hibernate-annotations.jar
-rw-r--r-- 1 66426 Jul 13 10:11 hibernate-commons-annotations.jar
-rw-rw-rw- 1 110645 Jun 11 2009 hibernate-entitymanager.jar
-rw-rw-rw- 1 60992 Jul 13 17:55 hibernate-validator-3.0.0.ga.jar
-rw-r--r-- 1 2255753 Jul 13 10:11 hibernate3.jar
-rw-r--r-- 1 471005 Jul 13 10:11 javassist.jar
-rw-r--r-- 1 6727 Jul 13 10:11 jdbc2_0-stdext.jar
-rw-r--r-- 1 50491 Jul 13 10:11 jsp-api.jar
-rw-r--r-- 1 8812 Jul 13 10:11 jta.jar
-rw-r--r-- 1 1540457 Jul 13 10:11 ojdbc14.jar
-rw-r--r-- 1 1539291 Jul 13 10:11 poi-3.6-20091214.jar
-rw-r--r-- 1 3774332 Jul 13 10:11 poi-ooxml-schemas-3.6-20091214.jar
-rw-r--r-- 1 795888 Jul 13 10:11 poi-scratchpad-3.6-20091214.jar
-rw-r--r-- 1 97693 Jul 13 10:11 servlet-api.jar
-rw-r--r-- 1 530678 Jul 13 10:11 struts1.2.6.jar
-rw-r--r-- 1 1010806 Jul 13 10:11 xerces-2.6.2.jar
-rw-r--r-- 1 109318 Jul 13 10:11 xml-apis-1.0.b2.jar
Please help.

Hi,
The exception NullPointerException is coming from your Application : com.cs.cbrs.utils.InitPropsLoader.init( InitPropsLoader.java:11 )
Can u please check what is the code written in the Line-11 of program "com.cs.cbrs.utils.InitPropsLoader.InitPropsLoader.java" inside init()
Putting some System.out.println("debug....."); will help a lot to identify which object is becoming Null..to isolate the issue.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Startup Steps performed by weblogic 6.1 SP5

Similar Messages

Maybe you are looking for