Weblogic 10.3.6 Error With SharedLibrary Unresolved Webapp Library references - weblogic
I'm trying to deploy a shared library as a webapp and have access to the libraries there reciden from another webapp.
My application server is WebLogic 10.3.6, my jdk is 1.6 JRockit
My WebApp with shared libraries is called clares_shared-0.1.0.BUILD-SNAPSHOT.war and is generated with maven.
within that webapp, in the META-INF directory I created the MANIFEST.MF file which contains the following:
Manifest-Version: 1.0
Specification-Title: Common libraries Clares
Specification-Version: 1.0
Implementation-Title: Common libraries Clares
Implementation-Version: 1.0
Extension-Name: clares_shared-0.1.0.BUILD-SNAPSHOT
when ant deploy this webapp via the log he says:
K:\Development\CLA_RES\clares>ant deploy_shared
Buildfile: build.xml
deploy_shared:
[wldeploy] weblogic.Deployer -debug -remote -verbose -upload -noexit -name clares_shared-0.1.0.BUILD-SNAPSHOT -source K:\Development\CLA_RES\clares\clares_shared\target\clares_shared-0.1.0.BUILD-SNAPSHOT.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy -library
[wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -upload -noexit -name clares_shared-0.1.0.BUILD-SNAPSHOT -source K:\Development\CLA_RES\clares\clares_shared\target\clares_shared-0.1.0.BUILD-SNAPSHOT.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -deploy -library
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7001
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache#a1bbe4
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache#a1bbe4
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#a33ce3
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#a33ce3
[wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: CLARES_base_domain
[wldeploy] [ServerConnectionImpl.setRemote():480] : Running in remote mode
[wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl#cfd032
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=clares_shared-0.1.0.BUILD-SNAPSHOT}, targeted=true
[wldeploy] [BasicOperation.deriveAppName():141] : appname established as: clares_shared-0.1.0.BUILD-SNAPSHOT
[wldeploy] <19-ago-2016 09H32' CLT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, clares_shared-0.1.0.BUILD-SNAPSHOT [archive: K:\Development\CLA_RES\clares\clares_shared\target\clares_shared-0.1.0.BUILD-SNAPSHOT.war], to AdminServer .>
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=clares_shared-0.1.0.BUILD-SNAPSHOT}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():628] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] AdminServer
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: C:\Users\ODONAT~1\AppData\Local\Temp\odonatafly\.\config\deployments\clares_shared-0.1.0.BUILD-SNAPSHOT
[wldeploy] App config: C:\Users\ODONAT~1\AppData\Local\Temp\odonatafly\.\config\deployments\clares_shared-0.1.0.BUILD-SNAPSHOT\plan
[wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=true,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=clares_shared-0.1.0.BUILD-SNAPSHOT,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
[wldeploy]
[wldeploy] [ServerConnectionImpl.upload():849] : Uploaded app to C:\Oracle\Middleware\user_projects\domains\CLARES_base_domain\.\servers\AdminServer\upload\clares_shared-0.1.0.BUILD-SNAPSHOT
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, clares_shared-0.1.0.BUILD-SNAPSHOT, on targets:
[wldeploy] [BasicOperation.execute():447] : AdminServer
[wldeploy] Task 50 initiated: [Deployer:149117]deploy library clares_shared-0.1.0.BUILD-SNAPSHOT on AdminServer.
[wldeploy] Task 50 completed: [Deployer:149117]deploy library clares_shared-0.1.0.BUILD-SNAPSHOT on AdminServer.
[wldeploy] Target state: deploy completed on Server AdminServer
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + clares_shared-0.1.0.BUILD-SNAPSHOT AdminServer
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
BUILD SUCCESSFUL
Weblogic Console
The webapp from which I want to access the SharedLibrary is called:
clares_web-0.1.0.BUILD-SNAPSHOT.war
is created with maven and the weblogic.xml file have the following:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
<container-descriptor>
<prefer-web-inf-classes>false</prefer-web-inf-classes>
</container-descriptor>
<library-ref>
<library-name>clares_shared-0.1.0.BUILD-SNAPSHOT</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
<exact-match>false</exact-match>
</library-ref>
</weblogic-web-app>
when I try to deploy this webapp (clares_web) says the following error:
K:\Development\CLA_RES\clares>ant deploy_web
Buildfile: build.xml
[wldeploy] weblogic.Deployer -debug -verbose -noexit -name clares_web-0.1.0.BUILD-SNAPSHOT -source K:\Development\CLA_RES\clares\clares_web\target\clares_web-0.1.0.BUILD-SNAPSHOT.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -debug -verbose -noexit -name clares_web-0.1.0.BUILD-SNAPSHOT -source K:\Development\CLA_RES\clares\clares_web\target\clares_web-0.1.0.BUILD-SNAPSHOT.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -deploy
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7001
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: true
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache#a07de5
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache#a07de5
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#a1ffa6
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache#a1ffa6
[wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: CLARES_base_domain
[wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl#d2f9ac
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=clares_web-0.1.0.BUILD-SNAPSHOT}, targeted=true
[wldeploy] [BasicOperation.deriveAppName():141] : appname established as: clares_web-0.1.0.BUILD-SNAPSHOT
[wldeploy] <19-ago-2016 09H43' CLT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, clares_web-0.1.0.BUILD-SNAPSHOT [archive: K:\Development\CLA_RES\clares\clares_web\target\clares_web-0.1.0.BUILD-SNAPSHOT.war], to AdminServer .>
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=clares_web-0.1.0.BUILD-SNAPSHOT}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():628] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] AdminServer
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: C:\Users\ODONAT~1\AppData\Local\Temp\odonatafly\.\config\deployments\clares_web-0.1.0.BUILD-SNAPSHOT
[wldeploy] App config: C:\Users\ODONAT~1\AppData\Local\Temp\odonatafly\.\config\deployments\clares_web-0.1.0.BUILD-SNAPSHOT\plan
[wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=clares_web-0.1.0.BUILD-SNAPSHOT,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
[wldeploy]
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, clares_web-0.1.0.BUILD-SNAPSHOT, on targets:
[wldeploy] [BasicOperation.execute():447] : AdminServer
[wldeploy] Task 51 initiated: [Deployer:149026]deploy application clares_web-0.1.0.BUILD-SNAPSHOT on AdminServer.
[wldeploy] dumping Exception stack
[wldeploy] Task 51 failed: [Deployer:149026]deploy application clares_web-0.1.0.BUILD-SNAPSHOT on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy] weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext#806038954[app:clares_web-0.1.0.BUILD-SNAPSHOT module:clares_web-0.1.0.BUILD-SNAPSHOT.war path:/clares_web-0.1.0.BUILD-SNAPSHOT spec-version:2.5]", defined in weblogic.xml [Extension-Name: clares_shared-0.1.0.BUILD-SNAPSHOT, Specification-Version: 1, Implementation-Version: 8.1, exact-match: false]
[wldeploy] at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
[wldeploy] at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
[wldeploy] at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
[wldeploy] at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
[wldeploy] at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
[wldeploy] at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
[wldeploy] at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
[wldeploy] at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
[wldeploy] at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
[wldeploy] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy] at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
[wldeploy] at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
[wldeploy] at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
[wldeploy] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy] at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
[wldeploy] at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
[wldeploy] at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
[wldeploy] at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
[wldeploy] at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
[wldeploy] at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
[wldeploy] at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
[wldeploy] at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
[wldeploy] at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
[wldeploy] at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
[wldeploy] at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
[wldeploy] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
[wldeploy] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
[wldeploy] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
[wldeploy] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
[wldeploy] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
[wldeploy] at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
someone can help me to know what is the mistake I am making
thanxs
Gos
enter code here
Related
CloudHub worker trying to connect to SFTP site which allows whitelisted IPs only
I have a Mule 4 application [App1] created on CloudHub. I tried to deploy the application's jar file onto CloudHub. This application has a Static IP [eg. 100.101.102.103] assigned to it in Runtime Manager. This IP address is whitelisted by customer to allow communication with their SFTP sites and APIs. My Mule application has APIs and some SFTP flows. When I try to deploy my mule application [App1], the deployment fails with below error: Connectivity test failed for config 'SFTP_Config'. Application deployment will continue. Error was: Could not establish SFTP connection with host: 'sftp.hostname' at port: '22' - Error during login to 'sftpuser#sftp.hostname'. The SFTP Config is: <sftp:config name="SFTP_Config" doc:name="SFTP Config" doc:id="5d626288-5181-41d5-807d-2786ea4292d8" > <sftp:connection host="${sftp.host}" port="${sftp.port}" username="${secure::sftp.username}" password="${secure::sftp.password}" connectionTimeoutUnit="MINUTES" connectionTimeout="2" responseTimeoutUnit="MINUTES" responseTimeout="2" workingDir="${sftp.peoplePosition.directory}"> <reconnection failsDeployment="false" > <reconnect frequency="${sftp.retryInterval}" count="${sftp.retryAttempts}" /> </reconnection> </sftp:connection> </sftp:config> I also tried using failsDeployment="false" in the SFTP configuration as recommended in this KB article but it didn't work either. The log shows: [2023-02-16 05:59:00.754] ERROR org.mule.extension.sftp.internal.connection.SftpConnectionProvider [qtp1351434790-36]: Auth fail com.jcraft.jsch.JSchException: Auth fail [2023-02-16 05:59:00.824] WARN org.mule.runtime.core.internal.connection. PoolingConnectionManagementStrategy [qtp1351434790-36]: Failed to create a connection while applying the pool initialization policy. org.mule.runtime.api.connection.ConnectionException: Could not establish SFTP connection with host: 'sftphost' at port: '22' - Error during login to sftpuser#sftphost at org.mule.runtime.core.internal.connection.ErrorTypeHandler ConnectionProviderWrapper.lambda$connect$0(ErrorTypeHandler ConnectionProviderWrapper.java:70) at java.util.Optional.map(Optional.java:215) I have verified the SFTP credentials, they are working fine with Winscp. Is there any way a CloudHub worker can complete the deployment successfully or validate the SFTP configuration using Static IP instead of it's own IP address?
Unable to get the cluster and node details in Web Console agent for Apache Ignite
I am trying to get the node and cluster details in the Apache Ignite WebConsole. Below are the steps i have performed: 1. Download the Apache Ignite WebConsole. 2. My applications is running the ignite node as a cache layer(Ignite node started OK (id=ac87a66c,) 3. Ignite is running on Ignite discovery url 192.168.0.102:47500 4. I ran the bat file: web-console-agent.bat. But it is not able to connect to the agent and hence the web console: [2020-05-26T18:05:33,245][INFO ][main][AgentLauncher] Starting Apache GridGain Web Console Agent... [2020-05-26T18:05:33,415][INFO ][main][AgentLauncher] [2020-05-26T18:05:33,416][INFO ][main][AgentLauncher] Web Console Agent configuration : [2020-05-26T18:05:33,535][INFO ][main][AgentLauncher] User's security tokens : ********************************af05 [2020-05-26T18:05:33,539][INFO ][main][AgentLauncher] URI to Ignite node REST server : http://localhost:8080 [2020-05-26T18:05:33,540][INFO ][main][AgentLauncher] URI to GridGain Web Console : https://console.gridgain.com [2020-05-26T18:05:33,548][INFO ][main][AgentLauncher] Path to properties file : default.properties [2020-05-26T18:05:33,548][INFO ][main][AgentLauncher] Path to JDBC drivers folder : C:\pluralsight\gridgain-web-console-agent-2020.03.01\jdbc-drivers [2020-05-26T18:05:33,557][INFO ][main][AgentLauncher] Demo mode : enabled [2020-05-26T18:05:33,560][INFO ][main][AgentLauncher] [2020-05-26T18:05:33,621][INFO ][main][WebSocketRouter] Starting Web Console Agent... [2020-05-26T18:05:33,635][INFO ][Connect thread][WebSocketRouter] Connecting to server: wss://console.gridgain.com [2020-05-26T18:05:35,996][INFO ][http-client-16][WebSocketRouter] Successfully completes handshake with server [2020-05-26T18:05:40,035][WARN ][pool-2-thread-1][ClusterHandler] Failed to connect to cluster. [2020-05-26T18:05:40,036][WARN ][pool-2-thread-1][ClusterHandler] Check that '--node-uri' configured correctly. [2020-05-26T18:05:40,039][WARN ][pool-2-thread-1][ClusterHandler] Ensure that cluster nodes have [ignite-rest-http] module in classpath (was copied from libs/optional to libs folder). [2020-05-26T18:05:40,045][INFO ][pool-2-thread-1][ClustersWatcher] Failed to establish connection to node Please let me know where i am missing steps
Apache Twill HelloWorld example fails
When I run Apache twill HelloWorld example as stated in http://twill.incubator.apache.org/GettingStarted.html I get this log: 10:44:47.888 [ STARTING] DEBUG o.a.twill.yarn.YarnTwillController - Yarn application status for HelloWorldRunnable application_1443786884805_0185: ACCEPTED 10:44:48.383 [ STARTING-SendThread(hadice.dev:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Got ping response for sessionid: 0x15028da0ff0009d after 0ms 10:44:48.889 [IPC Parameter Sending Thread #0] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root sending #45 10:44:48.894 [IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root got value #45 10:44:48.894 [ STARTING] DEBUG o.a.hadoop.ipc.ProtobufRpcEngine - Call: getApplicationReport took 6ms 10:44:48.895 [ STARTING] DEBUG o.a.twill.yarn.YarnTwillController - Yarn application status for HelloWorldRunnable application_1443786884805_0185: ACCEPTED 10:44:49.711 [Kafka-Consumer-log-0] DEBUG o.a.t.i.k.client.SimpleKafkaConsumer - No leader for topic partition TopicPartition{topic=log, partition=0}. 10:44:49.895 [IPC Parameter Sending Thread #0] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root sending #46 10:44:49.902 [IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root got value #46 10:44:49.902 [ STARTING] DEBUG o.a.hadoop.ipc.ProtobufRpcEngine - Call: getApplicationReport took 7ms 10:44:49.902 [ STARTING] DEBUG o.a.twill.yarn.YarnTwillController - Yarn application status for HelloWorldRunnable application_1443786884805_0185: FAILED 10:44:50.902 [ STARTING] INFO o.a.twill.yarn.YarnTwillController - Yarn application HelloWorldRunnable application_1443786884805_0185 is in state FAILED 10:44:50.903 [ STARTING] INFO o.a.twill.yarn.YarnTwillController - Yarn application HelloWorldRunnable application_1443786884805_0185 is not in running state. Shutting down controller. 10:44:50.907 [IPC Parameter Sending Thread #0] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root sending #47 10:44:50.908 [ STARTING-SendThread(hadice.dev:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Reading reply sessionid:0x15028da0ff0009d, packet:: clientPath:/HelloWorldRunnable/instances/5e72cb8c-cf94-4718-a44b-ec983304efa0 serverPath:/HelloWorldRunnable/instances/5e72cb8c-cf94-4718-a44b-ec983304efa0 finished:false header:: 10,3 replyHeader:: 10,1797,-101 request:: '/HelloWorldRunnable/instances/5e72cb8c-cf94-4718-a44b-ec983304efa0,T response:: 10:44:50.913 [IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root] DEBUG org.apache.hadoop.ipc.Client - IPC Client (431687661) connection to gin1.dev/10.0.22.129:8032 from root got value #47 10:44:50.913 [ STOPPING] DEBUG o.a.hadoop.ipc.ProtobufRpcEngine - Call: getApplicationReport took 6ms 10:44:50.916 [ STOPPING] DEBUG o.a.twill.yarn.YarnTwillController - Yarn application HelloWorldRunnable application_1443786884805_0185 completed with status FAILED The Application gets ACCEPTed but then transitions to the "FAILED" state. The YARN Web UI shows this as the error (very unspecific): Application application_1443786884805_0185 failed 2 times due to AM Container for appattempt_1443786884805_0185_000002 exited with exitCode: 1 For more detailed output, check application tracking page:http://gin1.dev:8088/proxy/application_1443786884805_0185/Then, click on links to logs of each attempt. Diagnostics: Exception from container-launch. Container id: container_1443786884805_0185_02_000001 Exit code: 1 Stack trace: ExitCodeException exitCode=1: at org.apache.hadoop.util.Shell.runCommand(Shell.java:538) at org.apache.hadoop.util.Shell.run(Shell.java:455) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:715) at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:211) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Container exited with a non-zero exit code 1 Failing this attempt. Failing the application. And the node log shows: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/hadoop/conf/Configuration at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2693) at java.lang.Class.privateGetMethodRecursive(Class.java:3040) at java.lang.Class.getMethod0(Class.java:3010) at java.lang.Class.getMethod(Class.java:1776) at org.apache.twill.launcher.TwillLauncher.main(TwillLauncher.java:85) Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.conf.Configuration at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 6 more What can be wrong? I supposed that hadoop classes should be on classpath in yarn application. How to fix that?
I assume you are launching the application with the result of hadoop classpath in the classpath (as shown in the example). You need to make sure the result of running hadoop classpath on launcher box points to local paths that contain hadoop jars. The other thing you might want to check is the stdout file in the container log directory. It prints out classpath that it uses to launch the application and see if you find hadoop jars there.
How to access remote MBean server from jboss as 7 through RMI
I have two applications, one is deployed in jboss as 7, another is a java application (Camel). The camel has an exposed JMX service: service:jmx:rmi:///jndi/rmi://172.20.30.85:19999/jmxrmi/camel now, I need to access it from a EJB(jboss as 7). I have tried the following two ways, but both are fialed. A) works well with jboss as 5.x: JMXServiceURL target = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + host + ":" + port.toString() + "/jmxrmi/camel"); JMXConnector connector = JMXConnectorFactory.connect(target); got exception: Caused by: javax.naming.NameNotFoundException: rmi://172.20.30.85:19999/jmxrmi/camel -- service jboss.naming.context.java.rmi:."172.20.30.85:19999".jmxrmi.camel at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:241) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) at javax.naming.InitialContext.lookup(InitialContext.java:411) at javax.naming.InitialContext.lookup(InitialContext.java:411) at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1929) at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1896) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286) B) JMXServiceURL target = new JMXServiceURL("service:jmx:remoting-jmx://172.20.30.85:19999/jmxrmi/camel"); got exception: ERROR [org.jboss.remoting.remote.connection] (Remoting "endpoint" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000202: Abrupt close on Remoting connection 79f4a60c to sha-lri-pc-161/172.20.30.85:19999 11:33:44,415 WARN [com.lombardrisk.reform.process.api.ProcessInspectorBean] (http-/127.0.0.1:8080-29) Could not connect to integration MBean server: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:235) at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:148) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:99) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268) at com.lombardrisk.reform.process.api.ProcessInspectorBean.getIntegrationMBeanServerConnection(ProcessInspectorBean.java:328) at com.lombardrisk.reform.process.api.ProcessInspectorBean.getRoutes(ProcessInspectorBean.java:486) Is there anyone who can guide me? Thanks in advance.
Configuration of CloudAMQP Connection
I'm having difficulty configuring my connection to CloudAMQP in my deployed grails application. I can run the application locally against a locally installed RabbitMQ instance but can't figure out how to correctly define my application to run on CloudBees using the CloudAMQP service. In my Config.groovy, I'm defining my connection info and a queue: rabbitmq { connectionfactory { username = 'USERNAME' password = 'PASSWORD' hostname = 'lemur.cloudamqp.com' } queues = { testQueue autoDelete: false, durable: false, exclusive: false } } When the application starts and tries to connect, I see the following log messages: 2013-08-23 21:29:59,195 [main] DEBUG listener.SimpleMessageListenerContainer - Starting Rabbit listener container. 2013-08-23 21:29:59,205 [SimpleAsyncTaskExecutor-1] DEBUG listener.BlockingQueueConsumer - Starting consumer Consumer: tag=[null], channel=null, acknowledgeMode=AUTO local queue size=0 2013-08-23 21:30:08,405 [SimpleAsyncTaskExecutor-1] WARN listener.SimpleMessageListenerContainer - Consumer raised exception, processing can restart if the connection factory supports it org.springframework.amqp.AmqpIOException: java.io.IOException at org.springframework.amqp.rabbit.connection.RabbitUtils.convertRabbitAccessException(RabbitUtils.java:112) at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:163) at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createConnection(CachingConnectionFactory.java:228) at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils$1.createConnection(ConnectionFactoryUtils.java:119) at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils.doGetTransactionalResourceHolder(ConnectionFactoryUtils.java:163) at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils.getTransactionalResourceHolder(ConnectionFactoryUtils.java:109) at org.springframework.amqp.rabbit.listener.BlockingQueueConsumer.start(BlockingQueueConsumer.java:199) at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:524) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:106) at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:102) at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:124) at com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:381) at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:516) at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:545) Caused by: com.rabbitmq.client.ShutdownSignalException: connection error; reason: java.net.SocketException: Connection reset at com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:67) at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:33) at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:343) at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:216) at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:118) ... 3 more Caused by: java.net.SocketException: Connection reset at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:95) at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:131) at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:508) 2013-08-23 21:30:08,406 [SimpleAsyncTaskExecutor-1] INFO listener.SimpleMessageListenerContainer - Restarting Consumer: tag=[null], channel=null, acknowledgeMode=AUTO local queue size=0 2013-08-23 21:30:08,406 [SimpleAsyncTaskExecutor-1] DEBUG listener.BlockingQueueConsumer - Closing Rabbit Channel: null 2013-08-23 21:30:08,407 [SimpleAsyncTaskExecutor-2] DEBUG listener.BlockingQueueConsumer - Starting consumer Consumer: tag=[null], channel=null, acknowledgeMode=AUTO local queue size=0 Aug 23, 2013 9:30:11 PM org.apache.catalina.core.ApplicationContext log INFO: Initializing Spring FrameworkServlet 'grails' Aug 23, 2013 9:30:11 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8634 Aug 23, 2013 9:30:11 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8634
According to https://developer.cloudbees.com/bin/view/RUN/CloudAMQP when you bind your CloudAMQP service to your app - some config params are provided in the pattern of CLOUDAMQP_URL_ - this is the type of thing you would need to put in your config files so they can be wired in when the app launches.
Make sure to specify the virtualHost for CloudAMQP connections. That worked for me.