[JBoss jBPM] - java.net.NoRouteToHostException - Hello World sample
by meghanai_99
Hello,
I am getting following exception while running Hell sample BPEL client. My jndi.properties looks like this -
java.naming.provider.url=jnp://127.0.0.1:1099
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming.client
j2ee.clientName=jbpmbpel-client
The exception stack -
javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: 10.30.12.124; nested exception is:
java.net.NoRouteToHostException: No route to host: connect]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.test.ws.JBossTestDeployer.getServer(JBossTestDeployer.java:56)
at org.jboss.test.ws.JBossTestDeployer.deploy(JBossTestDeployer.java:43)
at org.jboss.test.ws.JBossWSTestHelper.deploy(JBossWSTestHelper.java:47)
at org.jboss.test.ws.JBossWSTestSetup.setUp(JBossWSTestSetup.java:72)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421)
at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912)
at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766)
Caused by: java.rmi.ConnectIOException: Exception creating connection to: 10.30.12.124; nested exception is:
java.net.NoRouteToHostException: No route to host: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
... 12 more
Caused by: java.net.NoRouteToHostException: No route to host: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
I don't understand why it is trying to connect to 10.30.12.124
Please let me know.
Thanks,
Meghana
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013142#4013142
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013142
19Â years, 2Â months
[JBossWS] - org.jboss.ws.WSException: Unsupported schemaLocation:
by anusanj
<?xml version="1.0" encoding="UTF-8"?>
|
| <configuration xmlns="http://www.jboss.org/jbossws-tools">
|
| <wsdl-java file="http://eutils.ncbi.nlm.nih.gov/entrez/eutils/soap/eutils.wsdl">
| <mapping file="jaxrpc-mapping-client.xml" />
| </wsdl-java>
|
| </configuration>
Consuming web service.
I am trying to run wstools to get client side artifacts. but i keep running into this exception
Exception in thread "main" org.jboss.ws.WSException: Unsupported schemaLocation:
egquery.xsd
at org.jboss.ws.metadata.wsdl.WSDL11Reader.getLocationURL(WSDL11Reader.j
ava:417)
at org.jboss.ws.metadata.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Rea
der.java:371)
at org.jboss.ws.metadata.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Re
ader.java:349)
at org.jboss.ws.metadata.wsdl.WSDL11Reader.processTypes(WSDL11Reader.jav
a:205)
at org.jboss.ws.metadata.wsdl.WSDL11Reader.processDefinition(WSDL11Reade
r.java:118)
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitio
nsFactory.java:145)
at org.jboss.ws.tools.WSDLToJava.convertWSDL2Java(WSDLToJava.java:110)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(Too
lsHelper.java:322)
at org.jboss.ws.tools.WSTools.process(WSTools.java:132)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:61)
Any help is appreciated,
Thanks
anu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013135#4013135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013135
19Â years, 2Â months
[JBoss jBPM] - Re: Unable to locate current JTA transaction
by crussell42
Ok, at this point things are running pretty well.
I have deployed the cvs trunk build jbpm.3 (3.2.beta2)'s jbpm-enterprise.ear to
jboss4.0.5ga with ejb3 and messaging.
I am able to create start and transition through process;s.
Keep in mind the reason for this posting.
We have isTransactionEnabled set to false and isCurrentSessionEnabled set to false.
So here I almost have it working with Transactions turned OFF.
When a process transitions to an end state however and the clean up of the process instance begins, I get the following exception:
| 16:26:00,719 ERROR [STDERR] org.hibernate.TransactionException: Could not register synchronization
| at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159)
| at org.jbpm.db.JobSession.deleteJobsForProcessInstance(JobSession.java:214)
| at org.jbpm.scheduler.ejbtimer.EjbSchedulerService.deleteTimersByProcessInstance(EjbSchedulerService.java:165)
| at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:276)
|
So back to the original question, HOW DO I PROPERLY CONFIGURE USE OF EITHER JTA OR CMT TRANSACTIONS?????????
I've managed to make it hobble along with the transactions turned off (I think) but what I really want is to properly configure transactions....
PLEASE HELP!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013125#4013125
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013125
19Â years, 2Â months