[Installation, Configuration & Deployment] - Re: JBoss EJB Lifecycle
by iudoka
"genman" wrote : You need to post more information. Exceptions, code samples, test cases, etc.
I'm not sure what more information is needed, I believe that there is some EJB life cycle property that can be set in order to determine how long the container should hold on to an EJB before passivating it. I just can't for the life of me find which properties file has this property. I'm not sure if I'm being too vague but I'm not sure how else to explain it because my issue (I don't think) should be specific to any code, its more of a general question about property file for deploying EJB's.
I simply connect to an EJB via JNP and after about 30 minutes the EJB is passivated. I put in a print statement in the beans ejbPassivate() function and it prints on the server after about 30 minutes. I want to see how I can increase this passivation time to a high number if possible. And I'm under the impression that you can do it through a properties file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037563#4037563
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037563
19 years
[EJB/JBoss] - Error while using DBScheduleProvider with Sybase
by chandrasekarv
hi,
i am using database scheduler service in jboss ie DBScheduleProvider. For this i am using Sybase as database.As i doing all the configuration, i am not able to fetch data through DBSchedulerProvider.
Sybase Database Configuration
Sybase Adaptive Server Enterprise (ASE) is a database server by Sybase Inc. ASE is used on both UNIX and Linux platforms. As before, the first step is getting the database driver classes into the CLASSPATH, by copying the .jar file jconn2.jar to the /server/default/lib directory. Then use its data source by copying /docs/examples/jca/sybase-ds.xml to /server/default/deploy dir.
Modify the sybase-ds.xml configuration file, setting <driver-class/> to com.sybase.jdbc2.jdbc.SybDriver and <connection-url/> to jdbc:sybase:Tds::/, where is the Sybase host server, is the Sybase host server port number, and is the Sybase database name.
Then, as before, we need to modify standardjaws.xml or jaws.xml to set the and<type-mapping> elements:
java:/SybaseDS
<type-mapping>Sybase</type-mapping>
We also need to modify standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml to set the and <datasource-mapping> elements:
<jbosscmp-jdbc>
java:/SybaseDS
<datasource-mapping>Sybase</datasource-mapping>
</jbosscmp-jdbc>Finally, we modify login-config.xml to use the Sybase database. Add the following <application-policy/> element to the file:
<application-policy name = "SybaseDbRealm">
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name ="principal">sa</module-option>
<module-option name = "userName">sa</module-option>
<module-option name = "password"></module-option>
<module-option name = "managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=SybaseDS
</module-option>
</login-module>
</application-policy>By modifying the sybase-ds.xml, standardjaws.xml, standardjbosscmp-jdbc.xml, and login-config.xml, the JBoss 4.0 server is configured to be used with a Sybase database.
---
After done this also, i am still getting error. I dont know why it is coming.
If any one knows the solution, help me.
thanks in advance
by
chandrasekar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037561#4037561
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037561
19 years
[JBoss Seam] - Re: Seam CVS now on JBoss AS 4.2 CR1
by avbentem
"petemuir" wrote : Just download the zip for 4.2.CR1, unzip it, and deploy the app. No installer needed
You're right, thanks.
How can we assure the "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer" will be removed when Seam 1.3 is released? Should I add an issue to JIRA? This will also apply to the Getting Started, which is already outdated anyhow. Of course, we can change the wiki ourselves.
Just for the archives, to use Seam 1.3.x from CVS:
- download JBoss AS 4.2 CR1 and unzip it
- check-out jboss-seam from :pserver:anonymous@anoncvs.forge.jboss.com:/cvsroot/jboss
- edit build.properties to set jboss.home (ignore the Tomcat settings)
- run "ant antlr" to generate SeamTextParser and SeamTextLexer
- optionally edit build.xml to read something like the following (I guess this should be fixed in CVS):
<property name="version" value="1.3" />
| <property name="patchlevel" value="0.SNAPSHOT" />
- when getting compile errors in GWTRemoteService then optionally download the Google Web Toolkit (Beta), unzip, copy gwt-user.jar to jboss-seam/lib and add the JAR to Eclipse using Project, Properties, Java Build Path, Add JARs (this gets one com.google.gwt.user.client.*; I'm not sure if this is the right approach to get rid of the errors)
And then, for example:
- run "ant deploy" from examples/dvdstore
- browse to http://localhost:8080/seam-dvd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037560#4037560
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037560
19 years
[JBoss jBPM] - Re: deploying bpel as a service in jboss
by asma14
thinks Martin,
but i still have the same errors. i wonder how it can't bind data source ?
i put the xml file JbpmBpelDS.xml under jboss/server/default/deploy
| 15:50:37,375 FATAL [DatasourceConnectionProvider] Could not find datasource: java:/JbpmBpelDS
| javax.naming.NameNotFoundException: JbpmBpelDS not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(Unknown Source)
| at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
| at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:385)
| at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:61)
| at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1928)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211)
| at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:91)
| at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94)
| at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:98)
| at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:281)
| at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:526)
| at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:109)
| at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:56)
| 15:50:37,375 ERROR [JobExecutorThread] exception in job executor thread. waiting 30000 milliseconds
| org.hibernate.HibernateException: Could not find datasource
| at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:56)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
| at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:385)
| at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:61)
| at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1928)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211)
| at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:91)
| at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94)
| at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:98)
| at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:281)
| at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:526)
| at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:109)
| at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:56)
| Caused by: javax.naming.NameNotFoundException: JbpmBpelDS not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(Unknown Source)
| at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)
| ... 13 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037554#4037554
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037554
19 years