WLI 8.1 MBean Cluster
We are builing cluster environment for WLI usage. There is one admin server and two managed servers. We setup a cluster and included these two managed servers.
And of course we created and deploy some workflow projects into this cluster.
We need to use MBean API to access the workflow in other server. But the problem is ~~ I see that MBean is registed in "admin server". If the admin server is crash and managed server also alive. Does the MBean API also work well?? Does the cluster setting is useless when calling MBean? Anybody know that?
Regards,
Scharwenka
Thanks for your reply.
We need to get the nodes in someone workflow, so we use MBean API to do that. For example: A flow A->B->C->D.
We need to got total flow view (the result from SVGView is not useful). And we need to get previous(B) or next(D) node in someone step(C).
In WLI 7.0, the workflow operating API is provided. But in WLI 8.1, we just got the information that only MBean API can meet our requirement.
So anybody know how to solve MBean cluster problem?
Similar Messages
-
Cannot Deploy JPD with Timer Event Subscription in WLI 9.2 MP1 cluster
Has anyone had any luck deploying a JPD with a timer event subscription to a 9.2 MP1 WLI cluster? I am able to deploy Synchronous Client Request JPDs without any trouble but the ones that rely on internal WLI queues for invocation will not deploy in production. I am able to deploy the problematic JPDs to a non-clustered development environment without any issues but when I try to deploy the same artifact to a 9.2 MP1 cluster I see the following error:
Throwable: java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
Stack Trace:
java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: tosipDomain_phase2:Name=cgJMSServer,Type=JMSServer
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:667)
at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:1025)
at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnitForURI(DispCache.java:946)
at com.bea.wli.management.adminhelper.AdminHelperBean.getDispFile(AdminHelperBean.java:348)
at com.bea.wli.management.adminhelper.AdminHelperBean.getProcessMetadata(AdminHelperBean.java:94)
at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl.getProcessMetadata(AdminHelperSSB_wivmoo_EOImpl.java:70)
at com.bea.wli.management.adminhelper.AdminHelperSSB_wivmoo_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:434)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I am suprised about this error, b/c we are running out of a vanilla WLI domain created with the Configuration Wizard and the error message has to do with an internal JMS server that we have left with the default configuration. Has anyone else had success with this?
On a side note, I have to complain about the lack of 9.2 WLI documentation about deploying applications to production. The links on e-docs.bea.com actually redirect you to 8.5 documentation?!? I can't believe that this is the documentation we are left to use for 9.2 because there are so many changes between WLS 8 and 9.Hey buddies,
I have a very similar error on WLI 9.2 MP2 on development mode with a cluster of managed servers on the same machine. I'm afraid that the automatic resource creation feature of dev mode is creating the error.
The ...processes.UnlockService is jpd called by a JMS Broker thru a channel, and I considering it as the first suspect point.
Any help is welcome.
LOG CONTENT:
<May 15, 2008 8:04:57 PM GMT-03:00> <Notice> <Stdout> <000000> <2008-05-15 20:04:57,575 [PERFO] localServer 10.10.10.10 xMDA [iid=15899 prd=TC DATA act=INSTALL otp=I onb=00011552111 cid=12345189 mrt=] END Designar_TCDATA OK>
<May 15, 2008 8:04:57 PM GMT-03:00> <Error> <WLI> <000000> <Exception processing com.oi.integra.provisioning.lockManager.processes.UnlockService
java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator.deployWorkshopQueues(EJBGenerator.java:178)
at com.bea.wli.knex.runtime.core.dispatcher.DispResources.deployQueues(DispResources.java:727)
at com.bea.wli.knex.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:671)
Truncated. see log file for complete stacktrace
java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureQueue(EJBGenerator.java:442)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator.ensureWorkshopQueues(EJBGenerator.java:412)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator$3.run(EJBGenerator.java:194)
Truncated. see log file for complete stacktrace
java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator.doesQueueExist(EJBGenerator.java:359)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator$6.run(EJBGenerator.java:449)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
Truncated. see log file for complete stacktrace
javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getProxy(MBeanHomeImpl.java:68)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:88)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getAdminMBean(MBeanHomeImpl.java:265)
at com.bea.wli.knex.runtime.core.bean.WLSUtil.getWorkshopJMSServer(WLSUtil.java:713)
at com.bea.wli.knex.runtime.core.bean.EJBGenerator$5.run(EJBGenerator.java:372)
Truncated. see log file for complete stacktrace
>
java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: granite_wli_dev:Name=cgJMSServer,Type=JMSServer
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) -
IDM JMX monitoring - Synchronization MBean
Does anyone know how to additionally expose Waveset data using JMX MBeans? In earlier versions of the product (at least 7.0) I thought it provided insight into the synchronization processes currently running within the system, under:
ObjectName=IDM:type=Cluster,service=Synchronization,component=ActiveSync,resType=”<Resource type>”,name=”<resource name>”
However, looking at the documentation for 8.1.1, for example, I only see the following:
From: http://docs.sun.com/app/docs/doc/820-7976/byajd?l=en&a=view
Data Exposed in JMX
So what kind of data does Waveset expose using JMX MBeans? The following table contains a list of MBeans, describes the data they provide, and explains how to use that data.
List of MBeans:
Cluster
Names of the servers in the Waveset cluster, including which servers Waveset considers active.
Provides a quick status of the cluster from the perspective of one Waveset server.
ObjectRepository
Waveset repository configuration data, including database name and version, JDBC driver version, and connection pooling settings
Shows everything you need to know about how Waveset talks to the repository.
Performance
Contains sub-beans for DataExporter, DataQueue, FormConverter, ObjectChangeNotification, Reconcile, Rule, TaskInstanceCache, ViewMaster, and WorkItemCache execution.
Identifies GUI performance problems and provides visibility into how these subsystems perform. You can enable these beans to capture data that can quickly isolate why a particular page loads slowly on a production server.
Scheduler
Internal processing counters for the Scheduler
Provides detailed visibility into what the Scheduler is doing at any given point in time. Making use of this bean requires an in-depth understanding of how the Scheduler works.
Server
Current status of this Waveset server
Shows server status
<resource name>
Operational statistics for each resource and connector used by Waveset.
Shows the count and maximum, minimum, and average time for each resource operation. Gives visibility into the performance of the resource, the Waveset interface, and the Waveset activity on each resource.
Was the ability to monitor ActiveSync taken out sometime between 7.0 and 8.1.1? Is there a way to incorporate this into JMX again? Anything I am missing?
Any additional info would be great.
Thanks again!How is the WebSphere node connected to the cluster? Is it using TCMP? Extend?
Local, Distributed, Replicated, Near, Overflow, External and Optimistic cache statistics appear in the Coherence JMX server. However, near and local caches created on extend nodes do not appear. Therefore the -Dtangosol.coherence.management.remote=true on an Extend client will not register the near or local caches.
Thanks,
Everett -
Getting an exception error when adding a server to a cluster
I am using WL 6.0 and have configured a "Machine", two "Servers" and a
"Cluster", and I want to create two servers on a single machine in order to
test some clustering issues.
I am using the default "myserver" as one of the servers. I have selected
the "machine" that I have configured in the "Machine" section for each of
the servers.
In the ""Cluster Address" of the configured cluster I have typed the comma
seperated list of the IP's of the configured servers and ":7001".
Now when I go to add one server (the default myserver) to the cluster I get
the below error.
Can anyone tell me what might be causing the error.
<Error> <HTTP> <[WebAppServletContext(4344699,cons
ole)] exception raised on '/console/panels/mbean/Cluster.jsp'
java.lang.NullPointerException
at
weblogic.servlet.internal.HttpServer.setServerList(HttpServer.java:25
1)
at weblogic.servlet.internal.HttpServer.getHash(HttpServer.java:270)
at
weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletRes
ponseImpl.java:659)
at
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutput
StreamImpl.java:124)
at
weblogic.servlet.internal.ServletOutputStreamImpl.flushWithCheck(Serv
letOutputStreamImpl.java:451)
at
weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutput
StreamImpl.java:243)
at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:139)
at weblogic.management.console.tags.BaseTag.print(BaseTag.java:118)
at
weblogic.management.console.tags.TabbedDialogTag.printImageTag(Tabbed
DialogTag.java:668)
at
weblogic.management.console.tags.TabbedDialogTag.printTab(TabbedDialo
gTag.java:575)
at
weblogic.management.console.tags.TabbedDialogTag.printStart(TabbedDia
logTag.java:253)
at
weblogic.management.console.tags.TabbedDialogTag.doStartTag(TabbedDia
logTag.java:209)
at
weblogic.management.console.pages._panels._mbean._cluster._jspService
(_cluster.java:670)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:208)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1127)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1529)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
If you send me the config.xml file I can check it out. I don't have any problems
with a comma delimited list.
Cheers,
-- Prasad
John Boyd wrote:
> Thanks for the response, but I meant to say that I have done just the IP's
> and also tried it with ":7001", which is how it is shown in the
> documentation when using a comma seperated list of IP addresses. Either
> way, I am having the problem.
>
> "Prasad Peddada" <[email protected]> wrote in message
> news:[email protected]...
> > John,
> >
> > You don't have to give :7001 for cluster address. Its just ip
> addresses.
> >
> > -- Prasad
> >
> > John Boyd wrote:
> >
> > > I am using WL 6.0 and have configured a "Machine", two "Servers" and a
> > > "Cluster", and I want to create two servers on a single machine in order
> to
> > > test some clustering issues.
> > >
> > > I am using the default "myserver" as one of the servers. I have
> selected
> > > the "machine" that I have configured in the "Machine" section for each
> of
> > > the servers.
> > >
> > > In the ""Cluster Address" of the configured cluster I have typed the
> comma
> > > seperated list of the IP's of the configured servers and ":7001".
> > >
> > > Now when I go to add one server (the default myserver) to the cluster I
> get
> > > the below error.
> > >
> > > Can anyone tell me what might be causing the error.
> > >
> > > <Error> <HTTP> <[WebAppServletContext(4344699,cons
> > > ole)] exception raised on '/console/panels/mbean/Cluster.jsp'
> > > java.lang.NullPointerException
> > > at
> > > weblogic.servlet.internal.HttpServer.setServerList(HttpServer.java:25
> > > 1)
> > > at
> weblogic.servlet.internal.HttpServer.getHash(HttpServer.java:270)
> > > at
> > > weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletRes
> > > ponseImpl.java:659)
> > > at
> > > weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutput
> > > StreamImpl.java:124)
> > > at
> > > weblogic.servlet.internal.ServletOutputStreamImpl.flushWithCheck(Serv
> > > letOutputStreamImpl.java:451)
> > > at
> > > weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutput
> > > StreamImpl.java:243)
> > > at
> weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:139)
> > > at
> weblogic.management.console.tags.BaseTag.print(BaseTag.java:118)
> > > at
> > > weblogic.management.console.tags.TabbedDialogTag.printImageTag(Tabbed
> > > DialogTag.java:668)
> > > at
> > > weblogic.management.console.tags.TabbedDialogTag.printTab(TabbedDialo
> > > gTag.java:575)
> > > at
> > > weblogic.management.console.tags.TabbedDialogTag.printStart(TabbedDia
> > > logTag.java:253)
> > > at
> > > weblogic.management.console.tags.TabbedDialogTag.doStartTag(TabbedDia
> > > logTag.java:209)
> > > at
> > > weblogic.management.console.pages._panels._mbean._cluster._jspService
> > > (_cluster.java:670)
> > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> > > at
> > > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
> > > pl.java:208)
> > > at
> > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
> > > rvletContext.java:1127)
> > > at
> > > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
> > > pl.java:1529)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > > >
> >
Cheers
- Prasad
-
Process Instance shows status as "Running" for days/months
We have a wli proces deployed in cluster environment (WLI 8.1 SP4). The process is timer triggered every day. When we looked at the process monitoring section in wliconsole, we found that there were some process instances triggered a month back still showing the status as "Running". But the process actually ran to completion during those instances.
Is it a known issue? Another note is that the process uses an XA driver pool for querying a database and retrieves records.
Edited by elangosv at 05/01/2007 9:09 AMHi Michael,
thanks for your reply
I already read this note, unfortunately everything is configured correctly so far.
Release Info:
SAP_ABA 700 0008 Cross-Application Component
SAP_BASIS 700 0008 SAP Basis Component
ST-PI 2005_1_700 0002 SAP Solution Tools Plug-In
ST 400 0006 SAP Solution Manager Tool
ST-SER 700_2006_1 0003 SAP SolMan Service Tools
ST-ICO 150_700 0003 SAP Solution Manager
ST-A/PI 01H_CRM500 Application Servicetools for
My Checklist:
- any Server is "checked" (also "only central system...")
- SCOT is configured
- Background dispatcher and central system dispatcher started
- Mail sending from SolMan (CEN) works when testing from SBWP in both clients 003 and 000
I suppose SAP has not realized the problem still exists in Netweaver 2004s
Nevertheless the coding corrections metioned within the note exist in my function method
Can you explain me the interaction between "background dispatcher" and "central system dispatcher" (is there one?) ; or rather the interaction between the "central system disptacher" and "auto reaction methods"...
I couldn´t find sufficient information so far.
Looking forward to your reply.
Dom -
Hello everyone,
Trying to purge ALSB alerts using the WLST script extract found on the [Oracle website|http://blogs.oracle.com/MarkSmith/2008/11/osb_alerts_purging_is_essentia.html] yields the following exception, specifically when attempting to
access the com.bea.wli.monitoring.alert MBean using
alsbAlerts = cmo.getWLDFRuntime().getWLDFAccessRuntime().lookupWLDFDataAccessRuntime('CUSTOM/com.bea.wli.monitoring.alert')
The resulting strack trace looks like this:
Traceback (innermost last):
File "<console>", line 1, in ?
weblogic.management.ManagementException:
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:150)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:95)
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 weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:443)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:377)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:375)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:310)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: weblogic.management.ManagementException: [Diagnostics:320103]There was an error creating the DiagnosticDataRuntimeMBean instance with the given logical name CUSTOM/com.bea.wli.monitoring.alert.
at weblogic.diagnostics.accessor.DiagnosticDataAccessRuntime.createDiagnosticDataAccessRuntime(DiagnosticDataAccessRuntime.java:114)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime$1.run(DiagnosticAccessRuntime.java:145)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:141)
... 32 more
weblogic.management.ManagementException: weblogic.management.ManagementException:
This is using WebLogic Server 10.0 and ALSB 3.0
Any ideas what's going on?
Cheers,
JanAfter reading your mail, I assume that you are using JMS reporting provider bundled with OSB. Please be advised that, the bundled version is not full-pledged reporting provider designed to suit all customer needs/use case. More of a bare bones version.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/wwimages/reporting_framework.gif--- Will give you better clarity on the architecture. ReportingDataManager is not designed to hold statistics. So OSB will cannot expose any JMX API.
The data/statistics showed in sbconsole are directly picked from Database http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/wwimages/jms_reporting_provider.gif .
So if you wan to purge the details programatically then only option avaialble are
1) JDBC program to delete records from TABLES WLI_QS_REPORT_ATTRIBUTE,WLI_QS_REPORT_DATA (not recommended as reporting provider internal working is not in pubic domain. Said that it would not take much time to understand how report data is stored in the above tables).
2) Write a custom reporting provider which will have capability you are looking. http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/javadoc/index.html (easiest way)
Let me know if you need any clarification on the above.
Thanks
Manoj
Edited by: mneelapu on Apr 24, 2009 2:27 PM -
WLI 8.1SP2 Cluster over 2 Physical Machines Errs on Managed Svrs on 2nd mac
I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
Listen Address informatica-svr:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]
at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]>I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
Listen Address informatica-svr:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]
at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]> -
Deploying with Workshop to a WLI cluster
Hello!
I have a WLI 8.1 cluster running ok on server enviroment.
My WLS Workshop is installed on my workstation were Workflow developing will be
done.
I need Workshop to be able to deploy to the cluster and not to a particular managed
server, like the Tools-Weblogic Server-Server Properties... option only lets me
configure. The ServerHomeDirectory text box assumes a local WLI domain directory.
Mine is in another server on the network.
Please help
RicardoRicardo,
The Workshop IDE supports development in a single server environment. You
can point the IDE to a single WebLogic server instance. After you have
completed the development, you can create an EAR for the Workshop
application and deploy it on a cluster.
Please refer to the Workshop documentation section
How Do I > Deployment and Administration
for further details.
Regards,
Anurag
"Ricardo Madariaga" <[email protected]> wrote in message
news:3f832855$[email protected]..
>
Hello!
I have a WLI 8.1 cluster running ok on server enviroment.
My WLS Workshop is installed on my workstation were Workflow developingwill be
done.
I need Workshop to be able to deploy to the cluster and not to aparticular managed
server, like the Tools-Weblogic Server-Server Properties... option onlylets me
configure. The ServerHomeDirectory text box assumes a local WLI domaindirectory.
Mine is in another server on the network.
Please help
Ricardo -
Problems with Deploying WLI Tutorial App to a cluster
I'm using Weblogic 8.1 SP3 and have built the app (steps 1-5) listed below:
Tutorial
The app works fine in Workshop and even works fine deployed to a simple one-server WLI configuration once the 2 JMS Queus and required db tables are created manually. The problem is in deploying to a cluster. No error messages are generated but when loading the test page (http://localhost:8001/Tutorial_Process_ApplicationWeb/requestquote/RequestQuote.jpd?.EXPLORE=.TEST
) I do not get the same results as when loading in the single server setting (Note the port number is the port that my clustered managed server is running on). Basically the multi-tab page that loads in the one-server scenario only comes up as one tab - the Overview tab. None of the other tabs allowing you to test the web services are available.
I tried to cheat it by saving the SOAP test page from the working version and posting the form to the non-working version - but all that was returned was the Overview page. I suspect the issue is JTX-related but I am new the Weblogic so I'm somewhat lost.
Any help appreciated. I can be reached at [email protected]I am getting the following output from the Admin Server when I attempt to access the JPD process:
<19-Nov-2004 13:58:56 o'clock GMT> <Error> <JTA> <BEA-110412> <Xid=BEA1-0046F2A8360F0D4CF282(73146307),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=500,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=cgServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@429b2ce,re-Registered = false),SCInfo[integration-cluster-xa-changed+cgServer]=(state=committed)) completed heuristically: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: No connection associated with xid = BEA1-0046F2A8360F0D4CF282-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C)) -
Hi,
I would like to configure a WLI Server programmatically by creating JMSEventGenerators using the WLI MBeans.
I use the following code after getting the administration MBeanhome interface to find or create a JMSEventGenConfiguration MBean
home.findOrCreateAdminMBean("MyJMSEventGen", "JMSEventGenConfiguration");
The call does not succeed but throws the following exception:
java.lang.ClassNotFoundException: weblogic.management.configuration.JMSEventGenConfigurationMBean
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at weblogic.management.internal.TypesHelper.findClass(TypesHelper.java:477)
at weblogic.management.internal.TypesHelper.getAdminOrConfigMBeanInfo(TypesHelper.java:383)
at weblogic.management.internal.ConfigurationMBeanImpl.<init>(ConfigurationMBeanImpl.java:137)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at weblogic.management.internal.Helper.createMBean(Helper.java:1152)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:483)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBeanServerImpl.java:707)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:588)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHomeImpl.java:856)
at weblogic.management.internal.MBeanHomeImpl.findOrCreateAdminMBean(MBeanHomeImpl.java:683)
at weblogic.management.internal.MBeanHomeImpl.findOrCreateAdminMBean(MBeanHomeImpl.java:653)
at weblogic.management.internal.AdminMBeanHomeImpl.findOrCreateAdminMBean(AdminMBeanHomeImpl.java:912)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
That's of course the truth. There is no class with a FQCN: weblogic.management.configuration.JMSEventGenConfigurationMBean
So I tried to pass the FQCN to the method and I received the following error message:
java.lang.ClassNotFoundException: weblogic.management.configuration.com.bea.wli.management.configuration.JMSEventGenConfigurationMBean
It seems weblogic is always prepending "weblogic.management.configuration" to the classname of configuration MBeans (that's what the documentation says).
I have also tried to create the MBean via WLST and weblogic.ADMIN tool but had no success.
Below is a sample of a call of the weblogic.ADMIN tool to create the MBean:
java weblogic.Admin -adminurl localhost:7001 -username weblogic -password weblogic CREATE -mbean
integration:Name=myTestConfig -type JMSEventGenConfiguration
It doesn't work with FQCN either. The tool does not throw any exceptions nor does it write any other messages to the screen.
It simply quits.
Is there a way to solve this problem?
Environment:
Win XP
BEA WebLogic Integration 8.5
WLS 8.1
Thanks in advance
Ralftry using custom() after you connect WLI instance
e.g. connect(.......)
custom()
ls()
This may help you I think. -
Accessing the MBean for ProcessRuntime(WLI) through WLST
Since the cmo is not available for Custom MBeans and WLI MBeans are custom, how can I access or execute the methods for the MBean from WLST. I guess I can probably do it with the invoke command but the sytax foroperation invocation is not that intuitive. Is there another way i can access the ProcessRuntime Bean and invoke the methods directly.
Thanks.Marc,
This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
This section of the doc seems to walk through an example setting properties in adf-config.xml
I would interpret those instructions in the official doc to mean :
1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
(This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
Now comes the conflicting parts :
"If you must modify these properties, post deployment, you must edit adf-config.xml manually."
I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
So if we :
set the timeout to 1 minute initially at design time,
then change that to 5 minutes through WLST,
and then edit adf-config again in Jdev to a 10 minute value and redeploy,
the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
MDS documents are always applied on top of the deployed stuff.
The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
does make a good explanation of how the changes persisted in MDS affects the final configuration.
Hop that helps ! -
Using the App Server DAS to access "my" MBeans on cluster servers
I am wanting to use JMX to access some custom MBeans that are on server instances that are participating in app server clusters. I figured the way to do this is by connecting to the DAS, but the service groups don't show within the DAS (like when using JConsole), I can access other AMX services, but not my custom ones. I can access my MBeans if I directly connect to the app servers.
Any ideas? I am trying to keep my jmx client from having to know physical location of the clustered servers, and only knowing about the DAS.
Thanks,
ScottHi,
I am not an Application Server expert so I won't be able to answer your question
directly - but maybe the article 'Managing and Monitoring Web Services in
Project GlassFish' could be of help:
http://developers.sun.com/prodtech/appserver/reference/techart/ws_mgmt.html
There's also the doc on docs.sun.com which you may already know:
Chapter 20 Using the Application Server Management Extensions
http://docs.sun.com/app/docs/doc/819-3659/6n5s6m5ck?a=view
If you still don't get your answer - you may also want to visit the glassfish project:
https://glassfish.dev.java.net/ (perhaps join its user's mailing list?)
or The Aquarium: http://blogs.sun.com/theaquarium which has lots of interesting
tips and articles.
Hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/roller/page/jmxetc -
Java.io.EOFException while deploying RPD in OBIEE Cluster using Mbean
I am using oracle.biee.admin:type=BIDomain.BIInstance.ServerConfiguration,biInstance=coreapplication,group=Service to deploy RPD on a clustered environment with 3 servers, I get the following error, it works fine on a single host, any clue ?
Connecting using URL: service:jmx:t3://xxxxxxx/jndi/weblogic.management.mbeanservers.domainruntime ...
Transaction addAvayaRepository failed with error: ; nested exception is:
java.io.EOFException, review log to fix issue and re-execute.
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1017)
at com.avaya.reporting.bi.config.MBeanTransaction.invoke(MBeanTransaction.java:374)
at com.avaya.reporting.bi.config.MBeanTransaction.invoke(MBeanTransaction.java:349)
at com.avaya.reporting.bi.config.MBeanTransaction.doDomainCall(MBeanTransaction.java:314)
at com.avaya.reporting.bi.config.MBeanTransaction.lockDomain(MBeanTransaction.java:290)
at com.avaya.reporting.bi.config.MBeanTransaction.execute(MBeanTransaction.java:200)
at com.avaya.reporting.bi.config.MBeanConfigExecutor.execute(MBeanConfigExecutor.java:147)
at com.avaya.reporting.bi.config.RunBIConfig.runXmlTransaction(RunBIConfig.java:127)
at com.avaya.reporting.bi.config.RunBIConfig.runConfig(RunBIConfig.java:99)
at com.avaya.reporting.bi.config.RunBIConfig.main(RunBIConfig.java:84)
Caused by: java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:827)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:761)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:958)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:889)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:339)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)Thanks for your replies !!
In any of the RPD deployments I'm getting the same error , not for some particular RPD .
FYI , yesterday (before this issue) I had a issue with starting presentation services , so as adviced in forum I replaced the files sawguidstate and sawguidstate.atrin the location:
<Instance_Home>\instances\<instance_name>\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\<project>\root\system\mktgcache\<name>
with the same files from a backup or from another working OBIEE 11g (11.1.5)instance.
plese refer : Re: Unable to start presentation services , in OBIEE 11g
Is this causing the deployment issue ? -
Weblogic Integration failed to build Cluster ENV
Dear buddies,
I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
Here is the process how I created WLI cluster:
ENV:RedHat9+ WL8.1_SP4
Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
BEA_HOME=/opt/bea/
1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
and I didn't create extra JDBC POOL except the standard one.
2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
Now I am having following problem.
1.admin Server(cgServer) can startup without any problem
2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
but seems the pointbase only listen 9092!!
4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
below are detailed output when I startManagedServers:
command:
[root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
Listen Address 172.16.4.236:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.
-
Targeting ALSB and WLI components
Hello!
I'm using ALINT 3.0 + ALDSP 3.2 platforms in my project. I would like, my domain, to contain three clusters: one for ALSB and WLI services (ALSB cluster), one for ALDSP services (ALDSP cluster) and one for J2EE components (J2EE cluster). When I create everything from wizard, then all components related to ALSB and ALDSP are targeted everywhere. So, I have the following questions:
1. Is there any specification, which component should be targeted to ALSB cluster and which should be targeted to ALDSP cluster.
2. Which component of ALSB is responsible for targeting ALSB services. I mean, I don't want my services to be accessible from each cluster, just from ALSB cluster.
3. Most components, after creating domain from wizard, are targeted to AdminServer as well. Which components should really be targeted there? And which components can only be accessible from clusters.
4. Is there a really quick method of targeting a big number of ALSB and WLI components? Doing it from admin console is terribly time consuming. Of course I can edit config.xml manually, but do you have any less risky tool?
5. Is such a configuration supported and recommended by BEA/Oracle? I would like to avoid an effort related to configuring trust and security between domains so I prefer to do it all in one domain.1, 2, 3. Run the wizard separately for ALINT, ALDSP and ALSB. When you are creating/adding to a domain, you can select the option to target bits to specific places.
4. If you want 'fast' edit config.xml. If you want 'less-risky', use the Admin Console. If you want something in between, you can write a utility using the MBean api. (you can explore the MBean api using wlst). If you want Oracle/BEA to write it for you, open a Customer Support Case/Enhancement request.
5. I don't see why it wouldn't work.
Maybe you are looking for
-
Computer not reading ipod at all
i bought my nano like a month ago... i connected my nano to the computer and all the songs went on it... a week later though i got a message saying i needed to upgrade so i did and in the middle of the upgrading process it froze and all my songs were
-
Can I use a Konica Minolta PagePro with my IMac?
I am a new IMac owner and would love to use this printer (already have it) - is it possible? The manufacturer does not have a work around for it to work with Macs. TIA
-
Weblogic configuration wizard is not displaying correctly on windows 7
Please check the image attached. link . I only see buttons and check boxes, no text in it. It is only happening for oracle wizards. Other apps are working okay. This is on windows 7, virtual machine access via VM Player.
-
Duplicate files in itunes music folder with title 1.mp3
Can anyone tell me why there might be duplicate files with this number in my music folder? I'm interested to know what might cause this to happen.
-
I just finished a talking head video for a client. He says that the audio is not synched with the video. I click on the same link and it is fine for me. Any ideas as to why the difference? Here's the link http://sa.uldev.co/ Let me know if you have a