Unmanaged Servers in WLS 10?
Hi all,
I'm in the very early stages of developing a new web application. My company currently has several applications running on WLS 8.1, and we're using this new application as a proof-of-concept for upgrading to WLS 10.
My development box is running XP SP2.
I want to set up a server instance in WLS 10 that runs without a node manager. I used the Configuration Wizard to create my domain, and I run the startWebLogic.cmd script in the user_projects\mydomain\bin directory.
When the server starts up, it is unresponsive to web requests (I have a Hello World servlet configured). Checking in the administration console, I note that my server instance status is SHUTDOWN.
Okay, fine. I go into the server settings, to the Control tab, and click Start.
I get the following messages:
Warning: The server myserver does
not have a machine associated with it.
Warning: All of the servers selected are
currently in a state which is incompatible
with this operation or are not associated
with a running Node Manager or you are not
authorized to perform the action requested.
No action will be performed.So, here's my question. Do I HAVE to use a Node Manager? The documentation for setting up a node manager isn't very clear about how it's done, and I'd really rather not struggle through all of that just to get a server up and running.
I've never set up a WebLogic server before (of any version), so please bear with my ignorance. I've searched every documentation resource I can find, and I keep coming up empty.
Thanks!
Edited by jakerobb at 06/25/2007 6:26 AM
Well, I figured it out. For some reason, none of the documentation (that I found) mentioned that you can simply start a Node Manager by selecting it from the Start menu. It took maybe 30 seconds.
All of the documentation made it seem like a complicated process to configure and start a node manager, so I was reluctant to pursue that avenue. If the people responsible for writing the documentation are reading, I recommend that they revise the sections in question.
Thanks anyway! :)
Similar Messages
-
Starting managed Servers under WLS 8.1 using Operator Role
Hi,
we've configured a user who is acting in the default 'Operator' role.
He can shutdown a managed server using the admin console, but when
trying to restart that managed server via node manager he fails with an exception.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
this role should be allowed to start managed servers.
-- What are we doing wrong ? --
Cheers,
RobertI believe this is a known problem, please contact BEA support for a patch.
Thanks,
-satya
Robert Akolk wrote:
Hi,
we've configured a user who is acting in the default 'Operator' role.
He can shutdown a managed server using the admin console, but when
trying to restart that managed server via node manager he fails with an exception.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
this role should be allowed to start managed servers.
-- What are we doing wrong ? --
Cheers,
Robert -
Node Manager installed as service does not start managed servers. WLS 10.3
Hi All,
I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
<Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
<Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
The node manager properties file contains the following
#Mon Apr 20 10:54:45 PDT 2009
DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
JavaHome=C\:\\bea\\JROCKI~1
AuthenticationEnabled=false
NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
LogLevel=INFO
DomainsFileEnabled=true
StartScriptEnabled=false
StartScriptName=startWebLogic.cmd
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
The managed servers' boot.properties file and startup file are below
boot.properties:
#Thu Jul 23 13:48:26 PDT 2009
CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
TrustKeyStore=CustomTrust
password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
CustomTrustKeyStoreType=JKS
username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
startup.properties:
#Server startup properties
#Thu Jul 23 13:48:27 PDT 2009
Arguments=-Xms1024m -Xmx1024m -Xnohup
JavaHome=C\:\\bea\\jrockit_160_05
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
BeaHome=C\:\\bea
ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
AdminURL=http\://localhost\:7001
JavaVendor=BEA
AutoRestart=true
AutoKillIfFailed=false
I am wondering if I left out a parameter some where.
Any help would be greatly appreciated.
Thanks,
GregFirst of all, I assume you mean "... up it does NOT start ..."?
It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers. -
File too large error unpacking War during app deploy - RHEL &WLS 10.3.5
I'm stumped and I'm hoping someone can help out here. Does anyone have any insights into the cause of my problem below, or tips on how to diagnose the cause?
scenario
We ran into an open files limit issue on our RH Linux servers, and had the SA boost the our open files limit fro 1024 to 3096. This seems to have solved the open files limit issue, once we restarted the node managers and the managed servers (our WLS startup script sets the soft limit to the hard limit).
But now we've got a new issue, right after this change. The admin server is now no longer able to deploy and war/ear, as when I click on "Activate" after the install I get
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Failed to load webapp: 'TemplateManagerAdmin-1.0-SNAPSHOT.war'
Message icon - Error File too large
on the console, and see the stack trace below in the Admin server log (nothing in the managed server logs) - indicating it's getting the error in exploding the war.
I've tried both default deployment mode, and the mode "will make the deployment available in the following location" where the war is manually copied to the same location on each box, available to each server - all with the same result. I've also tried restarting the admin server, but no luck.
The files are not overly large (<=34 MByte) and we had no trouble with them before today. I'm able to log in as the WebLogic user and copye files, etc. with no problem.
There is no disk space issue - plenty of space left on all of our filesystems. There is, as far as I can tell, no OS or user file size limit issue:
-bash-3.2$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 73728
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 3096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
environment
WLS 10.3.5 64-bit
Linux 64-bit RHEL 5.6
Sun Hotspot 1.6.0_29 (64--bit)
stack trace
####<Mar 6, 2013 4:09:33 PM EST> <Error> <Console> <nj09mhm5111> <prp_appsvcs_admin> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <steven_elkind> <> <> <1362604173724> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Failed to load webapp: 'TemplateManagerAdmin-1.0-SNAPSHOT.war'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
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)
Caused by: java.io.IOException: File too large
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:282)
at weblogic.utils.io.StreamUtils.writeTo(StreamUtils.java:19)
at weblogic.utils.FileUtils.writeToFile(FileUtils.java:117)
at weblogic.utils.jars.JarFileUtils.extract(JarFileUtils.java:285)
at weblogic.servlet.internal.ArchivedWar.expandWarFileIntoDirectory(ArchivedWar.java:139)
at weblogic.servlet.internal.ArchivedWar.extractWarFile(ArchivedWar.java:108)
at weblogic.servlet.internal.ArchivedWar.<init>(ArchivedWar.java:57)
at weblogic.servlet.internal.War.makeExplodedJar(War.java:1093)
at weblogic.servlet.internal.War.<init>(War.java:186)
at weblogic.servlet.internal.WebAppServletContext.processDocroot(WebAppServletContext.java:2789)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:2666)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:413)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)In the end, the problem was not in the Admin server where the log entry is, but in one of the managed servers where there was no such log entry.
Somehow, and we have no idea how, the NodeManager process had the soft limit for max file size set to 2k blocks. Thus, the managed server inherited that. We restarted the Node Manager, then the managed server, and the problem went away.
The diagnostic that turned the trick:
cat /proc/<pid>/limits
for the managed server showed the bad limit setting, then diagnosis proceeded from there. The admin server, of course, had "unlimited" since it was not the source of the problem. -
Clustering Problems with WLS 4.5.1
Hi!
I'm trying to configure a WebLogic 4.5.1 cluster (named "cluster1", on two
WinNT4 SP5 servers (instances WLS "server A" and "server B")
When I start each WLS instance in each server, both create a cluster where I
can only find one WLS server, not two! So I have on each NT server, one
cluster which contain one WLS server!!!
To see that, I use the WLS console on the 2 servers, and I see that in each
server, there is a cluster "cluster1" and only one server ("server A" in the
first NT Server, and "server B" in the second one).
The two server are identical, same OS, same SP, same WLS version, same WLS
Service Pack, same IP Multicast address, same TCP port (7001), and there is
no multihoming.
I can't see how to put the two WLS servers in the same cluster!
Do someone have a clue?
Best regards,
Jean-Michel Gautreau
[email protected]
Here is a console screendump, taken after the two WLS servers' boot.
I forgot to tell we have installed WLBS on both NT servers, before
installing WebLogic 4.5.1. Is there a problem in the communication between
the two servers? I'm not sure but I feel it is a network problem, the two NT
servers don't seem to communicate correctly through WLBS with the WLS
cluster?
Any hint?
[dump.bmp]
-
Christian shows us how to get access to the appContext within EJB3's with WLS 9 and pitchfork in the following post.
http://springide.org/blog/2006/05/24/implementing-jee-with-spring-and-weblogic/
In the comments, however, he says on Jun 11, 2007 that
"Yes, I tested the example, but it didn’t work [in WLS 10.0]. There is a way to enable advanced Spring features in Bea WebLogic 10 (including AOP support), but this is not public right now and definitely not yet supported by BEA. Stay tuned for an upcoming BEA announcement."
My questions is:
Should we use the Spring abstract EJB base classes and ContextJndiBeanFactoryLocator/ContextSingletonBeanFactoryLocator to access the applicationContext in our EJB3's in WLS 10? There is at least 1 post on the Spring forum saying that this support is only for EJB2 (http://forum.springframework.org/showthread.php?t=47338).
Thanks for any help,Thanks for your reply.
Hmmm interesting.
We have 4 servers with WLS 10.3.1. - they were all installed using the package installer with 32bit JVM/s. They were all configured to use the included 32bit JRockit; so the JVM being used by WLS is the same for all servers. The only difference between environments is that 3 are on Win08 SP2 and 1 is on Win08 SP1.
My original post incorrectly states that the oddity was occuring with SP1 - in fact of the 4 servers the one on SP1 is reporting the OS correct and the 3 on SP2 are reporting the OS wrong.
I checked the logs both on one SP2 server and on the SP1 server: both logs have
os.arch = x86
os.name = Windows Vista
So "all" of the servers have that log entry with the OS wrong, but as stated the SP1 WLS reports the OS correctly in the Servers/Monitoring section of the console.
Ignoring the misreporting in the log entry the law of differences would suggest maybe it's something to do with Win08 SP2 vs SP1 ???
Or some weird combination because we also have WLS 10.3.2. with 32bit JRockit, one on Win08 SP1 and one on Win08 SP2 - they "both" report the OS correctly both in the log and via the servers monitoring page.
RT -
WTC config when WLS is clustered...
How does this WTC works with tuxedo when WLS is clustered.
I am using Tuxedo 8.0 and WLS 81. sp2.
This is what I am trying to achieve.
I have a tuxedo domain and two servers in WLS cluster. The WLS server has ejb's which provide identical sevices. These services must be accessed from tuxedo. I can make these two talk if WLS is not clustered. If WLS is clustered I see the tuxedo sending the transaction... but it reaches no where on the WLS side.., even though the -Dweblogic.wtc.TraceLevel=100000 is set.
Here is the config.xml
<WTCServer Name="CRSWTC1" Targets="crs-server1">
<WTCLocalTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
BlockTime="6" ConnPrincipalName=""
ConnectionPolicy="ON_STARTUP"
NWAddr="//base1.x.x.x:16666"
Name="WTCLocalTuxDom-1101230072422" RetryInterval="6"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
ConnectionPolicy="ON_STARTUP" LocalAccessPoint="TDOM2"
NWAddr="//chela.x.x.x:16665" Name="WTCRemoteTuxDom-1101230111003"/>
<WTCExport EJBName="tuxedo.service.WTCRatingService"
LocalAccessPoint="TDOM2" Name="WTCExport-1101230154745"
RemoteName="" ResourceName="CRS"/>
</WTCServer>
<WTCServer Name="CRSWTC2" Targets="">
<WTCLocalTuxDom AccessPoint="TDOM3" AccessPointId="TDOM3"
BlockTime="6" ConnectionPolicy="ON_STARTUP"
NWAddr="//base2.x.x.x:16666"
Name="WTCLocalTuxDom-1101250069145" RetryInterval="6"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
ConnectionPolicy="ON_STARTUP" LocalAccessPoint="TDOM3"
NWAddr="//chela.x.x.x:16665" Name="WTCRemoteTuxDom-1101250249369"/>
<WTCExport EJBName="tuxedo.service.WTCRatingService"
LocalAccessPoint="TDOM3" Name="WTCExport-1101250295839"
RemoteName="" ResourceName="CRS"/>
</WTCServer>
Any help is appreciated...Well your second WTC server instance isn't targeted (deployed) to anything. So WTC is only running on one node in your cluster, crs-server1.
What you want is to create a WTC server instance for each node in the cluster. To Tuxedo, each node in the cluster appears to be a separate domain. Then on the Tuxedo side in the domain gateway config file, import the service from each WLS domain (node).
Does that make sense?
Regards,
Todd Little
BEA Tuxedo Engineering -
Problem having a MDB connect to a remote JMS Topic (WLS 6.1 sp3)
Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
scenario:
> Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
not part of a cluster......both are independent servers
> One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
target is Server1})
> In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
file):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic7001"
Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
</JMSServer>
> In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
file):
<JMSServer Name="EventServicesJMSServer"
Store="ESJMSServerFileStore" Targets="Server1">
<JMSTopic JNDIName="jms/EventServicesTopic8001"
Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
</JMSServer>
> An MDB is deployed on WLSDomain1/Server1 with the following elements in its
weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 8001 -->
<destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:8001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
> An MDB is deployed on WLSDomain2/Server1 with the following elements in its
weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
the relevant info):
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<!-- This MDB is defined to listen to a Topic in another WLS Server running
on port 7001 -->
<destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://localhost:7001</provider-url>
<connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
> After starting both the WLS servers, I've verified that they have made connections
to each other; the Topics are defined in the JNDI tree of the respective servers;
and the MDBs have been deployed in their respective servers. But the MDBs can't
see/connect to their respective JMS destination. Here's the error message and
stack trace from one the WLS server's trace file:
<Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
attempt to
re-establish the connection with the JMS server. This warning may occur during
WebLogic Cluster start-up if the JMS destination is located on another server.
When the JMS server connection is re-established, the Message-Driven EJB will
again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
9)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Have you run into a similar problem? Any suggestion?
Thanks,
Farook
FAQ. Naming conflict. To interop between domains make sure:
All WL Servers are named differently.
All JMS Servers are named differently.
All JMS Stores are named differently.
Tom
Farook Wadia wrote:
> Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
> scenario:
>
>
>>Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
>
> not part of a cluster......both are independent servers
>
>
>>One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
>
> second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
> target is Server1})
>
>
>>In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
>
> file):
>
> <JMSServer Name="EventServicesJMSServer"
> Store="ESJMSServerFileStore" Targets="Server1">
> <JMSTopic JNDIName="jms/EventServicesTopic7001"
> Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
> </JMSServer>
>
>>In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
>
> file):
>
> <JMSServer Name="EventServicesJMSServer"
> Store="ESJMSServerFileStore" Targets="Server1">
> <JMSTopic JNDIName="jms/EventServicesTopic8001"
> Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
> </JMSServer>
>
>>An MDB is deployed on WLSDomain1/Server1 with the following elements in its
>
> weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
> the relevant info):
>
> ..
> <message-driven-descriptor>
> <pool>
> <max-beans-in-free-pool>1</max-beans-in-free-pool>
> <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
> </pool>
> <!-- This MDB is defined to listen to a Topic in another WLS Server running
> on port 8001 -->
> <destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
> <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
> <provider-url>t3://localhost:8001</provider-url>
> <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
> </message-driven-descriptor>
> ...
>
>
>>An MDB is deployed on WLSDomain2/Server1 with the following elements in its
>
> weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
> the relevant info):
>
> ..
> <message-driven-descriptor>
> <pool>
> <max-beans-in-free-pool>1</max-beans-in-free-pool>
> <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
> </pool>
> <!-- This MDB is defined to listen to a Topic in another WLS Server running
> on port 7001 -->
> <destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
> <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
> <provider-url>t3://localhost:7001</provider-url>
> <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
> </message-driven-descriptor>
> ...
>
>
>>After starting both the WLS servers, I've verified that they have made connections
>
> to each other; the Topics are defined in the JNDI tree of the respective servers;
> and the MDBs have been deployed in their respective servers. But the MDBs can't
> see/connect to their respective JMS destination. Here's the error message and
> stack trace from one the WLS server's trace file:
>
> <Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
> common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
> the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
> attempt to
> re-establish the connection with the JMS server. This warning may occur during
> WebLogic Cluster start-up if the JMS destination is located on another server.
> When the JMS server connection is re-established, the Message-Driven EJB will
> again receive JMS messages.
> The Error was:
> weblogic.jms.common.JMSException: Connection not found
> at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
> at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
> at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
> at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
> at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
> at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
> at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
> at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
> at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
> at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
> 9)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
>
> Have you run into a similar problem? Any suggestion?
>
> Thanks,
>
> Farook
-
Hi
We are upgrading our WLS 8.1 Servers to WLS 10.3.4 server. While adding the weblogic.jar from WLS 10.3.4 in the project, facing an issue of importing the packages "weblogic.jdbc.oci.Blob" and "weblogic.marathons.util.EditableList" in my project, which were present in weblogic.jar of WLS 8.1 but deprecated for WLS 10.3.4. Please suggest something for this.
Thanks...!!Hi ,
Dont add the weblogic.jar file in your application explicitly then check the error you get,and also dont specify the location of the class in your application.
Let me know if you face any errors after the above suggestions.
Regards,
Rohit Jaiswal -
Cannot deploy SOA composite to a managed server
My problem: cannot deploy SOA composite to a managed server.
The following is what I did:
1. I created a domain "devDomain". admin server is created automatically for me.
*2. I created a manged server (soa_server1) on my domain after.*
2. started the admin server
3. started soa_server1
4. see both servers in WLS control, both server state=running
5. see both server in EM console, both server status are up
6. in JDev(11.1.1.5.0), created an application server connection, and tested the connection successfully
7. when I tried to deploy my composite from JDev, I selected the application server connection, on step "SOA servers", it only lists AdminServer.
8. Then I tried to deploy the composite from EM by right-click soa_server1, but "SOA deployment" is not in the list.
My guess: there should be some libraries or other resources applied to soa_server1 before it could accept soa deployment. What are these libraries/resources?
I tried to target all 10 libraries under the path "oracle.soa." to soa_server1, and checked the config.xml and found the file was updated correcly, reboot my pc, restarted the servers, but still face the same problem.
My environment is weblogic 10.3.5.
Basically, my question is:
after a domain is created and admin server is there, if I want to add a managed server which will host soa composites, what should I do to configure the managed server?
Edited by: wiky on Jul 20, 2011 11:39 AMHow can I add new code to a clustered environment without causing an outage. Right
> now I have to deploy the new code using the admin server to both managed
servers.
> My question is if I pull one managed server out of the cluster, add new
code and
> test it, how do I add this one managed server back to the cluster that is
referencing
> the old code without causing an outage for the site?
This is something addressed much better in the 7.0 release.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"William" <[email protected]> wrote in message
news:3cc9847a$[email protected]..
>
-
Error when setting up cluster in weblogic 10.3.6
Hi All,
We are trying to set up a cluster with 2 managed servers in WLS 10.3.6. The issue is that we do not manage to deploy our application on the managed server as when we start the managed servesr we have the following error message :
javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved '']; remaining name 'ouaf/servicebean'
Unfotunately, we are failing to resolve this issue. Any help would be greatly appreciated !!!
Many thanks.HI,
Just try to clear tmp and cache once a see if you still face same problem.
If not please put the complete error stack to verify what exactly going on there.
Regards,
Kal -
Hi,
I've gotten everything working in our cluster except this. We have some
JSP's that retrieve resources via a URL that points back to the cluster.
i.e. the JSP retrieves an xml template from the server and then populates
the nodes before returning it to the client. Here is a sample JSP
<%@ page import="java.io.*" %>
<%@ page import="java.net.*" %>
<html>
<head></head>
<body>
<%
String fileURL = "http://"+request.getServerName() + ":" +
request.getServerPort()+request.getContextPath()+
"/xml_dataisland/posse_permissions.xml";
java.net.URL defaultURL = new URL(fileURL);
URLConnection connection = defaultURL.openConnection();
if(connection == null){
System.out.println("null connection in posse_menu.jsp");
InputStream reply = connection.getInputStream();
if(reply == null){
System.out.println("null reply connection in posse_menu.jsp");
BufferedReader from_server = new BufferedReader(new
InputStreamReader(reply));
String line = "";
StringBuffer results = new StringBuffer();
while(line != null)
line = from_server.readLine();
if(line != null)
results.append(line);
out.println(results);
%>
</body>
</html>
This is generating an exception:
<Jan 10, 2003 10:38:37 AM MST> <Error> <HTTP> <101019>
<[ServletContext(id=1213906002,name=posse,context-path=/posse)] Servlet
faile
d with IOException
java.net.ConnectException: Tried all: '1' addresses, but could not connect
over HTTP to server: '125.125.125.125', port: '64577'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:223)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:276)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:127)
at weblogic.net.http.HttpClient.New(HttpClient.java:169)
at
weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:111)
at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:28
1)
at jsp_servlet.__test._jspService(__test.java:101)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:445)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
>
The 125.125.125.125 address is the ip of our load balancer (cisco css11503)
and should just forward all traffic to one of the two cluster machines.
Either 125.125.125.1 or 125.125.125.2. Is there something I'm missing here?
It seems like this should work but I'm not following why it isn't.
Cluster environment: 2 managed servers running WLS 7.0 sp1
TIA,
-Brett Schmoll
ADP/SIS
If I understand, "SELECT count(*) ..." always returns one row.
So, just do
String count="SELECT count(*) c from anticles";
ResultSet rscount=stmt.executeQuery(count);
int countInt = 0;
if(rscount.next()){
//get the count, an integer
countInt = rscount.getInt("c");
//print out the count. If there were errors, countInt is already set to 0.
out.println(countInt);
Hope this helps. -
Weblogic Plugin Configuration Problem -- no more in server list
HELP! Has anyone seen anything like this before. What we are seeing
is that the plugin sporadically sends requests to the wrong weblogic
instance. When it sends it to the wrong instance we are seeing the
following in the wlproxy.log. Like I said, this happens sporadically.
Sometimes it will work just fine for an entire transaction. Does
anyone know what the "no more in server list" means. We've had bea on
the phone for the last 12 hours and they haven't been able to help us
up to this point. If I need to send any more information please let
me know....
Thanks in advance!!!
Jeremy Martin
========New Request: [POST
/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000
HTTP/1.1] =========
Wed Mar 20 08:45:14 2002 Content-Length=368 clength=0
Wed Mar 20 08:45:14 2002 Going to get the post data of size 368
Wed Mar 20 08:45:14 2002 SEARCHING
id=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001]
from current ID=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001]
Wed Mar 20 08:45:14 2002
@@@FOUND...id=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001],
server_name=[p02n0310.it.sprintspectrum.com], server_port=[80]
Wed Mar 20 08:45:14 2002 Init:
availcookie=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
COLORS=spring; ZIPCODE=64119]
Wed Mar 20 08:45:14 2002 PRIMARY 207.40.168.118:7001 no more in server
list
Wed Mar 20 08:45:14 2002 The request string is
'/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000'
Wed Mar 20 08:45:14 2002 After trimming path:
'/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000'
Wed Mar 20 08:45:14 2002 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Wed Mar 20 08:45:14 2002 AttemptConnect(): Srvr# [1] =
[207.40.168.115:7001]
Wed Mar 20 08:45:14 2002 AttemptConnect(): Srvr# [2] =
[207.40.168.13:7001]
Wed Mar 20 08:45:14 2002 general list: trying connect to
'207.40.168.13'/7001
Wed Mar 20 08:45:14 2002 Connected to 207.40.168.13:7001
Wed Mar 20 08:45:14 2002 Headers from the client [Accept]=[*/*]
Wed Mar 20 08:45:14 2002 Headers from the client
[Accept-Encoding]=[gzip, deflate]
Wed Mar 20 08:45:14 2002 Headers from the client
[accept-language]=[en-us]
Wed Mar 20 08:45:14 2002 Headers from the client
[Cache-Control]=[no-cache]
Wed Mar 20 08:45:14 2002 Headers from the client
[Content-Length]=[368]
Wed Mar 20 08:45:14 2002 Headers from the client
[content-type]=[text/xml]
Wed Mar 20 08:45:14 2002 Headers from the client
[Cookie]=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
COLORS=spring; ZIPCODE=64119]
Wed Mar 20 08:45:14 2002 Headers from the client
[Host]=[rmsweb.intranet.sprintspectrum.com]
Wed Mar 20 08:45:14 2002 Headers from the client
[User-Agent]=[Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)]
Wed Mar 20 08:45:14 2002 Sending header to WLS [Accept]=[*/*]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[Accept-Encoding]=[gzip, deflate]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[accept-language]=[en-us]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[Cache-Control]=[no-cache]
Wed Mar 20 08:45:14 2002 Sending header to WLS [Content-Length]=[368]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[content-type]=[text/xml]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[Cookie]=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
COLORS=spring; ZIPCODE=64119]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[Host]=[rmsweb.intranet.sprintspectrum.com]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[User-Agent]=[Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[X-WebLogic-Force-Cookie]=[true]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[Proxy-Client-IP]=[207.167.161.73]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[X-Forwarded-For]=[207.167.161.73]
Wed Mar 20 08:45:14 2002 Sending header to WLS
[x-weblogic-cluster-hash]=[fw44lcQkjNI+PhjBPgtTl5Qwmi4]
Wed Mar 20 08:45:16 2002 Header received from WLS : [HTTP/1.1 200 OK]
= []
Wed Mar 20 08:45:16 2002 Header received from WLS : [Server] =
[WebLogic 5.1.0 Service Pack 11 11/20/2001 08:39:10 #149952]
Wed Mar 20 08:45:16 2002 Header received from WLS : [Content-Length]
= [622]
Wed Mar 20 08:45:16 2002 Header received from WLS : [Content-Type] =
[text/xml]
Wed Mar 20 08:45:16 2002 Header received from WLS : [X-WebLogic-Load]
= [0]
Wed Mar 20 08:45:16 2002 Header received from WLS : [Set-Cookie] =
[WebLogicSession=PJigemmFCOSmpZvQ8VD8AEn7t7RtPEEbSQqarpCmUYbNZ5nhoL9j|-9091816865617485599/-819419123/6/7001/7001/7002/7002/7001/-1;
expires=Sunday, 11-May-2003 06:45:16 GMT; path=/]
Wed Mar 20 08:45:16 2002 Header received from WLS : [Connection] =
[Close]
Wed Mar 20 08:45:16 2002 Headers to the client [Server]=[WebLogic
5.1.0 Service Pack 11 11/20/2001 08:39:10 #149952]
Wed Mar 20 08:45:16 2002 Headers to the client [Content-Length]=[622]
Wed Mar 20 08:45:16 2002 Headers to the client
[Set-Cookie]=[WebLogicSession=PJigemmFCOSmpZvQ8VD8AEn7t7RtPEEbSQqarpCmUYbNZ5nhoL9j|-9091816865617485599/-819419123/6/7001/7001/7002/7002/7001/-1;
expires=Sunday, 11-May-2003 06:45:16 GMT; path=/]
Wed Mar 20 08:45:16 2002 r->status=200 returning 0
Wed Mar 20 08:46:58 2002
This one sound stricky. Have you checked all the usual suspects:
-same cookie name in WB-INF/weblogic.xml and the cookiename set in
plugin settings (defualts to JSESSIONID in 6.x)
-network errors between web servers and WLS servers
That utility can be invaluable in solving problems like this.I have seen
session settings cause sessions to be lost, but never the message you
are talking about. Try turning on the "DebugConfigInfo" setting and see
what the "?__WebLogicBridgeConfig" page can tell you about your
settings, what server list it is using and what servers are
primary/secondary. One tip, you need to hit the WLS server one time, and
then use the "?__WebLogicBridgeConfig". Until it communicates with the
WLS server, it can only tell you it's own settings and not any
information about up servers and primary/secondary assignements. Also
look to make sure each server in the "Server List" has a blue ":OK" next
to it to signify the plugin can see them.
Hope that can help, though I am not sure they will deal with the problem
you are seeing. Make sure you post the outcome to this issue, I will be
very interested in seeing it.
-Mark Vaughn
Jeremy Martin wrote:
>HELP! Has anyone seen anything like this before. What we are seeing
>is that the plugin sporadically sends requests to the wrong weblogic
>instance. When it sends it to the wrong instance we are seeing the
>following in the wlproxy.log. Like I said, this happens sporadically.
> Sometimes it will work just fine for an entire transaction. Does
>anyone know what the "no more in server list" means. We've had bea on
>the phone for the last 12 hours and they haven't been able to help us
>up to this point. If I need to send any more information please let
>me know....
>
>Thanks in advance!!!
>
>Jeremy Martin
>
>========New Request: [POST
>/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000
>HTTP/1.1] =========
>Wed Mar 20 08:45:14 2002 Content-Length=368 clength=0
>Wed Mar 20 08:45:14 2002 Going to get the post data of size 368
>Wed Mar 20 08:45:14 2002 SEARCHING
>id=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001]
>from current ID=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001]
>Wed Mar 20 08:45:14 2002
>@@@FOUND...id=[207.40.168.13:7001,207.40.168.115:7001,207.40.168.34:7001,207.40.168.118:7001],
>server_name=[p02n0310.it.sprintspectrum.com], server_port=[80]
>Wed Mar 20 08:45:14 2002 Init:
>availcookie=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
>CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
>CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
>COLORS=spring; ZIPCODE=64119]
>Wed Mar 20 08:45:14 2002 PRIMARY 207.40.168.118:7001 no more in server
>list
>Wed Mar 20 08:45:14 2002 The request string is
>'/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000'
>Wed Mar 20 08:45:14 2002 After trimming path:
>'/ra/controller/AuthenticationConversation/getAuthenticationXmlInfo?currenttime=03/20/2002%2008:45:12:548000'
>Wed Mar 20 08:45:14 2002 Now trying whatever is on the list;
>ci->canUseSrvrList = 1
>Wed Mar 20 08:45:14 2002 AttemptConnect(): Srvr# [1] =
>[207.40.168.115:7001]
>Wed Mar 20 08:45:14 2002 AttemptConnect(): Srvr# [2] =
>[207.40.168.13:7001]
>Wed Mar 20 08:45:14 2002 general list: trying connect to
>'207.40.168.13'/7001
>Wed Mar 20 08:45:14 2002 Connected to 207.40.168.13:7001
>Wed Mar 20 08:45:14 2002 Headers from the client [Accept]=[*/*]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[Accept-Encoding]=[gzip, deflate]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[accept-language]=[en-us]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[Cache-Control]=[no-cache]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[Content-Length]=[368]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[content-type]=[text/xml]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[Cookie]=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
>CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
>CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
>COLORS=spring; ZIPCODE=64119]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[Host]=[rmsweb.intranet.sprintspectrum.com]
>Wed Mar 20 08:45:14 2002 Headers from the client
>[User-Agent]=[Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)]
>Wed Mar 20 08:45:14 2002 Sending header to WLS [Accept]=[*/*]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[Accept-Encoding]=[gzip, deflate]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[accept-language]=[en-us]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[Cache-Control]=[no-cache]
>Wed Mar 20 08:45:14 2002 Sending header to WLS [Content-Length]=[368]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[content-type]=[text/xml]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[Cookie]=[WebLogicSession=PJZrt2jMA3CQTgvq2s31nz1Z1nh59Z81CQalCmaZLPWO2yVpAy71|6556818855266464983/-819419018/6/7001/7001/7002/7002/7001/-1;
>CFID=17578; CFTOKEN=9604102; FULLACCESS=1;
>CFGLOBALS=HITCOUNT%3D200%23LASTVISIT%3D%7Bts+%272002%2D03%2D06+10%3A52%3A38%27%7D%23TIMECREATED%3D%7Bts+%272001%2D11%2D03+17%3A29%3A44%27%7D%23;
>COLORS=spring; ZIPCODE=64119]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[Host]=[rmsweb.intranet.sprintspectrum.com]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[User-Agent]=[Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[X-WebLogic-Force-Cookie]=[true]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[Proxy-Client-IP]=[207.167.161.73]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[X-Forwarded-For]=[207.167.161.73]
>Wed Mar 20 08:45:14 2002 Sending header to WLS
>[x-weblogic-cluster-hash]=[fw44lcQkjNI+PhjBPgtTl5Qwmi4]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [HTTP/1.1 200 OK]
>= []
>Wed Mar 20 08:45:16 2002 Header received from WLS : [Server] =
>[WebLogic 5.1.0 Service Pack 11 11/20/2001 08:39:10 #149952]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [Content-Length]
>= [622]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [Content-Type] =
>[text/xml]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [X-WebLogic-Load]
>= [0]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [Set-Cookie] =
>[WebLogicSession=PJigemmFCOSmpZvQ8VD8AEn7t7RtPEEbSQqarpCmUYbNZ5nhoL9j|-9091816865617485599/-819419123/6/7001/7001/7002/7002/7001/-1;
>expires=Sunday, 11-May-2003 06:45:16 GMT; path=/]
>Wed Mar 20 08:45:16 2002 Header received from WLS : [Connection] =
>[Close]
>Wed Mar 20 08:45:16 2002 Headers to the client [Server]=[WebLogic
>5.1.0 Service Pack 11 11/20/2001 08:39:10 #149952]
>Wed Mar 20 08:45:16 2002 Headers to the client [Content-Length]=[622]
>Wed Mar 20 08:45:16 2002 Headers to the client
>[Set-Cookie]=[WebLogicSession=PJigemmFCOSmpZvQ8VD8AEn7t7RtPEEbSQqarpCmUYbNZ5nhoL9j|-9091816865617485599/-819419123/6/7001/7001/7002/7002/7001/-1;
>expires=Sunday, 11-May-2003 06:45:16 GMT; path=/]
>Wed Mar 20 08:45:16 2002 r->status=200 returning 0
>Wed Mar 20 08:46:58 2002
>
-
Could not register a HeartbeatMonitorListener
Hi!
Saw a different posting on this subject and have exactly the same
problem. I have 2 local servers, one WLS 7 server and the other is
Weblogic 8. I want messages sent to the WLS7 queue accessible from the
WLS 8 queue. WLS 7 runs on port 7001, and WLS 8 on 8001.
JMS Config for WLS 7:
============================
- JMS Config factory:
Name: WLS 7 Connection Factory
JNDI Name: rps.refapp.jms.jms_connfactory
- JMS Queue:
Name: WLS7
JNDI Name: jms.wls7.q
Foreign JMS Config for WLS 8:
=============================
- Foreign JMS Server:
Name: MyJMSServer
JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
JNDI Connection URL: t3://localhost:7001
- Foreign JMSConnection Factroy:
Name: WLS 7 Connection Factory
Local JNDI Name: jms.wls7connfactory
Remote JNDI Name: rps.refapp.jms.jms_connfactory
User Name: system
Password: weblogic
- Foreign JMS Destinations:
Name: WLS7
Local JNDI Name: jms.wls7_queue
Remote JNDI Name: jms.wls7.q
I have an MDB deployed on the WLS 8 server with no funtionality except
sending the contents of a message to system.out. Here is the contents of
the weblogic-ejb-jar:
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>MessageListener</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms.wls7_queue</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<jms-polling-interval-seconds>5</jms-polling-interval-seconds>
</message-driven-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>MessageListener</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
And here is the stacktrace after deploying the bean:
<2003-dec-15 kl 17:51 CET> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "mydomain">
<2003-dec-15 kl 17:52 CET> <Warning> <EJB> <BEA-010061> <The
Message-Driven EJB: MessageListener is unable to connect to the JMS
destination: jms.wls7_queue. The Error was:
[EJB:010196]'weblogic.jms.common.JMSException: Error creating session'
Linked exception = 'weblogic.jms.dispatcher.DispatcherException: Could
not register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver'
weblogic.jms.common.JMSException: Error creating session
at
weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:798)
at
weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1036)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2550)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:609)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
at
weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1814)
at
weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1645)
at
weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
at
weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1598)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1833)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:830)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
at
weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1583)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1411)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:668)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2017)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2058)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2005)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3136)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1688)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:407)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
Caused by: weblogic.jms.dispatcher.DispatcherException: Could not
register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:309)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:356)
at
weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:796)
... 26 more
Caused by:
weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
Could not register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0]
at
weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:305)
... 28 more
>
Well, I'm out of ideas, so I hope someone can help me out. This is a
fairly simple problem to duplicate. I can send more details as well.
Thanks in advance,
/Eje Thorarinsson
Hi!
Saw a different posting on this subject and have exactly the same
problem. I have 2 local servers, one WLS 7 server and the other is
Weblogic 8. I want messages sent to the WLS7 queue accessible from the
WLS 8 queue. WLS 7 runs on port 7001, and WLS 8 on 8001.
JMS Config for WLS 7:
============================
- JMS Config factory:
Name: WLS 7 Connection Factory
JNDI Name: rps.refapp.jms.jms_connfactory
- JMS Queue:
Name: WLS7
JNDI Name: jms.wls7.q
Foreign JMS Config for WLS 8:
=============================
- Foreign JMS Server:
Name: MyJMSServer
JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
JNDI Connection URL: t3://localhost:7001
- Foreign JMSConnection Factroy:
Name: WLS 7 Connection Factory
Local JNDI Name: jms.wls7connfactory
Remote JNDI Name: rps.refapp.jms.jms_connfactory
User Name: system
Password: weblogic
- Foreign JMS Destinations:
Name: WLS7
Local JNDI Name: jms.wls7_queue
Remote JNDI Name: jms.wls7.q
I have an MDB deployed on the WLS 8 server with no funtionality except
sending the contents of a message to system.out. Here is the contents of
the weblogic-ejb-jar:
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>MessageListener</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms.wls7_queue</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<jms-polling-interval-seconds>5</jms-polling-interval-seconds>
</message-driven-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>MessageListener</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
And here is the stacktrace after deploying the bean:
<2003-dec-15 kl 17:51 CET> <Notice> <WebLogicServer> <BEA-000327>
<Starting WebLogic Admin Server "myserver" for domain "mydomain">
<2003-dec-15 kl 17:52 CET> <Warning> <EJB> <BEA-010061> <The
Message-Driven EJB: MessageListener is unable to connect to the JMS
destination: jms.wls7_queue. The Error was:
[EJB:010196]'weblogic.jms.common.JMSException: Error creating session'
Linked exception = 'weblogic.jms.dispatcher.DispatcherException: Could
not register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver'
weblogic.jms.common.JMSException: Error creating session
at
weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:798)
at
weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1036)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2550)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:609)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
at
weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1814)
at
weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1645)
at
weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
at
weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1598)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1833)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:830)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
at
weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1583)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1411)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:668)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2017)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2058)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2005)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3136)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1688)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:407)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
Caused by: weblogic.jms.dispatcher.DispatcherException: Could not
register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:309)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:356)
at
weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:796)
... 26 more
Caused by:
weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
Could not register a HeartbeatMonitorListener for
[weblogic.jms.dispatcher.DispatcherImpl@1970ae0]
at
weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:305)
... 28 more
>
Well, I'm out of ideas, so I hope someone can help me out. This is a
fairly simple problem to duplicate. I can send more details as well.
Thanks in advance,
/Eje Thorarinsson
-
Weird issue with 10.0.1.0 on Linux - 5 mins delay in server start-up!!
Hi ...
I am having some weird (and unique??) issue with WLS 10.0.1.0 on RHEL servers.
WLS installation on our DEV env works perfectly fine and the server starts up in 15-20 secs. for each of the two domains created on it.
But the QA server is another story all together ! ... It has the same OS and version, WSL installation and version, hardware configs, processes running at the time of start-up etc. But the problem is that when I try to start the server on the only domain on that server, it always gets delayed by 5-6 mins in between the startup at this point -
+<Feb 17, 2009 *7:04:50 *PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >+
+<Feb 17, 2009 *7:10:56 *PM UTC> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /opt/bea/license.bea>+
(Notice the 6 mins delay in the timestamps)
There are no logs getting generated within this time and it seems like the WLS 10.0.1.0 just spaces out
After the delay it starts up pretty fast .. within 10-15 secs!!
Anybody here seen such behavior with WLS
thanks,
--Shailesh WelankarI recommend taking some thread dumps during this delay and contacting support to get some advice.
You can take the thread dumps by kill -3, JRockit Mission Control, etc.
Maybe you are looking for
-
HP Pavilion g6 Notebook - Sudden shutdowns without warning when battery is low
My notebook is only ten months old. Within the last week, it started shutting down unexpectedly when the battery was low (but not at a critical level). If I try to restart it, there won't be a response until I plug in the adaptor cord. Usually there
-
Having loads of trouble installing itunes on my new samsung laptop keep getting this message when i try to run the download . This installation package could not be opened verify that the package exists and that you can access it or contact the appli
-
Navigation controller back button
Hi i have a viewcontoller a) controlling a view with an nstimer. I want to suspend the timer if i switch to another viewcontroller b) which is fine, but i want to resume the timer when pressing the back button on the navigation controller. How do i e
-
Is there still a possibility to download Photoshop Elements 6 for Mac? I still have my serialnumber but not the software. Best regards Gerhard Burch
-
When you're collecting for output/packaging a print project from InDesign and you're using Adobe Typekit, the Typekit fonts will not be packaged. Will there be any sort of warning or message so that both the artist and the print vendor are aware thos