[JBoss Tools (users)] - Re: Seam EAR deployment problem
by speleomaniac
No it would be just unreadable :)
Anyway, I start surfing in the JBoss Tools Code, especially related with the problem I mentioned before in this thread...
I found the classes SeamFacetPostInstallDelegate and RegistrationHelper for registering the modules to a selected server after the creation of the Seam Facet.
Now my question, if I click run or debug project on the server, is any other component from JBoss Tools called.
In RegistrationHelper, publish to the server is already called but from my experiance I can say that when we say run/debug on server, eclipse build the project and republish it.
Is this happening in JBoss Tools or completely in WTP? If it is happening in JBoss Tools can you give me some tips where to look (or some other people that I can ask?)...
If it everything happening in WTP then I would start looking in m2eclipse to find out what can I do there?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203268#4203268
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203268
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Re: Problem deploying multiple WAR and MDB together
by randy.layman
I actually have a workable solution, but I still don't understand why this is needed.
In my EAR file I included the files to support the newer version of TreeCache (erby, jgroups, jboss-common-core 2.2.8, jcip-annotations, c3p0, and jbosscache-core 2.2.0). With these files in my EAR file, and referred to from a manifest of my WAR file, the MDB would not deploy with the error mentioned below.
To fix this, I moved the files above into my WAR's lib directory (and my code that directly referenced it) and removed it from the manifest file. Now, everything starts up and runs correctly.
I'm guessing that one of the JAR files for TreeCache is doing something to the JNDI lookup for StdJMSPool, but I can't figure out what it would be doing that would cause a problem.
I did briefly try upgrading to JBoss 4.2.3, and things appeared to start correctly, but I had other issues I didn't want to fix right now (particularly JSF)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203264#4203264
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203264
17 years, 3 months
[JBoss jBPM] - EJB Timer Lookup problem in BPEL
by dhanushgopinath
Hi,
I am using jbpm bpel 1.1.1 with Jboss 4.2.0 and I am extensively using the BPEL process using JBPM/BPEL API's.
I am getting this exception while the process ends
18:39:11,128 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
| org.jbpm.JbpmException: ejb timer entity lookup problem
| at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.getTimerEntityHome(EntitySchedulerServiceFactory.java:43)
| at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.openService(EntitySchedulerServiceFactory.java:50)
| at org.jbpm.svc.Services.getService(Services.java:150)
| at org.jbpm.svc.Services.getCurrentService(Services.java:94)
| at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
| at org.jbpm.graph.exe.ProcessInstance_$$_javassist_351.end(ProcessInstance_$$_javassist_351.java)
| at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
| at org.jbpm.graph.exe.Token.end(Token.java:301)
As per the code in CVS the EntitySchedulerServiceFactory class in jbpm bpel is looking up for a JNDI name java:comp/env/ejb/LocalTimerEntityBean and expecting org.jbpm.ejb.LocalTimerEntityHome.
But while deploying the JBPM BPEL it binds the jndi name ejb/LocalTimerEntityBean against the Local Home org.jbpm.ejb.LocalTimerEntityHome. I got this information from the ejb-jar.xml file in jbpm-enterprise.jar (inside jbpm-bpel.ear).
So when the EntitySchedulerServiceFactory code tries to lookup, it doesnt get it and throws the above exception.
This exception ONLY happens when I start the process in API mode. If I use SOAP-UI to test, it works perfectly fine.
Do I need to configure anything extra? Please let me know. I am kind of stuck here.
Thanks in Advance
Dhanush
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203251#4203251
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203251
17 years, 3 months
[JNDI/Naming/Network] - Error writing response to... Broken Pipe exception
by aiesulauro
Any hints on tracking down the source of the attempted
naming server access would be appreciated.
The exception shown below appears once per minute in the
server log.
The computing environment is jboss-5.0.0.GA (standard configuration),
RHEL5, on a machine with 8G of RAM and two 2GHz dual core processors.
The database is mySql executing locally (same machine as the JBossAS
instance).
The IP address shown in the exception is a VIP and the appServer is
started with the -b option.
/usr2/jboss/jboss-5.0.0.GA/bin/run.sh -c standard -b jestdev03
https://jira.jboss.org/jira/browse/JBAS-3417 references the problem but
does not suggest a solution. JBAS-3417 states that the source of the
naming port access must be tracked down.
| 2009-01-16 00:00:02,025 DEBUG [org.jboss.naming.Naming] (JBoss System Threads(1)-6) Error writing response to /134.243.51.107
| java.net.SocketException: Broken pipe
| at java.net.SocketOutputStream.socketWrite0(Native Method)
| at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
| at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
| at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1838)
| at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1747)
| at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1249)
| at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1203)
| at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1387)
| at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
| at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1538)
| at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:329)
| at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:591)
| at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203249#4203249
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203249
17 years, 3 months