Weblogic 8.1 SP2 loads applications twice.

Hi,
We are moving from Weblogic 6.1 to Weblogic 8.1 and we are seeing some weird
behaviour when whe stop the server regenerate an application (a .jar file in
the applications directory) and we start the server.
The fact is that each time one of this .jar files (which contains EJBs) are
changed, the server deploys them twice, it wouldn't be nothing more than an
annoing problem if we did not had an startup class that is executed after
the first application deploy but before the second "deploy" (it has code
dependant on connections obtained from entity beans. In fact it is a problem
with TopLink session being destroyed once a reference to an entity is
acquired) that are trashed by the "redeploy".
This is what we get on the console:
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from unprepared to prepared on server
foo.>
<Info> <EJB> <BEA-010008> <EJB Deploying file: ejbs_bar.jar>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from unprepared to prepared
on server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to active on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to active on
server foo.>
<Info> <Deployer> <BEA-149210> <Resumed.>
<Info> <WebLogicServer> <BEA-000287> <Invoking startup class:
foo.bar.startup.Test.startup()>
<Info> <Application Poller> <BEA-149412> <Application
"_appsdir_ejbs_bar_jar" is being redeployed, because it changed since the
previous server run.>
<Info> <Application Poller> <BEA-149400> <Activating application:
appsdirejbs_bar_jar>
<Info> <Deployer> <BEA-149038> <A deployment task with ID 0 for application
appsdirejbs_bar_jar is being initiated.>
<Info> <Deployer> <BEA-149033> <preparing application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from active to prepared on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from active to prepared on
server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to unprepared on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to unprepared
on server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from unprepared to prepared on server
foo.>
<Info> <EJB> <BEA-010008> <EJB Deploying file: ejbs_bar.jar>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from unprepared to prepared
on server foo.>
<Info> <Deployer> <BEA-149033> <prepared application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149033> <activating application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to active on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to active on
server foo.>
<Info> <Deployer> <BEA-149033> <activated application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149074> <Successfully completed deployment task:
[Deployer:149026]Deploy application appsdirejbs_bar_jar on foo.>
<Info> <Management> <BEA-141052> <The application poller has started for the
development server.>
<Info> <Socket> <BEA-000415> <System has file descriptor limits of - soft:
1.024, hard: 1.024>
<Info> <Socket> <BEA-000416> <Using effective file descriptor limit of:
1.024 open sockets/files.>
<Info> <Socket> <BEA-000406> <PosixSocketMuxer was built on May 22 2003
15:43:24>
<Info> <Socket> <BEA-000436> <Allocating 3 reader threads.>
<Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "foo"
for domain "bar" running in Development Mode>
<Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default"
listening on port 7001, ip address *.*>
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
The line:
Application "_appsdir_ejbs_bar_jar" is being redeployed, because it changed
since the previous server run.
Clearly points that the container has deployed the older ejbs_bar.jar file
and now it is going to deploy the newer one.
As you can see the startup class is in the middle of the two deployments and
the second one trashes some internal references of it.
I have been looking the news for anybody having similar problems and I found
this thread:
From : Amber
Date : 11/14/2003 8:12
Newsgroup: weblogic.developer.interest.application.deployment
Subject : Startup servlet loading twice
A similar problem is pointed by Taj when deploying an aplication with an
startup servlet on it.
It seems that the problem is solved setting the server in "production mode"
I dind't tried it yet as I have just finded it.
There are also some comments about the (in)convenience of using the
"applications" directory for application deployment. If so, then: where
should they be put instead?
Is this a "feature" of Weblogic 8.1 or is this a bug that may be fixed on
Weblogic 8.1 SP3
Thanks in advance.
Regards.
Ignacio.

Yes we get exactly the same problem and have raised a BEA Support Case about this.
Unfortunately this has been dragging on as using our EAR file BEA are unable
to reproduce the problem. I think this is more due to our ear file having many
ejbs and CMP EJBs etc that won't deploy in a different environment e.g no database
etc.
So BEA have asked us to produce a simple example EAR file that shows this problem,
but unfortunately due to deadlines we have been unable to do this yet - and probably
won't for 3 or 4 weeks.
If you have a more simple example maybe you could either send this to [email protected]
to be added to my case (just make sure email has "BEA Support Case: 508280")
in the title or maybe raise your own case.
Incidently if your ear is too large for email BEA have an FTP procedure for sending
stuff in I can send you this if necessary.
cheers
Pete
"Ignacio G. Dupont" <[email protected]> wrote:
Hi,
We are moving from Weblogic 6.1 to Weblogic 8.1 and we are seeing some
weird
behaviour when whe stop the server regenerate an application (a .jar
file in
the applications directory) and we start the server.
The fact is that each time one of this .jar files (which contains EJBs)
are
changed, the server deploys them twice, it wouldn't be nothing more than
an
annoing problem if we did not had an startup class that is executed after
the first application deploy but before the second "deploy" (it has code
dependant on connections obtained from entity beans. In fact it is a
problem
with TopLink session being destroyed once a reference to an entity is
acquired) that are trashed by the "redeploy".
This is what we get on the console:
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from unprepared to prepared on
server
foo.>
<Info> <EJB> <BEA-010008> <EJB Deploying file: ejbs_bar.jar>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from unprepared to prepared
on server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to active on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to active
on
server foo.>
<Info> <Deployer> <BEA-149210> <Resumed.>
<Info> <WebLogicServer> <BEA-000287> <Invoking startup class:
foo.bar.startup.Test.startup()>
<Info> <Application Poller> <BEA-149412> <Application
"_appsdir_ejbs_bar_jar" is being redeployed, because it changed since
the
previous server run.>
<Info> <Application Poller> <BEA-149400> <Activating application:
appsdirejbs_bar_jar>
<Info> <Deployer> <BEA-149038> <A deployment task with ID 0 for application
appsdirejbs_bar_jar is being initiated.>
<Info> <Deployer> <BEA-149033> <preparing application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from active to prepared on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from active to prepared
on
server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to unprepared on
server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to unprepared
on server foo.>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from unprepared to prepared on
server
foo.>
<Info> <EJB> <BEA-010008> <EJB Deploying file: ejbs_bar.jar>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from unprepared to prepared
on server foo.>
<Info> <Deployer> <BEA-149033> <prepared application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149033> <activating application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149059> <Module ejbs_bar of application
appsdirejbs_bar_jar is transitioning from prepared to active on server
foo.>
<Info> <Deployer> <BEA-149060> <Module ejbs_bar of application
appsdirejbs_bar_jar successfully transitioned from prepared to active
on
server foo.>
<Info> <Deployer> <BEA-149033> <activated application appsdirejbs_bar_jar
on foo>
<Info> <Deployer> <BEA-149074> <Successfully completed deployment task:
[Deployer:149026]Deploy application appsdirejbs_bar_jar on foo.>
<Info> <Management> <BEA-141052> <The application poller has started
for the
development server.>
<Info> <Socket> <BEA-000415> <System has file descriptor limits of -
soft:
1.024, hard: 1.024>
<Info> <Socket> <BEA-000416> <Using effective file descriptor limit of:
1.024 open sockets/files.>
<Info> <Socket> <BEA-000406> <PosixSocketMuxer was built on May 22 2003
15:43:24>
<Info> <Socket> <BEA-000436> <Allocating 3 reader threads.>
<Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server
"foo"
for domain "bar" running in Development Mode>
<Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default"
listening on port 7001, ip address *.*>
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
The line:
Application "_appsdir_ejbs_bar_jar" is being redeployed, because it changed
since the previous server run.
Clearly points that the container has deployed the older ejbs_bar.jar
file
and now it is going to deploy the newer one.
As you can see the startup class is in the middle of the two deployments
and
the second one trashes some internal references of it.
I have been looking the news for anybody having similar problems and
I found
this thread:
From : Amber
Date : 11/14/2003 8:12
Newsgroup: weblogic.developer.interest.application.deployment
Subject : Startup servlet loading twice
A similar problem is pointed by Taj when deploying an aplication with
an
startup servlet on it.
It seems that the problem is solved setting the server in "production
mode"
I dind't tried it yet as I have just finded it.
There are also some comments about the (in)convenience of using the
"applications" directory for application deployment. If so, then: where
should they be put instead?
Is this a "feature" of Weblogic 8.1 or is this a bug that may be fixed
on
Weblogic 8.1 SP3
Thanks in advance.
Regards.
Ignacio.

Similar Messages

Weblogic 6.1 sp2 , application which used to run on wl 6.1 sp1 does not run anymore

Hi
For some reason, my application 'portal' does not run on weblogic 6.1 sp2,
It used to run fine on 6.1 sp1 .
I am attaching the weblogic.log file with this msg.
Thanks,
Regards,
Lalitha
[weblogic6.1sp2logs.txt]

Tobin is right, my apoplication is called "portal", I am not using WLPortal. Anyway,
I managed to resolve my problem,I had sax2 , xp and xt parsers placed in the WEB-INF\lib
directory of my application in addition to my own jar file. I removed the parsers
, and now my application is running fine.
It is strange though, since my application used to load and work flawlessly on
weblogic 6 as well as weblogic 6.1 sp1 with the parsers in the lib directory....
Anyhow, thanks a lot for the help.
Regards,
Lalitha
"Tobin Paterson" <[email protected]> wrote:
>
Having applied WLS 6.1 sp2 upgrade today I am seeing the same fault.
I am not using
WL Portal. Also I think the original poster's application just happens
to be called
"portal" and is not using WL Portal.
cheers,
Tobin.
"BEA Support" <[email protected]> wrote:
Hello,
Only WLCS and/or WLPS 3.5 sp 2 support WLS 6.1 sp 2
WL Portal 4.0 support only WLS 6.1 sp 1.
Regards,
Developer Relations Engineer
BEA Support
"Lalitha" <[email protected]> a écrit dans le message de news:
[email protected]..
Hi
For some reason, my application 'portal' does not run on weblogic
6.1
sp2,
It used to run fine on 6.1 sp1 .
I am attaching the weblogic.log file with this msg.
Thanks,
Regards,
Lalitha

Can't deploy a SINGLE bean in weblogic 6.1 SP2 w/o application reload

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Double submission problem in J2EE application under Weblogic 8.1 SP2 server

Hi,
We are facing double submission problem in our J2EE application which is running under Weblogic 8.1 SP2 and for the same we already implemented or added the below preventive solutions.
1. We disable the SUBMIT button once the user clicks it.
2. We preventated pressing 'F5' button and clicking 'Refresh' button in the browser.
3. Also we tried to prevent by declaring the idempotent is 'true' under weblogic-ejb-jar.xml as below.
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempotent>
So please somebody help us on this issue like how to prevent in some other way.
Regards,
Dinesh.

I have no idea why you would think changing your EJB configuration would have anything to do with preventing double submission at your servlet layer.
One technique I've seen for preventing double submission was first used in the Struts framework several years ago. When a page is "prepared" for display, a token value is created and stored in the session. The page is displayed with a hidden field containing that value. When the page is submitted, the value of the hidden field is compared with the value stored in the session. If they're not equal, the submission is ignored.

JSP compiler in Weblogic 7.1 SP2 and Weblogic 8.1

          I have a web application (JSp and Servlets are generated) that loads fine with
          Weblogic 8.1. However, I have problems with Weblogic 7.1 SP2. In trying to load
          some of the JSP pages, I get the follwing type of errors
          Parsing of JSP File '/consume_int.jsp' failed:
          /consume_int.jsp(17): bean type com.mypackage.ConTypes.ConTypesJspBean has no
          read method for property 'consume_int_Int_parameter1'
          probably occurred due to an error in /consume_int.jsp line 17:
          <H4>consume_int_Int_parameter1:</H4> <jsp:getProperty name="ConTypesJspBean" property="consume_int_Int_parameter1"/>
          Wed Jun 09 20:01:34 BST 2004
          Looking further, I found that for property x, there are methods getx() and not
          getX(). Can this cause the problem. It seems to be working for some of the getx()
          methods and not for other ones.
          Any help would be appreciated.
          Thanks,
          MIB


          It does NOT seem to work with methods getX and setX for property 'x' in Weblogic
          7.1 SP2. It works fine in Weblogic 8.1. Any ideas ?
          - MBI
          "MIB" <[email protected]> wrote:
          >
          >I have a web application (JSp and Servlets are generated) that loads
          >fine with
          >Weblogic 8.1. However, I have problems with Weblogic 7.1 SP2. In trying
          >to load
          >some of the JSP pages, I get the follwing type of errors
          >
          >Parsing of JSP File '/consume_int.jsp' failed:
          >--------------------------------------------------------------------------------
          > /consume_int.jsp(17): bean type com.mypackage.ConTypes.ConTypesJspBean
          >has no
          >read method for property 'consume_int_Int_parameter1'
          >probably occurred due to an error in /consume_int.jsp line 17:
          ><H4>consume_int_Int_parameter1:</H4> <jsp:getProperty name="ConTypesJspBean"
          >property="consume_int_Int_parameter1"/>
          >
          >--------------------------------------------------------------------------------
          >Wed Jun 09 20:01:34 BST 2004
          >
          >Looking further, I found that for property x, there are methods getx()
          >and not
          >getX(). Can this cause the problem. It seems to be working for some of
          >the getx()
          >methods and not for other ones.
          >
          >Any help would be appreciated.
          >
          >Thanks,
          >
          >MIB

Deployment problem - Weblogic 8.1 SP2

I've created a simple, one-page project to test deployment to Weblogic 8.1 SP2.
I followed the instructions in http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/weblogicdeploy.html except for the database related parts (my project does not access a database).
On startup, Weblogic fails to proload the FacesServlet for my app:
####<May 18, 2006 2:45:42 PM PDT> <Error> <HTTP> <hqp-vs-hypdev01> <ProtivitiServer> <main> <<WLS Kernel>> <> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "HelloTest".
javax.servlet.ServletException
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
and when I try to access my Page1.jsp, Weblogic throws another (related?) exception:
<BEA-101017> <[ServletContext(id=1830320,name=HelloTest,context-path=/HelloTest)] Root cause of ServletException.
java.lang.NullPointerException
     at javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
     at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:993)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:869)
Any help with this? Do I need Weblogic 8.1 SP4?

hi,
0. Check WLS classpath in startWeblogic.{cmd.sh} for JSF jars
1. Check your web.xml with section conserning FacesServlet
it shoul look like:
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
2. Try to find any other servlet and look at its <load-on-startup> section.
Final Java Servlet Specification Ver. 2.4 page 127:
" The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value "
Kind regards,
Alex
Message was edited by:
AKlimenko

Error deploying Struts 1.1 on weblogic 6.1 sp2

Hello,
I am trying to deploy the struts-documentation.war that comes with struts 1.1
on weblogic 6.1 sp2.
I already have xerces.jar , xalan.jar and crimson.jar in WEB-INF/lib. I have also
tired giving the files in the weblogic classpath.
It does not deploy the application and it gives the following error:
####<Jul 13, 2004 2:26:44 PM IST> <Debug> <HTTP> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <101158> <Exception thrown while loading struts-documentation:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at
weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at
weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at
weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Jul 13, 2004 2:26:44 PM IST> <Error> <J2EE> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <160001> <Error deploying application struts-documentation:
Could not load struts-documentation>
####<Jul 13, 2004 2:26:44 PM IST> <Error> <Management> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <141042> <Error deploying application
.\config\mydomain\applications\struts-documentation.war:
java.lang.reflect.UndeclaredThrowableException>
Any help in this regard will be highly appreciated.

I'm also running Weblogic 6.1 SP2 and getting a very similar error during startup when trying to deploy JSTL (Apache's version 1.0.6 from here http://jakarta.apache.org/taglibs/) in an exploded application that starts up fine if I remove the JSTL jars from WEB-INF/lib.
The exact stack trace in my case is this:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:234)
at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3407)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy31.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy30.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy41.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)

Weblogic 6.0 sp2: War deployment not working !!

Hi,
I'm using weblogic 6.0 sp2, and it seems as though the war deployment is not
working. My war consists of jsps, images, and under the WEB-INF/classes
directory, Struts classes (i.e. Form and Action classes). When I try to run
a jsp, i get the following error :
<Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
<[WebAppServletContext(4655498,ati
nera)] Root cause of ServletException
javax.servlet.jsp.JspException: Exception creating bean of class
com.atinera.log
in.web.LoginForm: java.lang.ClassNotFoundException:
com.atinera.login.web.LoginF
orm
But if you look in the war, that class is in there.
What gives ?
Thanks,
Jamie

That's right - ActionServlet does Class.forName(actionClass) to load action
class, and this uses ClassLoader which loaded the current class (ActionServlet)
ClassLoaders always delegate to their parent before attempting to load
the class themselves, so it wasn't working until you moved struts.jar to your
WEB-INF/lib.
BTW, Struts doc mentions this problem:
lib/struts.jar - This JAR file contains all of the Java classes included
in Struts. It should be copied into the WEB-INF/lib directory of your web
application. WARNING - If you are going to be hosting multiple Struts based
applications on the same servlet container, you will be tempted to place the
struts.jar file into the shared repository supported by your container. Be
advised that this will like cause you to encounter ClassNotFoundException
problems unless all of your application classes are stored in the shared
repository.
Jamie Tsao <[email protected]> wrote:
So I found the solution to this problem, but it doesn't really make sense to
me.
I originally had struts.jar outside of the WAR file, but in my CLASSPATH.
Weblogic was able to load Strut's ActionServlet (controller), but when the
ActionServlet was looking for the LoginForm (which was inside the WAR), it
couldn't find it.
I solved the problem by putting struts.jar inside the WAR (under
WEB-INF/lib) instead that other directory. Now it works cause apparently
ActionServlet is now in the same classloader as LoginForm, the classloader
which loaded the WAR.
I'm confused because original way should have worked since the classloader
that loaded struts.jar from outside the war is the parent classloader for
the classloader that loaded the WAR. did that make any sense ?
anyone know why ?
thanks,
jamie
"Jamie Tsao" <[email protected]> wrote in message
news:[email protected]...
Hi,
I'm using weblogic 6.0 sp2, and it seems as though the war deployment isnot
working. My war consists of jsps, images, and under the WEB-INF/classes
directory, Struts classes (i.e. Form and Action classes). When I try torun
a jsp, i get the following error :
<Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
<[WebAppServletContext(4655498,ati
nera)] Root cause of ServletException
javax.servlet.jsp.JspException: Exception creating bean of class
com.atinera.log
in.web.LoginForm: java.lang.ClassNotFoundException:
com.atinera.login.web.LoginF
orm
But if you look in the war, that class is in there.
What gives ?
Thanks,
Jamie
Dimitri

Weblogic 6.1 SP2 hangs up at database command, PATCH needed!

Hello,
I use weblogic 6.1 SP2 on Windows and Solaris
DB-Driver: Oracle Thin Driver for Oracle 9i
Database OP System: Win2000
My application runs fine. After some time (about 15.000 db operations)
at load tests, the weblogic 6.1 server hangs up without an error message
in the logs at a any desired database command.
I use the database pool from weblogic.
The database operations are made with the TX-Datasource.
The main database operation is a call of an oracle stored
procedure.
I suppose, that the weblogic hangs up in a synchronized
block of the pool, but the crash could also have an other reason.
After the crash, the whole instance is dead and must be restarted.
I can reconstruct the crash on windows and solaris.
I always thought, weblogic is reliably?
Is there any patch to fix this problem?
I am very thankful for every help to fix this problem.
Thank you in advance
Markus

Hi,
here is the source code of the the stateless session bean (S1), which
calles the oracle stored procedure.The commit or rollback is done in
the main interface (stateless session bean with user managed
transactions).
java.sql.CallableStatement stmt=null;
java.sql.Connection conn = null;
try {
javax.sql.DataSource ds =
at.one.bmw.system.SystemConfig.getDataSource();
conn=ds.getConnection();
stmt=conn.prepareCall("{call routeChargingRecord(?,?,?,?,?,
int i=1;
stmt.setString(i++,seq_number);
stmt.setInt(i++,custTypeID.intValue());
stmt.setString(i++,msisdn.toString());
stmt.setLong(i++,billing_serviceID.longValue());
stmt.setLong(i++,serviceGroupID.longValue());
stmt.setString(i++,transactionID);
stmt.setInt(i++,typeID.intValue());
stmt.setInt(i++,applicationID.intValue());
stmt.setString(i++,gateway_number);
stmt.setString(i++,smsc_serviceID);
stmt.setString(i++,smsc_tarifID);
stmt.setString(i++,desc);
stmt.setString(i++,beneficiaries);
stmt.setString(i++,attr0);
stmt.setString(i++,attr1);
stmt.setString(i++,attr2);
stmt.setString(i++,attr3);
stmt.setString(i++,deliveryNotes);
int xx=stmt.executeUpdate();
try { stmt.close(); } catch (Exception en) {}
try { conn.close(); } catch (Exception eb) {}
conn=null; stmt=null;
} // end try
catch (Exception e) {
this.sessionContext.setRollbackOnly();
try { stmt.close(); } catch (Exception en) {}
try { conn.close(); } catch (Exception eb) {}
throw new EJBAppException(msg+"\n"+e.getMessage());
} // end catch
Thank you for your help.
"Sree Bodapati" <[email protected]> wrote in message news:<[email protected]>...
Hi Markus,
Can you please post the test code that can demonstrate the hang here.
sree
"Markus Häusler" <[email protected]> wrote in message
news:[email protected]...
Hello,
I use weblogic 6.1 SP2 on Windows and Solaris
DB-Driver: Oracle Thin Driver for Oracle 9i
Database OP System: Win2000
My application runs fine. After some time (about 15.000 db operations)
at load tests, the weblogic 6.1 server hangs up without an error message
in the logs at a any desired database command.
I use the database pool from weblogic.
The database operations are made with the TX-Datasource.
The main database operation is a call of an oracle stored
procedure.
I suppose, that the weblogic hangs up in a synchronized
block of the pool, but the crash could also have an other reason.
After the crash, the whole instance is dead and must be restarted.
I can reconstruct the crash on windows and solaris.
I always thought, weblogic is reliably?
Is there any patch to fix this problem?
I am very thankful for every help to fix this problem.
Thank you in advance
Markus

How to use call back and user session id based conversation with web service in weblogic 6.1 sp2 ?????????

Hi, every one:
Here's my question of my day - >>>
I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K, and
I got a web service up and running called Price Update web service through
which user can pick up a price and push a deal to another web service
called: deal service, the deal service will take the user deal and book the
deal ( sending a JMS message to a Queue, a MD will pick up and do the work,
then send the confirmation to another JMS Queue ), then the confirmation
will be picked up and sent to another web service , called: User Deal
Confirmation Service, here's the question:
1. Since the client application is only allowed to see its own confirmed
deals, how I can make the confirmed deal encrypted based on a server
generated key or the session id that client application provides
2. Now, I have 3 webservices: update, deal and confirm, each of them has a
client.jar file available - from the client application point of view, do I
need all these 3 client.jar, or I just need one of them ?????
3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
beta, you can do this easily in the workshop, in the second question above,
I think I need some how relate the confirmation to the client conversation
id ??
thanks a lot for the input, have a nice day.
regards,
mark.

Any comments ?
mark
"markhu" <[email protected]> wrote in message
news:[email protected]..
Hi, every one:
Here's my question of my day - >>>
I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K,and
I got a web service up and running called Price Update web service through
which user can pick up a price and push a deal to another web service
called: deal service, the deal service will take the user deal and bookthe
deal ( sending a JMS message to a Queue, a MD will pick up and do thework,
then send the confirmation to another JMS Queue ), then the confirmation
will be picked up and sent to another web service , called: User Deal
Confirmation Service, here's the question:
1. Since the client application is only allowed to see its own confirmed
deals, how I can make the confirmed deal encrypted based on a server
generated key or the session id that client application provides
2. Now, I have 3 webservices: update, deal and confirm, each of them has a
client.jar file available - from the client application point of view, doI
need all these 3 client.jar, or I just need one of them ?????
3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
beta, you can do this easily in the workshop, in the second questionabove,
I think I need some how relate the confirmation to the client conversation
id ??
thanks a lot for the input, have a nice day.
regards,
mark.

[Help] Weblogic throws exception under load testing

Hello All,
I have developed an application using struts 1.1 framework and deployed
it on weblogic 8.1. The application works fine. But when we load test
the application, weblogic throws an exception. I am not able to
understand why is weblogic throwing this exception. The exception
doesn't originate from my code
I am using struts 1.1 on BEA weblogic 8.1 on HP-UX 11i.
Please help me ... I will be very gratefull for your help.
Here is the stack trace :
<Jan 15, 2004 10:02:28 PM IST> <Error> <HTTP> <BEA-101020>
<[ServletContext(id=28318025,name=testWebApp,context-path=/testWebApp)]
Servlet failed with Exception java.lang.NullPointerException
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:305)
at
weblogic.servlet.internal.RequestDispatcherImpl$ForwardAction.run(Reques
tDis
patcherImpl.java:382)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatche
rImp
l.java:286)
at
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.jav
a:10
69)
at
org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProc
esso
r.java:274)
at
org.apache.struts.action.RequestProcessor.processForwardConfig(RequestPr
oces
sor.java:455)
at
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(Tiles
Requ
estProcessor.java:320)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
279)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(W
ebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etCo
ntext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java
:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Regards,
Abhishek.

Hello All,
I have developed an application using struts 1.1 framework and deployed
it on weblogic 8.1. The application works fine. But when we load test
the application, weblogic throws an exception. I am not able to
understand why is weblogic throwing this exception. The exception
doesn't originate from my code
I am using struts 1.1 on BEA weblogic 8.1 on HP-UX 11i.
Please help me ... I will be very gratefull for your help.
Here is the stack trace :
<Jan 15, 2004 10:02:28 PM IST> <Error> <HTTP> <BEA-101020>
<[ServletContext(id=28318025,name=testWebApp,context-path=/testWebApp)]
Servlet failed with Exception java.lang.NullPointerException
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:305)
at
weblogic.servlet.internal.RequestDispatcherImpl$ForwardAction.run(Reques
tDis
patcherImpl.java:382)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatche
rImp
l.java:286)
at
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.jav
a:10
69)
at
org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProc
esso
r.java:274)
at
org.apache.struts.action.RequestProcessor.processForwardConfig(RequestPr
oces
sor.java:455)
at
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(Tiles
Requ
estProcessor.java:320)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
279)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java
:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(W
ebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etCo
ntext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java
:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Regards,
Abhishek.

Deployment of OA Project in R12.2 - Could not load application module

I have deployed a project that is working without issue in JDeveloper to a R12.2 environment, but I am receiving the following error on loading of the page. This seems to be a common problem as I have another issue with deploying OA Framework projects in R12.2 Is anyone else using R12.2 or has seen this in any other R12 instance? Anything developed in 11.5.10 first and "upgraded" to the latest JDeveloper is working fine, but so far nothing developed directly in R12.2 JDeveloper works in the environment.
 oracle.apps.fnd.framework.OAException: Could not load application module 'xxaai.oracle.apps.inv.bptrequest.server.BPTRequestCreateAM'.
at oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicationRegistry.java:279)
at oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicationRegistry.java:78)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1313)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:556)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:444)
at _pages.__oa._jspService(__oa.java:233)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:159)
at _pages.__rf._jspService(__rf.java:239)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.apps.fnd.security.WLFilter.doFilter(WLFilter.java:203)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:429)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Matias
Try bouncing your server and then test it again.Generally this error comes due to uncompiled jsp files.Bounce Apache Server and then check.
You may check Metalink Note: 465812.1
Thanks
AJ

Error -- ISO8859_1 Not Supported in Weblogic 6.1 SP2

I've installed Weblogic 6.1 Service Pack 2 on Solaris 8, and when I go to install
and deploy and applications (including the Petstore Demo) I get an error message
which says 'ISO8859_1 is not supported'.
If I stop and then restart the Weblogic Server, I get the following StackTrace
included below.
I've noticed there have been several posts on this topic, but no response. Thanks
in advance to anyone who can help me out!
Gary Smith
[email protected]
--Stack Trace of Error when Server Startup:
weblogic.xml.process.XMLParsingException: The encoding "ISO8859_1" is not supported.
- with nested exception:
[org.xml.sax.SAXParseException: The encoding "ISO8859_1" is not supported.] Line:
0 Column: 0
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:135)
at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.process(J2EEDeploymentDescriptorLoader_J2EE12
.java:137)
at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:114)
at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
at weblogic.management.mbeans.custom.Application.getDD(Application.java:670)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:487)
at weblogic.management.mbeans.custom.Application.load(Application.java:387)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.load(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.loadApplications(ApplicationManager.java:556)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:367)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_Cach
ingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)

Gary:
Please try using a valid XML (also called MIME or IANA) encoding name
(ISO-8859-1) instead of the Java encoding name (ISO8859_1).
The IANA character set registry can be found at:
<http://www.iana.org/assignments/character-sets>
Regards --
Jim Brown
Gary Smith wrote:
>
I've installed Weblogic 6.1 Service Pack 2 on Solaris 8, and when I go to install
and deploy and applications (including the Petstore Demo) I get an error message
which says 'ISO8859_1 is not supported'.
If I stop and then restart the Weblogic Server, I get the following StackTrace
included below.
I've noticed there have been several posts on this topic, but no response. Thanks
in advance to anyone who can help me out!
Gary Smith
[email protected]
--Stack Trace of Error when Server Startup:
weblogic.xml.process.XMLParsingException: The encoding "ISO8859_1" is not supported.
- with nested exception:
[org.xml.sax.SAXParseException: The encoding "ISO8859_1" is not supported.] Line:
0 Column: 0
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:135)
at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.process(J2EEDeploymentDescriptorLoader_J2EE12
java:137)
at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:114)
at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
at weblogic.management.mbeans.custom.Application.getDD(Application.java:670)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:487)
at weblogic.management.mbeans.custom.Application.load(Application.java:387)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.load(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.loadApplications(ApplicationManager.java:556)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:367)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_Cach
ingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)--
Jim Brown
Developer Relations Engineer
BEA Support

Upgrading Weblogic 8.1, SP2 to Weblogic 8.1, SP6

wanna to the code changes that are required in web application while upgrading Weblogic 8.1, SP2 to Weblogic 8.1, SP6.

I am currently conducting the same type of upgrade. We have Platform 8.1 SP2 installed. We would like to upgrade to SP3, but I was not sure if any patches were required before the upgrade. After several dicussions with BEA Technical Support, here is what I learned.
To upgrade 8.1 SP2 to SP3, you must first install the following patch...
http://dev2dev.bea.com/products/wlplatform81/patch/wlplat81sp2_patch.jsp
...then use SmartUpdate to upgrade the SP3.
If you choose to fully install 8.1 SP3, then you do not need to install the patch because 8.1 SP3 includes the pacthes. Installing the patches would make no difference anyway since the SP2 installation would be deleted to make room for the SP3 installation. This option is not an upgrade, it is a full installation.
Hope it helps!
Raffi

Weblogic 8.1 SP2 ORA-01000 caused by Weblogic's pending XA recovery process.

Hi, we are migrating our application from Weblogic 6.1 SP5 to Weblogic 8.1
SP2 and we are facing the nasty ORA-01000 problem.
After tracking it for some days we happened to find "what" was causing it.
After issuing the following select on an Oracle instance used by a weblogic
running for a day
SELECT sql_text,count(*) FROM V$OPEN_CURSOR
GROUP BY sql_text
ORDER BY sql_text
and this is what we get::
SQL_TEXT COUNT(*)
ALTER SESSION SET NLS_LANGUAGE = 'AMERICAN' 2
ALTER SESSION SET NLS_TERRITORY = 'AMERICA' 2
SELECT 1 FROM DUAL 2
SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER =' 2
SELECT count (*) FROM SYS.DBA_PENDING_TRANSACTIONS 2
SELECT formatid, globalid, branchid FROM SYS.DBA_PENDING_TRA 2669
SELECT max(version) FROM "SYS"."JAVA$POLICY$SHARED$TABLE" 2
begin :1 := JAVA_XA.xa_commit_new (:2,:3,:4,:5); end; 2
begin :1 := JAVA_XA.xa_end_new(:2,:3,:4,:5); end; 2
begin :1 := JAVA_XA.xa_start_new(:2,:3,:4,:5,:6); end; 2
insert into javasnm$(short, longname, longdbcs) values(:1,:2 2
select longname from javasnm$ where short = :1 2
(In fact there are two Weblogic instances running against the same Oracle
instance and as we didn't filtered by connection I supouse that's why
numbers "seem" to be "duplicated")
We do currently have 1500 cursors max declared for session in our Oracle's
ora.init file.
After activating Weblogic's jdbc.log we have seen that with an interval of 5
seconds the
SELECT formatid, globalid, branchid FROM SYS.DBA_PENDING_TRANSACTIONS
is issued against the DBMS.
After executing both selects on an SQLPLUS console we have seen that the
SELECT count(*)... sentence returns 1 and after looking at
SYS.DBA_2PC_PENDING table there is one transaction on it (although it was
already manually rollback forced three months ago). I know we should delete
already forced transactions in order to clean up that table but the fact is
we didn't and maybe that is what is causing Weblogic issuing the second
select (the SELECT formatid, globalid... one) periodically.
A number of questions come to our mind:
1. Is this Weblogic's correct behaviour? I mean, is it normal for weblogic
to issue this select every five seconds?
If yes.
2. Why is this select leaving opened cursors? I presume that this select is
being executed within a transaction and it's neither commited nor rolledback
If actually it is being executed within a transaction then:
3. Why is Weblogic opening a transaction to issue a select?
As additional info we have two datasources configured into our weblogic
server, I must say we do use TopLink as our persistence manager and it
requires both transactional (XA) and not transactional datasources to work.
We are using Oracle thin drivers (classes12.zip) to connect to an Oracle
8.1.7 database instance. I know that Weblogic 8.1 now ships with the
ojdbc14.jar Oracle thin driver classes but we are not sure if we can use it
with Oracle 8.1.7 (as it seems to be prepared to be used with Oracle 9.0.2.
Is it?).
Looking at jdbc.log we can also see this at the beginging of the file:
java.sql.SQLException: SQL operations are not allowed with no global
transaction by default for XA drivers. If the XA driver supports performing
SQL operations with no global transaction, explicitly allow it by setting
"SupportsLocalTransaction" JDBC connection pool property to true. In this
case, also remember to complete the local transaction before using the
connection again for global transaction, else a XAER_OUTSIDE XAException may
result. To complete a local transaction, you can either set auto commit to
true or call Connection.commit() or Connection.rollback().
I have readed somewhere at edocs.bea.com that Weblogic 8.1 -by default-
begins a transaction whenever using an XA connection (as some XA drivers
require a transaction to be started when using them, although IIRC this can
be disabled on Weblogic's console). If in fact it happens that we can
disable the default transaction oppening when using an XA connection, is it
safe? Is there a prefered way to solve this than disabling the transaction
"auto begining" feature?
I think there is also possible to disable Weblogic's pending transactions
auto-recover mechanism but we think this is a great Weblogic feature and we
would prefer not having to do it. As in two years we have managed to get
about three of them due to unexpected server crashes (even if it those cases
Weblogic 6.1 didn't managed to recover them at least it showed the problem
on the log).
Thanks if advance.
Regards.
Ignacio.

Seems that removing classes12.zip from the classpath solves the problem. I
don't get that periodic error any more so now I don't get the ORA-01000. I
still seeing -from time to time- the "SQL operations are not allowed with no
global
transaction by default for XA drivers" error in the jdbc.log though, so I
presume the ORA-01000 would raise sooner or later but now with a much larger
period after starting the server.
Well there seems that ojdbc14.jar has not so subtle changes. Let's hope
there are not "newer" issues with it that would not happen with
classes12.zip.
Ignacio.

Weblogic 8.1 SP2 loads applications twice.

Similar Messages

Maybe you are looking for