[JBoss Tools (users)] - Re: deployment error 404
by bmuralirao1980
iam using jboss ide 2,0 beta version and jboss server 4.0.
These are the steps i followed while creating my simple application
(1)FILE>>NEW>>>JBOSS ECLIPSE IDE>>>J2EE1.4 projects
(2)Right-click on your project in the Package Explorer.
Go to Propertiesâ>Java Build Path.
Click on the Source tab.
Click on Add Folder.
Click on Create New Folder.
Set the folder name to "src".
Select Yes when it asks you to remove the project as a source folder and to create a "bin" folder.
(3)Click on the Libraries Tab (while still under Propertiesâ>Java Build Path).
Click Add Variable.
Select ECLIPSE_HOME and click Extend.
Navigate to the plugins/org.eclipse.tomcat.4.1.x directory.
Select servlet.jar and click OK.
Click OK to exit the properties dialog.
Now, create a class called HelloWorldSerlvet in the com.devx.example package, using the following code in your servlet
and my servlets class was like this
package com.devx.example;
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.ServletOutputStream;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class HelloWorldServlet extends HttpServlet
{
protected void service(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
{
ServletOutputStream out = response.getOutputStream();
out.println("<h1>Hello World!</h1>");
then created a folder under src called WEB-INF. Then, created a file called web.xml in that folder, using the following source.
This was my xml file
<!DOCTYPE web-app PUBLIC
'-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN'
'http://java.sun.com/j2ee/dtds/web-app_2.2.dtd'>
<web-app>
<servlet-name>HelloWorldServlet</servlet-name>
<servlet-class>com.devx.example.HelloWorldServlet</servlet-class>
<servlet-mapping>
<servlet-name>HelloWorldServlet</servlet-name>
<url-pattern>/Hello</url-pattern>
</servlet-mapping>
</web-app>
(5)Right clicked on the project in the Package Explorer.
Select Propertiesâ>Packaging Configurations.
Right click in the right frame and click Add Std. Archive.
Select Standard-WAR.war and click OK.
Right click on the configuration and click Edit.
Rename it to helloworld.war.
Expand the configuration.
Right click on the line with Manifest.MF and remove it.
when i clicked ok packaging-build.xml file got created..
(6)Created a WAR file by right-clicking on the project and clicking Run Packaging.
(7)Right click on the WAR file, select Deployment, and then Deploy To...
It deployed sucessfully...but when i opened browser and tyed the url i got status code error 404....
please help me how to trace this.
murali rao
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160547#4160547
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160547
18 years
[JBoss Portal] - Dynamic portal page?
by eskape
Hello!
How do I create a dynamic page in JBoss Portal? We have a lot of portlets, each has its own 'status' view (we are using Help view so far, because JBoss does not support custom-portlet-mode), and we have to display each portlet's status on the special 'My Statistics' page for each user. For example, Wiki Portlet Status: "Total articles: 1000; My Articles: 20; Awaiting Approval: 5".
The problem is that portlets are being developed and deployed separately from the main application, thus we are not able to enumerate them in the -object.xml file.
The desired scenario should look like the following:
1) User clicks "My Statistics" page;
2) Some interceptor handles this click, iterates over available portlets and checks for some "supportsStatisticPage" property.
3) All selected portlets are being instantiated and added to the page programmatically.
Are there any possibilities to do so?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160546#4160546
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160546
18 years
[Beginners Corner] - Re: shutdown.bat and cntrl-c not working but web-console doe
by amast
First, I'd like to thank you for your clarity and comprehensive series of tests. I appreciate it greatly.
"PeterJ" wrote : If you have not changed the ports JBossAS is using, you should be able to stop JBossAS (running on the same machine) using:
|
| shutdown -S
|
|
Well, I'm not sure if we changed the ports JBossAS is using, but I do know that during our installation, we are required to enter an unused http, https, and AJP port. I used 14080 for the http, which you'll see in the netstat below. I tried shutdown -S from the same machine on another console to no avail.
"PeterJ" wrote :
| Are you running shutdown on the same machine on which JBossAS is running? If not, did you start JBossAS using the "-b 0.0.0.0" option? If you did, then stopping a remote JBossAS can be done using:
|
| shutdown -S --server=hostname
|
Yes, I am running shutdown on the same machine. Yes, I do start JBossAS using the "-b 0.0.0.0" option. When attempting to run from a remote location, I get an connectException that localhost:1099 is unreachable. If I add hostname:port to the -s flag, it takes a while and throws a failed to receive stub from server:port.
"PeterJ" wrote :
| If you tried the above and still have problems, do this:
|
| 1) run netstat (or tcpview) and note the ports opened by JBossAS (they will be assigned to 'java', if you are running multiple java apps, you will have to also look at the process id to identify the ports assigned to JBossAS)
|
Here you go... fortunately I'm only running one java.exe process: (edited for privacy)
TCP JBossServer:2847 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:2848 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:2849 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:9098 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:9099 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:12444 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:12445 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:12446 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:14009 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:14080 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:16083 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:16093 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
TCP JBossServer:11873 JBossServer.my.domain.com:0 LISTENING 3440 [java.exe]
For fun, I ran "shutdown -s JBossServer:port -S" on each of those ports and all of them sat there, as they have.
"PeterJ" wrote :
| 2) Post the java command run when you run shutdown.bat
|
3) Once shutdown.bat hangs, type CTRL-Break and post the thread dump.
Here's that Java command .bat is running and the resulting thread dump. (thanks for that cntrl-Break tip, very handy!)
C:\myProgram\instance8\OITAppServer\bin>shutdown -S --server=jsmith
"..\jvm\win32\bin\java" -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y -Djboss.boot.loader.name=shutdown.bat -classpath ";C:\myProgram\instance8\AppServer\bin\\shutdown.jar;C:\myProgram\instance8\AppServer\bin\/../client/jbossall-client.jar" org.jboss.Shutdown -S --server jsmith
Listening for transport dt_socket at address: 8787
===== FULL THREAD DUMP ===============
Wed Jun 25 07:38:02 2008
BEA JRockit(R) R27.4.0-90-89592-1.6.0_02-20070928-1715-windows-ia32
"Main Thread" id=1 idx=0x4 tid=716 prio=5 alive, in native, native_waiting
"(Signal Handler)" id=2 idx=0x8 tid=3188 prio=5 alive, in native, daemon
"(GC Main Thread)" id=3 idx=0xc tid=1988 prio=5 alive, in native, native_waiting, daemon
"(GC Worker Thread 1)" id=? idx=0x10 tid=1044 prio=5 alive, in native, daemon
"(Code Generation Thread 1)" id=4 idx=0x14 tid=2780 prio=5 alive, in native, native_waiting, daemon
"(Code Optimization Thread 1)" id=5 idx=0x18 tid=324 prio=5 alive, in native, native_waiting, daemon
"(VM Periodic Task)" id=6 idx=0x1c tid=4012 prio=10 alive, in native, daemon
"(Attach Listener)" id=7 idx=0x20 tid=612 prio=5 alive, in native, daemon
"Finalizer" id=8 idx=0x24 tid=3380 prio=8 alive, in native, native_waiting, daemon
at jrockit/memory/Finalizer.waitForFinalizees([Ljava/lang/Object;)I(Native Method)
at jrockit/memory/Finalizer.access$500(Finalizer.java:12)
at jrockit/memory/Finalizer$4.run(Finalizer.java:143)
at java/lang/Thread.run(Thread.java:619)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Reference Handler" id=9 idx=0x28 tid=3116 prio=10 alive, in native, native_waiting, daemon
at java/lang/ref/Reference.getPending()Ljava/lang/ref/Reference;(Native Method)
at java/lang/ref/Reference.access$000(Reference.java:24)
at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:144)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Sensor Event Thread)" id=10 idx=0x2c tid=3360 prio=5 alive, in native, daemon
"JDWP Transport Listener: dt_socket" id=11 idx=0x30 tid=2352 prio=10 alive, in native, daemon
"JDWP Event Helper Thread" id=12 idx=0x34 tid=2792 prio=10 alive, in native, native_waiting, daemon
===== END OF THREAD DUMP ===============
This was the netstat -ab
TCP jsmith:2847 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:2848 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:2849 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:9098 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:9099 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:12444 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:12445 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:12446 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:14009 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:14080 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:16083 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:16093 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
TCP jsmith:11873 jsmith.OIT.DocFinity.com:0 LISTENING 3440 [java.exe]
I also have ESTABLISHED connections but I didn't include them because they simply were database connections for process id 3440 (above).
Thanks Again!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160537#4160537
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160537
18 years
[JBoss jBPM] - Row was updated or deleted by another transaction
by luiseterc
Hi,
I am using the jbpm console for orchestrate my process definition. However, some of the process nodes request asynchronous tasks to external systems. When those tasks finish, the workflow engine receives an incoming message through JMS (openMQ). What I'm currently doing in response to that message is just to signal the root token to the next node:
| try {
|
| MapMessage mapMessage = (MapMessage)message;
| JbpmConfiguration conf = JbpmConfiguration.getInstance();
| JbpmContext ctx = conf.createJbpmContext();
| try {
|
| ProcessInstance processInstance = ctx.loadProcessInstanceForUpdate(Long.parseLong(mapMessage.getString("processInstance")));
| processInstance.getRootToken().signal();
|
| }finally {
| ctx.close();
| }
|
|
It works but I'm getting this obvious exception:
| ERROR - AbstractFlushingEventListener.performExecutions(301) | Could not synchronize database state with session
| org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#64]
| at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1769)
| at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2412)
| at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2312)
| at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2612)
| at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:96)
| at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
| at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
| at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
| at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
| at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
| at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
| at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:256)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:214)
| at org.jbpm.svc.Services.close(Services.java:225)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
| at com.marketsentinel.workflow.messaging.MessageListener.onMessage(MessageListener.java:42)
| at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.deliverAndAcknowledge(MessageConsumerImpl.java:338)
| at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.onMessageToListenerFromReceiveQueue(MessageConsumerImpl.java:316)
| at com.sun.messaging.jmq.jmsclient.SessionReader.onMessageToLateListeners(SessionReader.java:171)
| at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:149)
| at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:189)
| at java.lang.Thread.run(Thread.java
|
Since I'm creating a new different hibernate session/Jbpm context from the message listener. I wonder how could I get the JbpmContext used by the console in order to use the same session to update the token status.
I've been searching the jbpm4jsf source code and all the action classes use a static "context" . Where does that object is instanciated?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160533#4160533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160533
18 years
[JBoss jBPM] - Jbpm-jpdl failed to launch login console in JBoss-4.0.2GA
by soumya_in
I tried to deploy JBPM ear in 4.0.4GA.
It deployed....
I tried the same with 4.0.2GA
Got following exception while launching the login console though sucessfully deployed the ear.
2008-06-25 16:35:54,020 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm
| -console].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
| java.lang.NoSuchMethodError: org.w3c.dom.Element.getTextContent()Ljava/lang/String;
| at org.jbpm.jsf.core.config.ConfigurationLocator.handleAuthenticationService(Configu
| rationLocator.java:177)
| at org.jbpm.jsf.core.config.ConfigurationLocator.handleConfiguration(ConfigurationLo
| cator.java:229)
| at org.jbpm.jsf.core.config.ConfigurationLocator.searchWar(ConfigurationLocator.java
| :275)
| at org.jbpm.jsf.core.config.ConfigurationLocator.configure(ConfigurationLocator.java
| :60)
| at org.jbpm.jsf.core.config.ConfigurationLocator.getInstance(ConfigurationLocator.ja
| va:51)
| at org.jbpm.jsf.core.phase.ProcessFilePhaseListener.beforePhase(ProcessFilePhaseList
| ener.java:45)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:218)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilte
| rChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.j
| ava:173)
| at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:
| 672)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatch
| er.java:463)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.ja
| va:398)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java
| :301)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticato
| r.java:238)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java
| :446)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
|
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
| (Http11Protocol.java:744)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527
| )
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.ja
| va:112)
| at java.lang.Thread.run(Thread.java:595)
| 2008-06-25 16:35:54,020 WARN [org.apache.catalina.authenticator.FormAuthenticator] Unexpected error
| forwarding to login page
| javax.servlet.ServletException: Servlet execution threw an exception
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilte
| rChain.java:275)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.j
| ava:173)
| at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:
| 672)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatch
| er.java:463)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.ja
| va:398)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java
| :301)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticato
| r.java:238)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java
| :446)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
|
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
| (Http11Protocol.java:744)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527
| )
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.ja
| va:112)
| at java.lang.Thread.run(Thread.java:595)
Looked into JDK 1.5/JDK-1.4 API this method is not available. However this error is not thrown by 4.0.4 version.
Process gets deployed from eclipse console fine.
Following jars required during deployment of the ear.
Hibernate 3.0 jar
Jboss-hibernate.jar
Jboss-backport-concurrent.jar
Commons-io_xxx.jar
Commons-fileupload.jar
Commons-collections.jar
Does anybody have an idea or tried this.
Tell me if I am going wrong anywhere.
Thanks in advance
Regards
Soumya
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160530#4160530
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160530
18 years
[Nukes User] - JBPM-3.2.2 failed to launch login console in JBoss standalon
by soumya_in
I tried to deploy JBPM ear in 4.0.4GA.
It deployed....
I tried the same with 4.0.2GA
Got following exception while launching the login console though sucessfully deployed the ear.
| 2008-06-25 16:35:54,020 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-console].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
| java.lang.NoSuchMethodError: org.w3c.dom.Element.getTextContent()Ljava/lang/String;
| at org.jbpm.jsf.core.config.ConfigurationLocator.handleAuthenticationService(ConfigurationLocator.java:177)
| at org.jbpm.jsf.core.config.ConfigurationLocator.handleConfiguration(ConfigurationLocator.java:229)
| at org.jbpm.jsf.core.config.ConfigurationLocator.searchWar(ConfigurationLocator.java:275)
| at org.jbpm.jsf.core.config.ConfigurationLocator.configure(ConfigurationLocator.java:60)
| at org.jbpm.jsf.core.config.ConfigurationLocator.getInstance(ConfigurationLocator.java:51)
| at org.jbpm.jsf.core.phase.ProcessFilePhaseListener.beforePhase(ProcessFilePhaseListener.java:45)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:218)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:238)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 2008-06-25 16:35:54,020 WARN [org.apache.catalina.authenticator.FormAuthenticator] Unexpected error forwarding to login page
| javax.servlet.ServletException: Servlet execution threw an exception
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:275)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:238)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
|
Looked into JDK 1.5/JDK-1.4 API this method is not available. However this error is not thrown by 4.0.4 version.
Process gets deployed from eclipse console fine.
Following jars required during deployment of the ear.
Hibernate 3.0 jar
Jboss-hibernate.jar
Jboss-backport-concurrent.jar
Commons-io_xxx.jar
Commons-fileupload.jar
Commons-collections.jar
Does anybody have an idea or tried this.
Tell me if I am going wrong anywhere.
Thanks in advance
Regards
Soumya
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160525#4160525
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160525
18 years