[Persistence, JBoss/CMP, Hibernate, Database] - OpenJPA and JBoss
by hungtru
Hi there,
Has anyone used OpenJPA with JBoss?
I've run into a problem where I have an application running in WAS utilizing OpenJPA and porting it over to JBoss. However, when deployed in JBoss, after removing a slew of errors, it seems that one of my EJBs is stuck.
I think that because i see it created in the server.log, but never started. It contains @PersistenceContext and i can see in the server.log that it states that the bean is dependent on the persistence unit. Which I'm gathering that the persistence unit needs to appear in JNDI or somewhere before JBoss will complete the startup.
Can anyone help :) ??
I have all the jars for openjpa in the jboss/server/all/lib directory. I did try to move them into my application directory, it was no help.
Any help would be greatly appreciated.
H
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167221#4167221
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167221
17 years, 8 months
[JBoss Portal] - Re: Accessing Request parameters from jsf portlet
by eskape
Wesley,
It definitely looks like this problem has nothing to do with portlet bridge.
When debugging GenericFacesPortlet.doDispatch() method, our team has realized that RenderRequest provided by PortletContainerImpl.doRender() invocation has null parameters (our uri is like http://localhost/portal/portal/default/mypage?foo=bar).
Thus, it is absolutely not possible implementing, f.ex., user password restoring use-case (user receives "activation link" with generated hash code by email, clicks it and enters special portal page with "enter your new password" prompt) with JBoss Portal. Saying we are pretty surprised is like saying nothing at all. :-(
Then we were looking through JBoss Identity Portlet and found out that they are using some "URLCommand MBeans" there to handle these urls. They are OF COURSE proprietary, not documented, and I am NOT going to file jira issue regarding this because answer will be the same as we had here (https://jira.jboss.org/jira/browse/JBPORTAL-2056): "THIS IS A PRIVATE API".
Atm we are trying to provide some workaround with RedirectServlet (out of jboss portal) deployed together with our ear which will handle urls like:
http://localhost/session-redirect?foo=bar&baz=bag&url=http://localhost/
then it will save all request parameters to http session and redirect to URL provided. This is ABSOLUTELY UGLY way of doing things, but we do not see any other possibilities to handle our problem.
I do not expect anyone will answer this, because posting to jboss forums is always public speaking to myself :(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167217#4167217
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167217
17 years, 8 months
[Persistence, JBoss/CMP, Hibernate, Database] - Urgent : Hibernate , Jboss cache lock issues on jboss 4.2.0.
by Rajesh.Gajula
Hi,
I have portal application deployed in jboss cluster having 3 servers in it. When i deploy my .sar file and test it .. some times i get the below exception from the logs and failing to load the page ..
INFO | jvm 1 | 2008/07/29 02:43:26 | Caused by: org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/org/
jboss/portal/identity/db/HibernateUserImpl/dynamic/org.jboss.portal.identity.db.HibernateUserImpl.dynamic#13, caller=GlobalTr
ansaction:<3.57.41.6:38538>:25961, lock=write owner=GlobalTransaction:<3.57.41.5:56335>:25816 (activeReaders=0, activeWriter=
Thread[UpHandler (STATE_TRANSFER),5,JGroups threads], waitingReaders=0, waitingWriters=0, waitingUpgrader=0)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.Node.acquire(Node.java:500)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(Pe
ssimisticLockInterceptor.java:379)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLo
ckInterceptor.java:307)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(Pessimistic
LockInterceptor.java:181)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.ja
va:32)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInte
rceptor.java:39)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInte
rceptor.java:39)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.interceptors.TxInterceptor.replayModifications(TxIntercept
or.java:554)
INFO | jvm 1 | 2008/07/29 02:43:26 | ... 22 more
INFO | jvm 1 | 2008/07/29 02:43:26 | Caused by: org.jboss.cache.lock.TimeoutException: write lock for /org/jboss/portal/
identity/db/HibernateUserImpl/dynamic/org.jboss.portal.identity.db.HibernateUserImpl.dynamic#13 could not be acquired after 1
0000 ms. Locks: Read lock owners: []
INFO | jvm 1 | 2008/07/29 02:43:26 | Write lock owner: GlobalTransaction:<3.57.41.5:56335>:25816
INFO | jvm 1 | 2008/07/29 02:43:26 | (caller=GlobalTransaction:<3.57.41.6:38538>:25961, lock info: write owner=GlobalTr
ansaction:<3.57.41.5:56335>:25816 (activeReaders=0, activeWriter=Thread[UpHandler (STATE_TRANSFER),5,JGroups threads], waitin
gReaders=0, waitingWriters=0, waitingUpgrader=0))
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:206)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.Node.acquireWriteLock(Node.java:529)
INFO | jvm 1 | 2008/07/29 02:43:26 | at org.jboss.cache.Node.acquire(Node.java:476)
INFO | jvm 1 | 2008/07/29 02:43:26 | ... 31 more
INFO | jvm 1 | 2008/07/29 02:44:24 | 02:44:24,278 INFO [STDOUT] <2008.07.29 02:44:24.278> {2c39b9} L2 hrssp: --T-->Mon
itor alive... start system checks - ERR - ERR -
ERR - ERR LL:2
INFO | jvm 1 | 2008/07/29 02:46:41 | 02:46:41,021 WARN [BIRTDeleteTimer] --> Run Called 1.2 ()
INFO | jvm 1 | 2008/07/29 02:46:41 | 02:46:41,023 WARN [BIRTDeleteTimer] <-- Run Call Done 1.2 ()
INFO | jvm 1 | 2008/07/29 02:49:24 | 02:49:24,284 INFO [STDOUT] <2008.07.29 02:49:24.284> {2c39b9} L2 hrssp: --T-->Mon
And then returning 500 status messages as
HTTP Status-Code=500 (org.jboss.cache.lock.TimeoutException: read lock for /org/jboss/portal/identity/db/HibernateUserImpl/dynamic/org.jboss.portal.identity.db.HibernateUserImpl.dynamic#10 could not be acquired by GlobalTransaction:<3.57.41.4:42086>:20771 after 10000 ms. Locks: Read lock owners: [] Write lock owner: GlobalTransaction:<3.57.41.5:56335>:25446 , lock info: write owner=GlobalTransaction:<3.57.41.5:56335>:25446 (activeReaders=0, activeWriter=Thread[UpHandler (STATE_TRANSFER),5,JGroups threads], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)) for "http://abcd.com/aaa/
Could you please suggest to solve the issue
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167207#4167207
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167207
17 years, 8 months
[Remoting] - Re: JBoss Remoting 2.2.2.SP9 status?
by ron.sigal＠jboss.com
Remoting 2.2.2.SP9 is tagged (http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/2.2.2-SP9), but I've been thinking of 2.2.2.SP8 as the "official" release, in the sense that it is shipping with the current round of Application Server releases. There are just a few additional fixes for 2.2.2.SP9:
| Bug
|
| * [JBREM-1005] - Prevent build up of cancelled TimerTasks in bisocket transport
| * [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker
|
| Feature Request
|
| * [JBREM-1010] - Add feature to declaratively turn on leasing for 2.2.2
|
of which only JBREM-1005 is particularly significant, and that's only for JBossMessaging / bisocket transport users.
So, it is buildable, but I didn't plan to announce or release it. I could, of course, if there's a real demand. Otherwise, I'll release it, or more likely 2.2.2.SP10, in a couple of months.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167204#4167204
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167204
17 years, 8 months
[Beginners Corner] - Message redelivered=6, instead of 10??
by gan.gary
I have a Jboss apps, when it hit exception:
09:39:36,858 WARN [AbstractDLQHandler] Message redelivered=6 max=5 sending it t
| o the dlq SpyTextMessage {
| Header {
| jmsDestination : QUEUE.XXX/TestResults
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:3-12172955759981
| jmsTimeStamp : 1217295575998
| jmsCorrelationID: null
| jmsReplyTo : null
| jmsType : null
| jmsRedelivered : true
| jmsProperties : {JMS_JBOSS_REDELIVERY_COUNT=6}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:3
| }
I thought it's configured at "%JBOSS_HOME%/all/conf/standardjboss.xml", but it's the default value (10 times):
<invoker-proxy-binding>
| <name>message-driven-bean</name>
| <invoker-mbean>default</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <CreateJBossMQDestination>true</CreateJBossMQDestination>
| <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
anyone? I do not think it's at default folder as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167203#4167203
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167203
17 years, 8 months