[Beginners Corner] - Objects transfer to MySQL
by Rockym
Hi; I'm trying to transfer the Persisten Objects to MYSQL, but I have a problem, I am trying to move to my database, but It only creates the table, but doesn't move to MySQL. here is a litltle part of the error.
17:38:36,552 WARN [ServiceController] Problem starting service jboss.j2ee:jar=tutorialEstudiante.jar,name=EstudianteDAOBean,service=EJB3
javax.naming.NamingException: Could not bind stateful proxy with ejb name EstudianteDAOBean into JNDI under jndiName: EstudianteDAOBean/remote [Root exception is javax.naming.NameAlreadyBoundException]
at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:79)
at org.jboss.ejb3.stateful.StatefulRemoteProxyFactory.start(StatefulRemoteProxyFactory.java:88)
I don't know, the connector and the mysql-ds.xml are well located, so I don't know what's happening
Thanks Rodrigo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969135#3969135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969135
19 years, 7 months
[EJB 3.0] - Query parameter is modified and return as null
by urswag
I use a stateless session bean this method.
In this query the first parameter textKey is set to password.
The query returns a label object with textKey field value null.
It is completly unlogical, the property is different to the search property but an object is found.
And as consequence somewhere afte the call of the method the database field texkey will set to null.
anonymous wrote :
| public Label findByTextKey(String textKey, Language language) {
|
| Label label = (Label) labelsMap.get(textKey);
| if (label == null) {
| Query query = manager.createQuery(
| "from Label l where l.textKey = :textKey and l.language = :language");
| query.setParameter("textKey", textKey);
| query.setParameter("language", language);
| try {
| label = ((Label) query.getSingleResult());
| labelsMap.put(textKey, label);
| }
| catch (NoResultException nre) {
|
| }
| }
|
| return label;
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969129#3969129
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969129
19 years, 7 months
[Management, JMX/JBoss] - Re: Scheduler Jboss
by petr5250
"danj" wrote : "schrouf" wrote : Up to my knowledge it has always been "time from finish until next start".
|
| Strange. We have a nightly job that takes somewhere between 8 s and 50 min. We have configured it with SchedulePeriod = 24 * 60 * 60 * 1000.
|
| Using 3.2.5, the job has started same time every night (01:00), and finishin within the hour, in good time before people arrive in the morning.
|
| However, since upgrading to 3.2.7, the jobs have start "slipping", i e starting later and later. And, the slip is exactly the time the job took, i e starting at the last nights finish-time. If this is the intended behaviour, it feels strange.
I have exactly same problem, so after more then a year I want to ask, if there was any developement of this issue.
Thanks Petr
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969128#3969128
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969128
19 years, 7 months
[Clustering/JBoss] - Re: Weird apache behaviour in load-balancing, and form-based
by bstansberry＠jboss.com
Great!
Well, the first thing to do is think hard about SavedRequest and see if there is any reason it can't be Serializable. If not, then
1) Open a Feature Request JIRA under the Application Server project on jira.jboss.com.
2) You need to post a patch to the Tomcat development list making SavedRequest Serializable. I'm not a Tomcat committer, so I can't just commit it for you; needs to be blessed and committed by the TC people. If you want, reference the JIRA issue so they know what you're working toward.
3) Then we need to deal with replicating the note itself. In Branch_4_0 you're limited in what you can do, as changing the serialized format of a session is not allowed. So, probably the thing to do is in ClusteredSession override setNote(), check if the key is for your SavedRequest, and if it is also cache the value in a transient field. Then update write/readExternal to store your cached SavedRequest under a special key in the regular attribute map (via setAttribute()). This ensures the SavedRequest is stored in a way that's already part of the existing serialized format. You need to think about this; want to make sure the SavedRequest doesn't remain in the attribute map on either the sender or receiver side, no matter which of the ClusteredSession subclasses is used (SessionBased, FieldBased or AttributeBasedClusteredSession).
In HEAD we have more flexibility as to what to do, as it's OK to change the serialized format because there have been no releases of the 5.0.x series yet. I'm tempted to just replicate the notes map (or better yet a copy of it with anything that doesn't implement Serializable removed). But would need to analyze all uses of the map first.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969115#3969115
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969115
19 years, 7 months