Help about SPECjAppServer2002 and jboss.

[terryxian]

I am using SPECjAppServer2002 to do some experiment on jboss.
What I am using are jboss4.0, jsdk1.4.2_05, and oracle 9i.
I have downloaded the necessary toolkit and followed the setup instruction to setup the
environment. After I ran:
> $ANT_HOME/bin/ant -buildfile jboss40.xml -deployall
Then I copied all .war .ear and .jar files in $JAS_HOME/jars into
$JBOSS_HOME/server/specj/deploy.
Then I ran
> run.sh -c specj

I got the following output which indicates jboss server deployed the beans incompletely:

==============================================================
===========

JBoss Bootstrap Environment

JBOSS_HOME: /usr/java/jboss

JAVA: /usr/java/j2sdk1.4.2_05/bin/java

JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh
CLASSPATH:
/usr/java/jboss/bin/run.jar:/usr/java/j2sdk1.4.2_05/lib/tools.jar
==============================================================
===========
.................
.................
02:44:35,315 INFO [TomcatDeployer] deploy, ctxPath=/,
warUrl=file:/usr/java/jboss/server/specj/deploy/jbossweb-tomca
t50.sar/ROOT.war/
02:44:37,271 INFO [WrapperDataSourceService] Bound
connection factory for resource adapter for ConnectionManager
> 'jboss.jca:name=DefaultDS,service=DataSourceBinding to JNDI
> name 'java:DefaultDS'
> 02:44:37,309 INFO [TomcatDeployer] deploy,
> ctxPath=/jmx-console,
> warUrl=file:/usr/java/jboss/server/specj/deploy/jmx-console.war/
> 02:44:37,715 INFO [TomcatDeployer] deploy,
> ctxPath=/emulator,
> warUrl=file:/usr/java/jboss/server/specj/tmp/deploy/tmp16040em
> ulator-exp.war/
> 02:44:38,260 INFO [TomcatDeployer] deploy,
> ctxPath=/supplier,
> warUrl=file:/usr/java/jboss/server/specj/tmp/deploy/tmp16041su
> pplier-exp.war/
> 02:44:38,884 INFO [TomcatDeployer] deploy, ctxPath=/web,
> warUrl=file:/usr/java/jboss/server/specj/tmp/deploy/tmp16042we
> b-exp.war/
> 02:44:39,172 ERROR [URLDeploymentScanner] Incomplete
> Deployment listing:
> Packages waiting for a deployer:
> org.jboss.deployment.DeploymentInfo@a31eeeaf {
> url=file:/usr/java/jboss/server/specj/deploy/SPECjAppServer.ear }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/usr/java/jboss/server/specj/deploy/SPECjAppServer.ear
> altDD: null
> lastDeployed: 1098690279167
> lastModified: 1098690279000
> mbeans:
>
> org.jboss.deployment.DeploymentInfo@99874d8f {
> url=file:/usr/java/jboss/server/specj/deploy/emulator.ear }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/usr/java/jboss/server/specj/deploy/emulator.ear
> altDD: null
> lastDeployed: 1098690279170
> lastModified: 1098690279000
> mbeans:
>
> Incompletely deployed packages:
> org.jboss.deployment.DeploymentInfo@a31eeeaf {
> url=file:/usr/java/jboss/server/specj/deploy/SPECjAppServer.ear }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/usr/java/jboss/server/specj/deploy/SPECjAppServer.ear
> altDD: null
> lastDeployed: 1098690279167
> lastModified: 1098690279000
> mbeans:
>
> org.jboss.deployment.DeploymentInfo@99874d8f {
> url=file:/usr/java/jboss/server/specj/deploy/emulator.ear }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/usr/java/jboss/server/specj/deploy/emulator.ear
> altDD: null
> lastDeployed: 1098690279170
> lastModified: 1098690279000
> mbeans:
>
>
> 02:44:39,185 INFO [Server] JBoss (MX MicroKernel) [4.0.0RC1 (build:
> CVSTag=JBoss_4_0_0_RC1 date=200407202112)] Started in 25s:125ms
> 02:44:39,186 INFO [Tomcat5] Saw
> org.jboss.system.server.started notification, starting
> connectors 02:44:39,380 INFO [Http11Protocol] Starting
> Coyote HTTP/1.1 on http-0.0.0.0-8080
> 02:44:40,194 INFO [ChannelSocket] JK2: ajp13 listening on
> /0.0.0.0:8009
> 02:44:40,202 INFO [JkMain] Jk running ID=0 time=1/41
> config=null
> ===================================================================
>
> Obviously, all ear beans didnt get deployed. Why?
>
> Also, When I fired the driver, I got an IO error:
>
> > driver.sh
> Apps server is jboss40
> Driver Host: pcp060362pcs.unl.edu
> Binding controller to //pcp060362pcs.unl.edu/Controller
> Controller: Registering L1 on machine 129.93.68.36
> Controller: Registering O1 on machine 129.93.68.36
> L1 started ...
> O1 started ...
> Controller: Registering M1 on machine 129.93.68.36
> M1 started ...
> java.io.FileNotFoundException:
> http://localhost:8080/Emulator/EmulatorServlet?cmd=switchlog
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Ht pURLConnection.java:798)
> at
> org.spec.jappserver.launcher.Driver.switchLog(Driver.java:386)
> at
> org.spec.jappserver.launcher.Driver.runScript(Driver.java:319)
> at org.spec.jappserver.launcher.Script.main(Script.java:82)
>
How can I fix such problem. I was fighting with these errors for
several days. Any solution to them?
Thanks in advance!

Feng Xian

[aloubyansky]

Well after all, I removed the tag and just let the branch tag since I will try to simplify the DB feeding problem. I will try to tweak jae+sacha+noel xml/xsl/bsh solution to have the default settings put in DB with a bash file. What's annoying with the current in that the DB content format is dependant on the database (i.e mysql and hsqldb don't encode data the same)

[terryxian]

Hello all,

I managed to integrate MQSeries with JBoss MDB. As long as I don't change the message-driven-bean configuration in standardjboss.xml it seems to work.
But I have to limit the MDB instances to 1. So I changed standardjboss.xml as follows:

<proxy-factory-config>
DefaultJMSProvider
StdJMSPool
<!--MaximumSize>15</MaximumSize-->
1
true
1

10
<!--DLQConfig>
queue/DLQ
10
0
</DLQConfig-->

</proxy-factory-config>

What happens is that when a few messages (5-10) are in the queue, JBoss seems to hang.
Im using Jboss 3.2.1 and Websphere MQ 5.3.
I turned on TRACE and the last line is:
18:16:23,178 TRACE [StdServerSessionPool] getting a server session

So it seems to hang in StdServerSessionPool at line 190:
synchronized (sessionPool)

When I run it in the debugger and stop and the line everything works fine, so it seems to be a timing problem with this synchronized(sessionPool).

Do I have to change my configuration somehow or is it a bug?

Any help would be appreciated

Rudi

[aloubyansky]

The fact that EAR deployer is not available hints that the specj configuration was not created properly. What does the specj directory contain?
You don't need to copy any war, jar, ear files. This all is done for you by deploy-all target.

[terryxian]

The specj directory under $JBOSS_HOME/server contains six sub-directories:
conf deploy lib log tmp work
among them the directory 'deploy' contains all ear files.
Why I copied these files manually is that I am afraid the command 'ant .. deploy-all" didnt copy .war files.
The other question is that jboss40.xml provided by the toolkit seems incorrect. You can easily see that it refers to the file config/jboss32.env. It is supposed to refer to jboss40.env, but no such file in config directory.
Now I am frustrated about jboss4.0. Do I need to try jboss3.2??

[aloubyansky]

There is no jboss40.env. jboss32.env works for both 3.2 and 4.0.
What else does the deploy directory contain?

[terryxian]

Actually, there are only three files after I ran ''ant ..... deploy-all'' comand.
These three files are:

emulator.ear
jboss32-oracle-ds.xml
SPECjAppServer.ear

[aloubyansky]

Do you have default configuration (server/default) in jboss-4.0?

[terryxian]

Yes, it has

[aloubyansky]

What is the value of J2EE_HOME and the location of jboss-4.0?

[terryxian]

J2EE_HOME=/usr/java/jboss

/usr/java/jboss contains all jboss4.2 files (five directories):

bin/
client/
docs/
lib/
server/

[terryxian]

Actually, I am now trying jboss3.2.6, but I cannot deploy ear beans still.
After I ran
> run.sh -c spec
I got the following errors:

2004-10-26 02:10:03,659 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/usr/java/jboss/server/specj/de
ploy/SPECjAppServer.ear
2004-10-26 02:10:05,776 INFO [org.jboss.ejb.EjbModule] Deploying RuleEnt
2004-10-26 02:10:06,311 INFO [org.jboss.ejb.EjbModule] Deploying DiscountEnt
2004-10-26 02:10:06,327 INFO [org.jboss.ejb.EjbModule] Deploying CustomerEnt
2004-10-26 02:10:15,600 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
java.lang.NoClassDefFoundError: oracle/dms/console/DMSConsole
at oracle.jdbc.driver.DMSFactory.(DMSFactory.java:28)
.........................................

A lot if errors. the root cause is that I cannot find class DMSConsole. But I already added classes12dms.jar to CLASSPATH.
Why???????? jboss4.0 is still not working also.. :-(

[aloubyansky]

There is a target specj-config. Is it executed? It copies stuff from default to specj. Can you now figure out why specj is empty? Add some echo logging from the target.

[terryxian]

Sorry I didnt make it clearer. Actually, there are several default files other than the three files just mentioned:

jbossweb-tomcat50.sar/
jmx-console.war/
jboss-local-jdbc.rar
jboss-xa-jdbc.rar
jbossjca-service.xml

[aloubyansky]

Ok, then paste the following into jboss40-service.xml somewhere inside server element:

 <!-- ==================================================================== -->
 <!-- The deployers... -->
 <!-- ==================================================================== -->

 <!-- EJB deployer, remove to disable EJB behavior-->
 <mbean code="org.jboss.ejb.EJBDeployer" name="jboss.ejb:service=EJBDeployer">
 <attribute name="VerifyDeployments">true</attribute>
 <attribute name="ValidateDTDs">false</attribute>
 <attribute name="MetricsEnabled">false</attribute>
 <attribute name="VerifierVerbose">true</attribute>

 <!--
 StrictVerifier: Setting this to 'true' will cause all deployments
 to fail when the Verifier detected a problem with the contained
 Beans.
 -->
 <attribute name="StrictVerifier">true</attribute>

 <depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>
 <depends optional-attribute-name="WebServiceName">jboss:service=WebService</depends>
 </mbean>

 <!-- EAR deployer, remove if you are not using Web layers -->
 <mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer">
 </mbean>

The deployers where taken out of jboss-service.xml and deployed as -deployer.xml in recent Branch_4_0. That's probably why you have problems.