Win a copy of Java Database Connections & Transactions (e-book only) this week in the JDBC forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
Bartenders:
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

JBoss-eap-6.1 standalone deployments for SAR file: Failed to process phase PARSE of deployment  RSS feed

 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am having this issue when deploying a SAR file either in "C:\JBossEXP\jboss-eap-6.1\standalone\deployments" or in
"JBoss' ENTERPRISE APPLICATION PLATFORM 6.1.0.GA". Please see the following attached error message.
Could anybody give some instructions?

"JBAS014671: Failed services" => {"jboss.deployment.unit.\"backEnd.sar\".PARSE"

10:32:55,783 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: F
ailed to start service jboss.deployment.unit."backEnd.sar".PARSE: org.jboss.msc.servic
e.StartException in service jboss.deployment.unit."backEnd.sar".PARSE: JBAS018733: Fai
led to process phase PARSE of deployment "backEnd.sar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(Deployment
UnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redh
at-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Service
ControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControlle
rImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS0172
24: Failed to parse service xml ["/C:/JBossEXP/jboss-eap-6.1/bin/content/backEnd.sar/M
ETA-INF/jboss-service.xml"]
at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeplo
ymentParsingProcessor.java:102)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(Deployment
UnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redh
at-8]
... 5 more
Caused by: java.lang.IllegalStateException: Not a textual event (START_ELEMENT)
at com.ctc.wstx.sr.BasicStreamReader.throwNotTextual(BasicStreamReader.java:5
510)
at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:855)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.getText(XMLExtendedStream
ReaderImpl.java:275)
at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.unexpected
Content(JBossServiceXmlDescriptorParser.java:629)
at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.parseMBean
(JBossServiceXmlDescriptorParser.java:219)
at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElemen
t(JBossServiceXmlDescriptorParser.java:190)
at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElemen
t(JBossServiceXmlDescriptorParser.java:47)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeplo
ymentParsingProcessor.java:95)
... 6 more

10:32:55,798 ERROR [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS0158
70: Deploy of deployment "backEnd.sar" was rolled back with the following failure mess
age:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"backEnd.sar\".PARSE" => "o
rg.jboss.msc.service.StartException in service jboss.deployment.unit.\"backEnd.sar\".P
ARSE: JBAS018733: Failed to process phase PARSE of deployment \"backEnd.sar\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS
017224: Failed to parse service xml [\"/C:/JBossEXP/jboss-eap-6.1/bin/content/dapmis.
sar/META-INF/jboss-service.xml\"]
Caused by: java.lang.IllegalStateException: Not a textual event (START_ELEMENT)"}
}
10:32:55,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS0158
77: Stopped deployment backEnd.sar (runtime-name: backEnd.sar) in 7ms


Thank you for your help,
Sam
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What does the contents of C:/JBossEXP/jboss-eap-6.1/bin/content/dapmis.sar/META-INF/jboss-service.xml file look like?
 
San-Yih Pan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good morning, Jaikiran,


Some information are listed as follows:

1. jdk1.7.0_67
2. I am using backEnd.sar for testing.
3. Under "C:/JBossEXP/jboss-eap-6.1/bin/" directory, it has no
"content/backEnd.sar/META-INF/jboss-service.xml" sub directory but don't know why it shows in the output error message.
4. Deploy in Application Platform. ( The JMX-console is no more for JBoss above eap 6.1.)
5. It used to be working in JBoss-5.0.1-GA and 2 services deployed successfully in JMX-console.
6. I've passed this issue after I removed "xmbean-dd" from following "jboss-service.xml".

<?xml version="1.0" encoding="UTF-8" ?>
<server xmlns="urn:jboss:service:7.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd">
<mbean code="com.BackEnd.server.BackEndServer"
name="BackEnd:service=BackEndServer"
xmbean-dd="META-INF/BackEndServer.xml">
<depends>jboss.jca:name=BackEnd,service=ManagedConnectionPool</depends>
<depends>jboss.jca:name=JmsXA,service=ConnectionFactoryBinding</depends>
<depends>jboss.mq.destination:name=ImageUploadQueue,service=Queue</depends
</mbean>

<mbean code="com.BackEnd.server.RRServer"
name="BackEnd:service=RRServer"
xmbean-dd="META-INF/RRServer.xml">
<depends>jboss.jca:name=BackEnd,service=ManagedConnectionPool</depends>
<depends>jboss.jca:name=JmsXA,service=ConnectionFactoryBinding</depends>
<depends>jboss.mq.destination:name=RRTopic,service=Topic</depends>
</mbean>

</server>


The new error messages come out like below:
13:24:45,761 ERROR [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "backEnd.sar" was rolled back with the following failure message:
{"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.mbean.service.BackEnd:service=BackEndServer.start is missing [jboss.mbean.service.\"jboss.jca:name=backEnd,service=ManagedConnectionPool\".start, jboss.mbean.service.\"jboss.jca:name=JmsXA,service=ConnectionFactoryBinding\".start, jboss.mbean.service.\"jboss.mq.destination:name=ImageUploadQueue,service=Queue\".start]",
"jboss.mbean.service.BackEnd:service=RRServer.create is missing [jboss.mbean.service.\"jboss.jca:name=JmsXA,service=ConnectionFactoryBinding\".create, jboss.mbean.service.\"jboss.mq.destination:name=RRTopic,service=Topic\".create, jboss.mbean.service.\"jboss.jca:name=backEnd,service=ManagedConnectionPool\".create]",
"jboss.mbean.service.BackEnd:service=RRServer.start is missing [jboss.mbean.service.\"jboss.jca:name=JmsXA,service=ConnectionFactoryBinding\".start, jboss.mbean.service.\"jboss.mq.destination:name=RRTopic,service=Topic\".start, jboss.mbean.service.\"jboss.jca:backEnd=backEnd,service=ManagedConnectionPool\".start]",
"jboss.mbean.service.BackEnd:service=BackEndServer.create is missing [jboss.mbean.service.\"jboss.jca:name=JmsXA,service=ConnectionFactoryBinding\".create, jboss.mbean.service.\"jboss.jca:name=backEnd,service=ManagedConnectionPool\".create, jboss.mbean.service.\"jboss.mq.destination:name=ImageUploadQueue,service=Queue\".create]"
]}




Wish you have a happy New Year,
Sam
 
Jaikiran Pai
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sam, a very happy new year to you too!

JBoss AS7 (on which JBoss EAP6 is based) is completely different from previous versions. In this specific case, it no longer supports the kind of jboss-service.xml that you are deploying. Although there is support for jboss-service.xml, the XSD for it has changed and only a minimal support is available.

Can you tell us what exactly are you using that jboss-service.xml for? From the looks of it, it appears that you are creating JMS queues/topics. If that's what you want to create then you can do that from the admin console in EAP 6 or follow the instructions here https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Administration_and_Configuration_Guide/sect-Configuration.html#Configure_the_JMS_Server1 (see "Add queue instances to HornetQ" section).
 
San-Yih Pan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Jaikiran,


The previous developer was using "jboss-service.xml" to deploy 2 services BackEndServer and RRServer onto JMX-Console. From eap-6.1 and up, should get rid of
"jboxx-service.xml" or replace it by other config file(s).

Followed the instructions the 1st way "Use the Management Console " in "Add queue instances to HornetQ" to add Topic/Queue destinations. The error messages come out the same.



Thanks,
San-Yih
 
Jaikiran Pai
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
San-Yih, I think you'll have to change the jboss-service.xml to remove the <depends> from those MBeans and probably also remove the xmbean-dd attributes from those MBeans. That won't guarantee a successful deployment but you can then focus on fixing or changing the MBean code to be compatible with the newer version of the server. Knowing what those MBeans are doing will also help you decide whether or not they are needed in this version of the server.
 
San-Yih Pan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Jaikiran,


It works and is moving on even the progress is slow. Will keep you posted.


Thanks,
Sam
 
San-Yih Pan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Jaikiran,

Took your suggestion to simplify the "jboss-service.xml" to be as follows. So far, got stuck at 2 errors. Please give some advice.

<?xml version="1.0" encoding="UTF-8" ?>
<server xmlns="urn:jboss:service:7.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd">
<mbean code="com.BackEnd.server.BackEndServer"
name="BackEnd:service=BackEndServer"
</mbean>

<mbean code="com.BackEnd.server.RRServer"
name="BackEnd:service=RRServer"
</mbean>
</server>



12:08:52,768 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: F
ailed to start service jboss.mbean.service.BackEnd:service= BackEndServer.start: org.jbo
ss.msc.service.StartException in service jboss.mbean.service.BackEnd:service= BackEndSer
ver.start: JBAS017222: Failed to execute legacy service start() method
at org.jboss.as.service.StartStopService.start(StartStopService.java:57)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Service
ControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControlle
rImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_
67]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57) [rt.jar:1.7.0_67]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:43) [rt.jar:1.7.0_67]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_67]
at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService
.java:64)
at org.jboss.as.service.StartStopService.start(StartStopService.java:55)
... 5 more
Caused by: java.lang.NoClassDefFoundError: com/sun/media/jai/codec/SeekableStream
at mil.army.perscom.backEnd.rr.ImageQueueListener.<init>(ImageQueueListener.j
ava:39)
at mil.army.perscom.backEnd.server.BackEndServer.startImageQueueListener(BackEnd
Server.java:1332)
at mil.army.perscom.backEnd.server.BackEndServer.start(BackEndServer.java:344)
... 11 more
Caused by: java.lang.ClassNotFoundException: com.sun.media.jai.codec.SeekableStream f
rom [Module "deployment.backEnd.sar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurre
ntClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concurrent
ClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLo
ader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.ja
va:119) [jboss-modules.jar:1.2.0.Final-redhat-1]
... 14 more

12:08:52,791 ERROR [backEnd] (MSC service thread 1-2) mil.army.perscom.backEnd.server.
RRServer.startRRTopicListener() unable to get ConnectionFactory: javax.naming.NameNo
tFoundException: topic/RRTopic -- service jboss.naming.context.java.topic.RRTopic
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.lookup(InitialContext.java:120)
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) [rt.jar:1.7.0_
67]
at mil.army.perscom.backEnd.server.RRServer.startRRTopicListener(RRServer.j
ava:811) [backEnd.sar:]
at mil.army.perscom.backEnd.server.RRServer.start(RRServer.java:614) [backEnd
.sar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_
67]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57) [rt.jar:1.7.0_67]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:43) [rt.jar:1.7.0_67]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_67]
at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService
.java:64)
at org.jboss.as.service.StartStopService.start(StartStopService.java:55)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Service
ControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControlle
rImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]

12:08:52,812 ERROR [backEnd] (MSC service thread 1-2) mil.army.perscom.backEnd.server.
RRServer.start(): javax.management.JMRuntimeException: topic/RRTopic -- service jbos
s.naming.context.java.topic.RRTopic
at mil.army.perscom.backEnd.server.RRServer.startRRTopicListener(RRServer.j
ava:820) [backEnd.sar:]
at mil.army.perscom.backEnd.server.RRServer.start(RRServer.java:614) [backEnd
.sar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_
67]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57) [rt.jar:1.7.0_67]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:43) [rt.jar:1.7.0_67]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_67]
at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService
.java:64)
at org.jboss.as.service.StartStopService.start(StartStopService.java:55)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Service
ControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControlle
rImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]

12:08:52,820 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: F
ailed to start service jboss.mbean.service.BackEnd:service=RRServer.start: org.jboss.
msc.service.StartException in service jboss.mbean.service.BackEnd:service=RRServer.st
art: JBAS017222: Failed to execute legacy service start() method
at org.jboss.as.service.StartStopService.start(StartStopService.java:57)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Service
ControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControlle
rImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_
67]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57) [rt.jar:1.7.0_67]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:43) [rt.jar:1.7.0_67]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_67]
at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService
.java:64)
at org.jboss.as.service.StartStopService.start(StartStopService.java:55)
... 5 more
Caused by: javax.management.JMRuntimeException: topic/RRTopic -- service jboss.namin
g.context.java.topic.RRTopic
at mil.army.perscom.backEnd.server.RRServer.startRRTopicListener(RRServer.j
ava:820)
at mil.army.perscom.backEnd.server.RRServer.start(RRServer.java:614)
... 11 more

12:08:53,042 ERROR [org.jboss.as.server] (HttpManagementService-threads - 5) JBAS0158
70: Deploy of deployment "backEnd.sar" was rolled back with the following failure mess
age:
{"JBAS014671: Failed services" => {
"jboss.mbean.service.BackEnd:service=RRServer.start" => "org.jboss.msc.service.St
artException in service jboss.mbean.service.BackEnd:service=RRServer.start: JBAS01722
2: Failed to execute legacy service start() method
Caused by: java.lang.reflect.InvocationTargetException
Caused by: javax.management.JMRuntimeException: topic/RRTopic -- service jboss.n
aming.context.java.topic.RRTopic",
"jboss.mbean.service.BackEnd:service= BackEndServer.start" => "org.jboss.msc.service
.StartException in service jboss.mbean.service.BackEnd:service= BackEndServer.start: JBA
S017222: Failed to execute legacy service start() method
Caused by: java.lang.reflect.InvocationTargetException
Caused by: java.lang.NoClassDefFoundError: com/sun/media/jai/codec/SeekableStream

Caused by: java.lang.ClassNotFoundException: com.sun.media.jai.codec.SeekableStream from [Module \"deployment.backEnd.sar:main\" from Service Module Loader]"


Thanks a lot,
Sam

 
San-Yih Pan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Jaikiran,


Thank you for your valuable suggestions. It works now.
Some portion of issues comes from some configuration code not cleaned up by previous owner.


Blessings,
Sam
 
Jaikiran Pai
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sam, glad to know you got this resolved.
 
I will open the floodgates of his own worst nightmare! All in a tiny ad:
how do I do my own kindle-like thing - without amazon
https://coderanch.com/t/711421/engineering/kindle-amazon
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!