Deploying in cluster env
HI,
we have a clustered env for our production system. i defined a track and set up the runtime systems. since our production box is a clustered environoment, i specified the SDM hostname as the host on which the central instance is running.
so when i try to transport, until QA everything is fine (as they are non - clustered), but while trying to import particluar assembly to production, the error shown in deploy log is
Error: An error occured while starting a cluster instance.
Error: There is no control instance running in the cluster:
Name:JM_T1137182930718_hostname |Host:hostname |State:5|
Info:|Name:JC_hostname |Host:hostname |State:5|
Info:Please check if there are running cluster instances.
do i need to configure something in SDM of our central instance?
please help us.
Thanks
This sounds like a bug to me. I'd suggest you contact [email protected]
-- Rob
Lars M wrote:
We are running WL 8.1 SP2
When the administration server is running, our ear is deployed to a cluster (2
managed instances on 2 different nodes) using stage mode, and everything is fine.
The problem:
Afterwards, if we try to start a managed server when the administraion server
is down, the managed server cannot activate the deployed application. It reports
that the application path is invalid.
The application path stored in the config.xml (and msi-config.xml) is the upload
path of the administration server (e.g. DOMAIN_HOME/adminserver/upload/OurApp.ear)
- and of course this path is only available on the node where the admin server
is running - and NOT on another hw node where the managed server is running.
Why is the managed server trying to open the original "source" application?
Especially when the application is staged?
Thanks
Lars
Similar Messages
-
ANT deployment in cluster env - urgent pls
All,
version: 10g(10.1.3.4)
We have set up 10g in cluster env. I tried to deploy a bpel thru ANT got the below error
A problem occurred while establishing a connection to the BPEL Server.
Please make sure the server is running on host "localhost", port "7777".
The same bpel, when I tried to deploy thru JDev it deployed succesfully! What could be the possible reason? Also, the same bpel deployed thru ANT successfully in non-cluster env
thanks,
sen1.Go to the particular composite and create folder build.
2. Place build.properties and build.xml files inside the folder.
3. Generate configuration plan on right clicking composite.xml.
4. Open build.properties file and cross check the following elements
composite.name=Process (particular composite name)
composite.revision=1.0 (version)
oracle.home=C:/Oracle/Middleware/jdeveloper ( middleware home)
soa.server.oracle.home=C:/Oracle/Middleware/jdeveloper
admin.server.host=test.checf.com (admin server host)
admin.server.port=7007 (admin server port)
server.domain.name=SOADEV (soa domain)
managed.server.host=soa.test.com (soa server host)
managed.server.port=8007 (soa server port)
server.user=weblogic (user credential)
server.password=soadev123 (server passwd)
java.home.set=D:/jdk160_18 (jdk path)
server.targets=WLS_SOA2 (target node)
config.plan=Process_cfgplan_17.xml (compiste config plan)
5.Open build.xml file check the following
<project name="rProcess " default="deploy" basedir="."> (check the project name)
Commands from cmd
1. Go to the cmd.
2. Set the following variables in cmd.
C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set ORACLE_HOME=C:\Oracle\Middleware
C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set ANT_HOME=%ORACLE_HOME%\jdeveloper\ant
C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set PATH=%ANT_HOME%\bin;%PATH%
C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>set JAVA_HOME=D:\jdk160_18
3. Go the particular composite build folder
Bpel Process
|-> SOA Content
|->build
4. Give ant command
C:\JDeveloper\mywork\CommonErrorHandlingApplication\ASYNCTesting\build>ant
check the same whther it helps u or not -
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.
-
Issue with LCM while migrating planning application in the cluster Env.
Hi,
Having issues with LCM while migrating the planning application in the cluster Env. In LCM we get below error and the application is up and running. Please let me know if anyone else has faced the same issue before in cluster environment. We have done migration using LCM on the single server and it works fine. It just that the cluster environment is an issue.
Error on Shared Service screen:
Post execution failed for - WebPlugin.importArtifacts.doImport. Unable to connect to "ApplicationName", ensure that the application is up and running.
Error on network:
“java.net.SocketTimeoutException: Read timed out”
ERROR - Zip error. The exception is -
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)Hi,
First of all, if your environment for source and target are same then you will have all the users and groups in shared services, in that case you just have to provision the users for this new application so that your security will get migrated when you migrate the from the source application. If the environs are different, then you have to migrate the users and groups first and provision them before importing the security using LCM.
Coming back to the process of importing the artifacts in the target application using LCM, you have to place the migrated file in the @admin native directory in Oracle/Middleware/epmsystem1.
Open shared services console->File system and you will see the your file name under that.
Select the file and you will see all your exported artifacts. Select all if you want to do complete migration to target.
Follow the steps, select the target application to which you want to migrate and execute migration.
Open the application and you will see all your artifacts migrated to the target.
If you face any error during migration it will be seen in the migration report..
Thanks,
Sourabh -
HAFileAdapter based OSB processing 1st file twice in 2 node cluster env
Hi,
I am trying my hands in OSB with HA File Adapter and came across a strange issue where in OSB service designed to pick up a message of "*.CSV" format and process it's record one at a time recursively as per below details:
The reason I am saying it's been processed by 2 nodes of the cluster independently is because I can see 2 separate threads picking up same file at the same time on both the nodes in log files. I enabled the debugging property on managed servers.
----------------------------------------------------- Start Log Snippet -----------------------------------------------------
Node 1 : ExecuteThread: '51'
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Translated inbound batch index "1" of fil
e {CCISU_500.csv} sucessfully.>
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Publisher::publishMessage called with prim
aryKey=[Qz6n0UOYTQ1oJ2QeawJThlv-jKbiLeH1Bkko5wHl1Lg.]>
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Sending batch to Adapter Framework for pos
ting to BPEL engine: {
batchId=_-H9OvOxmH30ZcxGkXWAK8mVTcajl3SHsnnVKxfsEBU., batchIndex=1, publishSize=1
}>
####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699920> <BEA-000000> <Copying file :/FileAdapters/Input/CCISU_500.csv to user-defined archive directory for processed files :/FileAdapters/Archive>
####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting/Soft deleting file : /FileAdapters/Input/CCISU_500.csv>
####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting file : CCISU_500.csv>
####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Deleted file : true>
####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Poller has reached max raise size, will not raise anymore>
Node 2 : ExecuteThread: '53'
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Translated inbound batch index "1" of file
{CCISU_500.csv} sucessfully.>
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Publisher::publishMessage called with prima
ryKey=[ODfzwSUr85GeHkzscyhXrh2URW1FEAposlikUkdTZL8.]>
####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Sending batch to Adapter Framework for post
ing to BPEL engine: {
batchId=ZkZ5HZA43QtsPZFqU2prPmxVS83NBMHcZa5n76yKC-Q., batchIndex=1, publishSize=1
}>
####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Def
ault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700939> <BEA-000000> <Since file could not be copied to specifi
ed archive directory, file : CCISU_500.csv_CbOXCcnMsRq44Slx2jiJrbM5vvgER0M_cYJsXlmvzWU= is being copied to a default archive directory :/oracle/ofmw3u/admin/ofmw3u_doma
in/mserver/ofmw3u_domain/fileftp/defaultArchive/>
####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.De
fault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <Endpoint will shutdown process to preven
t data loss as file :CCISU_500.csv could not be being copied to default archive : /oracle/ofmw3u/admin/ofmw3u_domain/mserver/ofmw3u_domain/fileftp/defaultArchive/. Plea
se ensure that there is enough free space available to copy this file.
java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or direct
ory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:120)
at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <ProcessWork::run Fatal exception caught
java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:120)
at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Processer thread calling onFatalError with exception [java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)]>
####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Unable to call onFatalError since the adapter could not find an endpoint>
####<Oct 17, 2012 3:21:40 PM EST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Poller::processFilesInSameThread will abort as the endpoint has been released>
----------------------------------------------------- End Log Snippet -----------------------------------------------------
----------------------------------------------------- Start Questions to the Gurus Out There -----------------------------------------------------
1. Is there any property to make sure that only one activation agent is active at anytime in a cluster env ?
2. Does JCA property "<property name="SingleThreadModel" value="true"/> holds good when used in OSB ? or it's just supported in composite ??
3. Does both the nodes of cluster polls independently ? As I have seen in logs that node1 polling and complaining about time to live factor while the other node picking it before node1 completes another cycle of polling.
4. In above log you can see that node1 processed all the records 1sec earlier than node2 in a race condition and as a result node2 completed about file not found exception?
Gurus any help will be appriciated.
----------------------------------------------------- End Questions to the Gurus Out There -----------------------------------------------------
----------------------------------------------------- Start Details -----------------------------------------------------
Protocol : jca
Endpoint URI : jca://eis/FileAdapter
Get All Headers : No Headers
JCA: <adapter-config name="RequestHandler" adapter="File Adapter" wsdlLocation="RequestHandler.wsdl"; xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/HAFileAdapter" UIincludeWildcard="*.csv"/>
<endpoint-activation portType="Read_ptt" operation="Read">
<activation-spec className="oracle.tip.adapter.file.inbound.ScalableFileActivationSpec";>
<property name="DeleteFile" value="true"/>
<property name="MinimumAge" value="120"/>
<property name="PhysicalDirectory" value="/FileAdapters/Input"/>
<property name="PhysicalArchiveDirectory" value="/FileAdapters/Archive"/>
<property name="PhysicalErrorArchiveDirectory" value="/FileAdapters/Error"/>
<property name="Recursive" value="true"/>
<property name="PublishSize" value="1"/>
<property name="PollingFrequency" value="300"/>
<property name="MaxRaiseSize" value="1"/>
<property name="SingleThreadModel" value="true"/>
<property name="IncludeFiles" value=".*\.csv"/>
<property name="UseHeaders" value="false"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
----------------------------------------------------- End Detail -----------------------------------------------------
Edited by: 964320 on Oct 17, 2012 10:58 PMYou need to define the below property in composite.xml file of your bpel. This will allow only one adapter active and another passive to pick up the file.
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PickupFile/FTPConsumer">
*<property name="clusterGroupId">BPELProcessNameCluster</property>*
<property name="portType">FTP/FileConsumer_Message_ptt</property>
</activationAgent>
</activationAgents>
Thanks,
Vijay -
WLS6sp2 Hot deployment in cluster does not work
I have two WLS6sp2 servers in cluster in two different machines. There is an EJB
deployed in the cluster that works fine. Now I go to the console and I undeploy
it: the servers show a message of "ejb undeployed". Now I activate the "deploy"
checkbox again: the following error appears:
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exception
is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
stub to a name that is currently bound to a replica-aware stub; remaining name
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
stub to a name that is currently bound to a replica-aware stub; remaining name
The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
It has been deployed to the cluster target. When is working it is load balanced
between both servers. It deploys perfectly when starting up both servers, but
hot deployment does not work.
This works fine when only one server is up.
¿Is not possible to do hot deployment in cluster?
Hm, where are you seeing the javax.naming.NameAlreadyBoundException? In one of your managed
servers, in all of your managed server, or in your admin server?
If you see this in your admin server, then this means you got your admin joined in the cluster,
which is not good. Remove it from the cluster if this is so.
Gene
"David Agudo" <[email protected]> wrote in message news:[email protected]...
>
> Yes, target="mycluster".
>
> "Gene Chuang" <[email protected]> wrote:
> >Did you target the ejb to the cluster, or to each individual Node in
> >your cluster? There is a
> >difference...
> >
> >Gene
> >
> >"David Agudo" <[email protected]> wrote in message news:[email protected]...
> >>
> >> I have two WLS6sp2 servers in cluster in two different machines. There
> >is an EJB
> >> deployed in the cluster that works fine. Now I go to the console and
> >I undeploy
> >> it: the servers show a message of "ejb undeployed". Now I activate
> >the "deploy"
> >> checkbox again: the following error appears:
> >>
> >> weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB;
> >nested exception
> >> is:
> >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> >replica-aware
> >> stub to a name that is currently bound to a replica-aware stub; remaining
> >name
> >> ''
> >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> >replica-aware
> >> stub to a name that is currently bound to a replica-aware stub; remaining
> >name
> >> ''
> >>
> >> The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
> >> It has been deployed to the cluster target. When is working it is load
> >balanced
> >> between both servers. It deploys perfectly when starting up both servers,
> >but
> >> hot deployment does not work.
> >>
> >> This works fine when only one server is up.
> >>
> >> ¿Is not possible to do hot deployment in cluster?
> >>
> >
> >
>
-
Get weblogic instance name in cluster env.
Hi, there, how can I get each weblogic instance name in cluster env. in my code?
thanks.
If you want the current instance name, it is 'weblogic.Name' I think. If you
want a list of all instances in the cluster, you can probably find it by browsing
WebLogic MBeans.
black <[email protected]> wrote:
> Hi, there, how can I get each weblogic instance name in cluster env. in my code?
> thanks.
Dimitri
-
How to deploy WebLogic Cluster on a Blade?
Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far.It sounds like you're getting request routing and fail-over in front of
WLS with the Big-IP. Typically people would enable WLS clustering to
get replicated HTTP sessions in an environment like this.
-- Rob
Michael Poulin wrote:
Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far. -
Set up cluster env in obiee11g
Hi,
How to set up cluster env in obiee 11g env
thanks
Edited by: 896398 on Jan 23, 2012 1:24 AMHi,
In OBIEE 11g, clustering is enabled by default during installation. There are only one instance of BI Server in the cluster though initially. Now, scaling of BI components(increasing the number of instances) is possible at two levels.
1. Vertical scaling : Increasing the number of instances of various BI Components running in the same system. Yes, say we can increase the BI Server instances to 2 and notice that there are two nqserver.exe processes.
2. Horizontal Scaling: The BI instances can be run on a different system and be a part of the same cluster.
You can notice the same thing in EM -> Business Intelligence -> Core Application -> Capacity Management -> Scalability tab
Hope this helps.
Thank you,
Dhar -
HI,
we have a clustered env for our production system. I am trying to deploy an SDA file from SDM of central instance. I am getting the following error.
Error: An error occured while starting a cluster instance.
Error: There is no control instance running in the cluster:
Name:JM_T1137182930718_hostname |Host:hostname |State:5|
Info:|Name:JC_hostname |Host:hostname |State:5|
Info:Please check if there are running cluster instances.
do i need to configure something in sdm of our central instance?
please help us.
Thank youAs per the previous message, it should work if the
cluster is installed correctly.
With a clustered installation the SCS (SAP Central
Services) would be installed using a virtual hostname.
Later when the Central instance is installed it must
refer to this logical hostname for the SCS.
My guess is that SDM is using the hostname of the CI
instead of the SCS logical hostname.
When you installed the Central Instance, did you use
the HA instructions for installing a Central Instance ?
regards
Tom -
Problem with weblogic.deploy and cluster
I'm having some problems with the weblogic.deploy class when trying to refresh
a jsp file. Using the following command to redeploy the entire application works
fine:
java weblogic.deploy -port 9876 -host apptest01 update
administrator portal c:\portal-site
However using the following command to refresh just one jsp
file:
java weblogic.deploy -url t3://apptest01:9876 -username system
-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
refresh administrator portal
produces the following stack trace:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
remaining name ''
at weblogic.rmi.internal.BasicOutboundRequest.
sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:255)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.
lookup(WLContextImpl.java:323)
at weblogic.management.tools.WebAppComponentRefreshTool.
getMBeanHomeForManagedServer
WebAppComponentRefreshTool.java:498)
at weblogic.management.tools.
WebAppComponentRefreshTool.
getComponentMBeanForServer
(WebAppComponentRefreshTool.java:225)
at weblogic.management.tools.
WebAppComponentRefreshTool.findInternalPaths
(WebAppComponentRefreshTool.java:187)
at weblogic.management.tools.WebAppComponentRefreshTool.
refresh(WebAppComponentRefreshTool.java:151)
at weblogic.deploy.refresh(deploy.java:704)
at weblogic.deploy.runBody(deploy.java:374)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.deploy.main(deploy.java:1601)
Unable to resolve weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
Any ideas?
"John Murphy" <[email protected]> wrote:
>
>I'm having some problems with the weblogic.deploy class when trying to
>refresh
>a jsp file. Using the following command to redeploy the entire application
>works
>fine:
>
>java weblogic.deploy -port 9876 -host apptest01 update
>administrator portal c:\portal-site
>
>However using the following command to refresh just one jsp
>file:
>
>java weblogic.deploy -url t3://apptest01:9876 -username system
>-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
>refresh administrator portal
>
>produces the following stack trace:
>
>javax.naming.NameNotFoundException: Unable to resolve
>weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
>remaining name ''
> at weblogic.rmi.internal.BasicOutboundRequest.
> sendReceive(BasicOutboundRequest.java:85)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:255)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:222)
> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
> at $Proxy0.lookup(Unknown Source)
> at weblogic.jndi.internal.WLContextImpl.
> lookup(WLContextImpl.java:323)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> getMBeanHomeForManagedServer
> WebAppComponentRefreshTool.java:498)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.
> getComponentMBeanForServer
> (WebAppComponentRefreshTool.java:225)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.findInternalPaths
> (WebAppComponentRefreshTool.java:187)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> refresh(WebAppComponentRefreshTool.java:151)
> at weblogic.deploy.refresh(deploy.java:704)
> at weblogic.deploy.runBody(deploy.java:374)
> at weblogic.utils.compiler.Tool.run(Tool.java:79)
> at weblogic.deploy.main(deploy.java:1601)
>Unable to resolve weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
>
>Any ideas?
>
Hi John,
How's tricks?
It looks to me as though the olbcluster JNDI reference isn't being resolved from
the tree. A similar error results when a Connection Pool cannot be resolved, the
JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
it often turns out to be an error in the correlation between the deployment descriptors,
settings applied via the console and references made in the code.
That's my tuppence worth,
James :-)
-
Shutdown class in cluster env.
I have a shutdown class that basically cleans up some data from
database. In clustering env., obviously, I don't
want the cleanup to happen unless all my WL servers in the cluster are
shutdown, can someone tell me how can
I achieve this? thanks
Xiaodong
Startup/Shutdown Class will be available in 9.0.4.
However you can use a work around in 9.0.2/9.0.3 to simulate the Startup/Shutdown class:
Following are the steps required to achieve this functionality:
1) Write and compile your startup class as an application client. This class must contain a main method that will be called by OC4J during startup.
2) Create a META-INF/Manifest.mf file for the application-client, for example
Manifest-Version: 1.0
Main-Class: Oracle9iASStartup
3) Create a deployment descriptor for the application client as follows:
<application-client>
<display-name>Oracle9iASStartup</display-name>
</application-client>
4) Create the application-client jar file for your startup class with the above Manifest and deployment descriptor.
5) Create an EAR file for the application-client module with the an OC4J-specific deployment descriptor orion-application.xml as follows:
<orion-application>
<client-module path="startup-class-client.jar" auto-start="true" user="anonymous" />
</orion-application>
Build your EAR and deploy your application with auto-start set to "true". -
Error during application deployment in cluster
Hi All,
I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
Any pointers are greatly appreciated.
Thanks
--shashi
Here is the error log:
D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
D:\apps\bea\user_projects\domains\nclusterdomain>echo off
CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
.4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
Sun Microsystems Inc.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
k if there exists a running admin server at this URL.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
the initial configuration.>
<Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
SR.log is opened. All server side log events will be written to this file.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
<Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
Production Mode>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 28 more
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
java.net.ConnectException: Connection refused: connect; No available router to destination]]
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?
-
JNDI conflict for WTC in cluster env
I found this error when starting more than one managed server in clustered environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.40 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.41 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
Please help.Hi Salim,
Salim Djaffar wrote:
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
Salim Djaffar wrote:
I have a stateless ejb using this context to get the same JNDI namefrom tuxedo
connection factory. This ejb is deployed as clustered. I deployed thisejb into
many managed servers in the cluster. In other word every managed serverdeploys
this ejb.
I also have the web server configured with clustered plugin, but Iguess it has
nothing to do with it.
Isn't the wtc_config.xml stanza "WlsClusterName" a little misleadingsince it
does not support cluster at all ?Yes, it is kind of misleading. It is not used in WTC and will be removed
from dtd
(and document) in the future.
Besides in the admin console, I configured the WTC startup target to"cluster".
Is there any advise to overcome this problem ?I can't think of a good way to overcome this problem. One thing you
can do is to
target WTC to a WLS in the cluster. One drawback is that you have only
one WTC in
the cluster.
Honghsi
Does it mean I have to use RMI/IIOP to do the lookup to one particular server
for WTC ?No. The RMI/IIOP lookup is specific for CORBA NS lookup. It won't help you at
all.
>
Will WTC be available for clustered in the future ?There will be some changes to WTC that will make it possible for you to deploy WTC
instance on every WL server in the cluster. There are some administration (and
configuration) restrictions associate with it if you want to be able to do load
balancing and fail over.
Hong-Hsi :-)
>
>
Thanks.
Please help.
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
The current version of WTC will have this problem. Because the connection
factory is bound
to the same name in JNDI tre. However, the first WTC booted in the
WLS
cluster should
still be available to use.
BTW, I am interested in knowing how you use WTC currently, and howyou
plan to use in the
future.
Honghsi
Salim Djaffar wrote:
I found this error when starting more than one managed server in
clustered
environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.40 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.41 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
Please help. -
Web modules don't get deployed to cluster instance directory
Hi,
I have a domain with one cluster, which has one instance. Sometimes (!), the web aplications I deploy don't get unpacked in the directory {instanceRoot}/applications/j2ee-modules but only in {domainRoot}/applications/j2ee-modules. When that happens, they don't work and I cannot access them through their URL.
I deploy them using the web admin console, enable the to the cluster in question. Everything goes ok (or at least the UI says so) and in the domain.xml I have this:
<web-module availability-enabled="false" context-root="/myapp" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/myapp" name="myapp" object-type="user"/>
<server...
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
<cluster...
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
In both the apps the were copied to the instance applications dir and in the ones that remained only in the domain applications dir (and do not work). In the latter, the location dir does not exist.
Anyone has gone through any similar situation? This deployment process is a bit confusing for me, wrt instances, clusters, domains etc.
Thanks!
Jo�o.Thanks for the answer.
But how is this mechanism controlled? Sometimes, the domain just doesn't seem to propagate the changes to the cluster instances (or stand-alone instances). For example, sometimes when I change a property of a data source through the admin gui of the domain, it does not get propagated to the desired instance config, even after restarting the whole system.
I think that it may have something to do with the manual changes that I have to do sometimes in the domain.xml file (this is neede when you have huge config changes to be replicated in many servers).
Is there any option to enforce the replication of the config from the domain to the instances? Or at least to make it verbose so that I can realize what is going on underneath.
Thanks.
Maybe you are looking for
-
I have tried to re-install iTunes 11.0.3 at least 6 times. I have also downloaded iTunes 11.0.3 at least 5 times. I have changed my Apple ID password. I have downloaded (again, I've done that many times) iTunes 11.0.3, then I switched off the iMac, t
-
Procedure with Array IN parameter
Hi, I have requirement to create a procedure that accepts an Array as IN parameter , Query a table using this array and return the result as refcursor . please suggest the best approach . i tried to get it as below but not working . CREATE OR REPLACE
-
Create trace file on specific location
Hi all, I'm working with a 11gR2 Enterprise DB on Linux RedHat 5 Now I need to create a trace file. This trace will be huge and I need to create it on an specific folder on my system because the udump fs could be small for it. These are the commands
-
hi, how can i acheive running total functionality in discoverer..i want to sum row1 with row2 then result sum with row3 and so on.my giving example below: jan 1 1 feb 3 4 mar 4 8 apr 5 13..so on ,third col is runnig total col.. so if any one has solu
-
Spotlight Using Wrong Date .... And Changing It
Apologies in advance, as I know someone else must have already written about this and my cursory search didn't locate it. Searching for email messages containing specific text, and Spotlight does this well. Shift to the Show All window, allowing me t