JMS with managed servers
I have created two independent server instances, each with their own applications directory, config.xml file, etc. Now I want them to be able to use JMS to communicate with each other. It is my impression that there are a couple of ways to do this, the easiest of these being to add the server instances as managed servers to the same administration server so they exist in the same domain, then set up a single JMS configuration for that domain. Is this right?
If so, how do I set the administration server for an independent server instance? Must I also explicitly change its domain to match that of the administration server?
Or is this not possible and I need to use a messaging bridge?
Thanks in advance.
David
Hi David,
I'm not sure, but I don't think you can set up an admin server for an "independent server instance". I think all servers in the domain are either a "managed server", or an "admin server", where managed servers get their configuration from the admin server. Regardless, with the "domain" approach, I assume you are leaning towards going a bit further and configuring a cluster, which would automatically allow any app on any server within the cluster to transparently lookup any resource in the cluster in the global JNDI context. All of this information is in the general documentation (not the JMS documentation).
I think there are pluses and minuses to either approach you mention. For simplicity, if you don't need clustering features, you might simply want to try the "interop" approach and see if its good enough for your purposes, rather than going through the trouble of setting up an admin server and a cluster:
http://e-docs.bea.com/wls/docs81/faq/interop.html
In this approach, cross-communication always involves references the remote server's URL at some point, but this URL might be specified via configuration (MDB, bridge, SAF, foreign dest all provide ability to specify a URL).
Hope this helps,
Tom
Similar Messages
-
Configuratione exception with managed servers beta 2
Hello
I have downloaded the WLS 6.0 beta 2 version.
I did the following steps to start a managed server
1) I started the Default Admin server
2) I created new server called "testserver" throught default admin console
3)I saved the a)setEnv.cmd and b)startweblogic.cmd under as mydomain as a) setenvmanaged.cmd b)startweblogicmangaged.cmd
4) I edited the startweblogicmanaged.cmd and changed the -Dweblogic.name=testserver and i added -Dweblogic.management.server=http://127.0.0.1:7001
5) Opened another command window using "cmd" and I typed setenvmanaged.cmd first and then I typed startweblogicmanaged.cmd
But I get the following error messages
"Weblogic.management.configuration.ConfigurationException:admin URL: t3//127.0.0.1 with nested Exceiption" da da da da.....
I would appreciate if someone could tell me what is that wrong step I am doing. And also I have gonethrough the newsgroups and I also tried adding -Dweblogic.admin.host=127.0.0.1:7001 but still it gives the same error message
I appreciate ur response in advance
Thanks
RangaI am using beta-2 on Solaris
"Sanjeev Chopra" <[email protected]> wrote:
Are you using beta-1 ?
Joe Hoffman <[email protected]> wrote in message
news:[email protected]...
Sanjeev,
I get a similar problem when attempting to start PetStore as a managedserver
under the MyDomain admin server.
I have specified the following additional -D parameters in the petstorestart script:
weblogic.management.server=127.0.0.1:7001
weblogic.management.username=system
weblogic.managmenet.password=<I've tried the MyDomain pw and the petstorepw>
I get the following error on the petstore console:
The WebLogic Server did not start up properly.
Exception raised:weblogic.management.configuration.ConfigurationException: connecting to
http://127.0.0.1:7001/Bootstrap/ - with nested exception:
[java.io.FileNotFoundException: Response: '404' for url:
'http://127.0.0.1:7001/Bootstrap/'
java.io.FileNotFoundException: Response: '404' for url:
'http://127.0.0.1:7001/Bootstrap/'
atweblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:34
9)
atjava.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
atweblogic.management.Admin.getBootstrapLocalServer(Admin.java:812)
at weblogic.management.Admin.initialize(Admin.java:289)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:321)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:163)
at weblogic.Server.main(Server.java:35)
When I attempt to go to the http://127.0.0.1:7001/Bootstrap URL I get an
authentication
challenge. I've tried the Mydomain and Petstore credentials, but neitherwork.
Suggestions?
Thanks
Joe Hoffman
Denver, CO
"Sanjeev Chopra" <[email protected]> wrote:
I don't see anything wrong in your steps. Unless there is something which
we
are missing in your environment, this could be a bug in beta-2.
However, i have verified this with a recent internal release and do notget
any error. So this will be fixed as a part of the general release laterthis
month of WLS 6.0.
Can you post the complete error message with the stack trace which youget
at startup of the managed server ? It may throw some more light on whats
going on.
ranga <[email protected]> wrote in message
news:[email protected]...
Hello
I have downloaded the WLS 6.0 beta 2 version.
I did the following steps to start a managed server
1) I started the Default Admin server
2) I created new server called "testserver" throught default admin
console
3)I saved the a)setEnv.cmd and b)startweblogic.cmd under as mydomain asa) setenvmanaged.cmd b)startweblogicmangaged.cmd
4) I edited the startweblogicmanaged.cmd and changedthe -Dweblogic.name=testserver and i
added -Dweblogic.management.server=http://127.0.0.1:7001
5) Opened another command window using "cmd" and I typed
setenvmanaged.cmd
first and then I typed startweblogicmanaged.cmd
But I get the following error messages
"Weblogic.management.configuration.ConfigurationException:admin URL:t3//127.0.0.1 with nested Exceiption" da da da da.....
I would appreciate if someone could tell me what is that wrong step I
am
doing. And also I have gonethrough the newsgroups and I also tried
adding -Dweblogic.admin.host=127.0.0.1:7001 but still it gives the same
error message
I appreciate ur response in advance
Thanks
Ranga -
Troubles with managed servers start-up in RH EL AS 3.0
Hello
So, here is a problem: after release of Red Hat Enterprise Linux 3.0 with improved
thread management ppl normally expect instant performance boost and lots of other
nice things :)
The result is that JRocket does not work with this OS release (core dumps) - posted
to respectfull group.
When using Sun SDK (both bundled with WLS 8.1 sp1 and newer one from Sun (1.4.2_02)
it is not possible to properly start up managed server from the admin console:
somehow the NodeManager does not see the end of managed server output (the last
line it sees is about binding listener to port xxx). The managed server actually
starts up and works, also in the logs on the hard drive $BEA_HOME/weblogic81/common/
.. /NodeManagerLogs/server.log all the events are logged properly.
The fact that node manager can not read logs results in the CPU polling and extremelly
poor web interface (management) performance (node manager process consumes one
of CPUs completely), the managed server is shown as RUNNING, but the operation
is still in progress, so it is not possible to stop/restart it.
May be some nice patch available :) ? Or we have to go back to RH EL 2.1?
BR
VAYou can't declare the same variables/function more than once in a given timeline. That's what all the errors are telling you. The two options that Rob identified will work.
What you can do is extend the actions frame for the length of the occupied timeline so that variables/functions you declare in frame 1 are available in all frames along the timeline. To do this, you have the code in keyframe 1 and go to the end of the timeline and choose the command to Insert Frame. You should see the timeline between the first frame and the last becomes one large white frame area.
I will often have two layers dedicated to actionscript. One for the code that lives in frame 1 that gets shared along the timeline's length, and another for the commands that are specific to certain frames only.
If you need need text to appear/type-out in different frames then you just call the function that performs the typing while sending it the text that it needs to type. If you need to type it into a different textfield, then you could pass that to the typing function as well so that it targets the desired textfield. -
JMS ReplyTo - RequestQ and ResponseQ are in different Managed Servers
Hopefully this brief summary explains the issue:
1) Two managed servers, ServerA and ServerB
2) ServerA has JMSServerA with ResponseQ (hosted at t3:\\A)
3) ServerB has JMSServerB with RequestQ (hosted at t3::\\B)
a) Standalone JMS client sends message to ServerB RequestQ (t3:\\B) with replyTo field set to ResponseQ hosted by ServerA (t3:\\A)
b) Standalone JMS consumer onMessage() recieves message, extracts replyTo field, uses its Session (that it created off a connection to JMSServerB (t3:\\B), not t3::\\A)
and so when the replyTo message is sent, i.e.
producer = session.createProducer( replyToDestination); // session is created from a connection to B, not A
producer.send( replyMessage )
an exception is generated that says "no available router to destination, . . . "
How is the connection info supposed to be avail to consumer to know how to create a session on a connection to A so that the replyTo destination hosted by A is reachable?
(t3:\\A and t3::\B are notional so you get the idea that different physical connections are being used)
thanks for any insight
-mikeHi Mike,
It is generally a good goal to try and design applications to be made stateless, so that responses can be processed by any JVM.
Alternatively, if the response message is ephemeral -- only needed for the life of the client JVM - then I would consider using dynamically created JMS temporary queues instead of configured queues, with each client JVM creating a temporary queue when it starts.
Finally, if the responses must be long-lived, and your app can't be stateless, then, in general the easiest approach with a simple distributed response queue is to change the application to create consumers on each member. You can try the co-location approach that you mentioned if its known the app will always be running co-located with the distributed destination member that it works with - this type of approach tends to be incompatible with "service migration" style HA.
Hope this helps,
Tom -
Linking JMS Queues between two managed servers
I have an environment setup with an AdminServer and multiple managed servers all under the same domain and on the same cluster. They are all running under the same Instance of weblogic on one Windows Server.
I have two different applications on two managed servers that need to have a JMS Queue be linked between them. Essentially have Server1's 'inbox' link to Server2's 'outbox' and Server2's 'inbox' link to Server2's 'outbox'. Each has their own name for their inbox or outbox.
Server1(inbox)=Server2(outbox)
Server2(inbox)=Server1(outbox)
I've tried using Foreign JNDI Providers, however it doesn't allow me to input two addresses (Server1 and Server2).
Is there another function that would do the same thing?
Thanks!You can make use of Message Bridges between any 3th party JMS provider or SAF (store & forward) if both jms servers are weblogic servers.
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst
Edited by bschelst at 04/07/2008 1:27 PM -
Getting JMS Exception while starting the managed servers
Hi ,
I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
Thanks in advance...
<Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
*<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
MS destination: jms/BLAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
s "sbmejb1,sbmejb2">
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
JMS destination: jms/BLCacheSyncTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
m76" running in Production Mode>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
the JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
e JMS destination: jms/BPAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>Hi Rohit,
Thanks for your response..
Below is the BLAdminTopic configuration.Please let me know if you need any further info.
Topic:BLAdminTopic
Type:Distributed Topic
JNDI:jms/BLAdminTopic
Sub Deployment :N/A
Target:N/A
BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
Regards,
Jyotiranjan -
Browse jms destinations on managed servers (from admin server)
I need to browse JMS destinations from the admin server (in a WebLogic
9.2 console extension) that are only deployed on the managed servers.
I can get destination attributes via the domain runtime server, but
no JNDI or actually browse the destinations. All destinations in
which I am interested are queues.
I know I can change my initial context, but if that is the way to go, is there a way to determine the managed
servers' URLs at runtime?
Thank you for any help,
Sethhi
this worked for me (on 8.1). I suppose there are
better ways in 9.2
Context adminCtx = null;
adminCtx = getInitialContextForAdminServer();
MBeanHome adminhome = (MBeanHome)
adminCtx.lookup(MBeanHome.ADMIN_JNDI_NAME);
// Get the list of running managed
ning managed servers and iterate over itSet
Set srSet =
Set srSet =
adminhome.getMBeansByType("ServerRuntime");
Iterator sr_iter = srSet.iterator();
while (sr_iter.hasNext())
ServerRuntimeMBean bean =
timeMBean bean = (ServerRuntimeMBean) sr_iter.next();
// Get the home for the managed
for the managed server
MBeanHome remoteHome = (MBeanHome)
me = (MBeanHome) adminCtx.lookup(MBeanHome.JNDI_NAME
+ "." + bean.getName());
// Get the MBeanServer for the
anServer for the managed server
MBeanServer rmbs =
eanServer rmbs = remoteHome.getMBeanServer();
//invoke it
ObjectName objectName= new
objectName= new ObjectName("$mbean");
rmbs.invoke(objectName,operation,params,types);
Edited by deepshet at 05/05/2007 10:00 AMThank you for the help.
MBeanHome is deprecated as of 9.0, so I was unable to directly use your example. You have helped though, thank you.
As of now I am querying the domain runtime server for:
ObjectName("com.bea:*,Type=ServerRuntime")
I am then iterating through the returned Set to get the server URLs and then setting my InitialContext with a PROVIDER_URL of the managed servers. This allows me to Look Up a Destination without JNDI based on step 4 from [url http://edocs.bea.com/wls/docs92/jms/implement.html#wp1313933]here. I can then browse as needed.
The ugly part is that if I include the Admin URL in my PROVIDER_URL then it does not work, so I am checking for it as I loop through the set of ServerRuntimes and not including it.
Further though slightly less annoying is that the managed server URLs include "t3://" but if I leave it in there, a malformed URL exception is thrown when setting the PROVIDER_URL. So I also remove all of those and then preppend one on the front for PROVIDER_URL as I actually need.
It is not pretty, but it is working on the only cluster I have been able to try thus far.
If anyone was a cleaner suggestion, please share. -
Run Admin Server with multiple Managed Servers each using different userid?
We currently run separate WebLogic domain instances for each business application in a Unix environment. Each one is created using a unix userid unique to that application and which owns all the files and is used to run the process when that particular WebLogic instance is started up. We have run this way for a while.
I am considering altering our approach to the one that is recommended, i.e. in our Production environment we would run a single Admin instance with numerous managed servers. One issue I'm stuck on is the fact that in our current environment, each application has a different unix userid that owns the files making up the WebLogic domain instance and that WebLogic instance is run under that userid.
I've investigated and experimented using WebLogic 10.3 preview and WebLogic 10.0, but I haven't been able to determine what I have to do to make each managed server's files and processes belong to a different unix userid, if that is even possible.
Is there a way, using the recommended approach, where there is a single Admin instance that has multiple managed servers whose files and processes are owned by different unique, unix userids?
If not, how would you separate access to each of the Managed Servers so that the programmers who maintain them don't have access to Managed Servers that they are not responsible for?
Thanks for any help or suggestions.....Hi:
I played with this stuff and I found that this will work, without the Location elements:
<IfModule mod_weblogic.c>
MatchExpression /app1 WebLogicHost=server1|WebLogicPort=7003
MatchExpression /app2 WebLogicHost=server2|WebLogicPort=7003
</IfModule>
Also this will work too, with no entries inside the IfModule element:
<Location /app1 >
SetHandler weblogic-handler
WebLogicHost server1
WebLogicPort 7003
</Location>
<Location /app2 >
SetHandler weblogic-handler
WebLogicHost server2
WebLogicPort 7003
</Location> -
Re: Precompiling JSP with admin/managed servers
Thanks, but I'm not doing any copying.
The admin/managed-server communication copies things to the managed server,
which then always recompiles the pages when hit.
-Greg
Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
"Robert Coonrad" <[email protected]> wrote in message
news:[email protected]...
>
> check out post 8366...i found that i was not preserving
> the lastmodified date on my jsps and this was causing
> unnecessary re-compilation.
>
> hope it helps...
> bobc
>
> "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
> >I believe I have exhausted all permutations of EARing/notEARing,
> >WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
> >placing them in a static location and setting workingDir to that
location,
> >combinations of the above.
> >
> >No matter what, the managed server re-compiles pages the first time they
> >are
> >hit. Non admin/managed-server I have no problems.
> >
> >Can anyone from BEA comment on this problem? Or give me a workaround
> >for
> >getting a cluster working with precompiled jsps?
> >
> >-Greg
> >
> >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >news:[email protected]...
> >> Grrr... The JSP engine is extremely frustrating! I've spent many hours
> >> fighting the "staleness" checker in WL. I've been through all of the
> >> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
> >> pre-compilation working on single-server deployments, but admin/managed
> >> server deployments have me beat.
> >>
> >> WL6.1, SP1, Solaris
> >>
> >> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
> >> place. The fixed place contains pre-compiled versions of all jsps
> >made on
> >> that machine using jspc not 20 minutes earlier using the JSP files
> >in the
> >> exploded EAR file used by the admin server as the model for managed
> >> servers.. The managed servers are on the same machine.
> >>
> >> When the admin server gives an application to a managed server, the
> >managed
> >> server creates a temporary directory containing all of the webapp
> >> components, etc. The file timestamps on these files is the set by
> >the
> >> copying process to the time of the managed server boot (why?!?!????!?),
> >so
> >> the staleness check always thinks they are new and could care less
> >what
> >> precompiled jsps I have in my workingDir, the WEB-INF/classes
directory,
> >or
> >> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
> >in
> >> this scenario.
> >>
> >> If I tell the managed server to precompile everything on boot (about
> >45
> >> minutes for this app) it will create versions of the classes that match
> >th
> >e
> >> new JSP file timestamps, but this does not even survive a reboot of
> >the
> >> managed server because it AGAIN creates a new temp version of
everything
> >on
> >> the next reboot with new timestamps.
> >>
> >> If I wait for the managed server to boot and find the directory like
> >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
> >copy
> >> (via cp -pr to retain timestamps) all of the original webapp components
> >on
> >> top of the temp versions, the staleness checker is happy and the
> >> pre-compiled versions work fine.
> >>
> >> There HAS to be a way to package pre-compiled versions of the JSPs
> >in the
> >> "model" application in the admin server and keep from having to
precompile
> >> the JSPs on every managed server every time managed server is booted..
> >>
> >> It would help if we had a way to bypass the staleness checking
> >completely..
> >> Or you guys should make the timestamps on the files copied by the
> >> admin/managed deployment process match properly so the staleness
checker
> >> doesn't think the JSP is different.
> >>
> >> It would also help if the engineer who wrote this could explain the
> >rules
> >> being implemented by the staleness checker. So far all the messages
> >in
> >the
> >> newsgroup have amounted to point solutions for problems without a good
> >> understanding of what the engine is checking for and/or doing under
> >the
> >> covers. Looking at the generated .java files for the JSP pages helps,
> >but
> >> it is not good enough...
> >>
> >> Anyone out there have a working admin/managed server JSP application?
> >> -Greg
> >>
> >> -----------------------------------------------------------
> >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >>
> >>
> >>
> >
> >
>
The admin/managed-server communication copies things to the managed server, which then always recompiles the pages when hit.
This is a known issue and is fixed. The timestamps of the compiled classes was not being preserved when extracted from the war file used to distribute to the managed servers. This will be available in WLS6.1 Service Pack 3 - and there is a temporary patch available for SP2. Please ask your friendly BEA support person for it (you can refer to CR058946)
I'd give you the patch myself, but they like to keep track of these things...
Regards,
Alex
"Girish" <[email protected]> wrote in message news:[email protected]...
>
> "Aditya Kiran Gavvala" <[email protected]> wrote:
> >Greg,
> >
> >I have been following your posts, because our application deployment
> >ran
> >into exact same problem you ran into. I had spent a full two days
> >researching into the problem. And I figured the solution. Hope this
> >helps.
> >
> >Here are my discoveries:
> >
> >The following applies only to the following environment:
> >OS: Linux (perhaps for Win/Unix/Solaris etc)
> >WLS 6.0 SP2 ( no rolling patches): I found Rolling Patch2 (RP2) not useful
> >for this problem.
> >Clustered environment with Admin/Managed servers
> >
> >- When you compile JSP using weblogic.jspc compiler it puts the JSP file
> >timestamp into the compiled class. You can see it in the generated java
> >file
> >(you need to supply -keepgenerated switch to jspc)
> >
> >- When a request is made to a JSP page after the application is deployed,
> >it
> >seems to be retrieving this timestamp from the compiled class file and
> >comparing it with the JSP file timestamp. If they dont match a compile
> >command gets run by the server. Thereby you see a compile happening at
> >run
> >time.
> >
> >- If you have exploded directory deployment, when you start the managed
> >servers they create a ".war" file (under some temp dir) with all the
> >JSP
> >source files going into the file. You can notice this by looking into
> >the
> >server log file. Therefore all JSP source files get a brand new timestamp
> >in
> >the archive (a timestamp later than what was put class files by
> >weblogic.jspc). So, the server at run time sees that the timestamp in
> >the
> >class file is older than the JSP source file and runs a recompile. So
> >DONT
> >DO EXPLODED directory deployment if your environment is as described
> >in this
> >post.
> >
> >- If you have ".war" file deployment, you will not have a problem. At
> >the
> >start up time managed server still creates "".war" file under a temp
> >directory however it seems to be copying the content of the your ".war"
> >file. So, the timestamps of JSP remain the same as they were before.
> >SO NO
> >RE-COMPILATION.
> >
> >- Another important thing to remember is to make sure you specify the
> >workingDir in the weblogic.xml file. That is where the precompiled class
> >files should reside. This should be any directory the server uses as
> >scratch
> >pad to compile classes or find (pre)compiled classes. This is not a
> >directory inside your .war file is what I am trying to get at.
> >
> >Hope this helps,
> >Aditya
> >
> >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >news:[email protected]...
> >> Thanks, but I'm not doing any copying.
> >>
> >> The admin/managed-server communication copies things to the managed
> >server,
> >> which then always recompiles the pages when hit.
> >>
> >> -Greg
> >>
> >> -----------------------------------------------------------
> >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >>
> >> "Robert Coonrad" <[email protected]> wrote in message
> >> news:[email protected]...
> >> >
> >> > check out post 8366...i found that i was not preserving
> >> > the lastmodified date on my jsps and this was causing
> >> > unnecessary re-compilation.
> >> >
> >> > hope it helps...
> >> > bobc
> >> >
> >> > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
> >> > >I believe I have exhausted all permutations of EARing/notEARing,
> >> > >WARing/notWARing, placing precompiled jsp class files in
> >WEB-INF/classes,
> >> > >placing them in a static location and setting workingDir to that
> >> location,
> >> > >combinations of the above.
> >> > >
> >> > >No matter what, the managed server re-compiles pages the first time
> >they
> >> > >are
> >> > >hit. Non admin/managed-server I have no problems.
> >> > >
> >> > >Can anyone from BEA comment on this problem? Or give me a workaround
> >> > >for
> >> > >getting a cluster working with precompiled jsps?
> >> > >
> >> > >-Greg
> >> > >
> >> > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >> > >news:[email protected]...
> >> > >> Grrr... The JSP engine is extremely frustrating! I've spent many
> >hours
> >> > >> fighting the "staleness" checker in WL. I've been through all
> >of the
> >> > >> newsgroup messages pertaining to pre-compiling, etc., and I've
> >gotten
> >> > >> pre-compilation working on single-server deployments, but
> >admin/managed
> >> > >> server deployments have me beat.
> >> > >>
> >> > >> WL6.1, SP1, Solaris
> >> > >>
> >> > >> I've done the pageCheckSeconds=-1 and the workingDir is set to
> >a
> >fixed
> >> > >> place. The fixed place contains pre-compiled versions of all
> >jsps
> >> > >made on
> >> > >> that machine using jspc not 20 minutes earlier using the JSP files
> >> > >in the
> >> > >> exploded EAR file used by the admin server as the model for managed
> >> > >> servers.. The managed servers are on the same machine.
> >> > >>
> >> > >> When the admin server gives an application to a managed server,
> >the
> >> > >managed
> >> > >> server creates a temporary directory containing all of the webapp
> >> > >> components, etc. The file timestamps on these files is the set
> >by
> >> > >the
> >> > >> copying process to the time of the managed server boot
> >(why?!?!????!?),
> >> > >so
> >> > >> the staleness check always thinks they are new and could care
> >less
> >> > >what
> >> > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
> >> directory,
> >> > >or
> >> > >> anywhere else. The pageCheckSeconds=-1 seems to be completely
> >ignored
> >> > >in
> >> > >> this scenario.
> >> > >>
> >> > >> If I tell the managed server to precompile everything on boot
> >(about
> >> > >45
> >> > >> minutes for this app) it will create versions of the classes that
> >match
> >> > >th
> >> > >e
> >> > >> new JSP file timestamps, but this does not even survive a reboot
> >of
> >> > >the
> >> > >> managed server because it AGAIN creates a new temp version of
> >> everything
> >> > >on
> >> > >> the next reboot with new timestamps.
> >> > >>
> >> > >> If I wait for the managed server to boot and find the directory
> >like
> >> > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
> >> > >copy
> >> > >> (via cp -pr to retain timestamps) all of the original webapp
> >components
> >> > >on
> >> > >> top of the temp versions, the staleness checker is happy and the
> >> > >> pre-compiled versions work fine.
> >> > >>
> >> > >> There HAS to be a way to package pre-compiled versions of the
> >JSPs
> >> > >in the
> >> > >> "model" application in the admin server and keep from having to
> >> precompile
> >> > >> the JSPs on every managed server every time managed server is
> >booted..
> >> > >>
> >> > >> It would help if we had a way to bypass the staleness checking
> >> > >completely..
> >> > >> Or you guys should make the timestamps on the files copied by
> >the
> >> > >> admin/managed deployment process match properly so the staleness
> >> checker
> >> > >> doesn't think the JSP is different.
> >> > >>
> >> > >> It would also help if the engineer who wrote this could explain
> >the
> >> > >rules
> >> > >> being implemented by the staleness checker. So far all the messages
> >> > >in
> >> > >the
> >> > >> newsgroup have amounted to point solutions for problems without
> >a
> >good
> >> > >> understanding of what the engine is checking for and/or doing
> >under
> >> > >the
> >> > >> covers. Looking at the generated .java files for the JSP pages
> >helps,
> >> > >but
> >> > >> it is not good enough...
> >> > >>
> >> > >> Anyone out there have a working admin/managed server JSP application?
> >> > >> -Greg
> >> > >>
> >> > >> -----------------------------------------------------------
> >> > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >
> >
>
[att1.html]
-
Precompiling JSP with admin/managed servers
Grrr... The JSP engine is extremely frustrating! I've spent many hours
fighting the "staleness" checker in WL. I've been through all of the
newsgroup messages pertaining to pre-compiling, etc., and I've gotten
pre-compilation working on single-server deployments, but admin/managed
server deployments have me beat.
WL6.1, SP1, Solaris
I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
place. The fixed place contains pre-compiled versions of all jsps made on
that machine using jspc not 20 minutes earlier using the JSP files in the
exploded EAR file used by the admin server as the model for managed
servers.. The managed servers are on the same machine.
When the admin server gives an application to a managed server, the managed
server creates a temporary directory containing all of the webapp
components, etc. The file timestamps on these files is the set by the
copying process to the time of the managed server boot (why?!?!????!?), so
the staleness check always thinks they are new and could care less what
precompiled jsps I have in my workingDir, the WEB-INF/classes directory, or
anywhere else. The pageCheckSeconds=-1 seems to be completely ignored in
this scenario.
If I tell the managed server to precompile everything on boot (about 45
minutes for this app) it will create versions of the classes that match the
new JSP file timestamps, but this does not even survive a reboot of the
managed server because it AGAIN creates a new temp version of everything on
the next reboot with new timestamps.
If I wait for the managed server to boot and find the directory like
.../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically copy
(via cp -pr to retain timestamps) all of the original webapp components on
top of the temp versions, the staleness checker is happy and the
pre-compiled versions work fine.
There HAS to be a way to package pre-compiled versions of the JSPs in the
"model" application in the admin server and keep from having to precompile
the JSPs on every managed server every time managed server is booted..
It would help if we had a way to bypass the staleness checking completely..
Or you guys should make the timestamps on the files copied by the
admin/managed deployment process match properly so the staleness checker
doesn't think the JSP is different.
It would also help if the engineer who wrote this could explain the rules
being implemented by the staleness checker. So far all the messages in the
newsgroup have amounted to point solutions for problems without a good
understanding of what the engine is checking for and/or doing under the
covers. Looking at the generated .java files for the JSP pages helps, but
it is not good enough...
Anyone out there have a working admin/managed server JSP application?
-Greg
Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
check out post 8366...i found that i was not preserving
the lastmodified date on my jsps and this was causing
unnecessary re-compilation.
hope it helps...
bobc
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
>I believe I have exhausted all permutations of EARing/notEARing,
>WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
>placing them in a static location and setting workingDir to that location,
>combinations of the above.
>
>No matter what, the managed server re-compiles pages the first time they
>are
>hit. Non admin/managed-server I have no problems.
>
>Can anyone from BEA comment on this problem? Or give me a workaround
>for
>getting a cluster working with precompiled jsps?
>
>-Greg
>
>"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
>news:[email protected]...
>> Grrr... The JSP engine is extremely frustrating! I've spent many hours
>> fighting the "staleness" checker in WL. I've been through all of the
>> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
>> pre-compilation working on single-server deployments, but admin/managed
>> server deployments have me beat.
>>
>> WL6.1, SP1, Solaris
>>
>> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
>> place. The fixed place contains pre-compiled versions of all jsps
>made on
>> that machine using jspc not 20 minutes earlier using the JSP files
>in the
>> exploded EAR file used by the admin server as the model for managed
>> servers.. The managed servers are on the same machine.
>>
>> When the admin server gives an application to a managed server, the
>managed
>> server creates a temporary directory containing all of the webapp
>> components, etc. The file timestamps on these files is the set by
>the
>> copying process to the time of the managed server boot (why?!?!????!?),
>so
>> the staleness check always thinks they are new and could care less
>what
>> precompiled jsps I have in my workingDir, the WEB-INF/classes directory,
>or
>> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
>in
>> this scenario.
>>
>> If I tell the managed server to precompile everything on boot (about
>45
>> minutes for this app) it will create versions of the classes that match
>th
>e
>> new JSP file timestamps, but this does not even survive a reboot of
>the
>> managed server because it AGAIN creates a new temp version of everything
>on
>> the next reboot with new timestamps.
>>
>> If I wait for the managed server to boot and find the directory like
>> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
>copy
>> (via cp -pr to retain timestamps) all of the original webapp components
>on
>> top of the temp versions, the staleness checker is happy and the
>> pre-compiled versions work fine.
>>
>> There HAS to be a way to package pre-compiled versions of the JSPs
>in the
>> "model" application in the admin server and keep from having to precompile
>> the JSPs on every managed server every time managed server is booted..
>>
>> It would help if we had a way to bypass the staleness checking
>completely..
>> Or you guys should make the timestamps on the files copied by the
>> admin/managed deployment process match properly so the staleness checker
>> doesn't think the JSP is different.
>>
>> It would also help if the engineer who wrote this could explain the
>rules
>> being implemented by the staleness checker. So far all the messages
>in
>the
>> newsgroup have amounted to point solutions for problems without a good
>> understanding of what the engine is checking for and/or doing under
>the
>> covers. Looking at the generated .java files for the JSP pages helps,
>but
>> it is not good enough...
>>
>> Anyone out there have a working admin/managed server JSP application?
>> -Greg
>>
>> -----------------------------------------------------------
>> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
>> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
>>
>>
>>
>
>
-
Problem with discovering Managed Servers
Hi,
I got problem with discovering managed servers, when I restart only administration
server while managed servers are running. During restart of admin server everything
seems to be ok (the directive: Starting discovery of managed server... appears
on the screen).
However when I start admin console through http, I cannot monitor performance,
browse logs etc. I can only shutdown managed server and I can see in a server
tag that particular managed servers are running.
I'm looking forward for any clues
MichalSorry,
i cannot stop those managed server - in Control tab I have active only option
to start those server but they are running. In logging tab when I want to browse
the log the message that probably this server is not running appear. However in
the tab when all servers are listened there is a message that they are running
"Michal" <[email protected]> wrote:
>
Hi,
I got problem with discovering managed servers, when I restart only administration
server while managed servers are running. During restart of admin server
everything
seems to be ok (the directive: Starting discovery of managed server...
appears
on the screen).
However when I start admin console through http, I cannot monitor performance,
browse logs etc. I can only shutdown managed server and I can see in
a server
tag that particular managed servers are running.
I'm looking forward for any clues
Michal -
Managed Servers not starting with options configured in config.xml
Hi,
I Installed an Weblogic 10.3 on a Red Hat system and i configured an domain and 2 managed servers.
I configured the servers with some java arguments like this:
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m
I do see in the ${DOMAIN_HOME}/config/config.xml the managed servers with the settings that I have configured it via the Web Gui Admin Console.
Now I want to start the Managed Servers with the following command:
+cd ${DOMAIN_HOME}/bin+
+./startManagedWebLogic.sh managed-server1 http://admin:port+
When i check the console, I don't see the correct JVM settings! Also other options that I configured in the Web Gui Admin Console, don't appear in the logfile.
The JVM settings I see, are those from the AdminServer.
How can I change/fix this?
Please help.
Kind regards,
WernerHi,
Please add the changes to the startup script startManagedWeblogic.sh.
You can add the memory args settings as "-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m"
Please let me know if it dosent fix. -
JMS topic-cache topic is not getting broadcasting in other managed servers
Hi All,
Please give me some idea in fixing the issue that im facing.
I have created the JMS topic in my weblogic console server which has 2 managed servers.
I have a feature in my application which is kept in a cache that will be used by my JMS topic. If my request hits managed 1 server im able to see the newly created feature.
But the same feature is not working when i make the request hit managed 2 server.
It means the JMS topic is not getting broadcasted properly in other managed server. I dont want to go for a server recycle which will resolve the issue.
Please let me know if im not clear enough.
Below is the description provided by my partner on the same issue in his words..
"The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.
The same problem is observed in Production as well. Let us know if there is anything wrong in the way the JMS Topic is created or any other configuration is missing, that is not allowing the proper functioning of the Topic."
fyi...i have all my firewall enabled between the managed servers.And multicast property is also declared correctly only.Please let me know if im not clear enough.No. Please explain again.
The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.Is it a distributed topic? Or does it mean a topic message doesnt get delivered to all subscribers?
ram. -
SCOM 2012 Get Gray Management Servers With PowerShell
Hi,
I have SCOM 2012 R2.
I want to get all the Management Servers that are in Gray state using powershell. How can I do that?
I couldn't find anything good in the internet.
The best I got was Get-SCOMManagementServer but when I tested it out - it still showed that my gateway's HealthState was "Success" even though it was gray.
Thanks,
Yakir.Hi,
Check if this one helps
Get-SCOMClass-name"Microsoft.SystemCenter.ManagementServer"|get-scomclassinstance|selectdisplayname,healthstate
I dont what is your final objective, but check this link
http://blogs.technet.com/b/jasonrydstrand/archive/2013/03/27/daily-scom-health-check-with-powershell.aspx -
Creating Weblogic domain with Admin Server and managed servers on different
I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.
Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056
Maybe you are looking for
-
Why Can't I use an Apple Gift card to buy an ipad!?!
So, I received an apple gift card for graduation from college. It was $500 and I wanted to use to buy an iPad. The person at the apple store said I was not allowed to use a gift card to pay for more than %50 of an iPad. My question is...WHY? They got
-
Volume control for specific programs.
Hi guys, I was wondering if there was an avalible mixer , that would allow unique volume contro lfor different programs. IN windows vista/7 the volume mixer gives you the option of turning up or down the volume for different applications instead of t
-
Okay, I want to be able to click anywhere and get the instance name of any object. The kicker is this actionScript needs to be on the main timeline and not on the movieClip. In other words, if I have one movieClip on the stage named "my_MC". I want t
-
Good morning, I am interested in thé mac book air, but until now i have been working with window xp and Microsoft office. Shall i be able to transfer and use all my document with à Mac ? And what about mails under Outlook ? Tank you for help
-
Can the airport express range be limited
I am getting ready to go off to college, and I know I'm going to get a power book. I want to get an airport express to use in my dorm because the school doesn't have wireless internet. However, wireless routers are not allowed on campus because of se