Support #3428

Creating Clusters in WebSphere

Added by Raj 2 months ago. Updated about 1 month ago.

Status:ClosedStart date:01/30/2020
Priority:HighDue date:
Assignee:Raj% Done:

0%

Category:-
Target version:RapidDeploy - 5.0-FIX
Affects Version:5.0-FIX Additional version details:
Timesheet Code:

Description

HI Team

i am new to MIDVISION RAPID DEPLOY, using the RAPID Deploy i want to create a Cluster in WebSphere 9,
1) i created a project and when i run it, i am getting the below error

Initiating RapidDeploy Pipeline Job at: Thu Jan 30 17:05:59 UTC 2020

------------------------------------
User: mvadmin
Total Steps: 1
Total Jobs: 1
------------------------------------
2020-01-30 17:06:01 - INFO: Package File Path: /var/rd/midvision/buildstore/var/rd/midvision-0.0.1.jar
Pipeline Execution Fatal Error (details follow):

FileExistsException [RapidDeployBusinessException [com.midvision.rapiddeploy.exceptions.FileExistsException: /var/rd/midvision/buildstore/var/rd/midvision-0.0.1.jar]]
at com.midvision.rapiddeploy.plugins.artifact.localfile.LocalFile.createArchive(LocalFile.java:127)
at com.midvision.rapiddeploy.service.deploy.impl.DeploymentPackageServiceImpl.createNewDeploymentPackage(DeploymentPackageServiceImpl.java:852)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy93.createNewDeploymentPackage(Unknown Source)
at com.midvision.rapiddeploy.service.jobplan.PipelineRunner.preparePackageVersions(PipelineRunner.java:455)
at com.midvision.rapiddeploy.service.jobplan.PipelineRunner.run(PipelineRunner.java:266)
at java.lang.Thread.run(Thread.java:745)

midvision-deploy-orchestration.xml Magnifier (7.93 KB) Raj, 01/30/2020 04:49 pm

RIDP_Cluster_Creation.zip (10 KB) Raj, 01/30/2020 05:56 pm

RIDp Cluster.zip (10.2 KB) Raj, 01/30/2020 05:56 pm

History

#1 Updated by Rafael 2 months ago

  • Status changed from New to Feedback
  • Assignee changed from MidVision RapidDeploy Support to Raj
  • Priority changed from Blocker to High
  • Affects Version changed from 5.0.0 to 5.0-FIX

Hi Raj,

It seems you're trying to create a deployment package with the name of a file that already exists.

Could you please attach the entire log file for the job plan and the log files for each of the jobs executed up to the failure?

It would also help if you can attach an export of the job plan so I can check it locally for any error.

Cheers!

Rafa

#2 Updated by Raj 2 months ago

Hi Rafa,

i have figured out the above error, now i am getting the below error, can you please help me on the below?

2020-01-30 18:14:24,216 [RemoteInvocationHandler_383] INFO com.midvision.rapiddeploy.utilities.exec.LocalScriptRunner - WASX7017E: Exception received while running file "/var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py"; exception information: com.ibm.bsf.BSFException: exception from Jython:
java.lang.RuntimeException: Method code too large!
at org.python.objectweb.asm.MethodWriter.a(Unknown Source)
at org.python.objectweb.asm.ClassWriter.toByteArray(Unknown Source)
at org.python.compiler.ClassFile.write(ClassFile.java:215)
at org.python.compiler.Module.write(Module.java:620)
at org.python.compiler.Module.compile(Module.java:676)
at org.python.compiler.Module.compile(Module.java:657)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.ostream(LegacyCompiler.java:59)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.loadCode(LegacyCompiler.java:43)
at org.python.core.CompilerFacade.compile(CompilerFacade.java:33)
at org.python.core.Py.compile_flags(Py.java:1942)
at org.python.core.Py.compile_flags(Py.java:1947)
at org.python.core.Py.compile_flags(Py.java:1977)
at or
2020-01-30 18:14:24,216 [RemoteInvocationHandler_383] INFO com.midvision.rapiddeploy.utilities.exec.LocalScriptRunner - g.python.util.PythonInterpreter.exec(PythonInterpreter.java:267)
at com.ibm.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:120)
at com.ibm.bsf.BSFManager$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:703)

#3 Updated by Raj 2 months ago

Attached is the Full Project and plan

#4 Updated by Raj 2 months ago

even i cant run manully from the server too, looks like when rapid deploy creating the file /var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py there is some problem. please let me know what to do next

[root@ip-10-101-54-34 bin]# ./wsadmin.sh -useranme wasadmin -password i-094b004941ed03abc -f /var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py
WASX7209I: Connected to process "dmgr" on node Dmgr01 using SOAP connector; The type of process is: DeploymentManager
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[-useranme, wasadmin]"
WASX7017E: Exception received while running file "/var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py"; exception information: com.ibm.bsf.BSFException: exception from Jython:
java.lang.RuntimeException: Method code too large!
at org.python.objectweb.asm.MethodWriter.a(Unknown Source)
at org.python.objectweb.asm.ClassWriter.toByteArray(Unknown Source)
at org.python.compiler.ClassFile.write(ClassFile.java:215)
at org.python.compiler.Module.write(Module.java:620)
at org.python.compiler.Module.compile(Module.java:676)
at org.python.compiler.Module.compile(Module.java:657)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.ostream(LegacyCompiler.java:59)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.loadCode(LegacyCompiler.java:43)
at org.python.core.CompilerFacade.compile(CompilerFacade.java:33)
at org.python.core.Py.compile_flags(Py.java:1942)
at org.python.core.Py.compile_flags(Py.java:1947)
at org.python.core.Py.compile_flags(Py.java:1977)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:267)
at com.ibm.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:120)
at com.ibm.bsf.BSFManager$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:703)
at com.ibm.bsf.BSFManager.exec(Unknown Source)
at com.ibm.ws.scripting.AbstractShell.executeScript(AbstractShell.java:1290)
at com.ibm.ws.scripting.AbstractShell.run(AbstractShell.java:2394)
at com.ibm.ws.scripting.WasxShell.main(WasxShell.java:1256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:101)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:422)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:179)

java.lang.RuntimeException: java.lang.RuntimeException: Method code too large!

#5 Updated by Raj 2 months ago

I also see this when i ran manually, either you need to Modify the script or we need to Downgrade the Python to 21,

[1/30/20 19:01:12:286 UTC] 00000001 AbstractShell W The wsadmin is running with Jython V2.7 and it might not work with your script properly. You can modify your script or switch to Jython V2.1 by running wsadmin command '-usejython21 true'.
[1/30/20 19:01:12:287 UTC] 00000001 AbstractShell A WASX7093I: Issuing message: "WASX7017E: Exception received while running file "/var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py"; exception information: com.ibm.bsf.BSFException: exception from Jython:
java.lang.RuntimeException: Method code too large!

#6 Updated by Rafael 2 months ago

  • Status changed from Feedback to In Progress
  • Assignee changed from Raj to Rafael

Hi Raj,

Let me investigate!

Can you please attach the entire log of the project deployment?

Thanks!

Rafa

#7 Updated by Raj 2 months ago

Sorry i had to terminate the server in AWS And i will spinup new one and send to you, But this is the error i am getting

2020-01-30 18:14:24,216 [RemoteInvocationHandler_383] INFO com.midvision.rapiddeploy.utilities.exec.LocalScriptRunner - WASX7017E: Exception received while running file "/var/rd/midvision/web-apps/tomcat/temp/8f0b8c3c-7b78-4e21-b5e7-d89e8b9728d2_tmpFunction.py"; exception information: com.ibm.bsf.BSFException: exception from Jython:
java.lang.RuntimeException: Method code too large!
at org.python.objectweb.asm.MethodWriter.a(Unknown Source)
at org.python.objectweb.asm.ClassWriter.toByteArray(Unknown Source)
at org.python.compiler.ClassFile.write(ClassFile.java:215)
at org.python.compiler.Module.write(Module.java:620)
at org.python.compiler.Module.compile(Module.java:676)
at org.python.compiler.Module.compile(Module.java:657)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.ostream(LegacyCompiler.java:59)
at org.python.compiler.LegacyCompiler$LazyLegacyBundle.loadCode(LegacyCompiler.java:43)
at org.python.core.CompilerFacade.compile(CompilerFacade.java:33)
at org.python.core.Py.compile_flags(Py.java:1942)
at org.python.core.Py.compile_flags(Py.java:1947)
at org.python.core.Py.compile_flags(Py.java:1977)
at or
2020-01-30 18:14:24,216 [RemoteInvocationHandler_383] INFO com.midvision.rapiddeploy.utilities.exec.LocalScriptRunner - g.python.util.PythonInterpreter.exec(PythonInterpreter.java:267)
at com.ibm.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:120)
at com.ibm.bsf.BSFManager$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:703)

#8 Updated by Rafael 2 months ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Rafael to Raj

Hi Raj,

I thing I realised the problem, you're using the wrong task category. I can see this in you're XML orchestration file:

<class>com.midvision.rapiddeploy.orchestration.tasks.WebSphereDeploymentTask</class>

That class is associated with the categories:

  • IBM WebSphere 7
  • IBM WebSphere 8
  • IBM WebSphere 8.5

Which work very similarly.

But for WebSphere Application Server 9, as you correctly spotted, they have changed the Jython version, and our framework needs to keep working with the previous version.

You shouldn't notice this problem if you chose the "WebSphere9DeploymentTask" instead of the "WebSphereDeploymentTask" in the tasks list under the category "IBM WebSphere 9".

You can confirm you're using the right task category by checking the class name in the XML orchestration file:

<class>com.midvision.rapiddeploy.orchestration.tasks.was9.WebSphere9DeploymentTask</class>

The problem here is there's a little mismatch in the template you have used.

In this particular case, as a very quick fix you can just replace that line in the XML orchestration file, but please, in general try NOT to modify configuration files manually. :-)

Let me know how it goes! ;-)

Cheers!

Rafa

#9 Updated by Raj 2 months ago

Hi Rafa

i have updated that and it is worked fine, but i have selected the WebSphere 9 and i am guessing the websphere 9 template somehow using the WebSphere 7 class, please double check the template for us

#10 Updated by Rafael 2 months ago

  • Status changed from Feedback to Marked for Closure

Hi Raj,

That's exactly what I mentioned in my previous comment, there was a little bug in our WebSphere Application Server 9 templates that I have already solved for future releases.

Thanks for the spot! :-)

Let me know if you need further help on this, otherwise I'll time out the ticket in a few days time.

Cheers!

Rafa

#11 Updated by Raj 2 months ago

Thanks Rafa

is there any release schedule do you guys have?
or when can we expect the new Release?

Thanks
Raj

#12 Updated by Rafael 2 months ago

Hi Raj,

We don't have a release planned for the moment, but you can easily deal with this problem with the workaround I explained in my previous update (#3428): modifying the "<class>" tag in the XML orchestration file.

If you don't use a template you don't even need to worry about this bug.

Cheers!

Rafa

#13 Updated by Rafael about 1 month ago

  • Status changed from Marked for Closure to Closed

Also available in: Atom PDF