Project compiling during Weblogic startup

Hi,
Is there any way to avoid Weblogic to recompile bpm proyects every time the server is restarted?
We have plenty of projects (and version) deployed on the OBPM engine, compiling each of them every time the server starts up takes quite a lot of time.
We are running the server in production mode.
Product version: WL 10.3.0.0 – OBPM 10 R3
Thanks!
Edited by: user10987017 on 12-ago-2011 12:45
Edited by: user10987017 on 12-ago-2011 12:46

This error happens to me after i installed WebLogic and tried to deploy an application.
I added then a dataSource and connection pool using the WebLogic console.
After that i restared my machine, because it become so slow.
After that i was not able to restart WebLogic, i got the error:
Caused By: java.lang.ClassNotFoundException: oracle.jbo.server.DatabaseTransactionFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
I modified the file config.xml, by commenting the entry <!-- jdbc-data-source-factory...
I renamed the name of the file JDBC_Data_Source-0-3407-jdbc.xml (may be the 3407 is a specific number for my installation)
After that i restarted the WebLogic, i now i can acces it by its console.
Thanks.
Zahir Djail.

Similar Messages

Deployed application is not picked up during weblogic startup

I'm having this strange problem, my application is deployed with java.Deployer
tool, works fine, then when ever i reboot the weblogic server, the application
is not accessible untill i explicitly redeploy it again.
Please help!

http://e-docs.bea.com/wls/certifications/certs_810/overview.html
Looks 141_03. But you have to understand what "certification" means.
Typically within minor revs of the VM 141_03 and 142 you are ok and there
should be no problems.
As for the proving it to you... There were lots of changes and improvemetns
to the 8.1 code line for deployment. As for knowing what your testing for,
OOM is a general error with no clear indication of where the problem lies,
its not clear if it is WLS version or the VM itself. I am sure you know the
hard answer there, it takes digging in with a profiler to find the culprit.
You have two options:
1) Drill down with a profiler in your env and figure out exactly WHAT is the
cause of the leak in the current environment
2) switch between different app verndors/versions and VMs.
Either way you have alot of varialbes to track, take care of and compare.
There is no silver bullet as always.
Cheers
mbg
"Stephen" <[email protected]> wrote in message
news:[email protected]...
>
BTW, is 8.1 certified with 1.4.2 on Solaris/Sparc yet? Otherwise it is anon-starter
>
"Stephen" <[email protected]> wrote:
SOS, we hear this one all the time, the new and improved version fixes
the problem.
Is this a 1.4.2 fix that helps 8.1 or something in the code that is
different?
be specific, I have this problem as well and am not willing to give it
another
try unless I know what I am testing for.
"Mark Griffith" <[email protected]> wrote:
My suggestion would be to try 8.1, I developed many sample applications
over
the course of the release and never had to restart the server and could
continually redeploy. The worst it got was having to completely
undeploy
and redeploy the application. (undeploy + redeploy is different that
just
redeploy).
Cheers
mbg
"Tom Wilson" <[email protected]> wrote in message
news:[email protected]...
This probably doesn't help but....we were doing our initial
development
using
Weblogic 7.0 using 1.3.1_08 but finally we got tired of dealing withthe
out
of memory issues resulting from continuously deploying new versionsof JSP
pages on our system. We found that running into the "Out of Memory"exceptions
combined with restarting and redeploying the app wasted too much time- an
average of 7 minutes about 7-8 times a day resulting in about 1 hourworth
of downtime for each developer using Weblogic. We finally trieddeveloping
our system with Tomcat and OpenEJB and now we never get "Out of
Memory"
exceptions requiring us to restart Tomcat - provided we are onlyworking
on JSP's.
Also, we used JDK 1.4.2 with Tomcat which helps get around the memoryleak
issue
that results from compiling JSP's using JDK 1.3.1.
My suggestion...try something else
"Stephen Westbom" <[email protected]> wrote:
I have had the same problem with Weblogic 7.0 sp4 using 1.3.1_08.
I
found that
turning off deadspot helps (otherwise known as hotspot).
It makes it unusable after a while in a production environment.
Our
firm is considering
switching to JBoss because it is simpler and more reliable, despiteno
good user
friendly deployment tools.
Weblogic concentrates too much on bells and whistles that sound good
rather than
reliability and usability. I guess existing customers are not asimportant
as
new business.
"Dmitry Amelchenko" <[email protected]> wrote:
Also, I don't know if that helps, but in general we've been
experiencing
some
other problems with the web logic deployment. For instance, aftera
number
of
redeployments, the application throwth OutOfMemoryException (about
10
deployments
MAX).
Internally we've been discussing what's the best way of deployingthe
ear application
into the weblogic -- using java deploy tool, or using hot deployby
just
dropping
the app in a particular bea folder.
Is there a prefered/recommended way of deployment?
If not, what people have found to be the most stable way of
deploying?
>>>>>>
Please help!
P.S. I'm little dissappointed, isn't bea an industry leader? Isn'tit
supposed
to take all these little issues away from the developpers so theycan
concentrate
on solving the business problems? It has not been the case for usso
far. BTW
-- JBOSS just works.
"Dmitry" <[email protected]> wrote:
I'm having this strange problem, my application is deployed with
java.Deployer
tool, works fine, then when ever i reboot the weblogic server,
the
application
is not accessible untill i explicitly redeploy it again.
Please help!

JDBC Initialization Failure during WebLogic Startup BEA-001136

Getting the BEA-001136 when attempting to start up SOA
receiving :
java.lang.NullpointerException
at java.util.Hashtable.put(Hashtable.java: 401)
at weblogic.jdbc.module.JDBCDataSourceFactory.addDataSourceFactory(JDBCDataSourceFactory.java:37)
at weblogic.jdbc.common.internal.JDBCService.initFactories(JDBCService.java:370)
at weblogic.jdbc.common.internal.JDBCService.initialize(JDBCService.java:116)
at weblogic.jdbc.common.internal.JDBCService.start(JDBCService.java:135)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
We are running on Weblogic 10.1.3
Any help would be great

This error happens to me after i installed WebLogic and tried to deploy an application.
I added then a dataSource and connection pool using the WebLogic console.
After that i restared my machine, because it become so slow.
After that i was not able to restart WebLogic, i got the error:
Caused By: java.lang.ClassNotFoundException: oracle.jbo.server.DatabaseTransactionFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
I modified the file config.xml, by commenting the entry <!-- jdbc-data-source-factory...
I renamed the name of the file JDBC_Data_Source-0-3407-jdbc.xml (may be the 3407 is a specific number for my installation)
After that i restarted the WebLogic, i now i can acces it by its console.
Thanks.
Zahir Djail.

Configure weblogic startup class in deployment jar

We need to invoke a class during weblogic startup that is part of application deployment jar...
It works if startup class is added to server classpath ( Weblogic documentation also insists that). But our startup class uses application logic and needs to be part of application jar..
We are getting java.lang.ClassNotFoundException for the class during start up. setting LoadBeforeAppDeployments to false also does not help...
Is there any other way to invoke a application class during weblogic startup...?
Any help would be appreciated.
Thanks,
Rajasekar.

here is the solution to this:
in the conventional method of implementing a startup class, one needs to impletent the T3STartupDef interface and register the class as a startup class in the console / config.xml
in this method, the startup class need not implement the T3STartupDef interface, it just needs to have a "main" method that will be called. the process of registeration is also simple, if you have an application ear.
while making the application ear, add a weblogic-application.xml along with the application.xml. the weblogic-application.xml should contain :
<startup>
<startup-class>myStartup</startup-class>
<startup-uri>myStartupArchive.jar</startup-uri>
</startup>
the myStartupArchive.jar should contain the startup class and all classes used by it
also, use a "manifest" file to point to other library jars within the ear
hope this helps someone !
going, going, ... gone.

Trying to create test project, and get NPE during server startup

Hi
I am trying to create simple test project using JSF RI (usually use myfaces), but I am getting a couple of NPE's during server startup.
I am using :
jetty (maven plugin)
jsf 1.2_03
facelets 1.1.12
I am probably missing something simple, but I just can't figure it out.
My web.xml:
<?xml version = '1.0' encoding = 'ISO-8859-1'?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
          version="2.4">
     <context-param>
          <param-name>facelets.REFRESH_PERIOD</param-name>
          <param-value>2</param-value>
     </context-param>
     <context-param>
        <param-name>facelets.LIBRARIES</param-name>
        <param-value>
            /WEB-INF/tomahawk.taglib.xml
        </param-value>
    </context-param>
     <context-param>
          <param-name>facelets.DEVELOPMENT</param-name>
          <param-value>true</param-value>
     </context-param>
     <context-param>
         <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
         <param-value>client</param-value>
         
     </context-param>
     <context-param>
          <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
          <param-value>.xhtml</param-value>
     </context-param>
     <context-param>
          <param-name>javax.faces.CONFIG_FILES</param-name>
          
        <param-value>
               /WEB-INF/faces-config.xml,/WEB-INF/faces-beans.xml,/WEB-INF/faces-nav.xml
          </param-value>
     </context-param>
     
     
     <listener>
          <listener-class>
               com.sun.faces.application.WebappLifecycleListener
          </listener-class>
     </listener>
     <listener>
          <listener-class>
               com.sun.faces.config.ConfigureListener
          </listener-class>
     </listener>
     <context-param>
          <description>
            Set this flag to true if you want the JavaServer Faces
            Reference Implementation to validate the XML in your
            faces-config.xml resources against the DTD. Default
            value is false.
        </description>
          <param-name>com.sun.faces.validateXml</param-name>
        <param-value>false</param-value>
    </context-param>
    <context-param>
         <description>
            Set this flag to true if you want the JavaServer Faces
            Reference Implementation to verify that all of the application
            objects you have configured (components, converters,
            renderers, and validators) can be successfully created.
            Default value is false.
        </description>
        <param-name>com.sun.faces.verifyObjects</param-name>
        <param-value>true</param-value>
    </context-param>
     
     <servlet>
          <servlet-name>faces</servlet-name>
          <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
     
     <servlet-mapping>
          <servlet-name>faces</servlet-name>
          <url-pattern>*.jsf</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.html</welcome-file>
     </welcome-file-list>
</web-app>My faces-config.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
                              "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
     <application>
           
          <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
          <locale-config>
               <default-locale>en</default-locale>
          </locale-config>
     </application>
</faces-config>My Stack traces :
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b09-FCS) for context '/test'
2007-01-23 15:41:57.351::WARN: failed ContextHandler@964130{/test,file:/C:/code/tests/rcfacesTest/src/main/webapp/}
java.lang.NullPointerException
        at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
        at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
        at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
        at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
        at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
        at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
        at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
        at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
        at org.mortbay.jetty.Server.doStart(Server.java:221)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
        at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
        at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.367::WARN: failed ContextHandlerCollection@91b9b0
java.lang.NullPointerException
        at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
        at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
        at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
        at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
        at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
        at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
        at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
        at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
        at org.mortbay.jetty.Server.doStart(Server.java:221)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
        at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
        at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.367::WARN: failed HandlerCollection@1360c93
java.lang.NullPointerException
        at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
        at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
        at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
        at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
        at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
        at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
        at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
        at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
        at org.mortbay.jetty.Server.doStart(Server.java:221)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
        at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
        at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.523::INFO: Started SelectChannelConnector @ 0.0.0.0:8080
2007-01-23 15:41:57.523::WARN: failed Server@188f506
java.lang.NullPointerException
        at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
        at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
        at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
        at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
        at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
        at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
        at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
        at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
        at org.mortbay.jetty.Server.doStart(Server.java:221)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
        at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
        at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
        at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
        at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Jetty server exiting.Thanks,
Mike

This has been fixed in the RI head. Hopefully we'll be able to get a 1.2_04 out shortly.
Please download a nightly from the RI project site and give that a shot.

Enable Diagnostics for WebLogic Startup

Hi
I am using the Integrated WLS within JDeveloper Studio 11.1.1.5.
I am trying to diagnose a problem where the WLS is deploying an application at startup that is failing. I would like to get low level diagnostics during startup to enable me to debug the problem. Currently I am only seeing the stack that throws the error which is not sufficient.
Currently only 'Warning' and 'Notice' level statements are being written to the log files/console.
I have tried the following none of which have affected the level of messages displayed in the log files/console:
1) Add additional debugging Java options to the ADF Fusion Applications project I am starting the WLS from under 'Project Properties --> Run/Debug/Profile --> Launch Settings --> Java Options'. I have tried adding various WLS debug switches which have had no effect i.e. '-Dweblogic.debug.DebugDeployment=true -Dweblogic.debug.DebugDeploy=true'
2) Add debugging Java options above to Integrated WLS Launch Settings under 'Application Server Properties --> Launch Settings --> Java Options'.
3) Added debugging Java options above directly to startWebLogic.cmd script.
4) Enable all weblogic debug flags from the WLS console under 'Summary of Servers >DefaultServer >Summary of Servers >DefaultServer>Debug'.
5) Changed WLS startup scripts to enable environment variable 'debugFlag'. This results in the JAVA_DEBUG variable being set to '-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n -Djava.compiler=NONE'.
5) Set the log level to FINEST for all 'weblogic*' classes in the Oracle Diagnostic Logging Configuration.
Surely there's a simple way of getting more diagnostics out of WebLogic during the startup phase?
Any assistance greatly appreciated.
Thanks

Hi,
It seems you did lot of things here but missed to make server logging in debug mode. As you have already enabled debuggers from admin console now go to servers > logging and change server logging to debug for all. This will help print the debug statements too.
For diagnostic you can enable it from admin console, but remember logging will be done in WLDF archive files that can be read using WLST only using WLST command - exportDiagnosticDataFromServer.
## rank the answer if it is helpful.. ;) ##
Thanks,
Ranjan
Edited by: Ranjan K on Apr 12, 2013 5:59 AM

10.1.3.5 - unable to find ws-addressing.xsd during SOA startup

I see the following messages in my logs during server startup any clue how to fix this ? the file seems to be there under bpel/system/xmllib
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Attempt (2/30) ... testing http access to server
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://10.10.10.10:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://10.10.10.10:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://localhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://localhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <ERROR> <collaxa> <ProcessJob::execute> Attempt (2/30) ... failed to connect ... retrying in 15 seconds ...

Hi,
Thanks a lot for your reply.
I set the ORACLE_HOME and WL_HOME to E:\OraHome\10g
But still the same error is coming.
I have already installed Weblogic server 10.3 in E:\OraHome\10g
When I try to install the SOA suite here is the step I am following
1) Source: F:\download\SOA\10g\ias_windows_x86_101351\Disk1\stage\products.xml
Destination: Name: oracleas
Path: E:\OraHome\10g
2) Language Selection
3) Weblogic server location: E:\OraHome\10g\wlserver_10.3
here when I press next it is throwing the error "The ORACLE_HOME needs to be at the same level as WL_HOME"
Do I need any preinstallation like database before going for SOA suite?
Thanks,
Balaram

After Effects can't continue: unexpected failure during application startup

Im running 10.10, Mac OSX, it was running fine before a minor update came out, and now I can not open AE CS6. I have uninstalled, reinstalled it, installed the trial of CC 2014. No messages beside "After Effects can’t continue: unexpected failure during application startup" come up.
System log:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
            Call location:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 0   CarbonCore                          0x00007fff82bb637d ___Gestalt_SystemVersion_block_invoke + 113
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 1   libdispatch.dylib                   0x00007fff8bf70fa2 _dispatch_client_callout + 8
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 2   libdispatch.dylib                   0x00007fff8bf70f00 dispatch_once_f + 79
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 3   CarbonCore                          0x00007fff82b5e932 _Gestalt_SystemVersion + 987
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 4   CarbonCore                          0x00007fff82b5e51f Gestalt + 144
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 5   AdobeCrashDaemon                    0x0000000100002e69 -[MyDaemon GetOSVersionMajor] + 33
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 6   AdobeCrashDaemon                    0x0000000100002d4a -[MyDaemon isRunningOnLeopard] + 25

Well, looks like a bug in Yosemite. You might wanan read the pertinent announcements, anyway. At this point Adobe apps are not compatible with OSX 10.10.
Mylenium

How can I disable the behance pics during the startup of my CC 2014 programmes?

When I start my photoshop cc 2014 and illustrator and all other apps, there ware always some behance pics from users.
is there a way to disable them?
thanks a lot
alex

hi sarah,
thanks for getting back to me.
i mean these images:
when the programmes are starting up…
thanks a lot for your help
alex
Am 08.01.2015 um 16:05 schrieb SarahBehance1 <[email protected]>:
How can I disable the behance pics during the startup of my CC 2014 programmes?
created by SarahBehance1 in Behance - View the full discussion
HI Alex - can you send a screenshot of what you're seeing? I'm not sure what you're referring to.
Talk to you soon, thanks!
If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7077548#7077548 and clicking ‘Correct’ below the answer
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7077548#7077548
To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"
Start a new discussion in Behance by email or at Adobe Community
For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.
Alex an der Haas
Art Direction
// Die Goldkinder
// Ausdenken und Machen.
// Mollardgasse 85A / Stiege 3 / Top 142, 1060 Wien
// Tel: +43 (0) 1 595.37.07
// Mob: +43 (0) 699.816.366.31
// http://www.diegoldkinder.at

After upgrading HANA from rev. 69.1 to rev.72 OOM errors occure during HDB startup

Hello,
we upgraded our HANA scale out system from rev. 69.1 to rev. 72.
~4 hours after the upgrade our HDB crashed with OOM errors on the master indexserver.
Since than we are trying to start it back up and face OOM errors during startup in the index rebuild phase:
The errors clearly state the HANA runs out of allocatable memory for Pool/IndexRebuildAllocator during startup.
It looks like HANA requires more memory during this phase compared to rev. 69.1
Our Master node has 512GB of physical memory and the Allocation limit is set to 95% of this (default).
Here is what we read from our logs during startup:
[3331]{-1}[-1/-1] 2014-03-24 01:35:36.735498 i Service_Startup ptime_master_start.cc(00719) : Rebuilding system indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.236971 i Service_Startup ptime_master_start.cc(00733) : Rebuilding system indexes done.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.237002 i Service_Startup ptime_master_start.cc(00735) : Rebuilding indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.244660 i Service_Startup IndexManager_rebuild.cc(00478) : Number of indexes: 2837
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.245606 i Service_Startup IndexManager_rebuild.cc(00580) : Number of JobEx indexes: 2798
[3367]{-1}[9/-1] 2014-03-24 01:36:33.729391 w ResMan           ResourceContainer.cpp(01300) : Information about shrink at 24.03.2014 01:28:46 000 Mon:
Reason for shrink: Precharge for big block allocation. User size: 6269307200
ShrinkCaller
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465154 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465164 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : Current callstack:
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : Current callstack:
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465245 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465256 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
GLOBAL_ALLOCATION_LIMIT (GAL) = 520645177866b (484.88gb), SHARED_MEMORY = 243742983024b (227gb), CODE_SIZE = 6919073792b (6.44gb)
PID=2987 (hdbnameserver), PAL=487793667686, AB=1596952576, UA=0, U=1415644701, FSL=0
PID=3196 (hdbcompileserve), PAL=487793667686, AB=447041536, UA=0, U=356200477, FSL=0
PID=3193 (hdbpreprocessor), PAL=487793667686, AB=416477184, UA=0, U=292814063, FSL=0
PID=3254 (hdbstatisticsse), PAL=54199296409, AB=1040187392, UA=0, U=862081043, FSL=0
PID=3257 (hdbxsengine), PAL=487793667686, AB=1100451840, UA=0, U=907234077, FSL=0
PID=3251 (hdbindexserver), PAL=487793667686, AB=265382010522, UA=0, U=218447843045, FSL=0
Total allocated memory= 520645177866b (484.88gb)
Total used memory     = 472943874222b (440.46gb)
Sum AB                = 269983121050
Sum Used              = 222281817406
Heap memory fragmentation: 9
Top allocators (ordered descending by inclusive_size_in_use).
1: /                                                                       218448756093b (203.44gb)
2: Pool                                                                    214254480696b (199.53gb)
3: Pool/IndexRebuildAllocator                                              196297409104b (182.81gb)
4: Pool/PersistenceManager                                                 9920106968b (9.23gb)
5: Pool/PersistenceManager/PersistentSpace(0)                              9779577952b (9.10gb)
6: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA                  9473884512b (8.82gb)
7: Pool/ResourceContainer                                                  2852314824b (2.65gb)
8: AllocateOnlyAllocator-unlimited                                         2832931544b (2.63gb)
9: Pool/malloc                                                             2660566632b (2.47gb)
10: Pool/malloc/libhdbrskernel.so                                           2467813288b (2.29gb)
11: Pool/RowEngine                                                          2284285840b (2.12gb)
12: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>                       2135949312b (1.98gb)
14: Pool/RowEngine/CpbTree                                                  1417842512b (1.32gb)
15: AllocateOnlyAllocator-limited                                           1184520640b (1.10gb)
16: AllocateOnlyAllocator-limited/ResourceHeader                            1184517680b (1.10gb)
17: Pool/RowEngine/LockTable                                                536881408b (512mb)
18: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator   360752520b (344.04mb)
19: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>                         360752520b (344.04mb)
20: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter            239921680b (228.80mb)
Top allocators (ordered descending by exclusive_size_in_use).
1: Pool/IndexRebuildAllocator                                               196297409104b (182.81gb)
2: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA                   9473884512b (8.82gb)
3: Pool/ResourceContainer                                                   2852314824b (2.65gb)
4: Pool/malloc/libhdbrskernel.so                                            2467813288b (2.29gb)
5: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
6: Pool/RowEngine/CpbTree                                                   1417842512b (1.32gb)
7: AllocateOnlyAllocator-limited/ResourceHeader                             1184517680b (1.10gb)
8: Pool/RowEngine/LockTable                                                 536881408b (512mb)
9: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator    360752520b (344.04mb)
10: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter/ConvPage    239075328b (228mb)
11: Pool/RowEngine/Internal                                                  205837824b (196.30mb)
12: StackAllocator                                                           176672768b (168.48mb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<48,128>/FreeBigBlockInfoAllocator 144301008b (137.61mb)
14: Pool/RowEngine/Transaction                                               103391528b (98.60mb)
15: Pool/malloc/libhdbexpression.so                                          90507984b (86.31mb)
16: Pool/malloc/libhdbbasement.so                                            90380472b (86.19mb)
17: AllocateOnlyAllocator-unlimited/ReserveForUndoAndCleanupExec             84029440b (80.13mb)
18: AllocateOnlyAllocator-unlimited/ReserveForOnlineCleanup                  84029440b (80.13mb)
19: Pool/Statistics                                                          83825720b (79.94mb)
20: Pool/PersistenceManager/ContainerNameDirectory                           59182968b (56.44mb)
In order to fix this bottleneck, we first need to get HDB started, but how?
Is there a way to aviod that row store tables are being loaded during startup? (this would allow enough memory for the index rebuild)
Is there a way to skip the index rebuild during startup?
Can we increase the allocation limit to more than 95% of the physical memory? (e.g. we could configure swap space to be utilized, just to get over the edge of this during the startup in order to bring our HDB back up and work on reducing the memory requirement on the master index server)
Kind Regards
Florian Wittmann
ps. we also have a call with SAP.

To update everyone who runs into the same issue during startup of HANA, here is the solution that has worked for us. But I highly recommend to have such an approach reviewed by SAP service before I you perform this!
For us the only chance left to bring HANA up was to configure swap space on the master node. (We configured 20GB...we could not know how much memory it would need during the startup to get passed the index rebuild, so that was just a guess that turned out to be just enough for us to get passed that memory peak during the startup phase).
After that we adjusted the custom parameter file /sapmnt/<SID>/global/hdb/custom/config/global.ini
and maintained a global_allocation_limit that we manually calculated as (512GB physical mem. + 20GB swap mem.)/0.95
e.g.
[memorymanager]
global_allocation_limit=517530
Than we started HANA up again and made use of the page file during the index rebuild in the startup phase...of course this dramatically slows down the startup...well you do an index reorg using swap space...but after 1hour we got passed the index rebuild and memory utilization went down again. (With this error we learned that HANA has a significantly higher memory consumption during startup and the upgrade from SP 6 to SP 7 must have even increased this slightly, since we managed to startup our HANA db before upgrading without this issue, but it was not the root cause!)
Now that we had HANA back up, we investigated memory consuming indices together with SAP, and with the help of below query, we identified row store table RSMONMESS to hold 25GB of 2ndary indices!
select table_name, round((sum(index_size)) / 1024 / 1024, 2) as
SIZE_IN_MB, count(*) as number_of_indexes from M_RS_INDEXES group by
table_name order by SIZE_IN_MB desc
Before droping 2ndary indices:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;30.883,8;6
drop index SAP<SID>."RSMONMESS~AXX";
drop index SAP<SID>."RSMONMESS~TIM";
drop index SAP<SID>."RSMONMESS~AU1";
drop index SAP<SID>."RSMONMESS~RID";
drop index SAP<SID>."RSMONMESS~AXY";
After drop:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;5.708,43;1
With that change we reset our custom parameter on global_allocation_limit and went back to the default (95% of main physical mem.), removed the swap file and started up HANA again...and during this startup we managed to stay in our global_allocation_limit and bring HANA back up again!

WLS 10.0 Mp1 - Weblogic startup class to initialize client's SSL channels

Hi,
Is it possible to use Weblogic startup class to initialize client's SSL channels?
Any pointers are appreciated.
Thanks in advance.

Hey
If possible can you explain the issue in detail.
What do you mean by “initialize client's SSL channels”
Regards,
Hussain

Message in alert log file during the startup of the DB

Hi,
i have two instances, i have the same warning in the alert log file during the startup of the DB:
Oracle instance running on a system with low open file descriptor limit.
Tune your system to increase this limit to avoid severe performance degradation.
The db_files parameter was at 1024 for the two instances, i have set it to 300 for the first instance and 550 for second, the message for the first instance was droped(it's ok), but the message was there in the alert log for the second instance.
The two instance are on the same machine.
The number of the open file limit on the linux machine is equal to 1024.
I have shutdown the first instance (with db_files=300) the problem persits for the second instance (with db_files=550).
My question is how to determinate the right value of db_files parameter to avoid this message.
Regards.
Message was edited by:
learn

Increase the max number of open file on Linux or decrease db_files.
f the OS limit is 1024 db_files would have to be >= 472 for the message to be printed. t is printed if an instance is configured to access more datafiles than the OS-specific limit on the number of files that can be open in a single process. In this case the server will re-cycle the file descriptors.
Vadim Bobrov
Oracle Database Tools
http://www.fourthelephant.com

Weblogic Startup Class does not run as Windows Service

If you know the answer, plase send me an email at [email protected]
I'm running a weblogic startup class that starts a Thread. I need to
run a batch program that should be running as long as WebLogic is
running (to process new orders).
It works fine when I run WebLogic (5.1 SP8) from a script, but causes
problem when I'm running it as a Windows Service. It calls the
startup class, however, the startup class never spawns the Thread
class.
Following is excerpts from different components:
=============================================================
*** weblogic.properties ***
weblogic.system.startupClass.pdfCreatorStart=WebLogicStartupPdfCreator
*** WebLogicStartupPdfCreator.java ***
public class WebLogicStartupPdfCreator implements T3StartupDef {
public String startup(String name, Hashtable args) throws
Exception {
Thread t = new ProductionPdfBatchRunner();
t.start();
return "success";
*** ProductionPdfBatchRunner.java ***
public class ProductionPdfBatchRunner extends Thread {
public void run() {
try {
//work being done here
this.sleep(30000);
catch (InterruptedException ie) {
catch(Exception e) {
e.printStackTrace();
=============================================================
Thanks for any help

Hi,
Ok. Few suggestions.
1. Can you review the SAP note:
552286 Troubleshooting for the SAP Web Dispatcher
2. When you said: "web dispatcher does not get started ", what error you got ? Can you be more details here ?
3. Please check the trace file dev_webdisp" that generated in the work directory. If the log entries is not abvious, increase the trace level to 2 or 3, and reproduce and re-check the trace file.
4. What is the output of the command "sapwebdisp -v"
5. How about sapwebdisp.pfl ? Are those settings correct ?
Hope this helps.
Regards,
Vincent

Weblogic startup class (urgent)

Hi All,
I need a java program (weblogic startup class) which should fetch data from the database and instantiate another one class (it will be the data holder) and store that object into a webapplication context. Anyone tried this? Since its urgent any help will be appreciated.
Thanks in advance
Cheers,
Pandiaraj

Do this in the init() method of a servlet and start
the servlet when you start your weblogic server
second that. just give a value of 1 for <load-on-startup> in web.xml

Automating Weblogic Startup/Shutdown on Linux

hello and hope you fine
im using weblogic 10.3 with oracle db 11g on CentoOS 5.5
everything is working fine
but my problem is that i want to startup/shutdown weblogic on system start/shutdown
i defined weblogic as service ( i tried all levels) and it works but the problem is
when the system is booting it start weblogic but it stops continue system boot!
i also tries put the start weblogic on the .bash_profile
the system boot but when im trying to login it stops because the same problem
(weblogic startup and prevent contitnue the loginin )
i also tried to add startWeblogic in /etc/rc.d/rc.local
and the same problem when weblogic start system cant continue booting
i also tried using nohup
also the same problem
so how can i start/shutdown weblogic ?
and thanks for help
Edited by: user13113692 on Aug 2, 2010 3:22 AM

thank you for your replay
but its the same
when server is booting
the weblogic start and goes to the running state
it stops continue the other services and
the server boot could not continue
here is some of my script
#!/bin/sh
WEBLOGIC_HOME=/root/Oracle/Middleware/user_projects/domains/mydomain/
# source function library
. /etc/rc.d/init.d/functions
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh &
i also tried something like this to grape all the output to a log file
but the problem here is that the weblogic give me a exception about the paths
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh ALL > ${WEBLOGIC_HOME}/logz/start.log 2>&1 &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh ALL >${WEBLOGIC_HOME}/logz/stops.log 2>&1 &
i also tried this with the standalone weblogic and its the same
any help will be appreciated

Project compiling during Weblogic startup

Similar Messages

Maybe you are looking for