Re: [jboss-user] [JBoss Web Services] - JBossWS - AS 7 FAQ
by Jefferson Diefenbach
Jefferson Diefenbach [http://community.jboss.org/people/jdiefenbach83] commented on the document
"JBossWS - AS 7 FAQ"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16722#comment-7078
--------------------------------------------------
So, I has an application on AS6, it's using Apache CXF, that's all Ok. I'm trying to migrate to AS7 but it doesn't export the JARs to use in my code, like AS6. I read that FAQ and I don't found out a way to make to work my application. I need to use both client and server side. That's FAQ is so confuse and doesn't explain exactly how to do it. I don't care to rewrite my application, only need a sample. Please, can you help me?
--------------------------------------------------
14 years, 9 months
[jBPM] - jbpm5.x compatability with Sybase
by Sasi R
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"jbpm5.x compatability with Sybase"
To view the discussion, visit: http://community.jboss.org/message/616189#616189
--------------------------------------------------------------
While using Sybase as the underlying , we are getting the below issue as there is a BLOB column in ProcessInstanceInfo table. Is this a known issue and please let me know if you know the work around
I understand its an issue of Sybase/Hibernate but its tied with jBPM 5.x usage
1. javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not insert: [org.jbpm.persistence.processinstance.ProcessInstanceInfo]
at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614)
at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:226)
at org.jbpm.persistence.JpaProcessPersistenceContext.persist(JpaProcessPersistenceContext.java:22)
at org.jbpm.persistence.processinstance.JPAProcessInstanceManager.addProcessInstance(JPAProcessInstanceManager.java:33)
at org.jbpm.process.instance.AbstractProcessInstanceFactory.createProcessInstance(AbstractProcessInstanceFactory.java:36)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:139)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:119)
at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1099)
at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:302)
at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:119)
at org.drools.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:38)
at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:295)
at org.drools.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:219)
at com.jbpm.sample.StartupServlet.init(StartupServlet.java:129)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:92)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.hibernate.exception.GenericJDBCException: could not insert: [org.jbpm.persistence.processinstance.ProcessInstanceInfo]
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:64)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2186)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2666)
at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:71)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:321)
at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:204)
at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:130)
at org.hibernate.ejb.event.EJB3PersistEventListener.saveWithGeneratedId(EJB3PersistEventListener.java:49)
at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:154)
at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:110)
at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:61)
at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:645)
at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:619)
at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:623)
at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:220)
... 28 more
*Caused by: java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0SL: Unsupported SQL type 2004.*
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseErrorCheckDead(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.language(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.sendQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.sendQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365)
at org.hibernate.id.IdentityGenerator$GetGeneratedKeysDelegate.executeAndExtract(IdentityGenerator.java:94)
at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:57)
... 43 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616189#616189]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 9 months
[JNDI and Naming] - regarding ejb remote access with global JNDI Namespace
by Dominique Jean-Prost
Dominique Jean-Prost [http://community.jboss.org/people/djeanprost] created the discussion
"regarding ejb remote access with global JNDI Namespace"
To view the discussion, visit: http://community.jboss.org/message/616187#616187
--------------------------------------------------------------
Hello everybody,
After searching for an error during half a day, I found a very strange behaviour in jboss 5.1.0GA that I can't explain. Here is my case :
My jboss server holds an EJB 2.1 bound to this jndi name : +"A"+. Please note that it is bound to a global jndi namespace (not a +java:+ namespace). As is, it is considered as remote.
I wrote a unit test where I :
- lookup this EJB using +java:/A+ <-- my error I searched for a long time
- call a method on the stub
--> It works, even though I made a mistake on the jndi name.
Then I deployed a second ejb on another jboss server, which looked up the A ejb on the other server using the same "wrong" name +"java:/A"+ : I got the *NameNotBoundException* which is normal.
After searching half a day the reason why I got the *NameNotBoundException,* I realized that my mistake was the jndi name I kept on using : +java:/A+
So I changed it to "A", and then my lookup started to work.
I now have found my error and am happy with it. The only thing I don't understand is that my code in my unit test still works using +java:/A+ which is false.
Is there somewhere in jboss some code that would say. "ok, even if the name my client is requesting is +java:/foo+, I try to search +foo+ just in case my client would have made a mistake, because I do know that I'm called by a remote client". This behaviour would not occur when called within a jboss server, even if used as a remote client for another server ?
Can someone explain it to me ?
Thank you.
Dom
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616187#616187]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 9 months
[JBoss Messaging] - Can I remove the string "queue/" which infront the queue name ?
by farm tk
farm tk [http://community.jboss.org/people/farmtk] created the discussion
"Can I remove the string "queue/" which infront the queue name ?"
To view the discussion, visit: http://community.jboss.org/message/616175#616175
--------------------------------------------------------------
Hi, wish to get the answer of the following :
I have the following queue to consume jms and is working well . The queue name is -- jms_ABCD. The following java program is in Server_B.
*@MessageDriven(*
*activationConfig =*
* { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),*
* @ActivationConfigProperty(propertyName="destination", propertyValue="queue/jms_ABCD")*
* }*
*)*
*public class TestReceive implements MessageListener {*
*......*
*}*
>From other server (says Server_B) need to send jms to the Server_A's queue "jms_ABCD". Due to the JMS tools constrain which use in Server_B, the lookup queue name cannot put as "...../queue/jms_ABCD". but only "...../jms_ABC". So I change the program in Server_A to as follow , just to remove the string "queue/" in front of the queue name "jms_ABCD" as follow :
*...*
*..*
*@ActivationConfigProperty(propertyName="destination", propertyValue="jms_ABCD")*
*..*
*..*
It cannot work, because the JNDIName of this queue still "*queue/jms_ABCD".* This can be seen in the jboss console as shown below :
http://community.jboss.org/servlet/JiveServlet/showImage/2-616175-16748/s... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-616175-167...
So next step is to change the JNDIName from "queue/jms_ABCD" to "jms_ABCD" and press "Apply Changes" button in jboss console.
However after shuntdown and restart jboss, the JNDIName of this queue still go back to "queue/jms_ABCD".
Could any one advice how to remove the "queue/" ? Thank you.
I am using JBoss 4.2.2.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/616175#616175]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 9 months
