Issue listeneing queue from Weblogic Cluster server with multiple managed server

Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
  --ManagedServer01(http://server01.myhost.com:7001)
  --ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
  JMSserver01 targeting: ManagedServer01
  JMSserver02 targeting: ManagedServer02
  JMSmodule
  ConnectionFactory01 targeting:JMSserver01,JMSserver02
  UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
  mysystemmodule!JMSserver01@UDQueue01
  mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
  mysystemmodule!JMSserver01@UDQueue01 10
  mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
  mysystemmodule!JMSserver01@UDQueue01 0
  mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
  1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.

You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz

Similar Messages

  • 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>

  • JMS issues when migration from weblogic 9.2 to 10.3.5

    We are facing some issues when migration from weblogic 9.2 to 10.3.5
    In  weblogic 9.2 :_
    BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>
    Company
    </ejb-name>
    <entity-descriptor>
    <pool>
    <max-beans-in-free-pool>300</max-beans-in-free-pool>
    <initial-beans-in-free-pool>150</initial-beans-in-free-pool>
    </pool>
    <entity-cache>
    <max-beans-in-cache>3500</max-beans-in-cache>
    <idle-timeout-seconds>100000</idle-timeout-seconds>
    <read-timeout-seconds>0</read-timeout-seconds>
    <concurrency-strategy>ReadOnly</concurrency-strategy>
    </entity-cache>
    Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
    migration to Weblogic 10.3.5_
    With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
    Can some one look into this and provide your inputs to resolve this issue.

    I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
    Tom

  • JMX Connectivity has been discontinued with the managed server

    Dear all,
    I am getting following msg in my weblogic 11g manage server and admin server.
    Namage Server Log
    ####<Nov 22, 2010 2:15:39 PM IST> <Warning> <Log Management> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415539687> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    Admin Server Log
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <JMX> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-149507> <JMX Connectivity has been discontinued with the managed server NewTradeServer.>
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-002634> <The server "NewTradeServer" disconnected from this server.>
    ####<Nov 22, 2010 2:51:32 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417692374> <BEA-002635> <The server "NewTradeServer" connected to this server.>
    During this time my admin server in running, i can able to loggin to admin server console,
    Problem which i am faceing is that, i am not able to see the server status of that particular
    manage server, i am not able to see the any sub tabs statistic in Monitoring TAB of manage server, and after 1/2 and hours the manage server stop responding, then i restart the manage server and after that every thing work fine..
    any one have the solution for this error????///
    Regds
    Amar Shaw

    Kindly fing the log for the server problem time.
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.177.97.179:21,557 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.206.128.110:1,069 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 203.123.173.169:50,920 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.180.84.228:50,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,297 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.166.48.41:21,631 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.22.34.38:39,481 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 113.193.25.104:52,294 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.122:18,934 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.241.80.244:24,575 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 196.15.16.20:38,791 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 202.65.136.252:4,055 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,777 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 110.227.109.138:64,362 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.223.187:1,046 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 114.30.77.228:50,110 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.164.238.6:1,935 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 192.20.251.68:41,430 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 195.189.142.85:51,932 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:3,974 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 82.178.3.115:11,545 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.21.153.192:7,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.177.2.33:50,437 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.201.90.244:5,725 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 220.227.95.145:17,067 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.248.137.70:33,786 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:6,260 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.55.98:6,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.162.145.253:1,603 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,443 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,298 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 121.243.135.163:2,342 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,451 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 204.194.141.28:15,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.215.198.169:2,108 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:40,204 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,044 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.241.82.55:50,090 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.134.134:1,079 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.162.69.77:4,185 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:60,708 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 121.245.188.43:1,262 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 125.17.188.19:45,490 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.165.58.249:49,239 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.17.215.126:4,085 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 124.125.27.11:2,992 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:7,639 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.246.47.199:2,426 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.169.70.18:14,392 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:42,408 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.197.237.98:51,852 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.163.89.69:64,984 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 192.20.246.168:13,547 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:37,198 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:39,842 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,450 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.90.72.203:3,972 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:58,671 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,043 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.163.163.25:1,957 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 115.240.50.203:1,059 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.197.42.2:34,187 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.124.135.246:21,650 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 93.186.23.240:11,235 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.133:4,215 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.161.99.67:20,466 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <WebLogicServer> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576578> <BEA-000000> <WebLogic Server "NewTradeServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Notice> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576703> <BEA-170019> <The server log file D:\BEA11G\user_projects\domains\IndiabullsWLS\servers\NewTradeServer\logs\NewTrade_%yyyy%_%MM%_%dd%_%hh%_%mm%.log is opened. All server side log events will be written to this file.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576718> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Diagnostics> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576812> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "http" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "https" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:80
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576968> <BEA-002609> <Channel Service initialized.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576999> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000436> <Allocating 4 reader threads.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000446> <Native IO Enabled.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <IIOP> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577281> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578718> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578796> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_KNcrxQIcWPsGUMqWWNL3mWV+Tkc=>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579203> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579390> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Securit

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • How to control one server with multiple clients via TCP/IP

    I am wanting to control a single server with multiple clients.  Only one client would be active at a time, so there would be no conflict.  I want to use TCP/IP.  So far, I have programmed a cluster that passes data back to the server with no problems.  The challenge come in when a second client is added to the mix.  I have't been able to figure out how to turn each client on and send the appropriate data and then turn it off so it doesn't keep sending the same data to the server. 
    Here are the things that I have considered and did some preliminary testing, but don't really know how to impliment:
    1.  Send a numeric on the front of the cluster packet that tells the server that data is on the way.
    2.  Send a boolean on the front of the cluster packet to somehow turn the server TCP/IP on.
    The problem I have found is that LabVIEW TCP/IP doesn't like to be turned on and off.  If it doesn't get the data it expects, it goes into a reset mode and that kills the response time.
    Any help?

    You should consider implementing a set of simple one-byte commands that can be sent back and forth between the Server and the Clients. You can base all of these ideas off the example in the Example Finder under Networking >> TCP and UDP called Multiple Connections - Server.
    You will have two loops in the server VI: one to wait for new connections, and one to send and receive data from the existing connections. For instance, after one of the clients connects, it can request control of the server to send data to it by sending the character "R" for request. Every time the send/receive loop of the Server executes, the first thing it can do is to check all the existing connections to see if any of the clients have sent a control request ("R"). If so, it will create a buffer (array) of control requests. This could be in the form of Connection IDs or indexes in the array for a particular Connection ID. Your choice.
    After the Server receives a request for contol, if it is not already under control by another client, then it can send a response to the first client on the control request list. For instance, the server could send the first client a "S" command for send. Note that after the clients send their control request, they should execute a TCP Read and wait indefinitely for the server to respond with the one-byte "S" command. Then, once the client in control is finished sending data to the server, it could send the character "X" telling the Server to release it from control.
    The example I mentioned above already does a similar thing. Note how when a client wants to disconnect, they send the letter "Q". You can see this in the Multiple Connections - Client VI. The Server then checks each individual connection to see if it's received this one-byte command, and if it has, it closes the connection to the client. This is what you would want to implement, but instead of having just one command, you'll have to distinguish between a few and build up a buffer of control requests.
    Finally, if a client does decide to disconnect in your application, they could send the command "Q" just like the example above. At this point, close the connection and remove that Connection ID from the array of connections. You will also have to handle the case that this client was in the request control waiting line when it disconnected, in which case you need to delete it from that array as well.
    This will definitely work for you, but it will take some work. Best of luck!
    Jarrod S.
    National Instruments

  • Replacing a windows server with a Mac server

    Hi all,
    So this is a big company with about 150 employees using PC's (win xp and 7), considering replacing the current Windows server with a Mac server.
    Is it possible to give users profiles once they log in like Windows server does? So when the user logs in they get to their own personal stuff? Can Mac server do that?
    Can the user also get to the default printer and send prints to it regardless where they log in from inside the company?
    And can the home directory to each user NOT be copied anywhere on the local machine where they log in? Meaning that after they log out there will be no traces to their files on that local PC..
    Thanks a lot in advance!!

    By some standards, 150 is not "big" but a large small business :-)
    Regardless, please plan and test and plan some more, very carefully !
    The picture for what you want to do once looked far better with 10.6 server but that had its limitations as well.
    With 10.6 server, Apple was using Samba - they are no longer doing so,
    but/and the version of Samba they were using only provided NT-Domain level support.
    So that would not work with your Win 7 stations either. But could be made to work relatively well with XP workstations. You can no longer buy any new Mac that runs 10.6 server and 10.6 server would be hard to obtain.
    Not a great route to go.
    Bear in mind that the key problem with Apple's Samba was that Samba changed their licensing,
    and there's not a thing in the world Apple could do to implement a current version of Samba without violating their own operating principles and the licensing requirements.
    You'll be heading into heavily uncharted territory here. Odds are good that any desired domain-functionality is not going to work for you.
    Honestly, Apple appears to have thrown in the towel on directory-level support for Windows,
    and the best way to support Windows workstations in that regard is with Windows server and AD.
    Basic filesharing works, with some caveats.
    If there's no AD involved at all, then have a look at my earlier post,
    https://discussions.apple.com/thread/3206725?start=47
    Which worked a-ok for me but your mileage may vary.
    Samba new current versions and GPL3 licensing issue:
    https://discussions.apple.com/thread/3206725?start=75&tstart=0
    "GPLv3 makes it impossible to provide signed binaries without also providing the signing keys. A few seconds of thought will reveal why Apple is unwilling to provide copies of the keys they use to sign system software. Part of locking down OS X security profile required removing anythign that used GPLv3.
    Short version: GPLv3 is specifially desinged to be anti-company, and you are going to see a ever widening schism in the FSS/OSS community between GPL and all the other licenses, and you will be seeing less and less GPL code in commercial OSes and more BSD/Apache/&c code."
    http://discussions.apple.com/thread.jspa?messageID=12494378

  • Replace KMS server with same-named server

    I need to replace my KMS server (win2008r2) with a new server (win2012r2), but with the original server’s name.
     This is my plan:
          Shutdown the current KMS server and remove it from AD, WINS & DNS
          Rename the new server with the old server’s name
          I have already added the VAMT role to the win2k12 server, but not configured it
          Install our KMS VL & run the office 2013 volume license pack on the new server
      Does anyone see any problems with this plan? 
    Do I need to uninstall the KMS key from the original server first?
     What kinds of issues will the users see before the 25 client activations happen?
     Thanks!

    This is fine.    
    KMS is resolved via a DNS Service record: _vlmcs._tcp.<domainname>
    Whenever you are finished installing KMS on the new server, ensure the SRV record is correct.
    NOTE: Remember the new KMS server will not start to activate clients until the thresholds are met.  (5 servers or 25 clients)
    - Chris Ream -
    **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

  • Problem with starting managed server

    In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
    Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
    Message icon - 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.
    Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
    <Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at com.certicom.tls.record.ReadHandler.read(Unknown Source)
         at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
         at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
         at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
         at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
         at java.io.InputStreamReader.read(InputStreamReader.java:167)
         at java.io.BufferedReader.fill(BufferedReader.java:136)
         at java.io.BufferedReader.readLine(BufferedReader.java:299)
         at java.io.BufferedReader.readLine(BufferedReader.java:362)
         at weblogic.nodemanager.server.Handler.run(Handler.java:66)
         at java.lang.Thread.run(Thread.java:619)
    Can any one help me to troubleshoot this.

    Hi Jose,
    To Disable SSL communication for NodeManager do the following:
    <b><font color=maroon>Step1).</font></b> Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
    SecureListener=false
    <b><font color=maroon>Step2).</font></b> Login to AdminConsole and then
    AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
    <b><font color=maroon>Step3).</font></b> Restart the NodeManager ....better if you follow Step4) as well...
    <b><font color=maroon>Step4).</font></b> Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
    Thanks
    Jay SenSharma

  • SP2013: Scaling search with multiple app server

    Hi Team,
    I am scaling a new SP environment with multiple App Server.
    I have used AutoSPINstaller to install SP2013 and Search. My search components are spread across all servers. All Search components on all servers and I have a blank publishing site as part of my content source.
    My issue is when i start full/Incremental crawl. It keeps on crawling for the whole day and do not produce any crawl error neither it stops. We waited for even 2 das but the crawl kept on going on.
    Any help will be really appreciated.
    Thanks Ba$va

    Hi Basva ,
    Follow these steps (one at the time) to reset the Content Source crawl:
    Start -> Run -> Services.msc -> Restart the “SharePoint Server Search 15”.
    Make sure  the Application Server Administration Service Timer Job working .
    Navigate to Central Administration-> Manage service application->
    Search Service Application,
    Reset Index and see if that fixes the problems.
    Go into the Services.msc  on each server and change the "RECOVERY" method of the “SharePoint Server Search 15” from "FIRST FAILURE"  to "TAKE NO ACTION" so that the service did not restart before
    all the servers had their "SharePoint Server Search 14" stopped.
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Logon problem with oracle management server

    I have problem with Oracle Management Server when I connect to the OMS message comes
    The exception (java.lang.NullPointerException) occurred.
    if any body have any idea pls tell us

    Hi,
    Oracle has changed the Enterprise Manager from version 1.5 to 2.0 .
    With the new Oracle8i dataase server another service has been added.
    If you want to user the OEM you have to install The Managment Server.
    The Managment server has its own user and privileges and is recommended when using OEM.

  • How does create a server with multiple Clients ?

    Any people can lead me .
    How does create a server with multiple Clients ?
    Thanks

    For a multithreaded server you will need a thread to listen and at least one thread per client. If the conversation is half duplex, one thread per client works very well, if it's full duplex you will find one thread to send and one to receive much easier to program.
    I posted a Simple Socket Server that uses 1+2*clients threads.

  • Sql server with multiple instance

    hi  All,
    i want  to  install sql server with two instance   and i want  to assign two  separate is  ips   for  both   default instance  and named  instance   and  both   should  work like
    two different server
    note:  If i  logged  with  one  ip(default instance)   it should  show  its  own  databases  not both or  named   instance  databases
    thanks 
     chintala

    Hi chintala,
    According to your description, if you want to assign the two different IP to stand for default instance 
    and named  instance, I recommend you set up aliases on a SQL Server with multiple instances. For example, a physical server is named WinServer and 2 instances of SQL Server named WinServer and WinServer\instance1.
    We need to add 1 IP addresse to the WinServer, there is one IP address already assigned to WinServer, 192.168.1.1, by adding one new IP's, 192.168.1.2 .
    We need to move into DNS to configure our host names and aliases.  The physical machine must be steup as a static IP in DNS. SQLAlias1, which point to the default instance on WinServer, will be setup as a DNS with an address of 192.168.1.1.
    SQLAlias2, which will point to WinServer\Instance1, will be setup as a new Host (A) record in DNS with an address of 192.168.1.2.
    When everything has been completed on the DNS side, you need to open up SQL Server Configuration Manager on WinServer and configure the protocols for each instance one at a time, restart the 3 SQL services.
    For more information about how to set up aliases on a SQL Server with multiple instances, you can review the similar article.
    http://kevine323.blogspot.com/2013/08/setting-up-aliases-on-sql-server-with.html
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • WOL question. SCCM server with multiple nics.

    Hi,
    I have a sccm server with multiple nics, I can wake up any machine using a 3ed party magic packet utility, if I set a schedule and use sccm wol functionally the machine never wakes up. As I pointed out my server has multiple nics, does anyone have a sccm
    server with multiple nics with sccm built in wol functionally working?. I am curious on how you achieved this.

    Hey Garth,
    Yes the problem is solved but we had to buy a 3rd party power management utility to accomplish WOL. Because we have many different subnets in our environment we found that this was the fastest way to get WOL working,
    So out of the box SCCM would not work for us, with a 3rd party utility that had an SCCM plugin WOL now works flawlessly.

  • Any Guidelines on Configuring Weblogic 8.1 with Node Manager

    Hi All, I want to configure Weblogic 8.1 with Node Manager using 4 ports. Is there any step by step guide? Please let me know...
    Currently I am referring to this link:
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/nodemgr.html
    Thanks.

    Hi,
    Hope the below link may be little helpful: http://middlewaremagic.com/weblogic/?p=971
    NOTE: you need not to follow Step8). mentioned in above link because.... WLS8.1 nmEnroll() is not available as part of WLST ...In WLS8.1 no need to start the NodeManager. You can also ignore the Clustering part in the above link ...rest all you need to follow.
    Thanks
    Jay SenSharma

Maybe you are looking for