[JNDI/Naming/Network] - Re: JNDI Data Source
by manofspider
I checked it, previously, I placed driver jar into \simplej2ee.war\WEB-INF\lib\classes12.jar
Now I place driver jar into %JBOSS_HOME%\server\< serverName>\lib folder: \Install\jboss-4.0.2\server\simplej2ee\lib\classes12.jar.
Output:
anonymous wrote :
| 15:56:32,010 INFO [Server] Starting JBoss (MX MicroKernel)...
| 15:56:32,010 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
| 15:56:32,010 INFO [Server] Home Dir: D:\Work\Install\jboss-4.0.2
| 15:56:32,010 INFO [Server] Home URL: file:/D:/Work/Install/jboss-4.0.2/
| 15:56:32,010 INFO [Server] Library URL: file:/D:/Work/Install/jboss-4.0.2/lib/
| 15:56:32,010 INFO [Server] Patch URL: null
| 15:56:32,010 INFO [Server] Server Name: simplej2ee
| 15:56:32,010 INFO [Server] Server Home Dir: D:\Work\Install\jboss-4.0.2\server\simplej2ee
| 15:56:32,010 INFO [Server] Server Home URL: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/
| 15:56:32,010 INFO [Server] Server Data Dir: D:\Work\Install\jboss-4.0.2\server\simplej2ee\data
| 15:56:32,010 INFO [Server] Server Temp Dir: D:\Work\Install\jboss-4.0.2\server\simplej2ee\tmp
| 15:56:32,010 INFO [Server] Server Config URL: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/conf/
| 15:56:32,026 INFO [Server] Server Library URL: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/lib/
| 15:56:32,026 INFO [Server] Root Deployment Filename: jboss-service.xml
| 15:56:32,026 INFO [Server] Starting General Purpose Architecture (GPA)...
| 15:56:32,477 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
| 15:56:32,477 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
| 15:56:32,477 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
| 15:56:33,070 INFO [Server] Core system initialized
| 15:56:34,488 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
| 15:56:34,581 INFO [WebService] Using RMI server codebase: http://tra10:8083/
| 15:56:34,846 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
| 15:56:39,007 INFO [Embedded] Catalina naming disabled
| 15:56:39,303 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
| 15:56:39,303 INFO [Catalina] Initialization processed in 249 ms
| 15:56:39,303 INFO [StandardService] Starting service jboss.web
| 15:56:39,303 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
| 15:56:39,334 INFO [StandardHost] XML validation disabled
| 15:56:39,365 INFO [Catalina] Server startup in 62 ms
| 15:56:39,474 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/http-invoker.sar/invoker.war/
| 15:56:39,739 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
| 15:56:40,145 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/tmp/deploy/tmp60090jboss-ws4ee-exp.war/
| 15:56:40,269 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jbossweb-tomcat55.sar/ROOT.war/
| 15:56:40,581 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
| 15:56:42,326 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/management/console-mgr.sar/web-console.war/
| 15:56:43,386 INFO [MailService] Mail Service bound to java:/Mail
| 15:56:43,807 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jboss-ha-local-jdbc.rar
| 15:56:43,916 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jboss-ha-xa-jdbc.rar
| 15:56:44,165 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jboss-local-jdbc.rar
| 15:56:44,243 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jboss-xa-jdbc.rar
| 15:56:44,337 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jms/jms-ra.rar
| 15:56:44,430 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/mail-ra.rar
| 15:56:45,568 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
| 15:56:45,817 INFO [A] Bound to JNDI name: queue/A
| 15:56:45,817 INFO [B] Bound to JNDI name: queue/B
| 15:56:45,817 INFO [C] Bound to JNDI name: queue/C
| 15:56:45,817 INFO [D] Bound to JNDI name: queue/D
| 15:56:45,833 INFO [ex] Bound to JNDI name: queue/ex
| 15:56:45,848 INFO [testTopic] Bound to JNDI name: topic/testTopic
| 15:56:45,848 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
| 15:56:45,848 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
| 15:56:45,848 INFO [testQueue] Bound to JNDI name: queue/testQueue
| 15:56:45,895 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
| 15:56:45,926 INFO [DLQ] Bound to JNDI name: queue/DLQ
| 15:56:46,082 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
| 15:56:46,191 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=training-db-ds to JNDI name 'java:training-db-ds'
| 15:56:46,222 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/D:/Work/Install/jboss-4.0.2/server/simplej2ee/deploy/jmx-console.war/
| 15:56:46,378 INFO [TomcatDeployer] deploy, ctxPath=/simplej2ee, warUrl=file:/D:/Work/eclipse/simplej2ee/training1/dist/appdev/simplej2ee.war/
| 15:56:46,596 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
| 15:56:46,736 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
| 15:56:46,768 INFO [JkMain] Jk running ID=0 time=0/63 config=null
| 15:56:46,768 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 14s:742ms
| 15:57:00,621 INFO [STDOUT] Connected to DB successfully.
| 15:57:00,746 INFO [STDOUT] ITEM: 1 Monitor
| 15:57:00,746 INFO [STDOUT] ITEM: 2 Keyboard
| 15:57:00,746 INFO [STDOUT] ITEM: 3 Mouse
|
jaikiran, good answer! It works now, thanksss.
And do you know how to make my previous example worked ? by keeping driver jar in \simplej2ee.war\WEB-INF\lib\classes12.jar ?
looking forward to your next answers!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173894#4173894
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173894
17 years, 7 months
[EJB/JBoss] - JBM server shutdown curiously when Jboss cluster is running.
by funnyone
We have three nodes in our jboss cluster. We deployed our JBM server on one of three nodes. But in recent days we found our JBM server shutdown curiously when the jboss cluster is running. And all topic was closed.
We checked the server.log in the /server/default/log and found the following information:
2008-09-03 11:29:42,628 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/DLQ] stopped
| 2008-09-03 11:29:42,630 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/ExpiryQueue] stopped
| 2008-09-03 11:29:42,631 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/testTopic] stopped
| 2008-09-03 11:29:42,633 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/securedTopic] stopped
| 2008-09-03 11:29:42,634 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/testDurableTopic] stopped
| 2008-09-03 11:29:42,635 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/testQueue] stopped
| 2008-09-03 11:29:42,636 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/A] stopped
| 2008-09-03 11:29:42,637 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/B] stopped
| 2008-09-03 11:29:42,638 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/C] stopped
| 2008-09-03 11:29:42,640 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/D] stopped
| 2008-09-03 11:29:42,641 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/ex] stopped
| 2008-09-03 11:29:42,642 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/PrivateDLQ] stopped
| 2008-09-03 11:29:42,644 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/PrivateExpiryQueue] stopped
| 2008-09-03 11:29:42,645 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/QueueWithOwnDLQAndExpiryQueue] stopped
| 2008-09-03 11:29:42,646 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/TopicWithOwnDLQAndExpiryQueue] stopped
| 2008-09-03 11:29:42,648 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/QueueWithOwnRedeliveryDelay] stopped
| 2008-09-03 11:29:42,649 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/TopicWithOwnRedeliveryDelay] stopped
| 2008-09-03 11:29:42,650 INFO [DRM Async Publisher#0] destination.QueueService ( QueueService.java:189) - Queue[/queue/testDistributedQueue] stopped
| 2008-09-03 11:29:42,651 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/testDistributedTopic] stopped
| 2008-09-03 11:29:42,653 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/cmtopic] stopped
| 2008-09-03 11:29:42,709 ERROR [WorkerThread#110[192.166.32.132:3212]] socket.ServerThread ( ServerThread.java:377) - Worker thread initialization failure
| java.io.EOFException
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:529)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| 2008-09-03 11:29:42,754 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/cmomttopic] stopped
| 2008-09-03 11:29:42,756 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/Fm4NeaTopic] stopped
| 2008-09-03 11:29:42,758 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/FmTopic] stopped
| 2008-09-03 11:29:42,760 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/FmOmtTopic] stopped
| 2008-09-03 11:29:42,864 INFO [JMS SessionPool Worker-2] server.AbstractCommonMDB ( AbstractCommonMDB.java:48) - [RouterMDB]receive msg id:50 sequenceId=79742
| 2008-09-03 11:29:42,866 INFO [JMS SessionPool Worker-2] server.AbstractCommonMDB ( AbstractCommonMDB.java:48) - [RouterMDB]receive msg id:50 sequenceId=79743
| 2008-09-03 11:29:49,837 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/FmNbiTopic] stopped
| 2008-09-03 11:29:49,840 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/LMTopic] stopped
| 2008-09-03 11:29:49,842 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/LMOmtTopic] stopped
| 2008-09-03 11:29:49,844 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/sectopic] stopped
| 2008-09-03 11:29:49,846 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/RouteTopic] stopped
| 2008-09-03 11:29:49,847 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/smtopic] stopped
| 2008-09-03 11:29:49,849 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/topotopic] stopped
| 2008-09-03 11:29:49,850 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/Fm2TopoTopic] stopped
| 2008-09-03 11:29:49,853 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/PmTopic] stopped
| 2008-09-03 11:29:49,854 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/Pm4NeaTopic] stopped
| 2008-09-03 11:29:49,855 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/Pm4ServerTopic] stopped
| 2008-09-03 11:29:49,856 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/TDMTopic] stopped
| 2008-09-03 11:29:49,860 INFO [DRM Async Publisher#0] destination.TopicService ( TopicService.java:179) - Topic[/topic/TDMOmtTopic] stopped
| 2008-09-03 11:29:49,867 ERROR [WorkerThread#29[192.166.32.8:59979]] remoting.ServerInvoker ( ServerInvoker.java:1820) - Error executing server oneway invocation request: InvocationRequest[12e727b, JMS, org.jboss.jms.wireformat.SessionSendRequest@5deceb]
| org.jboss.jms.exception.MessagingShutdownException: Cannot handle invocation since messaging server is not active (it is either starting up or shutting down)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:133)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
| at org.jboss.remoting.ServerInvoker$1.run(ServerInvoker.java:1815)
| at org.jboss.jms.server.remoting.DirectThreadPool.run(DirectThreadPool.java:63)
| at org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:1826)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:758)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| 2008-09-03 11:29:49,872 ERROR [WorkerThread#29[192.166.32.8:59979]] remoting.ServerInvoker ( ServerInvoker.java:1820) - Error executing server oneway invocation request: InvocationRequest[6d7710, JMS, org.jboss.jms.wireformat.SessionSendRequest@a3d239]
| org.jboss.jms.exception.MessagingShutdownException: Cannot handle invocation since messaging server is not active (it is either starting up or shutting down)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:133)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
| at org.jboss.remoting.ServerInvoker$1.run(ServerInvoker.java:1815)
| at org.jboss.jms.server.remoting.DirectThreadPool.run(DirectThreadPool.java:63)
| at org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:1826)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:758)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
it was already confirmed that nobody executed shutdown() or stop() operation using jboss web-console. It's just like JBM server shutdown itself, and we don't know what is the cause.
any help will be greatly appreciated here.
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173893#4173893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173893
17 years, 7 months
[JBoss Portal] - JBoss Portal Portlet 2.0 compatiblility
by mbien
Hello everyone,
is the JBoss Portal 2.7.0b implementation of the Portlet 2.0 spec already feature complete?
I got a ClassCastException in my prototype while evaluating the Portal event wirering.
| @Override
| public void processEvent(EventRequest request, EventResponse response) throws PortletException, IOException {
| System.out.println("portlet 2.0 events rock!")
| //...
| //...
| PortletRequestDispatcher prd = getPortletContext().getRequestDispatcher("/WEB-INF/iframe/iframe.jsp");
| prd.include(request, response);
| }
|
anonymous wrote :
| portlet 2.0 events rock!
| java.lang.ClassCastException: org.jboss.portal.portlet.impl.jsr168.api.EventRequestImpl cannot be cast to javax.portlet.RenderRequest
| at org.jboss.portal.portlet.impl.jsr168.taglib.DefineObjectsTag.doEndTag(DefineObjectsTag.java:63)
| at org.apache.jsp.WEB_002dINF.iframe.iframe_jsp._jspService(iframe_jsp.java:67)
| at org.jboss.portal.core.servlet.jsp.PortalJsp.service(PortalJsp.java:143)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| ...
|
(afaik JBP should expect a PortletRequest instead of a RenderRequest if it implements the Portlet 2.0 spec at this point)
I also noticed some differences comparing the jboss doc with the apache pluto portlet 2.0 reference impl (e.g PortletRequestDispatcher):
http://portals.apache.org/pluto/portlet-api/apidocs/javax/portlet/Portlet...
http://docs.jboss.com/jbportal/v2.7.0.B1/javadoc/portlet/javax/portlet/Po...
thank you in advance,
mbien
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173891#4173891
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173891
17 years, 7 months