Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Could not obtain connection to any of these urls: localhost:1099

 
hamlin stephen
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I configured eclipse3.0 with Lomboz3 and jboss 3.2.5.
But when running jboss through Lomboz i am getting jboss test page but not deploying MBeans showing the error
shown below.
I am using jboss325.server to configure jboss, please help

Error
-----------------------------------------------------------

6:55:12,465 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss:service=ClientUserTransaction
state: CREATED
I Depend On: jboss:service=proxyFactory,target=ClientUserTransactionFactory
jboss:service=proxyFactory,target=ClientUserTransaction

Depends On Me:
ObjectName: jboss:service=proxyFactory,target=ClientUserTransactionFactory
state: FAILED
I Depend On: jboss:service=invoker,type=jrmp

Depends On Me: jboss:service=ClientUserTransaction
MBeanException: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
Cause: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
ObjectName: jboss:service=invoker,type=pooled
state: FAILED
I Depend On: jboss:service=TransactionManager

Depends On Me: MBeanException: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
Cause: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
ObjectName: jboss:service=invoker,type=http
state: FAILED
I Depend On:
Depends On Me: MBeanException: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
Cause: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
state: FAILED
-----------------------------------------------------------------

jboss325.server
-------------------------------------------------

<serverDefinition
name="JBOSS 3.2.5"
ejbModules="true"
webModules="true"
earModules="true">
<property id="serverRootDirectory"
label="Application Server Directory:"
type="directory"
default="/home/workshop/jboss-3.2.5" />
<property id="serverAddress"
label="Address:"
type="string"
default="127.0.0.1" />
<property id="serverPort"
label="Port:"
type="string"
default="8080" />
<property id="serverConfig"
label="Server Configuration (minimal/default/all):"
type="string"
default="default" />
<property id="classPathVariableName"
label="Classpath Variable Name:"
type="string"
default="JBOSS325" />
<property id="classPath"
label="Classpath Variable:"
type="directory"
default="/home/workshop/jboss-3.2.5" />
<serverHome>${serverRootDirectory}</serverHome>
<webModulesDeployDirectory>${serverRootDirectory}/server/${serverConfig}/deploy</webModulesDeployDirectory>
<ejbModulesDeployDirectory>${serverRootDirectory}/server/${serverConfig}/deploy</ejbModulesDeployDirectory>
<earModulesDeployDirectory>${serverRootDirectory}/server/${serverConfig}/deploy</earModulesDeployDirectory>
<jndiInitialContextFactory>org.jnp.interfaces.NamingContextFactory</jndiInitialContextFactory>
<jndiProviderUrl>jnp://${serverAddress}:1099</jndiProviderUrl>
<startClass>org.jboss.Main</startClass>
<startWorkingDirectory>${serverRootDirectory}/bin</startWorkingDirectory>
<startVmParameters></startVmParameters>
<startProgramArguments>-c ${serverConfig}</startProgramArguments>
<stopClass>org.jboss.Shutdown</stopClass>
<stopWorkingDirectory>${serverRootDirectory}/bin</stopWorkingDirectory>
<stopVmParameters></stopVmParameters>
<stopProgramArguments>-S</stopProgramArguments>
<serverClassPath>
<jar type="variable">JDK_TOOLS</jar>
<jar type="variable">${classPathVariableName}/bin/run.jar</jar>
<jar type="variable">${classPathVariableName}/bin/shutdown.jar</jar>
<jar type="variable">${classPathVariableName}/client/jboss-j2ee.jar</jar>
<jar type="variable">${classPathVariableName}/lib/concurrent.jar</jar>
<jar type="variable">${classPathVariableName}/lib/jboss-system.jar</jar>
<jar type="variable">${classPathVariableName}/lib/dom4j.jar</jar>
<jar type="variable">${classPathVariableName}/lib/xercesImpl.jar</jar>
<jar type="variable">${classPathVariableName}/lib/xml-apis.jar</jar>
<jar type="variable">${classPathVariableName}/lib/gnu-regexp.jar</jar>
<jar type="variable">${classPathVariableName}/lib/getopt.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/deploy/jbossweb-tomcat50.sar/servlet-api.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/bcel.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jboss.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jboss-transaction.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jnpserver.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jpl-pattern.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jpl-util.jar</jar>
</serverClassPath>
<clientClassPath>
<jar type="variable">${classPathVariableName}/client/jboss-j2ee.jar</jar>
<jar type="variable">${classPathVariableName}/client/jboss-client.jar</jar>
<jar type="variable">${classPathVariableName}/client/jboss-common-client.jar</jar>
<jar type="variable">${classPathVariableName}/client/jboss-jaas.jar</jar>
<jar type="variable">${classPathVariableName}/client/jbosssx-client.jar</jar>
<jar type="variable">${classPathVariableName}/client/jnet.jar</jar>
<jar type="variable">${classPathVariableName}/client/jnp-client.jar</jar>
<jar type="variable">${classPathVariableName}/client/log4j.jar</jar>
<jar type="variable">${classPathVariableName}/server/default/lib/jnpserver.jar</jar>
</clientClassPath>
<projectClassPath>
<jar type="variable">JDK_TOOLS</jar>
<jar type="variable">${classPathVariableName}/bin/run.jar</jar>
<jar type="variable">${classPathVariableName}/bin/shutdown.jar</jar>
<jar type="variable">${classPathVariableName}/client/jboss-j2ee.jar</jar>
<jar type="variable">${classPathVariableName}/lib/concurrent.jar</jar>
<jar type="variable">${classPathVariableName}/lib/jboss-system.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/deploy/jbossweb-tomcat50.sar/servlet-api.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/bcel.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jboss.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jboss-transaction.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jnpserver.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jpl-pattern.jar</jar>
<jar type="variable">${classPathVariableName}/server/${serverConfig}/lib/jpl-util.jar</jar>
</projectClassPath>
<adminTool>
<web><deploy /><undeploy />
</web>
<ejb><deploy /><undeploy />
</ejb>
<ear><deploy /><undeploy />
<webModule><deploy /><undeploy />
</webModule>
<ejbModule><deploy /><undeploy />
</ejbModule>
</ear>
</adminTool>
<adminToolPath>
</adminToolPath>
</serverDefinition>
-------------------------------------------------------
 
hamlin stephen
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Is it necessory to open portb 1099 explicitly for my machine?
Still i need help..
 
Bernardo Hermont
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Maybe 1099 is not your JNDI port. Check your conf/jboss-service.xml if you are using Jboss.
 
Peter Johnson
author
Bartender
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The "Incomplete deployment listings" text you posted is a report by the deployer on what it could not deploy. That report usually does not contain enough information to diagnose the problem. Earlier in the console output there will be several stack traces for the actual error. You need to post the the text for the first stack trace. (You might have to increase the terminal buffer size to do this - my KDE terminal has 1000 lines by default which is not enough; I set it to 10000.)

(Wow, its been years since I used Lomboz...)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic