Apache Pulsar maximum supported message size - stream

What is the maximum message size supported by Apache Pulsar?
I tried reading the documentation. But I couldn't find any relevant information.

The default max message size is 5242880 bytes (5 MiB), but it can be adjusted. See this Wiki page for details:
https://github.com/apache/pulsar/wiki/PIP-36%3A-Max-Message-Size

Related

Inspecting pcap file with Wireshark: [Packet size limited during capture]

I'm inspecting a pcap file with Wireshark and some of the entries have this written in their information field:
10001 → 27017 Len=121[Packet size limited during capture]
I read that this happens when you capture packets with tcpdump and tcpdump cuts off the packet at a specific length.
What does 10001 → 27017 mean?
In the information field it says Len=121, but in the Length field it says it is 163 Bytes long. What is the correct length?
What does 10001 → 27017 mean?
As #SteffenUllrich pointed out, these are the ports.
In the information field it says Len=121, but in the Length field, it says it is 163 Bytes long. What is the correct length?
I am not entirely sure, but I think the difference in the length could be because of the [Packet size limited during capture].
By default, Director has a packet size limit to capture data on the wire. Larger packets than the packet size limit will show "Packet size limited during capture" when reading the packet capture. Taking a capture on larger packet sizes increases the processing time of packets.
(https://knowledge.broadcom.com/external/article/165718/error-packet-size-limited-during-capture.html)
So, my speculation is that the packet is 163 bytes, but only 121 were captured.

MAximum Number of Modules

this doc states the maximum number of modules in a deployment is 20. I am having problems getting over 15. Nothing ever happens, no error messages but the modules don't get deployed.
I also would like to know if this is a soft limit and if it is, what is the process to override it.
Did you find any error in edgeAgent log? probably you hit the limit of twin message size; Maximum size per twin section (tags, desired properties, reported properties) is 8 KB.

Allowed memory size of 16777216 bytes exhausted (tried to allocate 78 bytes) in

I am using PHPbb , everything works fine,
But i am getting the following error in a single page inside admin.
Allowed memory size of 16777216 bytes exhausted (tried to allocate 78 bytes) in home/mytestsite/public_html/includes/template.php on line 458
How to fix this error?
As you can imagine, this error message occurs when PHP tries to use more memory than is avialable. I'm assuming that changing code is not an option but you CAN increase the amount of memory available to PHP.
To change the memory limit for one specific script, include a line such as this at the top of the script:
ini_set("memory_limit","20M");
The 12M (for example) sets the limit to 20 Megs. If this does not work, keep increasing the memory limit until your script fits or your server squeals for mercy.
You can also make this a permanent change for all PHP scripts running on the server by adding a line such as this to the server’s php.ini file:
memory_limit = 20M
Hope this helps

beyond frame max size

In the source code of rabbit.app, frame has max size {frame_max,131072}.
If the message's size beyond the limit, will message will be refused to send or the message will be divided and then to be sent again?
Your message will be split into several frames if it is larger than the frame_max variable, see section 2.3.5.2 in the AMQP specification. On the receiving side it is reassembled automatically and you are presented with the message.
The actual frame size used may be different from the configured frame_max as it is negotiated with clients. I think the frame size is configurable mainly for performance tuning, see the comments in the RabbitMQ configuration docs

What is the maximum URL length you can pass to the Wininet function, HttpOpenRequest?

What is the maximum URL length you can pass to the Wininet function, HttpOpenRequest?
There are some max length consts in WinInet.h:
...
//
// maximum field lengths (arbitrary)
//
#define INTERNET_MAX_HOST_NAME_LENGTH 256
#define INTERNET_MAX_USER_NAME_LENGTH 128
#define INTERNET_MAX_PASSWORD_LENGTH 128
#define INTERNET_MAX_PORT_NUMBER_LENGTH 5 // INTERNET_PORT is unsigned short
#define INTERNET_MAX_PORT_NUMBER_VALUE 65535 // maximum unsigned short value
#define INTERNET_MAX_PATH_LENGTH 2048
#define INTERNET_MAX_SCHEME_LENGTH 32 // longest protocol name length
#define INTERNET_MAX_URL_LENGTH (INTERNET_MAX_SCHEME_LENGTH \
+ sizeof("://") \
+ INTERNET_MAX_PATH_LENGTH)
...
HttpOpenRequest does not have a maximum length but server software you are targeting will likely have a limit on your URL length.
Apache (Server)
My early attempts to measure the
maximum URL length in web browsers
bumped into a server URL length limit
of approximately 4,000 characters,
after which Apache produces a "413
Entity Too Large" error. I used the
current up to date Apache build found
in Red Hat Enterprise Linux 4. The
official Apache documentation only
mentions an 8,192-byte limit on an
individual field in a request.
Microsoft Internet Information Server (Server)
The default limit is 16,384 characters
(yes, Microsoft's web server accepts
longer URLs than Microsoft's web
browser). This is configurable.
Perl HTTP::Daemon (Server)
Up to 8,000 bytes will work. Those
constructing web application servers
with Perl's HTTP::Daemon module will
encounter a 16,384 byte limit on the
combined size of all HTTP request
headers. This does not include
POST-method form data, file uploads,
etc., but it does include the URL. In
practice this resulted in a 413 error
when a URL was significantly longer
than 8,000 characters. This limitation
can be easily removed. Look for all
occurrences of 16x1024 in Daemon.pm
and replace them with a larger value.
Of course, this does increase your
exposure to denial of service attacks.
(from Boutell.com)
I would suggest less than 2000 characters., but this KB article suggests Internet Explorer has a limit of 2083, which may well apply to your case too.

Resources