Trouble deploying libraries to JobServer

One Star

Trouble deploying libraries to JobServer

I've installed a JobServer on RHEL4 and Java 6. Everything shows up fine in the Admin Console, and when deploying a very simple job to run, things are good. However, when attempting to deploy a "real" job (connects to Oracle and HornetQ), things fall apart.
I am receiving:
Exception in component tJMSOutput_3
javax.naming.CommunicationException
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:392)
at zeus_integration.choosecandidates_0_2.ChooseCandidates.tOracleInput_1Process(ChooseCandidates.java:1033)
at zeus_integration.choosecandidates_0_2.ChooseCandidates.tOracleConnection_1Process(ChooseCandidates.java:336)
at zeus_integration.choosecandidates_0_2.ChooseCandidates.runJobInTOS(ChooseCandidates.java:2179)
at zeus_integration.choosecandidates_0_2.ChooseCandidates.main(ChooseCandidates.java:2081)
Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.lang.ClassNotFoundException: org.hornetq.jms.referenceable.SerializableObjectRefAddr (no security manager: RMI class loader disabled)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:178)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
... 6 more
Caused by: java.lang.ClassNotFoundException: org.hornetq.jms.referenceable.SerializableObjectRefAddr (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:375)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1667)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:306)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:155)
... 8 more

I investigated both the JobServer's lib folder and the job's lib in the repository and noticed that SOME, but not all of my dependent JARs did not go along with it. Basically, all the hornetq and netty jars. The JNP-client and jboss-all did.
I could not find anything here on the forums, nor in the Admin or User manuals for deploying these libraries. Would much appreciate it if someone can give me a pointer!
Thanks
Andy
One Star

Re: Trouble deploying libraries to JobServer

I have the same problem with a SAP job. The job runs fine when i generate it with TIS Studio.
Generated with Commandline i gor the following error:
### Job STARTED at 2010/06/08 18:20:25 (jobId=QNYwwkY7, jobExecutionId=20100608182025_S1WZ2) ###
Exception in thread "main" java.lang.Error: Unaufgelöste Kompilierungsprobleme:
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw.jco.JCO kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw.jco.JCO kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw kann nicht in einen Typ aufgelöst werden.
com.sap.mw.jco.JCO kann nicht in einen Typ aufgelöst werden.
at kbw1.poc2_sapgetflightdetail_0_3.PoC2_SAPGetFlightDetail.tWaitForFile_1Process(PoC2_SAPGetFlightDetail.java:2900)
at kbw1.poc2_sapgetflightdetail_0_3.PoC2_SAPGetFlightDetail.runJobInTOS(PoC2_SAPGetFlightDetail.java:5280)
at kbw1.poc2_sapgetflightdetail_0_3.PoC2_SAPGetFlightDetail.main(PoC2_SAPGetFlightDetail.java:5172)
### Job ENDED WITH ERROR at 2010/06/08 18:20:26 (jobId=QNYwwkY7, jobExecutionId=20100608182025_S1WZ2) ###
Investigation shows that the sapjco.jar is not included.
Does anybody know about the differences.
Thanks
Heinz-Werner
Employee

Re: Trouble deploying libraries to JobServer

@agartzke
Make sure that you have your jars in the classpath on your jobserver. If it still gives you trouble use the tLibraryLoad component in the job to specifically call the proper jar.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog

How Media Organizations Achieved Success with Data Integration

Learn how media organizations have achieved success with Data Integration

Read

6 Ways to Start Utilizing Machine Learning with Amazon We Services and Talend

Look at6 ways to start utilizing Machine Learning with Amazon We Services and Talend

Blog