Starting SOA server using proxy fails with exception

Hi,
The problem is as mentioned in the subjet.
In console-servers-soa server - server start - arguments , I have entered
-Dhttp.proxyHost=XX.XX.140.2 -Dhttp.proxyPort=80
When i try to start the server, I get this in the log:
Listen Address server1:8001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
<Jan 19, 2011 1:10:23 PM CST> <Info> <Server> <BEA-002609> <Channel Service initialized.>
<Jan 19, 2011 1:10:24 PM CST> <Info> <Socket> <BEA-000436> <Allocating 2 reader threads.>
<Jan 19, 2011 1:10:24 PM CST> <Info> <Socket> <BEA-000446> <Native IO Enabled.>
<Jan 19, 2011 1:10:24 PM CST> <Info> <IIOP> <BEA-002014> <IIOP subsystem enabled.>
<Jan 19, 2011 1:10:53 PM CST> <Error> <Net> <BEA-000903> <Failed to communicate with proxy: XX.XX.140.2/80. Will try connection admin/7001 now.
java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.1 403 Forbidden'
at weblogic.socket.utils.ProxyUtils.getProxySocket(ProxyUtils.java:206)
at weblogic.socket.utils.ProxyUtils.getClientProxy(ProxyUtils.java:221)
at weblogic.socket.SocketMuxer.newClientSocket(SocketMuxer.java:345)
at weblogic.socket.ChannelSocketFactory.createSocket(ChannelSocketFactory.java:79)
When i tried the below cmd from my soa server console,
wget www.yahoo.com
I get proper response.
oracle@server:/data/oracle/domains/soau_domain/servers/soa_server01_01/logs> wget www.yahoo.com
--2011-01-19 13:50:33-- http://www.yahoo.com/
Resolving proxy.sample.local... XX.XX.140.2
Connecting to proxy.sample.local|XX.XX.140.2|:80... connected.
Proxy request sent, awaiting response... 302 Found
Location: http://au.yahoo.com/?p=us [following]
--2011-01-19 13:50:34-- http://au.yahoo.com/?p=us
Connecting to proxy.sample.local|XX.XX.140.2|:80... connected.
Proxy request sent, awaiting response... 200 OK
Length: unspecified [text/html]
So looks like proxy server is reachable from soa server.
Can anyone help me with where this could be getting wrong?
Thanks
Ganesh

java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.1 403 ForbiddenThis looks like that the proxy is expecting an username from soa server for authentication and you have not configured soa server to send the username/password to authenticate at the proxy server. I am not sure if soa server has a way to specify username/password for proxy authentication, but a workaround we used to do in an earlier version of OSB ( ALSB 2.5, where there was no provision to specify proxy authentication crdentials) was to add the URL's you want to access via proxy, to the 'proxy-free-list' of the proxy server. A proxy wont prompt for username/password for accessing an URL which is in its 'proxy-free-list'.

Similar Messages

  • Unable to start soa server with anonymous attempt to JNDI resource error

    I created a new outbound connection in my JMS Adapter deployment then I also created a new Foreign Server in my JMS Module that is deployed on my SOA server.
    Now when i try to restart my SOA server it is failing with the below exception.
    <Jul 1, 2011 10:43:23 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.SecurityException: Anonymous attempt to get to a JNDI resource
    java.lang.SecurityException: Anonymous attempt to get to a JNDI resource
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:194)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)
    I have deleted the outbound connection as well as the new Foreign server but still when restarting I am getting the same error.
    How can I fix this?
    This is blocking me from doing my development work.
    Thanks,
    Rajesh

    Can you check the config.xml of the domain and see if you are still having any references to the JNDI name you had used? If yes try removing the references manually and save the file and then restart the server. PLEASE TAKE A BACKUP OF THE config file before doing so.
    Thanks,
    Patrick

  • Unable to start SOA server through Node Manager

    Hi All,
    I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
    I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
    Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
    Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
    I am getting an error while trying to start soa server with nmStart() command, below is the error message...
    "Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
    I executed the dumpStack() command, and i am getting the output as "No stack trace available"
    If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
    I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
    I followed some of the blogs like...
    http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
    http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
    Experts, please give your advice.
    Many Thanks,
    N

    Hi Narsing,
    I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
    Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
    As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
    Regards,
    Neeraj Sehgal
    Hi Neeraj,
    I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
    I have made sure the property StartScriptEnabled= true.
    I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
    If i see the log messages in the nodemanager.log, this is the below message...
    <Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
    <Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    The log message in the soa_server1.out file is as below...
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
    <Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
    Many Thanks.

  • Problem in starting weblogic server as proxy

    I am using weblogic server as Proxy to forward the requests to weblogic cluster.
    When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
    I am Pasting my complete logs below.
    Setting JVM memory params for server IRISProxy
    Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
    WLS Production Mode=true
    ./startWebLogic.sh[68]: B: not found.
    maxfiles=8192
    CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.4.1.05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
    Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
    Starting WLS with line:
    /home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
    Bad level value for property: com.iplanet.services.debug.level
    Bad level value for property: com.sun.identity.agents.logging.level
    Bad level value for property: com.sun.am.policy.amFilter.audit.level
    <Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
    WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
    WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
    WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
    <Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
    <Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
    java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
         at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
         at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
         at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
    >
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
    Can someone help me in solving this problem
    Thanks
    Kris

    I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
    WebLogic Temporary Patch for CR211812
    WebLogic Temporary Patch for CR235145
    Once i commented the above patches in the CLASSPATH.
    The issue is resolved.

  • Unable to start Manager server using Node Manager

    Hi,
    I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    Managed server log: -
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    [root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    Nodemanager log:
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
    <Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
    <Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)

    You can start a managed server as follows:
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');
    print 'CONNECT TO ADMIN SERVER';
    connect(adminusername, adminpassword);
    print 'START MANAGED SERVER';
    start('VideotheekWebServer','Server');
    nmServerStatus('VideotheekWebServer');
    print 'START CLUSTER';
    start('VideotheekCluster','Cluster');
    nmServerStatus('VideotheekServer1');
    nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
    The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

  • Starting Manage Server using node manager

    Hi,
    Hi,
    I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    plz help me out in this
    Thanks in advance

    An example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
    "By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped."

  • Attempt to process file failed with Exception in XML Parser-format problem

    Hi all,
    Iam getting an unusual error in the J2EE stack in XI.
    And the message is:
    006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
    This means that error occured during content conversion of XML to the prescribed file format.
    Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
    Thanks in advance...
    karun

    Hi Bhavesh,
    Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
    The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
    2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
    2006-11-30 17:30:50 Success Start converting XML document content to plain text
    2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
    2006-11-30 17:31:07 Error Exception caught by adapter framework: null
    2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
    2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
    2006-11-30 17:31:07 Success The message status set to WAIT.
    2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
    2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
    2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

  • Errors while starting admin server using WLST and NodeManager

    Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
    thanks
    manohar
    C:\oracle\Middleware\wlserver_10.3\server\bin>
    C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
    Connecting to Node Manager ...
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
    loading of the trusted certificate list raised a certificate parsing exception
    PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
    \,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
    arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
    0.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
    of the trusted certificate list raised a certificate parsing exception PKIX: Un
    supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : I/O error while reading domain directory
    Use dumpStack() to view the full stacktrace
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline> dumpStack()
    This Exception occurred at Tue May 03 10:45:03 EDT 2011.
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:299)
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:312)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
    a:248)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:199)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:205)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
    java:52)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
    eManagerService.java:179)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
    rService.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
    at org.python.pycode._pyx2.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.pycode._pyx16.f$0(<console>:1)
    at org.python.pycode._pyx16.call_function(<console>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.core.Py.exec(Unknown Source)
    at org.python.util.PythonInterpreter.exec(Unknown Source)
    at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.WLST.main(WLST.java:29)
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    wls:/offline>
    wls:/offline>

    Hi manohar,
    Please try the following article... (With Node Manager Communication type as "Plain" because it looks like you are getting PKIX security certificate chain message ) Just to isolate the issue
    Topic: Start AdminServer And NodeManager Using WLST
    http://middlewaremagic.com/weblogic/?p=6580
    Thanks
    Ravish Mody

  • Starting admin server using WLST and NodeManager

    Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
    thanks
    manohar
    C:\oracle\Middleware\wlserver_10.3\server\bin>
    C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
    Connecting to Node Manager ...
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
    =T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
    e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
    ithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
    loading of the trusted certificate list raised a certificate parsing exception
    PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
    \,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
    arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
    0.113549.1.1.11.>
    <May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
    sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
    of the trusted certificate list raised a certificate parsing exception PKIX: Un
    supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : I/O error while reading domain directory
    Use dumpStack() to view the full stacktrace
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline>
    wls:/offline> dumpStack()
    This Exception occurred at Tue May 03 10:45:03 EDT 2011.
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:299)
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
    nt.java:312)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
    a:248)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:199)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
    ent.java:205)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
    java:52)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
    eManagerService.java:179)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
    rService.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
    at org.python.pycode._pyx2.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.pycode._pyx16.f$0(<console>:1)
    at org.python.pycode._pyx16.call_function(<console>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.core.Py.exec(Unknown Source)
    at org.python.util.PythonInterpreter.exec(Unknown Source)
    at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.WLST.main(WLST.java:29)
    weblogic.nodemanager.NMException: I/O error while reading domain directory
    wls:/offline>
    wls:/offline>

    Hi manohar,
    Thank you, Pierluigi for encouraging Middleware Magic Team :)
    manohar, apart from what *"Pierluigi"* has suggested, additionally please notice the following messsage in your StackTrace (whih is basically a NOTICE message but does not look good)
    The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object:In your case it looks like the actual issue is your Certificate which comes by default with JDK. As mentioned in this BUG.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022
    Additionally please refer to the following Thread:
    http://forums.oracle.com/forums/message.jspa?messageID=3958098#3958098
    I am suspecting that you need to do the following in order to get rid of Certificate Errors which is the ROOT cause of your issue
    Do the following: After taking a backup of *"$JAVA_HOME/jre/lib/security/cacerts"* file
    cd $JAVA_HOME/jre/lib/security
    cp -p cacerts cacerts.original
    chmod 644 cacerts
    keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
    keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacertsAlso try with Node Manager Communication type as "*Plain*" because it looks like you are getting PKIX security certificate chain message, just to isolate the issue.
    Regards,
    Ravish Mody

  • Starting WebLogic Server using Console

    This is a simple question. I am trying to start the WebLogic Server
    using the WebLogic Console. It seems to be starting the wrong WebLogic
    server.
    When I monitor the log information in the console I see it starts the
    server with a 32ms and a 32mx whereas in my startWebLogic.sh script I
    have specified 128ms and 128mx. How do I make my startconsole.sh script
    read the correct startWebLogic.sh script ? This is on solaris.
    When I ran the script startWebLogic.sh it was able to start up
    completely.
    Thanks.

    Ted,
    Thanks for the reply. Just another question on this-I have added a lot of jar files to the
    WEBLOGICCLASSPATH in my startWebLogic.sh script. I presume since I am starting the server using the
    console I need to add this information(the WEBLOGICCLASSPATH variable) to the startConsole.sh script
    and try running the server again.
    Currently its reporting that its unable to find the server classes which I wrote.
    Aswin.
    Ted Dyer wrote:
    Aswin,
    Sorry for the confusion. When you start the server in the console, you get a dialog window. There
    is a button labled "Advanced..." Click on that and set the "Java Heap (MB)" to 128. That will do
    what you want it to.
    Ted
    Aswin Dinakar <[email protected]> wrote:
    Ted,
    I guess I was not clear on my problem. When I start the weblogic server using the
    weblogic console it doesnt seem to be running the startweblogic.sh script. It seems to be
    running another version of the startweblogic.sh script which I dont know where its getting
    from.
    Aswin.
    Ted Dyer wrote:
    Aswin,
    Did you edit your startConsole.sh? The last line in that file should set your ms and mx.
    It should say something like:
    $JAVA -ms16m -mx48m -classpath $JAVACLASSPATH weblogic.Console
    Changing the ms and mx values here should have the affect you're looking for.
    Ted
    Aswin Dinakar <[email protected]> wrote:
    This is a simple question. I am trying to start the WebLogic Server
    using the WebLogic Console. It seems to be starting the wrong WebLogic
    server.
    When I monitor the log information in the console I see it starts the
    server with a 32ms and a 32mx whereas in my startWebLogic.sh script I
    have specified 128ms and 128mx. How do I make my startconsole.sh script
    read the correct startWebLogic.sh script ? This is on solaris.
    When I ran the script startWebLogic.sh it was able to start up
    completely.
    Thanks.

  • Approval task SP09: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'

    Hi everyone,
    I just installed SP09 and i was testing the solution. And I found a problem with the approvals tasks.
    I configured a simple ROLE approval task for validate add event. And when the runtime executes the task, the dispatcher log shows a error:
    ERROR: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'
    And the notifications configured on approval task does not start either.
    The approval goes to the ToDO tab of the approver, but when approved, also the ROLE stays in "Pending" State.
    I downgraded the Runtime components to SP08 to test, and the approvals tasks works correctly.
    Has anyone passed trough this situation in SP09?
    I think there is an issue with the runtime components delivered with this initial package of SP09.
    Suggestions?

    Hi Kelvin,2016081
    The issue is caused by a program error in the Dispatcher component. A fix will be provided in Identity Management SP9 Patch 2 for the Runtime component. I expect the patch will be delivered within a week or two.
    For more info about the issue and the patch please refer to SAPNote 2016081.
    @Michael Penn - I might be able to assist if you provide the ticket number
    Cheers,
    Kristiyan
    IdM Development

  • Servlet failed with Exception java.lang.LinkageError: Class javax/servlet/ServletConfig

              Hi
              I registered a web app with Weblogic 5.1 in the weblogic.properties file. I try
              to run the web app from my browser typing http://localhost:7001/xxx(Webapp name)
              and a jsp page. Following is the error I get. It would be helpful if some one
              could point me to a fix for this problem
              Tue May 01 13:56:41 CDT 2001:<I> <ServletContext-omxclient> Generated java file:
              D:\weblogic\myserver\omxclient\_tmp_war\jsp_servlet\_omx\_login.java
              Tue May 01 13:56:43 CDT 2001:<E> <ServletContext-omxclient> Servlet failed with
              Exception
              java.lang.LinkageError: Class javax/servlet/ServletConfig violates loader constr
              aints
              at jsp_servlet._omx._login._jspService(_login.java:59)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:105)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:123)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:742)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:686)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java:247)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a:361)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

              Sorry, I didn't look very closely - the exception is for
              javax.servlet.ServletConfig - should be in weblogicaux.jar.
              Is there anything wrong with it? What service pack are you
              using? Could be a problem with weblogic.policy.
              mike
              >>java.lang.LinkageError: Class javax/servlet/ServletConfig
              "KC" <[email protected]> wrote:
              >
              >Hi Mike
              >The login.jsp page just contains a javascript function and two text boxes
              >in it.
              >Will try making changing it. If that is not the issue could you let me
              >know of
              >any other issues.
              >
              >"mreiche" <[email protected]> wrote:
              >>
              >>I would guess that login.jsp is a very large JSP and that
              >>the generated service method is too large for the classloader's
              >>liking. Try making it smaller.
              >>
              >>Mike
              >>
              >>
              >>"KC" <[email protected]> wrote:
              >>>
              >>>Hi
              >>>I registered a web app with Weblogic 5.1 in the weblogic.properties
              >>file.
              >>>I try
              >>>to run the web app from my browser typing http://localhost:7001/xxx(Webapp
              >>>name)
              >>>and a jsp page. Following is the error I get. It would be helpful if
              >>>some one
              >>>could point me to a fix for this problem
              >>>
              >>>Tue May 01 13:56:41 CDT 2001:<I> <ServletContext-omxclient> Generated
              >>>java file:
              >>> D:\weblogic\myserver\omxclient\_tmp_war\jsp_servlet\_omx\_login.java
              >>>Tue May 01 13:56:43 CDT 2001:<E> <ServletContext-omxclient> Servlet
              >>failed
              >>>with
              >>>Exception
              >>>java.lang.LinkageError: Class javax/servlet/ServletConfig violates
              >loader
              >>>constr
              >>>aints
              >>> at jsp_servlet._omx._login._jspService(_login.java:59)
              >>> at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              >>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              >>>pl.java:105)
              >>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              >>>pl.java:123)
              >>> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              >>>textImpl.java:742)
              >>> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              >>>textImpl.java:686)
              >>> at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              >>>ContextManager.java:247)
              >>> at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              >>>a:361)
              >>> at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              >>>
              >>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >>>
              >>>
              >>
              >
              

  • Add-on 9000005 failed with exception; Event Type: 1

    Hi Experts,
    I am woking on a project which uses DI API and creates AP Invoice by reading an excel file.
    I used all the invoice in one sap transaction.
    I read excel line by line and create one AP Invoice per line. It works when excel is having less then 500 records. But if there are more then 500 records or more then 600 records, it give following error to me
    Add-on 9000005 failed with exception; Event Type: 1
    Can anyone help me in it?
    Thanks!!
    Ritu

    Hi,
    I'm sure there is a limit to the number of rows you can add to an Invoice but I think it's probably limited on memory rather than a fixed limit on the number of rows.  This might be an out of memory error that's causing the exception.  Have you tried putting a try/catch around your code to see what the exact details are of the exception?  Also, if you are filling in any text fields on the invoice (remarks), they are limited to 30K.
    David

  • SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

    Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
    Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
    Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
    at Teradata.Client.Provider.WpMessageManager.CheckForError()
    at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
    at Teradata.Client.Provider.WpLogonManager.Action()
    at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
    at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
    at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
    at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
    at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
    at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
    at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
    at Teradata.Client.Provider.TdConnection.Open()
    at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
    at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
    at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
    at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
    End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
    Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
    Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
    End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
    Description: There were errors during task validation. End Error
    DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
    Elapsed: 6.692 seconds. The package execution failed. The step failed.
    SQL Server agent job fails with above error, Please let me know process tohandle it.
    Thanks,
    Vishal.

    The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Non-SysAdmins get error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.

    I have a SQL 2008 R2 system (10.50.4000) where I'm having problems connecting any user that is not a SysAdmin.  Example: I setup a new SQL Login to use Windows Authentication and grant that user db_datareader on the target database.  The user attempts
    to connect using Excel client or Access or SQL Management Studio and receives Error 18456.  The SQL Server Logs shows Error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    The strange part is that if I temporarily grant the user the sysadmin server role then the user can connect successfully and retrieve data.  But, if I take away that sysadmin server role then the user can no longer connect but again receives the Error
    18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    We've turned off UAC on the client machine to see if that was the problem, but no change.
    I have dropped and re-added the user's SQL Login (and the related database user login info).  No success.
    The Ring Buffers output shows:
    The Calling API Name: LookupAccountSidInternal
    API Name: LookupAccountSid
    Error Code: 0x534
    Thanks for any help.
    -Walt

    Yes, you understand correctly.  The user is logging onto a workstation (not the server) with a Windows Authenticated id.  The user is using either Excel or Access or SSMS and connecting to the server using a Windows Authenticated SQL Login account.
     If the account has sysadmin role (which is only for testing) then the connection is successful.  If I take away sysadmin role from the account then the connection is unsuccessful and the SQL Server Log shows Error
    18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    (SQL Authentication is not an option here.  I must use Windows Authentication).
    Any other troubleshooting assistance you can offer would be appreciated.  Thanks.
    -Walt 

Maybe you are looking for

  • Jabber on Android and CUCM 8.6.2

    Hello. We are trying to use jabber on a galaxy android tablet, but we can't register client to CUCM 8.6.2. I've followed this guide: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a0080bb5104.shtml for cucm co

  • Third party PO - Intercompany

    Hello, I need to know if third party PO is applicable to intercompany process. I will try to explain: One of my plants buy to vendor  a stock material, but the receipt will be made in another plant. The vendor bill to the buyer plant and dispatch to

  • Issues With Permissions With iTunes/iMac

    Hey there - I hope someone out there can help me. I have all my media files (music, movies etc) on the MacHD. There are two profiles on the iMac...for myself and my partner. I have over 200 gigs of stuff that we both pull from. Lately, my partner is

  • Basis HR

    Hi All, Sorry if i am in wrong thread.Its related to HR so i thought this thread would be the right one. I am Basis Consultant and for the first time i am going to implement HR Module. I need some help or documentation and not only that i want to kno

  • Query processor ran out of internal resources

    I have a query in the following format where @ID takes about 20000 IDs.  select * from students where name in (@ID)  Because of the high amount of IDs in the list, I'm getting the error that "query processor ran out of internal resources and could no