Autodeploy of blazeds failure on weblogic11g
Hi,
I copied the blazeds.war, ds-console.war, and samples.war to the autodeploy directory and all three got this kind of error. Weblogic 11g is really 10.3.4. Does anyone have any clues. This is a brand new weblogic installation with no other installs.
Weblogic is installed on a Redhat Linux E3 edition.
-Denis
####<Feb 27, 2011 8:17:57 PM EST> <Error> <Deployer> <freedom.dynalias.org> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62d4e071356f6b67:-79c6ad94:12e69d7ada6:-8000-0000000000000002> <1298855877782> <BEA-149231> <Unable to set the activation state to true for the application '_appsdir_blazeds_war'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "MessageBrokerServlet" failed to preload on startup in Web application: "blazeds.war".
flex.management.ManagementException: MBeanServerLocator 'flex.management.WebSphereMBeanServerLocator' failed to retrieve MBeanServer.
at flex.management.WebSphereMBeanServerLocator.getMBeanServer(WebSphereMBeanServerLocator.ja va:78)
at flex.management.BaseControl.register(BaseControl.java:186)
at flex.management.runtime.AdminConsoleDisplayRegistrar.<init>(AdminConsoleDisplayRegistrar. java:40)
at flex.management.runtime.messaging.MessageBrokerControl.<init>(MessageBrokerControl.java:8 3)
at flex.messaging.MessageBroker.<init>(MessageBroker.java:194)
at flex.messaging.MessageBroker.<init>(MessageBroker.java:164)
at flex.messaging.MessageBroker.<init>(MessageBroker.java:158)
Be sure to consider how the session cookies are assigned. If they're to
the domain as a whole, or even the web application context, then just
because you create two channels with different path info, the two
channels to the same domain may both send the same session cookie.
From: Nicola Muneratto [mailto:[email protected]]
Sent: Sunday, July 20, 2008 8:09 AM
To: [email protected]
Subject: Re: BlazeDS authentication with RemoteObject endpoints
A new message was posted by Nicola Muneratto in
Configuration and Getting Started Discussion --
BlazeDS authentication with RemoteObject endpoints
Hi Mete, thank you for your quick reply!
I verified that my RemoteObject doesn't share the same authenticated
channel and it seamlessy calls the remote methods ..
I'm going to do some tests next couple of days and i'll let you know .
Thank you again for your kindness.
Bye
View/reply at BlazeDS authentication with RemoteObject endpoints
Replies by email are OK.
Use the unsubscribe
form
to cancel your email subscription.
Similar Messages
-
Blazeds war and weblogic server: a failure?
when i try to deploy the latest blazeds release 3.2.0.3978 to weblogic 10.3 i get the following exception:
[J2EE:160144]Failed to register library Extension-Name: blazeds, Implementation-Version: 3.2.0.3978: Library cannot have Implementation-Version set, without also specifying its Specification-Version.
as simple as that. when i examine the manifest of the war, indeed the Specification-Version field is not there. what should i do?you will have to wait for WLS 9.0.2
Chris Jolley
Portal Architect -
Server stopped due to start up failure
hi!
i have downloaded and installed j2ee sdk without any problems.
however when i start the server it closes itself.
at the end of the log file it says:
" [#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]"
the whole log file is below. can anybody help?
ps: i am a beginner.
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-07-13T09:52:32.438+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2005-07-13T09:52:36.413+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-07-13T09:52:37.104+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-07-13T09:52:46.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-07-13T09:52:46.187+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-07-13T09:52:46.237+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-07-13T09:52:54.299+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-07-13T09:52:59.106+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-07-13T09:53:02.210+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-07-13T09:53:05.565+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-07-13T09:53:05.856+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.956+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.986+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.007+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.017+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.117+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.127+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-07-13T09:53:07.298+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-07-13T09:53:08.900+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2005-07-13T09:53:10.683+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2005-07-13T09:53:10.693+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-07-13T09:53:10.743+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-07-13T09:53:11.363+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2005-07-13T09:53:25.003+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2005-07-13T09:53:32.724+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:32.864+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:33.916+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:33.946+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:34.006+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:53:34.026+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
... 25 more
|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2005-07-13T09:54:36.336+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2005-07-13T09:54:36.506+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2005-07-13T09:54:36.536+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2005-07-13T09:54:37.027+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-07-13T09:54:37.057+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-07-13T09:54:37.057+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]Hi,
Did you resolve this issue? I have the same problem. I appreciate if you could please let me know what the problem was.
Thanks -
JBoss 7 and BlazeDS Authentication
Hi,
Has anybody tried to set up Database authentication and BlazeDS though JBoss 7?
I've performed steps I previously used with other versions but still getting the usual error;
'There was an unhandled failure on the server. flex/messaging/security/TomcatLoginHolder'
The truth is I feel like I'm stubbling around in the dark because JBoss 7 is so different to previous versions.
Any help would be appreciatedI found the answer for this;
The trouble I was having was setting the tomcat valve in JBoss 7. Previously this was done in tomcat configuration files and is documented in BlazeDS docs.
Now the configuration is achieved by;
1) putting flex-tomcat-common.jar and flex-tomcat-server.jar in the WEB-INF/lib folder of your blazeds war and in the same war
2) in your jboss-web.xml under WEB-INF the following content
<jboss-web>
<security-domain>yourSecurityDomain</security-domain>
<valve>
<class-name>flex.messaging.security.TomcatValve</class-name>
</valve>
</jboss-web>
The blazeds configuration remains the same. -
Revision: 4258
Author: [email protected]
Date: 2008-12-08 16:33:17 -0800 (Mon, 08 Dec 2008)
Log Message:
Bug: LCDS-522 - Add more configurable reconnect handling for connecting up again over the same channel when there is a connection failure/outage.
QA: Yes
Doc: No
Checkintests Passes: Yes
Details:
* Updates to configuration handling code and MXMLC code-gen to support new long-duration reliable reconnect setting.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-522
Modified Paths:
blazeds/trunk/modules/common/src/flex/messaging/config/ClientConfiguration.java
blazeds/trunk/modules/common/src/flex/messaging/config/ClientConfigurationParser.java
blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
blazeds/trunk/modules/common/src/flex/messaging/config/ServicesDependencies.java
blazeds/trunk/modules/common/src/flex/messaging/errors.properties
Added Paths:
blazeds/trunk/modules/common/src/flex/messaging/config/FlexClientSettings.java
Removed Paths:
blazeds/trunk/modules/core/src/flex/messaging/config/FlexClientSettings.javaRemember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.
-
Revision: 21014
Revision: 21014
Author: [email protected]
Date: 2011-04-04 13:44:59 -0700 (Mon, 04 Apr 2011)
Log Message:
bug fix for RTMP security test case failure for Tomcat 7,
defer the ValveBase.getContainer() call to run time.
Checkin tests not run as it only applies to Tomcat 7
Modified Paths:
blazeds/trunk/modules/opt/src/tomcat/flex/messaging/security/Tomcat7Valve.javaRevision: 21014
Revision: 21014
Author: [email protected]
Date: 2011-04-04 13:44:59 -0700 (Mon, 04 Apr 2011)
Log Message:
bug fix for RTMP security test case failure for Tomcat 7,
defer the ValveBase.getContainer() call to run time.
Checkin tests not run as it only applies to Tomcat 7
Modified Paths:
blazeds/trunk/modules/opt/src/tomcat/flex/messaging/security/Tomcat7Valve.java -
Hi,
I have a WAR file that causes WL 6.1 (refresh build) to fail when I attempt
to deploy it from the console. This WAR file deploys correctly on WL 6.0 SP2
and several other Web containers (Tomcat, Orion, JRun, Resin). The file is
large (> 5 MB) but I can send it by email if somebody wants to give it a
try.
I have noticed in the logs (see below) that the failure is caused by a
NullPointerException that is thrown in our DataSourceProxy class here:
private void setPingQuery(GenericDataSource dataSource)
dataSource.setPingQuery(PropertiesGetter.getInstance("Constants.properties")
.getProperty("persistency.pingQuery"));
here is the relevant piece of code in PropertiesGetter:
public static Properties loadProperties(String propertiesFileName)
throws IOException
Properties props = new Properties();
InputStream in =
PropertiesGetter.class.getClassLoader().getResourceAsStream(propertiesFileNa
me);
props.load(in);
return props;
so it is the loading of the Constants.properties file that fails and causes
the NullPointerException. This properties file is located under
WEB-INF\classes.
Note that with WL 6.0 SP2, although deployment goes fine, the application
fails later at runtime when Log4J tries to load its own properties file from
the same place. Other Web containers do not have this problem.
Alain.
Alain Rogister
http://www.ubiquity.be
####<Jul 31, 2001 11:52:37 AM CEST> <Debug> <HTTP> <VENUS> <myserver>
<ExecuteThread: '10' for queue: 'default'> <system> <> <101158> <Exception
thrown while loading actel: java.lang.NullPointerException>
java.lang.NullPointerException
at
be.actel.persistence.database.DataSourceProxy.setPingQuery(DataSourceProxy.j
ava:51)
at
be.actel.persistence.database.DataSourceProxy.setDataSource(DataSourceProxy.
java:46)
at be.actel.servlet.ActelDirectServlet.init(ActelDirectServlet.java:23)
at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
:698)
at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
va:641)
at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
a:586)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
ontext.java:2157)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
Context.java:2101)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav
a:873)
at
weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j
ava:804)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:411)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
90)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy32.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
t(WebServerMBean_CachingStub.java:1093)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
90)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(Confi
gurationMBeanImpl.java:482)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
.java:913)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
.java:900)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:885)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:618)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
90)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy60.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
anager.java:794)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
ionManager.java:891)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
ionManager.java:813)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
.java:729)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
.java:662)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
er.java:191)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
90)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy2.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload
_app.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:191)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:111)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:147)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2349)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:1956)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Jul 31, 2001 11:52:37 AM CEST> <Error> <J2EE> <VENUS> <myserver>
<ExecuteThread: '10' for queue: 'default'> <system> <> <160001> <Error
deploying application actel: Could not load actel>
####<Jul 31, 2001 11:52:37 AM CEST> <Error> <Management> <VENUS> <myserver>
<ExecuteThread: '10' for queue: 'default'> <system> <> <141042> <Error
deploying application .\config\mydomain\applications\actel.war:
java.lang.reflect.UndeclaredThrowableException>
####<Jul 31, 2001 11:56:07 AM CEST> <Error> <Kernel> <VENUS> <myserver>
<ExecuteThread: '9' for queue: 'default'> <> <> <000000> <ExecuteRequest
failed>
weblogic.management.configuration.ConfigurationError: undefined parent for
mydomain:Application=actel,Name=actel,Type=WebAppComponent:
mydomain:Name=actel,Type=Application
at
weblogic.management.internal.xml.ConfigurationGenerator.getXml(Configuration
Generator.java:210)
at
weblogic.management.internal.xml.XmlFileRepository.saveDomain(XmlFileReposit
ory.java:194)
at
weblogic.management.internal.xml.XmlFileRepository.saveDomain(XmlFileReposit
ory.java:167)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
90)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy1.saveDomain(Unknown Source)
at
weblogic.management.internal.SaveDomainTrigger.trigger(SaveDomainTrigger.jav
a:47)
at
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
er.java:238)
at
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
:229)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)Hi All,
I have figured out the problem. The file path had '\' like c:\abc.xml. The java programs which read the archives does not like backward slash. So, what I did was I replaced backward slashes with forward slashes and things worked fine.
Winzip handles the slashes and that is the reason I was able to open the war file.
Hope this will help you.
Thanks,
Paran -
Unable to Deploy EJB (RMIC Failure)
Hi, I'm experiencing a problem using the J2EE Application Server to deploy one of the J2EE 1.4 Tutorial EJB Examples (ConverterAPP). I'm getting an RMIC compilation failure during RMI-IIOP Code compilation. The error is : java.lang.NullPointerException at sun.rmi.rmic.Main.doCompile(Main.java:479). This error is also happening when I start the server and it attempts to autodeploy MEjbapp. Any ideas? The trace is:
[#|2003-12-23T07:17:26.578-0700|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5109: EJBC - START of EJBC for [ConverterApp]|#]
Remote message: Processing beans ....
[#|2003-12-23T07:17:26.649-0700|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [ConverterApp]|#]
Remote message: Compiling wrapper code ....
Remote message: Compiling RMI-IIOP code ....
rmic compilation failed
at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:275)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:92)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:69)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:284)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:306)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:200)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:99)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:258)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:256)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:210)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:578)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:196)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:175)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:974)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:207)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:648)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:498)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:575)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:649)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sun.ejb.codegen.JavaCompilerException: java.lang.NullPointerException
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:76)
at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:269)
... 80 more
Caused by: java.lang.NullPointerException
at sun.rmi.rmic.Main.doCompile(Main.java:479)
at sun.rmi.rmic.Main.compile(Main.java:130)
at com.sun.ejb.codegen.RMICompiler.nativeCompile(RMICompiler.java:137)
at com.sun.ejb.codegen.RMICompiler.internal_compile(RMICompiler.java:73)
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:67)
... 81 more
[#|2003-12-23T07:17:29.963-0700|WARNING|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=12;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- rmic compilation failedNever mind - reinstalled J2EE and problem is gone.
-
Need help in Delete operation using blazeDS
Please find the flex client code and servlet code given below
Trying to call a DELETE methods on the servlet using BlazeDS.Configuration is perfect in the proxy-config.xml and services-config.xml
when DELETE is called with paramter user="krishna it is being printed as
received DELETE operation with parameternull
My Question is why the servlet printing null value for the user where it should print "someuser"?Can some one help me on this?
FLEX CLIENT
<?xml version="1.0" encoding="utf-8"?><mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="vertical">
<mx:Script><![CDATA[
import mx.controls.Alert;
import mx.rpc.http.HTTPService;
import mx.rpc.events.ResultEvent;
import mx.rpc.events.FaultEvent;
public function callServletDELETE():void {
var service:HTTPService = new HTTPService();
//service.url= "http://localhost:8080/examples/blazeDS";service.destination=
"BlazeDSHTTP"; //this is configured in proxy-config.xml fileservice.useProxy =
true; service.method =
"DELETE"; service.resultFormat=
"e4x"; service.addEventListener(
"result", billingCarrierResult);service.addEventListener(
"fault", httpFault); service.send({user:
'someuser'});}
protected function billingCarrierResult(event:ResultEvent):void{
serviceResultsTextArea.text =
"Success with BlazeDS!\n"+event.result;
protected function httpFault(event:FaultEvent):void{
serviceResultsTextArea.text =
"Failure trying to access service.\n"+ event.fault.faultString + "\n" + event.fault.faultDetail;}
]]>
</mx:Script> <mx:TextArea id="serviceResultsTextArea" width="50%" height="50%" />
<mx:Button label="DELETE" click="callServletDELETE()"/>
</mx:Application>
servlet
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
* Simple example intended to demonstrate BlazeDS with HttpService.
public class BlazeHttpExample extends HttpServlet
//excluded other methods GET,POST as they are working fine
* Handles the HTTP <code>DELETE</code> method.
* @param request servlet request
* @param response servlet response
@Override
protected void doDelete(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
System.out.println("received DELETE operation with parameter"+request.getParameter("user"));
@Override
public String getServletInfo()
return "Simple intended to illustrate BlazeDS HttpService support.";in your java code you are considering user as the parameter.. but that is not a parameter..
When making a http call in flex try something like this
var obj:Object = new Object();
obj["user"] = 'someuser';
service.send(obj);
this should work hopefully. -
Revision: 4561
Author: [email protected]
Date: 2009-01-16 10:59:37 -0800 (Fri, 16 Jan 2009)
Log Message:
Updated error.txt files for goodValidatorTest and patternFilterLoggingMessageFilterTest to fix failure on appservers other than Tomcat
checkintests: pass
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingMessageFilterTest/error.txtDude this worked fantastic. Thank you for posting.
-
Autodeploy fails, but application appears in console
I'm using the App Server Edition 8. I am getting autodeploy failures via the server log and the autodeploy directory (which is fine).
My MAIN concern is that my application is listed as enabled in the App Server Admin Console, even though the deploy supposedly failed.
If I remove my ear file from the autodeploy directory, the application vanishes from the Admin Console.
Has anybody else seen this? Is this "normal" behavior or a potential bug?Not sure if it was working... I am coding up an EJB client program to test drive.
I did have valid errors with the deployment, so I would assume the application would not be deployed upon failure. -
BlazeDS calling the service every 32 sec
We have application as Flex(flex-remoting) calls java webservices(hessian).
We have found some issues during the flex call java webservice.
What we have observed from java web service log is that if java web service does not return the result to the calling client (flex-remoting) within 32 sec, another java web service call is invoked , and as a result we sometime get error.
1. why every 32 seconds, can we reconfigure it to a bigger number ?
2. why BlazeDS invokes another service call when 32 sec get timeout, which flex event get fired ?
3
I would be appriciate,if you can help in this regard
Thanks in advance.
Regards
IsmailWaterfly,
If you are experiencing domain disconnect messages after a particular connection has been idle you should use the keepalive parameters available in the DMCONFIG file. The behavior you are seeing of dmadmin "pd -d domainid" and tmadmin psc showing the connection as available just before the failure occurs because when keepalive is not in use Tuxedo only tries to use the connection when there is a request, and Tuxedo does not yet know that the connection has been disconnected by TCP due to inactivity. If a request succeeds after a LIBGWT_CAT:1130 message it is either because a new connection has been set up or because the request was able to use some other connection to obtain the requested service.
In Tuxedo 8.1 and later, the *DMTDOMAIN section offers parameters
TCPKEEPALIVE=LOCAL
DMKEEPALIVE=numeric
DMKEEPALIVEWAIT=numeric
Either TCPKEEPALIVE or DMKEEPALIVE/DMKEEPALIVEWAIT can be used to configure periodic keepalive messages to be sent on a connection that is otherwise idle.
Regards,
Ed -
Flash Builder 4 and BlazeDS compatibility
Hi
I have downloaded Flash Builder 4.1 and the latest stable release of BlazeDS (blazeds-turnkey-4.0.0.14931.zip).
I am able to run the examples packaged in the BlazeDS. But when I try to build the source code in Flash Builder myself, I always get the connection failure due to not be able to find remote channel, for example.
But when I change flex compiler to select "Use Flex 3 compatibility mode", things started to work.
Is this expected? Is this the right way to set up my development env?
ThanksYes, I have it all working. (although i filed a jira bug against the FB4 service code-generator)
I found help from the Spring forum for Spring-BlazeDS integration:
http://forum.springsource.org/showthread.php?t=84702
which cites to James Ward videos. -
Revision: 20615
Revision: 20615
Author: [email protected]
Date: 2011-03-04 12:11:09 -0800 (Fri, 04 Mar 2011)
Log Message:
fixing the regression failure caused by the nest collection level fix, an actionscript type without remote alias will resolved as ">className", we should filter out the special case
Modified Paths:
blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.javaRemember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.
-
No content on faultEvent when using a BlazeDS proxy
All the articles I've read indicate that when using Flex mx.rpc.http.HTTPService to make a URL request you need to use a proxy (such as BlazeDS) if you want to receive the content of the response on a failure (non-2xx status code). My experience has been the opposite: making a direct (useProxy==false) request for a URL that fails does return the content but making a proxied request (useProxy==true) returns null for the content. I've tried this with BlazeDS 3.2.0.3978 and the latest version from trunk and both exhibit the same behavior.
Has anyone else seen this behavior or have a solution?
If it makes a difference, I'm using Java 6 update 16 and Tomcat 6.0.24.
Thanks,
Rangi KeenDouble tap the Home button, swipe all the way to the right to reveal the sound icon on the extreme left and see if it is muted. Click on it to change.
Maybe you are looking for
-
Problems with iomega External Hard Drive on MacBook Air
Hi community! I'm experiencing some problems with my MacBook Air and an external hard drive and I'm wondering if anybody would be able to help me out. I own a MacBook Air running Mac OS X 10.7.3. When I connect my iomega 500GB external hard drive, th
-
Hi All, i have problem in ALV GRID. On my ALV output i have VBAK-VBELN. when i click on filters, and if i provide vbeln as '106789' instead of '0000106789' the output is not displayed. please let me know how to solve this problem. if i provide 106789
-
hello, I am looking for the easiest way to hide empty columns in 'REUSE_ALV_GRID_DISPLAY'. I know i can work my way through the field catalog. I am just curious if there is a parameter that helps me to achieve this goal. thank you! Werner
-
Multiple article select in Folio Producer [Add] article feature
Folio Producer provides [Add] article feature allow designer collaborative workflow, thanks. I just completed adding articles from several shared folios, I would like to say, select multiple articles in folio is a MUST to make DPS sharing collaborati
-
My email is not working with os x lion - pls help
My email has stopped working since I upgraded to OS X Lion. Any ideas on what I can do to get it working again?