Deployment on SPARC
Are there any significant issues re. developing on Intel and then deploying on SPARC, or vica versa ?
Point me to a URL if appropriate
Thanks
register for the Sun developer connection
use Workshop compilers
write clean architecture independent code on Solaris Intel
recompile on Sparc
Download and run Appcert if you're a purist:-)
Similar Messages
-
We are able to run 6.0 and 6.1 versions in win2000 .can we do this on Solaris ..
Do we need a differnet license for clustering ...
Can we use one of the weblogic servers in cluster as proxy or sholud we use a
differnt one as a proxy server
Regards
Ranga
1. WebLogic runs on Sparc/Solaris. It is commonly deployed on Sparc/Solaris.
2. WebLogic clustering requires a clustering license from BEA.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ranga Rao" <[email protected]> wrote in message
news:[email protected]..
>
> We are able to run 6.0 and 6.1 versions in win2000 .can we do this on
Solaris ..
>
> Do we need a differnet license for clustering ...
>
> Can we use one of the weblogic servers in cluster as proxy or sholud we
use a
> differnt one as a proxy server
>
> Regards
> Ranga
>
>
-
Hi All,
I'm currently being asked to look creating a number of servers with mirroring. Ideally the whole server will use ZFS which would mean it would also need to boot from ZFS.
Looking at the OpenSolaris website:
http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/
It looks like it's possible to do this. My problem is that I need to use vanilla Solaris on SPARC, and some bits and pieces from those instructions don't work.
Is this even possible? If it's not, what's the best I can hope for?
I'm currently testing on x86 (in VMWare), I'll be deploying on SPARC.
Thanks for any help.....Darren_Dunham wrote:
Boot procedures on x86 and SPARC are still quite different. So your testing on one doesn't necessarily help on the other. You'll note that the link you show is only for x86.
A new boot method for SPARC is being developed that will work with ZFS, but it hasn't been released the way the x86 side has. So you can't boot from ZFS on SPARC just yet.
DarrenI've also had issues with ZFS root in the X86 world. I won't go into the details as I'm not 100% certain whether it was the Nevada Build I was using (76) or if it was user error.
The current roadmap has ZFS boot for mainline Solaris as coming in either U5 or U6 according to a briefing we had recently. That puts it out anywhere from mid to very late 2008.
Dev Express will likely have it sooner, but we're back to "Is this production"? If it is, I would wait for it to be solid and stable and in main-line Solaris.
Cheers, -
Unable to deploy 12c agent on Solaris 10 / Sparc
Hello everyone.
I'm currently evaluating the new Oracle Enterprise Manager 12c and have it installed on Solaris 11 (x86-64).
Now I want to deploy agents on some Solaris 10 ( Sparc64 ) server. The software is transferred and then the agentDeploy.sh script is executed but it always failed with accessing objects with the wrong ELFCLASS.
I receive the following error:
java.lang.UnsatisfiedLinkError: /oracle/emagent/core/12.1.0.1.0/oui/lib/solaris/liboraInstaller.so: ld.so.1: j
ava: Schwerer Fehler: /oracle/emagent/core/12.1.0.1.0/oui/lib/solaris/liboraInstaller.so: falsche ELF-Klasse:
ELFCLASS64 (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1806)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1702)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1003)
at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:402)
at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.<clinit>(OiipuUnixOps.java:125)
at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.getEnv(OiipgEnvironment.java:201)
at oracle.sysman.oii.oiip.oiipg.OiipgPropertyLoader.initUnixPtrFileLoc(OiipgPropertyLoader.java:213)
at oracle.sysman.oii.oiip.oiipg.OiipgPropertyLoader.<clinit>(OiipgPropertyLoader.java:126)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.updateProperties(OiicStandardInventorySession.j
ava:461)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:2
57)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:2
31)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:1
80)
at oracle.sysman.agent.installer.AgentInstaller.getAllHomesInfo(AgentInstaller.java:789)
at oracle.sysman.agent.installer.AgentInstaller.main(AgentInstaller.java:574)
The installed agent software shows the correct class ELF 64-Bit executable SPARCV9 Version 1 .
So what goes wrong ?
JoergHello,
I've found a workaround to solve the problem.
On the target server a temporary installation directory was created containing the agentDeploy.sh script.
Inside this script there are several java calls and some are missing the information to run as 64-bit.
I've changend the rows where the flag "-d64" was missing:
..../java -d64 -classpath....
and then I've made a retry from EM 12c.
And it works successfully.
Have a nice day!
Joerg -
Need help deploying to SJSWS6.1SP6 Solaris SPARC
The app was built with Creator2U1
I have used the example sun-web.xml file in the example: Deploying to Sun Java System Web Server 6.1"
Thanks...
Here is the sun-web.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc. //DTD Sun ONE Application Server 7.0 Servlet 2.3//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-1.dtd">
<sun-web-app>
<context-root>/employee</context-root>
<resource-ref>
<res-ref-name>UCHCDB</res-ref-name>
<jndi-name>jdbc/UCHCDB</jndi-name>
</resource-ref>
<sun-web-app>
The Creator data Source name is: UCHCDB
The pool name is: employee_pool
The JNDI name is: jdbc/UCHCDB
realizing I am going from windows to unix a have been careful with the "case."
Here is the start of the error log file (browser return server error)
[03/Aug/2006:12:26:34] info (23997): CORE5073: Web server shutdown in progress
[03/Aug/2006:12:26:38] info (24891): CORE1116: Sun ONE Web Server 6.1SP6 B05/07/2006 12:33
[03/Aug/2006:12:26:43] info (24892): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun Microsystems Inc.]
[03/Aug/2006:12:26:44] info (24892): WEB0100: Loading web module in virtual server [https-test] at [employee]
[03/Aug/2006:12:26:45] failure (24892): WEB0120: XML error parsing deployment descriptor [d0/SunONE/wsvcs/https-test/webapps/https-test/apps/employee/WEB-INF/sun-web.xml]
Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:314)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:630)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:549)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1734)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1758)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1186)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1509)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:341)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:828)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:758)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:228)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:711)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2075)
at com.iplanet.ias.web.WebContainer.loadWebModule(WebContainer.java:696)
at com.iplanet.ias.web.WebContainer.loadStandaloneWebModule(WebContainer.java:627)
at com.iplanet.ias.web.WebContainer.loadWebModules(WebContainer.java:601)
at com.iplanet.ias.web.WebContainer.createVS(WebContainer.java:376)
at com.iplanet.ias.server.J2EERunner.createVS(J2EERunner.java:223)The app runs ok in Creator 2.1 and Sun Application Server PE 8.1 and Oracle on the same remote box.
I appear to have gotten past a couple of problems..
Now it appears to be a Oracle parameter in the server.xml file?? or the app
I have successfully connected to the database with a small java utility program using the same URL as in the SJSWS6.1 JAVACONNECTIONPOOL: URL parameter.
so the user/password/connection string appear correct..
The error log shows "prerender" in file page1.java, line 338
which is here:
public void prerender() {
if (dropDown1.getSelected() == null) {
try {
orgDataProvider.cursorFirst();
getSessionBean1().getPsnnRowSet().setObject(1,
orgDataProvider.getValue(
"ORG"));
psnnDataProvider.refresh();
catch (Exception e) {
error("Cannot read Personnel File" + e.getMessage());
here is the error log from SJSWS6.1SP6:
ug/2006:11:35:50] failure (25139) RegionalIntranets: for host trying to GET /employee/JSCreator_index.jsp, service-j2ee reports: StandardWrapperValve[jsp]: WEB2792: Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException: oracle.jdbc.driver.OracleDatabaseMetaData.locatorsUpdateCopy()Z
at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536)
at jsps.JSCreator_index_jsp._jspService(_JSCreator_index_jsp.java:67)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:687)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:459)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:375)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:579)
----- Root Cause -----
java.lang.AbstractMethodError: oracle.jdbc.driver.OracleDatabaseMetaData.locatorsUpdateCopy()Z
at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:972)
at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:1410)
at com.sun.data.provider.impl.CachedRowSetDataProvider.checkExecute(CachedRowSetDataProvider.java:1219)
at com.sun.data.provider.impl.CachedRowSetDataProvider.absolute(CachedRowSetDataProvider.java:283)
at com.sun.data.provider.impl.CachedRowSetDataProvider.getRowKeys(CachedRowSetDataProvider.java:232)
at com.sun.data.provider.impl.CachedRowSetDataProvider.cursorFirst(CachedRowSetDataProvider.java:351)
at employee.Page1.prerender(Page1.java:338)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.prerender(ViewHandlerImpl.java:860)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:295)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:772)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:382)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:443)
at jsps.JSCreator_index_jsp._jspService(_JSCreator_index_jsp.java:59)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:687)
at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:459)
at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:375)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
Help would be greatly appreciated:
Thanks -
Can not deploy Federation Manager 7.0 (http 500 error)
Hi,
I am trying to install Sun Java System Federation Manager 7.0 on SunOS 5.8 sparc machine, and never get any further after build the federation.war file
Basically, I use standard script to build the war file
./fmsetup install -s fmsilence-template
and install the Sun web server 6.1 with standard installation.
If I then deploy the federation.war file , I will get following error message.
[31/May/2006:14:12:19] info (13892): CORE3276: Installing a new configuration
[31/May/2006:14:12:19] info (13892): WEB0100: Loading web module in virtual server [https-miranda.niss.ac.uk] at [federation]
[31/May/2006:14:12:19] warning (13892): WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[31/May/2006:14:12:19] info (13892): WEB0100: Loading web module in virtual server [https-miranda.niss.ac.uk] at [search]
[31/May/2006:14:12:51] failure (13892): WebModule[federation]: WEB2783: Servlet /federation threw load() exception
javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
----- Root Cause -----
java.lang.NullPointerException
at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:72)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[31/May/2006:14:12:51] info (13892): CORE3280: A new configuration was successfully installed
[31/May/2006:14:12:51] info (13892): WEB4202: Closing web application environment for virtual server [https-miranda.niss.ac.uk]
And if I try to access the federation manager console http://host:port/deployment-URI/UL/Login
I will get HTTP 500 Internal server error
Any one know how to solve the problem?
Thanks in advanceI'm getting the same thing. And I do have AM installed and working on the same machine.
Anyone have any ideas? -
NAS 4.0 evaluation version installation problem on SPARC/Solaris 2.8
Installing the NAS 4.0 that was bundled with a Sun SPARC/Solaris 2.8 throws
the following error:
( Installed with quick installation after correct installation of iWS 4.0,
from documentation Directory Server installed is not needed since NAS
installs its own)
In December of 1999, the Sun-Netscape Alliance announced
i P l a n e t A p p l i c a t i o n S e r v e r 6.0
* 100% J2EE compliant
* reliability and high availability for non-stop service required by
the Enterprise
* scalability to go the distance for unplanned success
* the best performance of any web application server
* broadest support of tools for J2EE application development
* high performance and complete solutions for internet enterprise
integration
Information and availability of this next generation application server
can be found at
Please enter the install location [usr/netscape/server4]:
Please enter the FULL PATH of the Web Server Instance to be used
for NAS:
/usr/netscape/server4/https-sofiana03.sofiana
Please enter the password for Netscape Directory Server Adminstrator
and Netscape Application Server Administrator.
The password needs to tb be at least 8 characters. [changeit]:
Installing Netscape core components
Installing Netscape Server Family Core Components
Installing Netscape Directory Suite
Installing Administration Services
Installing Netscape Application Server Suite
Starting the NAS install ...Installing Netscape Application Server 4.0
Core
Binaries
Extracting Netscape core components ...
Extracting Netscape Server Family Core Components ...
Extracting Netscape Core Java classes ...
Extracting Java Runtime Environment ...
Extracting Netscape Directory Server ...
Extracting Netscape Directory Server Console ...
Extracting Netscape Administration Server ...
Extracting Netscape Console ...
Extracting NAS Web Connector Component ...
Extracting NAS Core Server Component ...
Extracting NAS Administrator Component ...
Extracting NAS Deployment Manager ...
Extracting Netscape Application Server 4.0 Core Binaries ...
Fatal Slapd The required field AdminDomain is not present in the install
info fi
le.
Configuring Administration Server...
Your parameters are now entered into the Administration Server
database, and the Administration Server will be started.
Changing ownership to admin user root...
Setting up Admininistration Server Instance...
ERROR: Ldap authentication failed (151:Unknown error.)
Proceeding with installation of Netscape Application Server (NAS)...
Reading userinput log file ..... done
Configuring web server plugin
....../usr/netscape/server4/nas/bin/nas_postinstall
..ksh[49]: /usr/netscape/server4/https-sofiana03.sofiana/start.1007: cannot
creat
e
mv: cannot access /usr/netscape/server4/https-sofiana03.sofiana/start.1007
/usr/netscape/server4/nas/bin/nas_postinstall.ksh[188]:
/usr/netscape/server4/ht
tps-sofiana03.sofiana/config/.obj.conf: cannot create
mv: cannot access
/usr/netscape/server4/https-sofiana03.sofiana/config/.obj.conf
ERROR: Variable KIVAwebdocs was not defined. This command:
/usr/netscape/server4/nas/bin/.kconfns
/usr/netscape/server4/https-sofia
na03.sofiana /usr/netscape/server4/nas
did not set the DocRoot variable correctly.
Please make sure that this file exists and is executable:
/usr/netscape/server4/nas/bin/.kconfns
This NAS installation might not be succesful.
Please enter the WebServer docs directory pathname:
==>
What's WebServer docs? entered usr/netscape/server4/docs didn't help.
Thanks for the support
Pablohi,
Make sure that your network uses DNS naming.
This error occurs when a machine is not correctly configured to use DNS naming. The default fully qualified host and domain name presented during installation is not correct.
To successfully install, you need to provide a fully qualified domain name that consists of a local host name along with its domain name.
for example yoursystem is a host name and yourdomain.com is a fully qualified domain name.
regards,
saravanan -
Deploy ADF 11g to WebLogic Server: Unmarshaller failed
Hello,
I have an IBM server which was built with an Intel Xeon CPU; and I run Solaris 10 on it.
It seems there is no WebLogc 10.3 package installer for Solaris x86 (SPARC only). So I must install WebLogic 10.2.
Does JDeveloper 11g support WebLogic 10.2 ? (I see only 10.3 when create an Application Server connection)
When I tried to deploy my ADF application to WebLogic Server (with the connection for WebLogic 10.3) from my computer, an exception occurred:
weblogic.management.DeploymentException: Unmarshaller failed
When I read the log file on the server, it said that there was an error in weblog-application.xml, related to the descriptor. (Sorry, I am not at the server right now; so I cannot write exactly what it said. If necessary, I'll post it later.)
I hope someone will help me to resolve this problem.
Thanks for reading my thread!There are messages in the log file:
<1230546713435> <BEA-160197> <Unable to load descriptor /export/home/PhucNT/bea/wlserver_10.0/samples/domains/wl_server/./servers/examplesServer/upload/BKSync/app/BKSyncDeployment.ear/META-INF/weblogic-application.xml of module BKSyncDeployment.ear. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
... 28 more
.>
####<Dec 29, 2008 5:31:53 PM ICT> <Error> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546713523> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean BKSync. Error - weblogic.management.DeploymentException: Unmarshaller failed.
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Dec 29, 2008 5:31:53 PM ICT> <Error> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546713552> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1230546711085' for task '0'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Dec 29, 2008 5:31:54 PM ICT> <Warning> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546714489> <BEA-149004> <Failures were detected while initiating deploy task for application 'BKSync'.>
####<Dec 29, 2008 5:31:54 PM ICT> <Warning> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546714490> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException: Unmarshaller failed
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172) -
Helps for WLP9.2 in a cluster: deploy errors, propagation errors
I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts. -
Error during deploying agent 12.1.2.2162 with Ops
hi,
I install the latest Ops version available for linux machine (12.1.2.2161)
All works like it should but when I try to deploy the agent on a sparc T5220 with solaris 11 installed, I receive this error message from Ops :
+03/12/2013 10:35:45 AM CET ERROR Cannot launch job to provision agent to t5220: Cannot find agent bundle for operating system=SunOS, OS version 11, processor=sparc and version<=12.1.2.2161 for proxy pc304 (80304). The asset is currently managed agentlessly. To convert to agent management, select the OS and perform Switch Management Access after correcting the problem: (10211)+
On the server with Ops installed, I have this agent images :
OpsCenterAgent.Linux.i686.12.1.2.2161.zip
OpsCenterAgent.Linux.i686.12.1.2.2161.zip.sig
OpsCenterAgent.Solaris.i386.12.1.2.2162.zip.sig
OpsCenterAgent.Solaris.i386.12.1.2.2162.zip
OpsCenterAgent.Solaris.sparc.12.1.2.2162.zip
OpsCenterAgent.Solaris.sparc.12.1.2.2162.zip.sig
The problem is in the proxy when he checks the agent version present in Ops.
I didn't find the previous sparc agent version 12.1.2.2161
I don't know where I can modify this check or download the previous version.
If someone knows ?
Thanks in advance.
frboSolaris 11 agents can only be provisioned by a sol11 Enterprise Controller and Proxy Controller. Please check the support matrix in the docs.
-
How to backout a Recommended Patch cluster deployment in Solstice disksuite
Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07. -
Facing issue while deployment on 11.1.1.6 soa server
Problem Summary
Facing issue while deployment on 11.1.1.6 soa server
Problem Description
We are facing issue while deploying a bpm project over a newly built bps-soa server 11.1.1.6.
While we are deploying a bpm project, first it is taking around 40mins to create .jar file and then while deploying, it is getting failed with transaction timed out error.
"composite: Onboarding: javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 301 second".
we have tried with changing all transaction parameters also like JTA,XA( as similar to our exiting running QA/PROD environment which is on 11.1.1.5) but even then facing the same issue.
The code were originally build over 11.1.1.5 version, for the first time opening with jdev, code gets migrated and over the upgraded code we did some business specific changes and now trying to deploy over the new server.
Code is getting successfully compiled and also .jar file is creating properly but while deployment facing error(As shared earlier).
Also tried to deploy the same .jar file using em consle(to soa-infra) but facing similar issue.
Error Codes
Problem Category/Subcategory
BPM 11g installation issues
Uploaded Files
Template Question Responses
1) ### Product Versions Including Build Numbers ###
BPM SOA suite 11.1.1.6
2) ### Is the Issue Reproducible ###
Yes, mentioned in issue detailes.
3) ### OS Version ###
SunOS xxxxx 5.10 Generic_144488-06 sun4v sparc SUNW,T5440
More logs:
Name
=== ODM Data Collection ===
[2013-02-27T01:10:59.436-05:00] [soa_server1] [WARNING] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to obtain the audit metadta java.lang.IllegalStateException: The transaction associated with this transaction-scoped persistence context has been rolled back and as a result, the EntityManager has been closed. No further operations are allowed in this transaction context. Please see the server log for the cause of the rollback.
[2013-02-27T01:11:17.402-05:00] [soa_server1] [WARNING] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to obtain the audit metadta java.lang.IllegalStateException: The transaction associated with this transaction-scoped persistence context has been rolled back and as a result, the EntityManager has been closed. No further operations are allowed in this transaction context. Please see the server log for the cause of the rollback.
[2013-02-27T01:11:18.147-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] BPEL Component "default/Onboarding!2.0*soa_8130f118-f9b5-462a-8e75-5ec0f34b45bd/Remediation" successfully loaded.
[2013-02-27T01:11:18.166-05:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to activate process Remediation[[
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:156)
at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:595)
at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:455)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:52)
at oracle.bpm.bpmn.engine.ejb.impl.BPMNServerManagerBean_6gbx7k_IBPMNCubeServerManagerLocalBeanImpl.deployComponent(Unknown Source)
at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:842)
at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.load(BPMNServiceEngine.java:636)
at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.load(BPMNServiceEngine.java:151)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployComponents(CompositeDeploymentConnection.java:243)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
... 2 more
FileName
soa_server1-diagnostic-2.log2 things must be noticed:
First: ODI 11g is not supported by JDK 7, I always use the JDK1.6.0_27 and works fine. When you try to open the ODI Studio, this message appears, telling that ODI is supported only with JDK 6 versions, so don't try to use JDK 7.
Second: I always install the JDK in a path without spaces, like "C:\JDK1.6.0_27\" and the excatly same thing to odi install files. So I call via Command Prompt:
C:\ODI_INSTALL\Disk1\setup.exe -jreLoc C:\JDK1.6.0_27\
I did over 20 windows installations using these settings, it'll work perfectly.
Regards.
Luiz Araujo -
Hi All,
Has anybody deployed their ADF application on solaris successfully.
I am unable to do so since last two weeks.
My Jdev version 10.1.3.0.4.3673 (running local windows)
My Oracle app server 10.1.2.0.2 (running remote solaris)
1>Used Jdev adf installer wizard and installed the librarys successfully on remote windows machine (10.1.2.0.2) Oracle App Server. Deployed the .ear from Jdev to this windows box. smooth. application works fine.
2>Now, wanted to deploy on solaris box. Used two methods.
a>Used the ADF Runtime installer ver 10.1.3..0 from Oracle site. Ran it on solaris box. Installation fails with message "trying to update BC4J......" Connection Exception Connection refused etc etc "
Try, to up the EM and it is broken -------- Reason, this ADF installer overwrites/truncates configuration files like server.xml , applcation.xml etc etc
b>Oracle said, now try another method. Install Jdev same version directly on solaris box. and Use Jdev wizard to install the libs on solaris. So installed Jdev on solaris, and used ADF runtime wizard. Now, the wizards shows "Installation Successful" but as I see the server.xml, and other config files overwritten and truncated after running wizard. Again EM is broken.
Again, my question is :-----
Would it be wrong if I say "Jdev ADF installer (whether standalone OR Using Jdev ADF runtime wizard) runs good on windows (in my case it did work on remote windows box) BUT fails if you try to run on solaris. and worst keeps truncating important configuration files."
Is there anybody who had done successful ADF upgrade on solaris box ?
This is now urgent, as we spent two weeks on it.
thanks,
ppHi,
I downloaded jdevstudio11110install.jar and copied this to my file system(root). on click on this jar no even is occurring, i had tried on both x86 and sun sloaris 10 sparc getting the same result am unable to see base studio run on this platforms, do i missing any steps to run this jar.
Plz reply ASP.
--Shrinivas -
Errors when Automatically Deploying Planning into WebLogic 9.1
Dears,
I have installed Planning 9.3.1 on the Solaris OS.(SPARC 64-bit)
But when I want to deploy Planning into WebLogic 9.1 automatically. It has failed to deploy application "HyperionPlanning".
Please let me know if anyone has some ideas.
Thanks for your help.
SophiaHi,
Is planning supported on 64bit SPARC ?
You may have to manually deploy planning into weblogic.
Sorry I can't help further.
Cheers
John
http://john-goodwin.blogspot.com/ -
We have installed the OSM server on Solaris Sparc server with 10.3.1 Weblogic server. The Eclipse is installed on the Windows machine which has 10.3.3 weblogic. Will building the cartrdiges with 10.3.3 weblogic lib files and deploying them on to a server which is 10.3.1 cause any issues?
None of the Weblogic files referenced by Design Studio are bundled into the automation plugin files that are deployed to the server, so it shouldn't cause any issues. That being said, the safest (and supported) approach would be to have the same WLS version in both places.
Generally we would recommend customers use WLS 10.3.3 if you are on OSM 7.0.3.x. There are a number of important fixes in that release that are important to consider.
Brian.
Maybe you are looking for
-
Hi All, In the Fb03 Transaction When i give print Preview I want to show the Document Date as Blank, by default print preview its coming, hoe can i restrict this, i have done the following steps i don't know how to proceed after this, the steps ar
-
Purchase Requisition restriction at Material Type level
Hi MM Guru's as per Client requirment we want to restrict the Purchase Requisition creation at Material type level (i.e system should raise the error messege when we try to create the PR against Finished Goods) is that possible if yes how can we rest
-
XmlIndex on table not allowing delete or update
Hi Oracle and slqplus versions: Oracle Database 11g Release 11.2.0.2.0 - 64bit Production PL/SQL Release 11.2.0.2.0 - Production CORE 11.2.0.2.0 Production TNS for Solaris: Version 11.2.0.2.0 - Production NLSRTL Version 11.2.0.2.0 - Production I'm ha
-
Hashtable imcompletely deserialized?!
If anyone could help me with this I would be most appreciative. I appear to have a situation where a serializable class with an internal Hashtable is not deserilizing correctly. The class containing the Hashtable is called PropDb. In PropDb I have th
-
I loaded an album from a cd. Instead of showing it as one album, there are several albums because of a number of performers that were on the album. Can I combine all of these songs into one album?