[JBoss/Spring Integration] - spring deployer -- NoClassDefFound exception (works on Linux
by odigokid
Hi,
I have installed a JBoss application on Solaris 10, the same deployment works fine on Linux, AIX.
I am now getting this NoClassDef Exception when I can clearly see that the class is located in the spring-core.jar file that is in the server/default/lib folder and is also located in the jboss-spring.deployer package that is in the deploy directory.
I can't figure out why I am getting this NoClassDef Exception when deploying on Solaris.
I am using JBoss 4.0.4 I am using a spring-deployer version of 1.2 because I need to remain compatible with 1.4 JVM. However in this particular example, the JVM's for both Linux and solaris are 1.5.
The error is below
INFO | jvm 1 | 2008/06/20 15:58:12 | --- Incompletely deployed packages ---
INFO | jvm 1 | 2008/06/20 15:58:12 | org.jboss.deployment.DeploymentInfo@548a161b { url=file:/usr/local/jboss/server/default/deploy/Authentication.spring/ }
INFO | jvm 1 | 2008/06/20 15:58:12 | deployer: org.jboss.spring.deployment.SpringApplicationContextDeployer@15bfdbd
INFO | jvm 1 | 2008/06/20 15:58:12 | status: Deployment FAILED reason: org/springframework/core/io/support/ResourcePatternResolver
INFO | jvm 1 | 2008/06/20 15:58:12 | state: FAILED
INFO | jvm 1 | 2008/06/20 15:58:12 | watch: file:/usr/local/jboss/server/default/deploy/Authentication.spring/
INFO | jvm 1 | 2008/06/20 15:58:12 | altDD: null
INFO | jvm 1 | 2008/06/20 15:58:12 | lastDeployed: 1213991864100
INFO | jvm 1 | 2008/06/20 15:58:12 | lastModified: 1213961722000
INFO | jvm 1 | 2008/06/20 15:58:12 | mbeans:
INFO | jvm 1 | 2008/06/20 15:58:12 |
INFO | jvm 1 | 2008/06/20 15:58:12 |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159667#4159667
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159667
17 years, 10 months
[JBoss jBPM] - Re: TaskInstance.setActorId(String) causes set TaskInstance
by Octomac
I managed to find the problem, so I thought I'd come back here and post it just in case this helps anyone else.
The default JBPM database configuration uses the type "BIT" for boolean columns. BIT doesn't map exactly correctly to Java's "true" and "false," or even 1 and 0. As a result, no matter what data I placed into the database, JBPM and Hibernate would interpret it as "true." So, whenever I called, say, TaskInstance.setActorId("Name"), the Hibernate query was inserting correct data to the database, but that data was being interpreted as a BIT value.
To correct the problem, I manually changed each BIT column to a TINYINT(1) type. This ensured that the data Hibernate was passing into my database was interpreted correctly, and as a result, I am now able to handle assignment and creation of tasks correctly.
If anyone else experiences the same problem that I did, hopefully this will help. Thanks again to the JBoss Forum members who assisted me in this matter!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159666#4159666
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159666
17 years, 10 months
[EJB 3.0] - Timer with Jboss and MySql
by finalsayan
Hi,
i am new to EJB 3.0 and jboss
i am trying to create a timer with this code taken from the j2ee documentation
| /**
| * TimerBean is a stateless session bean that creates a timer and prints out a
| * message when a timeout occurs.
| * Created Jan 9, 2006 3:44:08 PM
| * @author ian
| */
| @Stateless
| public class TimerSessionBean implements TimerSession {
| private static final Logger logger = Logger.getLogger(
| "com.sun.tutorial.javaee.ejb.timersession.TimerSessionBean");
| @Resource
| TimerService timerService;
|
| public void setTimer(long intervalDuration) {
| Timer timer = timerService.createTimer(
| intervalDuration,
| "Created new timer");
| }
|
| @Timeout
| public void timeout(Timer timer) {
| System.out.println("Timeout occurred");
| }
| }
|
I get these errors...can someone help me?
I use the "4.5. EJB Timer Configuration" of the jboss configuraton guide
| <!-- ==================================================================== -->
| <!-- J2EE Timer Service -->
| <!-- ==================================================================== -->
|
| <!-- An EJB Timer Service that is Tx aware -->
| <mbean code="org.jboss.ejb.txtimer.EJBTimerServiceImpl"
| name="jboss.ejb:service=EJBTimerService">
| <attribute name="RetryPolicy">jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay</attribute>
| <attribute name="PersistencePolicy">jboss.ejb:service=EJBTimerService,persistencePolicy=database</attribute>
| <attribute name="TimerIdGeneratorClassName">org.jboss.ejb.txtimer.BigIntegerTimerIdGenerator</attribute>
| <attribute name="TimedObjectInvokerClassName">org.jboss.ejb.txtimer.TimedObjectInvokerImpl</attribute>
| <depends optional-attribute-name="TransactionManagerFactory" proxy-type="org.jboss.tm.TransactionManagerFactory">
| jboss:service=TransactionManager
| </depends>
| </mbean>
|
| <!-- A retry policy that uses a fixed interval in milli seconds -->
| <mbean code="org.jboss.ejb.txtimer.FixedDelayRetryPolicy" name="jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay">
| <attribute name="Delay">100</attribute>
| </mbean>
|
| <!-- A persistence policy that does not persist the timers
| <mbean code="org.jboss.ejb.txtimer.NoopPersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=noop"/>
| -->
|
| <!--
| A persistence policy that persists timers to a database.
|
| The 2 supported db persistence plugins are:
| org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin
| org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin
|
| The table name defaults to "TIMERS". It can be overriden using the
| 'TimersTable' attribute if the persistence plugin supports it.
| When overriding the timers table, an optional schema can be specified
| using the syntax [schema.]table
| -->
| <mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
| <!-- DataSourceBinding ObjectName -->
| <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=MySqlDS</depends>
| <!-- The plugin that handles database persistence -->
| <attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>
| <!-- The timers table name -->
| <attribute name="TimersTable">TIMERS</attribute>
| </mbean>
|
| <datasources>
| <local-tx-datasource>
| <jndi-name>MySqlDS</jndi-name>
| <connection-url>jdbc:mysql://localhost:3306/bidone</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>root</user-name>
| <password>*******</password>
| </local-tx-datasource>
| </datasources>
|
| 19:29:27,693 INFO [EJB3Deployer] Deployed: file:/home/finalsayan/Desktop/SE2/3-IMPLEMENTATION/jboss-4.2.2.GA/server/default/tmp/deploy/tmp46825BIDONE.ear-contents/BIDONEEJB.jar
| 19:29:27,700 INFO [TomcatDeployer] deploy, ctxPath=/BIDONEWeb, warUrl=.../tmp/deploy/tmp46825BIDONE.ear-contents/BIDONEWeb-exp.war/
| 19:29:27,824 INFO [EARDeployer] Started J2EE application: file:/home/finalsayan/Desktop/SE2/3-IMPLEMENTATION/jboss-4.2.2.GA/server/default/deploy/BIDONE.ear
| 19:29:27,845 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
| State: FAILED
| Reason: java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=MySqlDS,service=metadata
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=MySqlDS
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
| State: FAILED
| Reason: java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=MySqlDS,service=metadata
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=MySqlDS
|
|
| 19:29:27,976 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
| 19:29:28,105 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
| 19:29:28,128 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:276ms
|
thank you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159663#4159663
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159663
17 years, 10 months